> Deployment Planning > Migration and Staging

Deployment Planning

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Migration and Staging

This chapter summarizes migration capabilities for AquaLogic User Interaction deployments.

The purpose of this chapter is to assist in planning development, QA, and production environments. By utilizing its migration capabilities you can stage the AquaLogic User Interaction deployment in a testing environment where you can test quality and gain acceptance prior to pushing it to production.

The following table summarizes migration capabilities.

Component
Migration Guidelines
Portal and Image Service
Follow the guidelines in the Migrating, Backing Up, and Restoring Portal Objects chapter of the Administrator Guide for AquaLogic Interaction.
Search
Search should not be migrated. The Search Update Agent job indexes new portal objects and documents.
  • Identity Services
  • Content Services
  • Portlet Suite
Do not migrate these services. Import the original product .pte package and complete configuration as described in the installation guide for the specific product.
Publisher
Follow the guidelines in the Migrating Publisher Objects chapter of the Administrator Guide for AquaLogic Publisher.
Collaboration
Follow the guidelines in the Migrating, Backing Up, and Restoring Portal Objects chapter of the Administrator Guide for AquaLogic Interaction.
Studio
Follow the guidelines in the Migrating, Backing Up, and Restoring Portal Objects chapter of the Administrator Guide for AquaLogic Interaction.

Note:  

    • Migration is only relevant when the source and destination portals have distinct Studio installations.
    • Portlets must be created with a compatible version of Studio.
    • Do not include dependencies when creating the migration package.
    • Data in the source Studio portlet database is not migrated. Use the Studio data export/import functionality to move data.
    • If multiple Studio portlets share and underlying database, migrate these portlets in batch. This maintains the relationship between the portlets and their shared database.
Analytics
Do not migrate Analytics. Install and configure Analytics in the production environment.


  Back to Top       Previous  Next