|Bookshelf Home | Contents | Index | PDF|
When you use nonreal-time email processing, Communications Inbound Receiver monitors email accounts (email addresses) by using communications driver profiles to check for inbound messages. For information about enabling nonreal-time processing, see Enabling Nonreal-Time Email Processing.
When Communications Inbound Receiver detects an inbound email, it gets the email from the email server, converts the email into event data, and creates a server request for the Server Request Broker component to inform Communications Inbound Processor of the new event. Communications Inbound Processor uses workflows to process and route the event. Communications Outbound Manager uses communications driver profiles to handle outbound communications to customers.
Communications drivers. Drivers specify the protocol to use to access the email server, and driver parameters control the behavior of each driver. For example, the Internet SMTP/POP3 Server driver logs in to the POP3 server and checks for new email at an interval that you set in the PollingInterval driver parameter.
NOTE: Changes that you make to a communications driver's parameters affect everyone who uses that driver. Therefore, it is recommended that the person in your organization who maintains communications drivers makes or approves all changes.
Communications drivers and profiles for Siebel Email Response enable Communications Inbound Receiver to monitor mailboxes for inbound messages. Other communications channels, such as voice, use different communications drivers and profile types.
|Siebel Email Administration Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|