Siebel Assignment Manager Administration Guide > Running Siebel Assignment Manager > About Running Batch Assignment >

About Running Multiple Instances of Siebel Assignment Manager in Batch Mode

This topic is part of About Running Batch Assignment.

When there are many objects that need to be assigned, you can run multiple instances of Assignment Manager in batch mode to improve performance. First, develop a strategy for specifying multiple batches using the Object Where Clause parameter in the Batch Assignment component. Then, start multiple instances of batch assignment specifying the appropriate Object Where Clause value for each instance.

For example, you can run one instance of batch assignment for accounts that changed today and a different instance of batch assignment for accounts that changed yesterday. Use the Object Where Clause parameter to specify the following:

• For the batch that processes accounts changed today:

  Object Where Clause: WHERE LAST_UPD = SYSDATE

• For the batch that processes accounts changed yesterday:

  Object Where Clause: WHERE LAST_UPD = SYSDATE - 1

NOTE:  These examples use a nonindexed field: LAST_UPD. It is recommended, however, that you use indexed fields for object WHERE clause statements. Also, use the appropriate database datetime functions to determine the current date and time, depending on the database you are using. This example uses SYSDATE, which is specific to Oracle Database datetime functions.

To process mutually exclusive sets of records when running multiple instances of Assignment Manager simultaneously for the same assignment object, specify an Object Where Clause for each assignment task. You can also distribute the tasks on multiple Siebel Servers to enhance performance.

When Not to Run Multiple, Simultaneous Batch Jobs

There are several instances where you should not run multiple, simultaneous batch jobs:

• If multiple assignment batches are executed for the same object, then the results can potentially vary and may not be as desired
• If the batch jobs update rows on the same table or tables
• If one batch job updates records in a table or tables used by another batch job as input
• If the batch jobs use workload criteria to assign the same object

  NOTE:  If multiple assignment batches are executed for the same object using workload criteria, the results can potentially vary and may not be as desired.

Examples of when you should not run multiple simultaneous batch jobs include:

• Contact and Contact Denormalization, because the same tables are updated
• Account and Contact Denormalization, because Contact Denormalization uses Account team as input
• Opportunity and Contact Denormalization, because Contact Denormalization uses Opportunity team as input