Migrating Repository Changes from Development to Production Environment (Siebel CRM 18.8 or Later)
Once the development (source Design Time Repository/DR) environment is upgraded to the Siebel 18.8 Update or later release binary and repository, you must perform the steps in the following procedure to migrate the changes to the production (target Runtime Repository/RR) environment. You can use the asynchronous migration feature to do this only if both source (development) and target (production) environments are in a Repository Upgraded state. If either (source or target) environment is not in a Repository Upgraded state, then the migration execution will be performed in synchronous mode.
To migrate Siebel 18.8 Update or later release repository changes from a development (source) to a production (target) environment
Create a connection to the target environment.
For more information about creating a connection, see Creating a Connection.
Create a migration plan with Incremental Runtime Repository Service where source is the Development (DR) environment and target is the Target (RR or production) environment. (You can use the Runtime Repository Service instead of Incremental Runtime Repository Service.)
For more information about migration planning, see Creating a Migration Plan.
Run the migration plan that you created in Step 2.
After you complete Steps 1 to 3, you must add the seed data to the target (RR or production) environment.
For more information, see Adding Seed Data to the Production Environment.