Siebel Communications Server Administration Guide > Defining Outbound Communication Requests > Creating and Submitting Outbound Requests >

Configuring Subrequests

An outbound communication request can be broken into subrequests, which can be processed by more than one instance of the Communications Outbound Manager server component in order to achieve greater scalability for requests with a large number of recipients or large processing demands.

You can specify from 2 to 26 subrequests for a given request. Subrequests are divided based on the last name of each recipient.

For example, if 2 subrequests are specified, then all recipients with last names A-M are handled by one subrequest, and those with last names N-Z are handled by the second subrequest. If 3 subrequests are specified, recipients are allocated to three alphabetical groupings (A-I, J-R, S-Z). If 4 subrequests are specified, recipients are allocated to four alphabetical groupings (A-F, G-M, N-S, T-Z), and so on.

Subrequests are distributed to multiple instances of the server component whose name is specified for the request. This approach load-balances your communication requests to achieve scalability objectives—particularly when subrequests are divided among multiple Siebel Server machines. Requests are distributed by Server Request Processor and Server Request Broker.

If you click the Subrequests button after subrequests have already been specified, the number of subrequests is displayed. After a request has been processed, the Communication Subrequests view tab displays a list of the subrequests for the request. The form below the Communication Subrequests list includes the Recipient Search Specification field, which may display information about how the set of recipients for the subrequest was defined.

To configure your system for optimal processing of high-volume outbound communication requests using subrequests, you can designate Siebel Server instances running on multiple server machines to run Communications Outbound Manager. For more information about Communications Outbound Manager, see Administering Communications Outbound Manager.

NOTE:  Subrequests cannot be specified for any outbound communication request for which more than one recipient source object has been specified. For example, for a request based on the recipient group Campaign Contacts, one and only one campaign record can be specified if you are to specify subrequests for this request.

Subrequest SQL File Option

Depending on the requirements for your deployment, your company may choose to implement alternative SQL for processing subrequests. You can do this by creating a SQL file to be read in place of the default Siebel method of processing subrequests.

This file must be named commoutboundmgr.cfg, and it must be located in the subdirectory CMS of the Siebel File System directory. For example, depending on your installation, the full path might be as follows:

C:\sea78\FS\CMS\commoutboundmgr.cfg

If no file exists of this name exists in the designated location, then the default hardcoded SQL from Oracle is used for processing subrequests.

For more information on this issue, refer to Siebel SupportWeb.