Skip Headers
Siebel CRM System Administration Guide
Siebel Innovation Pack 2015, Rev. A
E24823-01
  Go to Documentation Home
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
  View PDF

About Migrating Parameters Between Environments

Migrating Siebel Enterprise or Siebel Server configuration parameter values from one Siebel Business Applications environment to another is a necessary part of migrating to a new development, test, or production environment. The configuration upgrade utility, cfgmerge, facilitates the automatic migration of these parameters between environments.

When it is undertaken manually, the parameter migration process can incur data entry errors and extend downtime of the target Siebel Business Applications environment. The cfgmerge utility allows for the automation of the parameter migration process.

The cfgmerge utility compares the source environment with the target environment and creates a parameter migration script, which includes documentation on the parameter differences between the two environments. The migration script documents the differences between environments, including noting parameters that cannot be updated automatically and identifying obsolete or modified parameters in the new environment.

After a review, the migration script can then be applied on the target environment to update the parameters. Use the automated migration process to:

Migrating parameters between environments can be run in either of the following modes:

For procedures on migrating parameters between environments, see "Process of Migrating Parameters Between Environments".

The cfgmerge utility runs on both Microsoft Windows and UNIX. For more information about this utility, see "About the cfgmerge Utility".


Note:

The cfgmerge utility migrates only parameter values between environments. Other environment configurations, such as custom components, are not migrated to the target environment. For example, if you have a custom component in the source environment, then you have to create a component definition of the same type, with the same name, in the target environment to migrate the parameter settings for that component. For information about creating component definitions, see "Creating a Custom Siebel Server Component Definition".