Siebel Email Administration Guide > Administering Siebel Communications Server for Siebel Email Response >

About Starting Server Components

For the Communications Inbound Receiver and the Communications Inbound Processor server components, a single component instance has multiple subtasks that run at the same time as the server component task. The Communications Inbound Receiver and the Communications Inbound Processor server component tasks and subtasks must be running before Siebel Email Response can process incoming email. Therefore, you must start all Communications Inbound Receiver and Communications Inbound Processor server component tasks and subtasks. For more information about enabling component groups when you configure the Siebel Server, see the Siebel Installation Guide for the operating system you are using and Siebel System Administration Guide.

Before starting any Communications Inbound Receiver or Communications Inbound Process component tasks, note the following guidelines:

• If you try to start the same Communications Inbound Receiver or Communications Inbound Processor component task twice, then the second attempt is rejected. However, the first instance is running as usual. You can always increase the number of subtasks for each component task if you have a high volume of incoming email messages.
• One component task can have multiple associated subtasks, and the subtasks route the email. The component task acts like a controller to coordinate its subtasks.

NOTE:  The preconfigured number of maximum threads is five. If you change the number of threads for a server component, then make sure that the Maximum Tasks parameter is greater than or equal to the number of response groups multiplied by the number of threads. A thread is represented by a task and three subtasks.

If you change the Siebel Email Response setup after you implement Siebel Email Response, then you must stop and restart the Communications Inbound Receiver and the Communications Inbound Processor server components for your changes to take effect.

For some changes, you must stop and restart these server components only if you want your changes to take effect immediately. For example, for changes to a workflow process take effect, you can submit them without stopping these server components. For information about submitting profile changes, see Submitting Changes for Communications Driver Profiles. For information about submitting requests, see Resubmitting Failed Email.