Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Outbound Manager >

Running Communications Outbound Manager

When the Communications Management component group is enabled, the Communications Outbound Manager component is started automatically. For any machine on which you do not want to run Communications Outbound Manager, configure the Siebel Server not to start it.

Communications Outbound Manager is a batch-mode server component. It relies on the services of the Server Request Broker and Server Request Processor server components. These components must be running on the Siebel Server for communication requests to be dispatched successfully.

NOTE:  If a messaging system server, such as an email server, is restarted, then the Communications Outbound Manager server component that connects to it must also be restarted.

As a batch-mode component, Communications Outbound Manager is subject to the requirements described in Synchronizing Batch-Mode Server Components. If Communications Outbound Manager has not been synchronized, as appropriate, then users who submit outbound communication requests may receive this error message:

Unable to find definition for component CommOutboundMgr.

For more information about monitoring communication requests and server requests, see Monitoring Outbound Communication Request Status and Monitoring Siebel Server Request Status.

For more information about configuring, starting, and stopping Siebel Server components, see Siebel System Administration Guide.