Cloning an Instance

You should clone an Instance so that two or more instances of the same system can coexist on a machine by changing few properties. By changing the properties, the second instance of the system is treated as a new system with a new COM+ application.

The command line syntax of creating a clone of a builder generated package is

ManagePackage /C /BP <SourcePackageLocation>
[/TP <TargetPackagePath>] [/DB <DBName>] [/DBS <DBSchema>]
[/DBR <DBServerRegistration>] [/SN <SystemName>] [/PN <PackageName>]
[/PD <PackageDir>] [/O <true|false]>] [/ ]

Parameters

Argument

Description

/C

Specifies whether you want to create a clone of the builder generated MSI package or CAB files.

Notes:

  • This argument is mandatory.

  • If you do not pass this argument, the error message "Mandatory Input missing or Invalid: /C /P /U", including the complete usage of the utility appears

/BP <SourcePackageLocation>

Specifies the path to builder generated package (.msi or .cab). You can specify the absolute path, relative file path, or network path (Uniform Naming Convention).

Note: This argument is mandatory and allows the Windows installer to determine the existing builder generated MSI or cab file so that the new system can coexist mutually by changing a few properties. If you do not pass any value with this argument, an error message specifying that the input is invalid, including the argument and the usage of the utility appears, for reference.

For example:

  • To create a clone of an MSI package, type

    ManagePackage /C /BP C:\GeneratedFiles\
BuilderGeneratedPackage.msi

  • To create a clone using the relative path for a builder generated package located at C:\GeneratedFiles\, type

    ManagePackage/C /BP ..\BuilderGeneratedPackage.msi

  • To create a clone of an MSI package using the Uniform Naming convention (UNC) syntax, type:

    ManagePackage /C /BP \\network\my folder\ 
BuilderGeneratedPackage.msi

  • When you create a clone of the MSI package without specifying the path to the builder generated package, the error message "Invalid input specified" appears. For instance,

    ManagerPackage /C /BP /TP C:\ClonedPackages

  • If you pass empty quotes, "" or an incorrect path, the error message "Invalid builder generated package provided." appears. For instance,

    ManagerPackage /C /BP ""
/TP <TargetPackagePath>

Specifies the absolute target path where the DPM generated package should be copied.

Note: The default path is "My Documents".

/DB <DBName>

Specifies the target database name of the DPM generated package.

Note: The default value is the Instance name appended with "DB".

For example: If Instance name is Sample, the DBName is SampleDB.

/DBS <DBSchema>

Specifies the Database schema name of the DPM generated MSI package.

Note: The default value is the Instance name.

For example: If Instance name is "Sample", the DBSchema is "Sample".

/DBR <DBServerRegistration>

Specifies the Database server registration name.

Note: The default value is the builder generated value.

/SN <SystemName>

Specifies the System name of the new .msi or .cab package name.

Note: This argument allows the Windows installer to determine the name of the cloned system. The default value is the builder generated value appended with "Clone".

For example: If the existing System name is "Sample", the SystemName of the newly created MSI package is "SampleClone".

/PN <PackageName>

Specifies the Package name of the new .msi or .cab package name.

Note: This argument allows you to set the output file name. The package name gets modified if the instance name is updated until the package name is set manually. The default value is the builder generated value appended with "Clone".

For example: If the existing System name is "Sample", the name of the newly created MSI package is "SampleClone".

/PD <PackageDir>

Specifies the Package installation directory, which is the absolute path to the builder generated instance package.

Note: The default value is the builder generated value appended with "Clone".

For example: If existing PackageInstallationDirectory is

"C:\ABSuite\Systems\Sample", the PackageInstallationDirectory of the newly created MSI package is

"C:\ABSuite\Systems\SampleClone"

To clone an MSI package for a specified Package installation directory, type

ManagePackage /C /BP C:\TEMP\stagingarea\Sample.msi /PD C:\ABSuite\Systems\ SampleClone
/CFD <ConfigurationData>

Specifies the path to the location configuration data file. Configuration data file is an input file for reconfiguring design time objects such as LOG Pack Location, ROC Pack Location, REORG Pack Location, EXTRACT Pack Location, and System Pack Location.

Note: The input file can be a text file which have multiple lines. Each line is separated by the object name and the desired location.

For example:

SegmentA.ReportA.AttributeA C:\ExtFileLocA
SegmentA.Location3 C:\TempLocation
/O <true|false>

You can set this argument to true to overwrite the existing OutPath package. The default value is false.

Notes:

  • If no value is specified for this argument or option is false and target path is available, the warning message Target Path is already available appears.

  • If a package with the same name exists in the target path, an error message specifying that the package already exists in the path appears.

/C /?

Displays command syntax and options of the utility for cloning an instance. If specified, a usage message displays, and the utility exits without starting the cloning process.

Example

The following command clones an instance:

ManagePackage /C /BP C:\TEMP\stagingarea\Sample.msi /TP C:\ClonedPackages /DB CLONESAMPLEDB /DBS CLONEDSAMPLESCHEMA /DBR SQLSERVER /SN SAMPLECLONE /PD C:\ABSuite\Systems\SampleClone /O True