# Deployment Guide

# Using Migration Features to Stage Your Deployment

This chapter summarizes migration capabilities for ALUI deployments.

The purpose of this chapter is to make you aware that in the ALUI environment, objects can be staged initially in a testing environment before they "go live" in a production environment.

BEA recommends you use this feature to test quality and gain acceptance on a development stage before you migrate components to a production stage.

Figure 8-1 Components that Can Be Migrated Are Indicated by an Arrow

The following table summarizes migration capabilities.

Component | Migration Guidelines
--- | ---
Portal and Image Service | Follow the guidelines in the Administrator Guide.
Search | If the portal is being deployed live for the very first time, BEA recommends that only the portal database, Web server, and so on, not Search be ported directly from the staging environment to production. The production Search installation should start out as a freshly installed component with an empty index. A Search Repair should then be scheduled, using Search Manager utility in the portal. The next run of the Search Update Agent will ensure that all portal objects and documents get indexed by Search. If the portal is already live, and some new portal objects are tested out in a staging environment and then pushed out onto production, no extra action needs to be taken in order for the new objects to be indexed. The Search Update Agent will soon run (it is typically scheduled to run every 10 minutes) and index the new objects for searching.
Identity Services Content Services Portlet Suite | BEA recommends you do not use the Migration Utility for these migrations. Instead, import the original .pte package and complete configuration as described in the installation guide for the BEA product.
Publisher | Follow the guidelines provided in the Publisher documentation.
Collaboration | Follow the guidelines provided in Collaboration documentation.
Studio | To export a Studio portlet Export it to a .pte file. Use the Migration Utility to import the .pte, which creates the portlet on the portal, as well as creates the underlying Studio application and database. Keep in mind the following: Migration is relevant only when the source portal and destination portal have independent Studio installations. You can migrate only portlets created with compatible versions. You do not need to include dependencies when migrating Studio portlets. Data in the source Studio portlet database will not be migrated. You can use the Studio data export/import functionality to move data from one Studio portlet to another. If multiple Studio portlets share the same underlying database, BEA recommends that all of these portlets be migrated in a batch, rather than individually, in order to maintain the relationship between the portlets and their shared database.
Analytics | BEA recommends that the Analytics installation not be migrated but freshly installed in a production environment.