Siebel Email Administration Guide > Defining Outbound Communication Requests > Creating and Submitting Outbound Communication Requests >

Configuring Subrequests

You can divide an outbound communication request into subrequests. More than one instance of the Communications Outbound Manager server component can process the subrequests to achieve greater scalability for requests with a large number of recipients or high processing demands.

You can specify from two to 26 subrequests for a request. Subrequests are allocated by using the last name of each recipient.

For example, if you specify two subrequests, then one subrequest handles all recipients with last names A through M, and the second subrequest handles all recipients with last names N through Z. If you specify three subrequests, then recipients are allocated to three alphabetical groupings (A through I, J through R, and S through Z). If you specify four subrequests, then recipients are allocated to four alphabetical groupings (A through F, G through M, N through S, and T through Z), and so on.

Subrequests are distributed to multiple instances of the server component with a name that you specify for the request. This approach load-balances your communication requests to achieve scalability objectives, particularly when subrequests are divided among multiple Siebel Server computers. Server Request Processor and Server Request Broker distribute requests.

If you click the Subrequests button after you specify subrequests, then the number of subrequests appears. After a request is processed, the Communication Subrequests view tab displays a list of the subrequests for the request. The form that appears below the Communication Subrequests list includes the Recipient Search Specification field. This field might display information about how the set of recipients for the subrequest is defined.

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

NOTE:  You cannot specify subrequests for any outbound communication request with more than one recipient source object. For example, for a request that is based on the Campaign Contacts recipient group, specify only one campaign record if you want to specify subrequests for the request.

Subrequest SQL File Option

Depending on the requirements for your deployment, your company might choose to implement alternative SQL for processing subrequests. In this scenario, you create a SQL file to be read in place of the default Siebel method of processing subrequests.

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

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

If no file with this name exists in the designated location, then the default hardcoded SQL from Oracle is used to process subrequests.