Bookshelf Home | Contents | Index | Search | PDF

Siebel Communications Server Administration Guide > Using Wireless Messaging > Installing and Configuring Siebel Wireless Messaging >

Configuring Communications Drivers and Profiles

---

To complete configuring Siebel Wireless Messaging, you must create a separate communications driver profile for each wireless network operator and each connection type that will be used to send or receive wireless messages. Do this whether you use the MobileSys Network or connect directly to wireless network operators.

Siebel Wireless Messaging drivers include:

Wireless Messaging 1-Way. Supports outbound wireless messaging using SMS, TAP, and SMTP wireless message types. Requires Siebel Wireless Messaging. For parameter information, see Wireless Messaging 1-Way Driver Parameters.
Wireless Messaging 2-Way. Supports inbound and outbound wireless messaging using SMS wireless message types. Requires Siebel Wireless Messaging. For parameter information, see Wireless Messaging 2-Way Driver Parameters.

NOTE:  The WAP V1.2 and WAP V1.1 communications drivers may also be used with Siebel Wireless Messaging. Using them does not require Siebel Wireless Messaging. For information, see Configuring WAP Push Messaging.

The Wireless Messaging 1-Way or Wireless Messaging 2-Way communications drivers send and receive wireless messages using XML over HTTP or HTTPS. The XML document contains content and addressing information for the message.

For one-way messaging, which uses MobileSys MX, Siebel Communications Server sends outbound messages to MobileSys MX in XML format over HTTP.
For two-way messaging, which uses the MobileSys Network and does not use MobileSys MX, Siebel Communications Server sends outbound messages to, and receives inbound messages from, the MobileSys Network in XML format over HTTPS.

NOTE:  After a wireless message is sent to a wireless messaging gateway using one of the communications drivers described in this section, the Communications Outbound Manager server component may log that the message has been successfully sent. However, the log file cannot indicate whether the wireless message was ultimately delivered to a valid wireless messaging address by the wireless messaging gateway. In addition, customers can retrieve message delivery status from MobileSys MX or the MobileSys Network.

For more information about communications drivers, see About Communications Drivers and Profiles and Configuring Communications Drivers and Profiles.

Bookshelf Home | Contents | Index | Search | PDF