Updating Your Siebel Assignment Manager Deployment with New Configurations

After configuring Siebel Assignment Manager objects and attributes or altering assignment policies, it is often necessary to redeploy the Siebel runtime repository and restart various server components and tasks. Table 6-8 lists the required server tasks and components that must be restarted based on the type of configuration process. (The task to restart Workflow Monitor Agent applies only to dynamic assignment.)

Note: You must redeploy the changes to the Siebel runtime repository whenever you add, inactivate, or delete any assignment object types, assignment criteria, and assignment attributes. Make sure that all projects are redeployed, not only the locked projects, if you inactivate or delete a high-level object type or assignment criteria.

Table 6-8 Server Administration Tasks After Configuring Assignment Manager

Configuration Process	Deploy Siebel Runtime Repository	Restart Assignment Manager	Regenerate Triggers	Restart Workflow Monitor Agent
Add or inactivate assignment objects	Yes	Yes	Yes	Yes
Configure assignment objects	No	Yes	Yes	Yes
Add, configure, or inactivate assignment attributes	Yes	Yes	Yes	Yes
Configure assignment attribute columns	No	Yes	Yes	Yes
Add, configure, or inactivate assignment criteria	Yes	Yes	Yes	Yes
Add, configure, or inactivate assignment criteria attributes	Yes	Yes	Yes	Yes
Activate, inactivate, or modify assignment policies	No	No	Yes	Yes

Use the following procedure to update your deployment with new configurations.

Caution: Some steps in the following procedure might not be required for your particular deployment. Follow the steps as they apply (or do not apply) to the configuration process performed as shown in Table 6-8.

Note: For information about checking out and checking in objects, see Using Siebel Tools.

To update your deployment with new configurations

1. Deploy changes to the Siebel runtime repository, if necessary, and deploy it to the server.

   
   

   Note: It is not necessary to redeploy the Siebel runtime repository whenever you configure an assignment object or an assignment attribute column, but you must redeploy the Siebel runtime repository whenever you add, inactivate, or delete any assignment object types, assignment criteria, or assignment attributes. Make sure that all projects are redeployed (not only the locked projects) if you inactivate or delete a high-level object type or assignment criteria.

   
   

2. If you are running dynamic assignment, then perform the following steps:

   1. Stop the Workflow Monitor Agent server component.

   2. Regenerate triggers by running the Generate Triggers server component.

   3. Release assignment rules (if rules have changed) by clicking Release in the Assignment Rules List view.

      For more information about releasing assignment rules, see "Releasing Assignment Rules".

   4. Restart the Workflow Monitor Agent server component.

   For more information about stopping and restarting server components, see Siebel System Administration Guide.

3. If you are running dynamic assignment, then stop and restart the Assignment Manager server component for the changes to take effect.

   1. Stop the Workflow Monitor Agent server component.

   2. Stop the Assignment Manager server component.

   3. Start the Assignment Manager server component.

   4. Start the Workflow Monitor Agent server component.

   For more information about stopping and restarting server components, see Siebel System Administration Guide.

   You must stop and restart the Assignment Manager server component whenever you add, inactivate, or delete any assignment object types, assignment criteria, or assignment attributes.