Migrating application domains > How to migrate application domains

How to migrate application domains
When you migrate an application domain you unpack a package file and deploy configurations to the StreamServer applications in the target environment.
To migrate an application domain (Composition Center not included)
1
2
In Control Center, right-click the target application domain node and select Migrate Application Domain. The Migrate Application Domain dialog box opens.
3
In Import file, browse to and select the package file to import.
4
5
Click Migrate. The Deploy Applications Confirmation dialog box opens.
6
7
Click Close.
Migrating application domains that include Composition Center
When you migrate an application domain that includes Composition Center, you can select to migrate all Composition Center resources, rules, permissions etc. to the target runtime repository from a zip file exported from the source runtime repository (see Packing domains that include Composition Center). Depending on the amount of data to migrate, this may take some time.
Migrating Composition Center resources separately
If you want to migrate the Composition Center resources etc. manually after you have migrated the application domain you can run DBAT in MIGRATE mode. See Command line interface for migration in the Database Administration Tool user guide for information.
Note:
You cannot export/migrate between different database vendors, e.g. export from SQL Server and migrate to Oracle.
To migrate an application domain
1
2
In Control Center, right-click the target application domain node and select Migrate Application Domain. The Migrate Application Domain dialog box opens.
3
In Import file, browse to and select the package file to import.
4
5
If you want to migrate Composition Center resources, select Post action, click the Import database file browse button, select the zip file to import and click OK.
6
Click Migrate. The Deploy Applications Confirmation dialog box opens.
7
8
Click Close.
Forcing the migration
You can select to force the migration, i.e. run the migration almost without any user interaction. The only interaction is to select which StreamServer applications to deploy to. This means you must be sure there are no conflicts regarding hosts etc. if you enable this option.
If you do not force the migration (this is the default option) you are prompted to accept or change the hosts etc. to use in the target environment. Each time you are prompted you can select:
OK – accept the current step.
Skip – skip the current step.
Abort – abort the migration. This does not include any rollback, i.e. all steps you have accepted before you abort are applied.
 
OpenText StreamServe 5.6 Updated: 2013-03-01