Cloning sites and application domains > Introduction to cloning sites and domains

Introduction to cloning sites and domains
To clone a site or application domain you must first pack the source site/application domain (see Packing sites and application domains) and then import the site/application domain to the target environment.
Administrator privileges
You must have administrator privileges to be able to import a site or application domain.
Deploying to StreamServer applications
During the import, all Design Center export files in the export package are deployed to the corresponding StreamServer applications. The physical layer tied to the application domain determines which physical layer to deploy.
Files extracted from the package file
Extracted by default
During the import, the following configuration files are copied to the working directories of the StreamServer applications:
Design Center Projects
When a Design Center Project is exported, there is an option to pack the Project and include the Project package file (*.dcpackage) in the export. All Project package files included in Project exports are also included in the packed site/application domain. When the site/application domain is imported to the target environment, the Project package files are copied to:
<ManagementGatewayRoot>\applications\<streamServerApplication>\
data\package
Additional files
When the package file was created, there was an option to export additional files from the working directories of the applications to the package. All export items with Copy Type set to Clone are copied to the working directories of the applications in the target environment when importing a site or application domain. See Exporting additional files to a package.
OpenText StreamServe 5.6 Updated: 2013-03-01