Going Live with Siebel Business Applications > Migrating Repositories Between Databases > Post-Repository Migration Tasks >
Re-creating Custom Environment Configurations
When migrating from one environment to another, re-create any custom environment configurations from the source environment in the target environment, if necessary. Custom environment configurations include data such as custom component definitions. This information is stored in the Siebel Gateway
siebns.dat file and is not migrated as part of a repository migration.
For specific details on automatically re-creating custom parameter values, see Migrating Parameters Between Environments.
Re-create custom environment configurations in one of two ways:
- Use the Server Manager GUI or command-line interface program (srvrmgr) to create these custom configurations manually in the new target environment. For information on creating custom component definitions, see Siebel System Administration Guide.
- Use the Server Manager command-line interface program (srvrmgr) with input scripts to automate this task in the new target environment. This is the preferred method because scripts can be saved and reapplied in future environment updates of the same version. For information on using scripts with srvrmgr, see Siebel System Administration Guide.
NOTE: If reapplying a srvrmgr script to re-create custom environment configurations, make sure to edit the script if the target environment is a new Siebel version (as in the case of a Siebel upgrade). New parameters or srvrmgr commands may be available with the new version.