Siebel Business Process Framework: Workflow Guide > Administering Workflow Policies > About Testing, Troubleshooting and Migrating a Workflow Policy >

Migrating Workflow Policies to the Production Environment

To migrate fully tested policies to your production environment, you must follow a process similar to the one used for implementing the policies in your test environment.

To migrate workflow policies to the production environment

1. Back up your production environment database.
2. Migrate your test repository environment into your production repository environment.

   The process is described in the upgrade guide for the operating system you are using.

3. Reenter your workflow policy action types, workflow policies, and workflow policy groups in the test environment into the production environment.
4. When reentering definitions into the production environment, make sure you enter them exactly as they are defined in the test environment.

   Note that it is not necessary to reenter information that you have entered using Siebel Tools.

5. In the Siebel client, navigate to Administration-Server Management > Jobs.
6. In the Jobs list, click New.
7. From the Component/Job drop-down list, choose Generate Triggers.

   This creates a new line entry but does not start the task.

8. In the Job Parameters list, click New to modify parameter settings.

   For a description of the component-specific parameters for Generate Triggers, see Administering Triggers on the Workflow Policy Server. For a description of generic and enterprise parameters, see Siebel System Administration Guide.

9. Choose Submit Query.

   For more information on trace files, see Tracing and Reporting a Workflow Policy. For more information on using trace flags, see Siebel System Administration Guide.

NOTE:  To help prevent invalid triggers from being applied to your production environment, apply your database triggers to your test environment before you apply them to your production environment.