Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Inbound Receiver >

Running Communications Inbound Receiver

When the Communications Management component group is enabled, the Communications Inbound Receiver component is started automatically. For any machine on which you do not want to run Communications Inbound Receiver, configure the Siebel Server not to start it. Communications Inbound Receiver restarts automatically if the Siebel Server goes down and is brought back up.

Communications Inbound Receiver is a batch-mode server component, although it also has characteristics of other component types. 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 communications to be processed successfully.

As a batch-mode component, Communications Inbound Receiver is subject to the requirements described in Synchronizing Batch-Mode Server Components.

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

To provide greater availability and reliability for your deployment of the Communications Inbound Receiver server component, active response groups and individual profiles loaded within active response groups can be updated without your having to stop and restart the server component:

  • Profiles can be updated by using the Submit Profile Changes command for the profile.
  • Response groups can be updated (all profiles within the current response group) by using the Submit Response Group Changes command for the response group.

For more information, see Specifying Parameter Override Values for Profiles. See also Siebel Email Response Administration Guide.

Siebel Communications Server Administration Guide