How to import application domains

When you import an application domain you import the package file created in the source environment to the target environment, and create a copy of the original application domain.

To import an application domain (Composition Center not included)

1	In Control Center, right-click the Application domains folder and select Import Application Domain. The Import Application Domain dialog box opens.

2	Enter a name for the application domain and click OK.

3	In Import file, browse to and select the package file to import.

4	Select whether to:

–	Force the import (see Forcing the import).

–	Import all applications to a specific host (see Multiple hosts).

–	Create databases (see Creating empty databases).

5	Optionally, specify an Automatic prefix for the imported applications (see Naming applications).

6	Click Import. The Deploy Applications Confirmation dialog box opens.

7	Select which StreamServer applications to deploy to and click OK.

8	Click Close.

Importing application domains that include Composition Center

When you import an application domain that includes Composition Center, you can select to import 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 import, this may take some time. Note that this requires that you already have the runtime repository in the target environment before you import the application domain.

Importing Composition Center resources separately

If you want to import the Composition Center resources etc. manually after you have imported the application domain you can run DBAT in IMPORT mode. See Command line interface for migration in the Database Administration Tool user guide for information.

Note:

You cannot export/import between different database vendors, e.g. export from SQL Server and import to Oracle.

To import an application domain

1	In Control Center, right-click the Application domains folder and select Import Application Domain. The Import Application Domain dialog box opens.

2	Enter a name for the application domain and click OK.

3	In Import file, browse to and select the package file to import.

4	Select whether to:

–	Force the import (see Forcing the import).

–	Import all applications to a specific host (see Multiple hosts).

–	Create databases (see Creating empty databases).

5	Optionally, specify an Automatic prefix for the imported applications (see Naming applications).

6	If you want to import Composition Center resources, select Post action, click the Import database file browse button, select the zip file to import and click OK.

7	Click Import. The Deploy Applications Confirmation dialog box opens.

8	Select which StreamServer applications to deploy to and click OK.

9	Click Close.

Additional information

Forcing the import

You can select to force the import, i.e. run the import 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, application names, etc. if you enable this option.

If you do not force the import (this is the default option) you are prompted to accept or change the hosts, application names, 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 import. This does not include any rollback, i.e. all steps you have accepted before you abort are applied.

Multiple hosts

If the source environment includes multiple hosts, this information is included in the export package. When you import, the default option is to connect all applications in the target environment to the same hosts used in the source environment. If you do not force the import, you are prompted to accept or change the host names. You also have the option to specify a host for all applications.

Creating empty databases

When you import an application domain, you have the option to create all databases used in the source application domain. This will create new empty runtime repositories, web content repositories, Document Broker repositories and Collector archives with the same configurations as defined in the source environment.

Naming applications

Applications running on the same host must have unique names. If an application name already exists in the target environment, the name of the imported application is by default prefixed with the name of the imported domain. For example, if you use import to create the domain Dev2, the applications in this domain are renamed to Dev2_<applicationName> in case of conflict. You also have the option to define a custom prefix.