|Bookshelf Home | Contents | Index | PDF|
Communications Inbound Receiver and Communications Inbound Processor will not stop if an incoming work item (such as an email or a phone call) causes abnormal behavior during processing. Instead, a log file entry will be created for the abnormal behavior. An example of abnormal behavior could be a missing From address in an email or a stopped UQ engine. The log files for Communications Inbound Receiver and Communications Inbound Processor are:
To investigate any abnormal behavior during processing, go to the Components view in the Administration - Communication > Communication Inbound Events screen and make sure there are entries for each email that is being processed. After an email has been successfully processed the entry will be deleted. If the email was not successfully processed, make sure that the status and comments are correct. You should also check the URL to make sure you have the right name. If you want to resubmit a failed email for processing, see Resubmitting a Request.
Before reporting any abnormal behavior during processing, make sure comminboundrcvr and comminboundprocessor are set to the proper debugging level and MIME message. You need to attach both of these files to the abnormal behavior when reporting the problem.
|Siebel Email Response Administration Guide|