|
Siebel Application Deployment Manager Guide > Configuring and Administering the Siebel ADM Framework > About Siebel ADM System Administration >
Configuring the ADM Enterprise Profile
This topic is part of About Siebel ADM System Administration. Configuring the ADM enterprise profile is a one-time setup task that must be performed before your initial deployment. The ADM enterprise profile requires subsequent updating only if changes are made to your environment or if deployment behavior changes are necessary. For more information on the ADM enterprise profile, which is an XML file, see About the ADM Enterprise Profile. For more information on configuring the ADM enterprise profile at installation, see Configuring the ADM Enterprise Profile After Installation. NOTE: Microsoft Office InfoPath or a similar XML editor is the preferred method for examining or modifying the contents of the enterprise profile or other XML files related to ADM. Alternatively, a text editor can be used.
To configure the ADM enterprise profile
- Navigate to the enterprise profile file entprofile_enterprise_name.xml in the
MgmtSrvrInstallDir\ADM directory.
- Open the enterprise profile file using an editor such as Microsoft Office InfoPath.
- Locate the environment and deployment-specific parameters, and enter the values for your environment.
For information on specific parameters, see Table 3. The changes made to the enterprise profile are reflected when you create a new session.
Table 3. Listing of ADM Enterprise Profile Parameters
|
|
|
PerformBackup
|
Y |
When set to Y, a backup of the target system's existing data is performed automatically before the deployment. This flag can be set at all three levels. Setting this flag at a lower level allows the backup operation to skip individual units or groups. Turning off the backup operation can increase performance of the deployment. |
DegParallelism
|
1 |
This parameter must be set to a nonzero number and is set at the category level only. For the repository category, set only to 1. For the database category, parallelism represents the number of database items deployed concurrently. For example, if the value is set to 2, two deployment units deploy concurrently. For the file category, parallelism represents the number of file servers deployed concurrently. This setting is dependent on the number of servers and the number of units inside the File category of the package. For example, if the File category consists of 5 units and there are 2 servers, the maximum value for the degree of parallelism is 10 (5 multiplied by 2). |
StopOnError
|
No |
This parameter is set at the profile level. If set to Yes, the deployment stops when an error occurs. If set to No, the deployment continues to the next unit or group even though an error occurs. ADM does not check dependencies between separate units, especially database items. If one unit fails and another database unit is dependent on the failed unit, then the second unit also fails. Database items that have been related though the ADM UI are treated as one unit in this case (one file). |
BackupDir
|
Not applicable |
This parameter contains the path of the ADM backup directory, which contains .sif files. The ADM backup directory must be a shared location. |
DeployServer
|
Not applicable |
This parameter contains the paths of the deployment servers in the target environment. NOTE: Entries for this parameter are case-sensitive.
|
Setting Dependencies
You can set dependencies in the entprofile_enterprise_name.xml file. The following example illustrates that the Repository category should start deploying only after the Database category reaches the deployment complete state and file category units are in the migration complete state: <Category Name="Repository">
<Dependencies>
<Dependency Category="Database" Status="DEPLOYMENT_COMPLETE"/>
<Dependency Category="File" Status="MIGRATION_COMPLETE"/>
</Dependencies>
You can apply the same approach to other required dependencies.
|
