Controlling the Number and Size of Batch Requests

Siebel CRM Desktop sends requests to the Siebel Server in batches. One Web Service call is one batch. Each batch includes multiple commands. Each command can request multiple IDs. To avoid overloading the server, you can specify the number of IDs that Siebel CRM Desktop requests for each command and the number commands that each batch contains.

For example, assume the following occurs:

• Siebel CRM Desktop must get 300 accounts

• A batch contains only one command

• One command requests the IDs for all 300 accounts

The server fails in this situation. To avoid this problem, you can reduce the number of commands that each batch contains and the number of IDs that each command requests. Siebel CRM Desktop sets these values to 50, by default. If Siebel CRM Desktop uses this default value to process the 300 accounts, then it creates six separate commands where each command requests 50 account IDs. It creates one batch that includes these six commands.

To control the number and size of batch requests

1. Use an XML editor to open the siebel_meta_info.xml file.

   For more information, see Files That the Customization Package Contains and Customizing Meta Information.

2. Create or find the existing section under the root tag that contains the following name:

   common_settings
   

   For more information, see Common Settings Tag of the Siebel Meta Information File.

3. Set the following subtags:

   • max_commands_per_batch. Defines the maximum number of commands that each batch contains. The default value is 50.

   • max_ids_per_command. Defines the maximum number of IDs that the command requests. The default value is 50.