Bookshelf v7.5: Starting Communications Inbound Manager Tasks

Siebel eMail Response Administration Guide > Completing Typical Setup Tasks >

Starting Communications Inbound Manager Tasks

One instance of the Communications Inbound Manager server component has multiple subtasks that run at the same time as the server component. Communications Inbound Manager server component tasks and subtasks must be running before eMail Response can process incoming email. Therefore, you must start all Communications Inbound Manager server component tasks and subtasks. For general information about server components, see the Siebel Server Installation Guide for your operating system.

NOTE: One component task can have multiple subtasks associated with it and the subtasks route the email. The component task acts like a controller to coordinate its subtasks.

After you implement eMail Response, certain situations require that you stop and restart Communications Inbound Manager server component tasks. The two most common reasons are:

When you make changes to the eMail Response setup, you must stop and restart Communications Inbound Manager server component so that your changes will take effect. For some changes, you must stop and restart the server component only if you want your changes to take effect immediately. The following are two examples:


Communications profiles are refreshed (reloaded) at regular intervals. If you make changes and want the changes to take effect immediately, you should stop and restart the Communications Inbound Manager server component.
Workflows are refreshed (reloaded) at regular intervals. If you make changes to a workflow process and want the changes to take effect immediately, you should stop and restart the Communications Inbound Manager server component.

If you need to make an eMail Response setup change, you should stop the corresponding Communications Inbound Manager component task before you make the change and start it after you make the change.

NOTE: You do not need to start or stop subtasks. The Siebel server infrastructure does not allow you to control subtasks directly.

Communications Inbound Manager automatically stops when an error in an incoming work item (for example, an email or a phone call) causes abnormal behavior during processing. An error of this type might be a missing From address in an email or a stopped UQ engine.

When Communications Inbound Manager stops the email server component, you have to restart Communications Inbound Manager in the Server Administration screen.

If you try to start the same Communications Inbound Manager component task twice, it will be rejected the second time. However, the first instance will be running as usual. You can always increase the number of subtasks for each component task if you have a high volume of incoming emails.