Siebel Communications Server Administration Guide > Defining Outbound Communication Requests >

Restarting an Aborted Outbound Communications Manager Component

If the Siebel Server aborts (or the host machine stops) while the Communications Outbound Manager component is processing a communication request, Communications Outbound Manager creates a file in the Siebel File System containing information about the last message sent.

The file is named CommOutboundMgrxxx.crf, where xxx is the ID number for the request.

If, at a later time, a request with the same request ID is submitted, Communications Outbound Manager will detect the corresponding file .crf file and resume the request where it left off.

If the request or the template data was modified since the time the request was originally submitted, then the total message output of the resumed request plus the aborted request may not exactly match the output that the original request would have generated had it not been aborted.

You can delete the .crf file if you do not need it. If you delete the .crf file and resubmit the request, then the request will be processed completely from start to finish.

The restart capability described in this section applies only to when the Communications Outbound Manager component aborts while processing a valid communication request. It does not apply to when the component stops processing a request due to error, such as incorrectly specified recipients. In such a case, Communications Outbound Manager does not abort and can continue to receive and process requests.