You're viewing help content for version:

Again the basic rules of Project Management apply, though here too various issues can be noted:

  • Installation and Configuration

    • Installation of AEM is extremely straightforward. The configuration management you maintained during development is used to ensure that the configuration is equally stable.
  • Content Generation and/or Migration

    • At this point you will need to start filling your new AEM installation with content - be that new content input by specialized staff, content imported from predefined files, or content migrated from an existing system.
  • User Training

    • The period between the Soft and Hard Launches (see Project Phases) gives you an ideal opportunity to train your users on the publish environment.
  • Knowledge Transfer to Support Staff

    • In addition to User Training, Knowledge Transfer sessions should be used to train your support staff.
    • Plan sufficient time and resources for knowledge transfer and handover to the support team; this is crucial to ensuring long-term support and therefore user satisfaction.
  • Performance Tuning and Optimization

    • As mentioned previously, performance is a key aspect of any AEM installation as it can affect the entire user experience.
    • During the period between Soft and Hard launches you should monitor and analyze the performance to tune and optimize as much as possible. This process will have to be continued during normal use of AEM, but these initial stages are the most crucial.
    • For further details on testing performance see:
  • Acceptance Testing and Sign-off

    • At some point during deployment you will want the customer to confirm that the system functionality and performance has been officially accepted. This usually includes specific tests - which should have been clearly defined and agreed upon at the beginning of the project.