Going Live with Siebel Business Applications > Migrating Parameters Between Environments >

About Migrating Parameters Between Environments

Migrating configured Siebel Enterprise and Siebel Server parameter values is a necessary task when updating from one Siebel environment to a newer or alternate Siebel environment. If undertaken manually, the process can incur data entry errors and extend downtime of the target Siebel environment. The configuration upgrade utility, cfgmerge, allows for the automation of the parameter migration process by comparing the source environment with the target environment and creating a parameter migration script, which includes documentation on the parameter differences between the two applications. 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:

  • Update environments of the same software version (for example, updating a test environment from the development environment).
  • Update environments with different software versions (for example, you can migrate parameter values between a 7.7 and a 7.8 environment).

NOTE:  In all cases, the target environment must be 7.8 or later.

Migrating parameters between environments can be run in either:

  • Enterprise mode. This mode migrates enterprise parameters, component definition parameters, and named subsystem parameters between environments.
  • Siebel Server mode. This mode migrates Siebel Server parameters and Siebel Server component parameters between Siebel Server environments.

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

The cfgmerge utility runs on both Windows and UNIX. For further detail on this utility, see About Cfgmerge Utility.

The cfgmerge utility only migrates 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, you need 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 on creating component definitions, see Siebel System Administration Guide.

Going Live with Siebel Business Applications