Siebel Field Service Guide > Scheduling Using Oracle Real-Time Scheduler Version 1.0 > Process of Configuring Siebel Field Service Integration to Oracle Real-Time Scheduler 1.0 >

Setting Up and Configuring Workflow Processes and Policies

You must perform the procedures in this topic to be able to use real-time synchronization of address and employee data from the Siebel application to Oracle Real-Time Scheduler 1.0.

This topic contains the following related information:

• Activating Workflow Processes
• Enabling Workflow Policies
• Shutting Down Workflow Monitor Agent
• Dropping Database Triggers
• Generating Database Triggers
• Configuring Workflow Monitor Agent

This task is a step in Process of Configuring Siebel Field Service Integration to Oracle Real-Time Scheduler 1.0.

Activating Workflow Processes

Siebel administrators use the following procedure to activate workflow processes.

To activate workflow processes

1. Navigate to the Administration - Business Processes screen, then the Workflow Deployment view.
2. Query for *ORS*.
3. Click Activate.
4. Query for the Advanced Scheduler Skill Persistence Process, and click Activate for this workflow process.

Enabling Workflow Policies

Siebel administrators use the following procedure to enable workflow policies.

To enable workflow policies

1. Navigate to the Administration - Business Processes screen, then the Workflow Policies view.
2. Make sure that Expiration Date is properly set for all the workflow policies that are not in use.
3. Query for *ORS*.
4. Verify that the Expiration Date is not set for these workflow policies.

Shutting Down Workflow Monitor Agent

Siebel administrators use the following procedure to shut down Workflow Monitor Agent.

To shut down Workflow Monitor Agent

1. Navigate to the Administration - Server Management screen, Servers, then Component Groups view.
2. Query for Workflow Management.
3. In the lower Components applet, query for Workflow Monitor Agent.
4. Click Shut Down.

Dropping Database Triggers

Siebel administrators use the following procedure to drop database triggers.

To drop database triggers

1. Navigate to the Administration - Server Management screen, then the Jobs view.
2. Create a job for the Generate Triggers component.
3. In the Job Parameters list, define the job parameter with the values in the following table.

   Name	Value
   EXEC	True
   Privileged User	MS22116
   Privileged User Password	(No example)
   Remove	True
   Trigger File Name	Droptrigger.sql

   NOTE:  The values for Privileged User and Privileged User Password must be the database user name and password that have the privileges to drop and generate triggers. The user name value in this table is an example.

4. Start the job.

Generating Database Triggers

Siebel administrators use the following procedure to generate database triggers.

To generate database triggers

1. Navigate to the Administration - Server Management screen, then the Jobs view.
2. Create a job for the Generate Triggers component.
3. In the Job Parameters list, define a job with the values in the following table.

   Name	Value
   EXEC	True
   Privileged User	MS22116
   Privileged User Password	(no example)
   Trigger File Name	Gentrigger.sql

   NOTE:  The values for Privileged User and Privileged User Password must be the database user name and password that have the privileges to drop and generate triggers. The user name value in this table is an example.

4. Start the job.

Configuring Workflow Monitor Agent

Siebel administrators use the following procedure to configure Workflow Monitor Agent.

To configure Workflow Monitor Agent

1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Definitions view.
2. Query for Workflow Monitor Agent, and perform the following steps:
   1. Change the Group Name to ORS Group.
   2. Change the Action Interval to 5.
3. Click Advanced, and perform the following steps:
   1. Change the Sleep Time value to 5.
   2. Change the Default Task value to 1.
4. Click Enable to change the status of the new component to Active.
5. Restart the Siebel Server.