Migrating and deploying IBM Content Navigator assets

Migration and deployment of IBM Content Navigator assets can occur at different stages of the application lifecycle:

• For initial deployment of an application from a source (development or test) environment to a destination (production) environment.
• For the propagation of incremental sets of changes from a source environment to a subset of the existing objects in a destination environment.
• For an environment with multiple repositories or instances of the IBM Content Navigator client to export assets and then import them to another repository or another client instance. For example, you can export teamspace templates or desktops to a file for import to another IBM Content Navigator instance.

Different tools might be required to migrate and deploy an IBM Content Navigator application and its assets. The tools that you must use are determined by the tools that are used to create the assets and the storage method for the assets.

• If your application includes assets that are managed by Content Cortex, use FileNet® Deployment Manager for migration and deployment tasks that are related to those assets. For more information about migration and deployment with FileNet Deployment Manager, see Deploying assets with FileNet Deployment Manager.
• If your application includes configuration information that is managed with IBM Content Navigator, not Content Cortex, you must use other tools for the migration and deployment of those assets. For more information, see Migrating assets for IBM Content Navigator in the online product documentation.