Bookshelf Home | Contents | Index | Search | PDF

Siebel Communications Server Administration Guide > Using Wireless Messaging >

Configuring WAP Push Messaging

---

In addition to the Siebel Wireless Messaging product option and communications drivers, the base Siebel eBusiness Applications also provide the following drivers:

WAP V1.2
WAP V1.1

NOTE:  The WAP V1.1 communications driver includes a single predefined profile, which requires no configuration. For more information, see Enabling WAP V1.1 Push Messaging.

The WAP V1.2 communications driver provides support to push linkable URLs along with wireless messages. The URL link allows the user to launch the Siebel Wireless application, or another application that is compliant with WAP V1.2.

Messages can be pushed to wireless browsers that support the WAP V1.2 Push standard. Such messages must be sent through a Push Proxy Gateway that can be hosted internally by an enterprise or externally outside the enterprise firewall, such as by a wireless network operator.

The following infrastructure elements support wireless messaging using WAP V1.2. Functionality is provided with the Siebel base applications, unless otherwise noted.

Mobile device and device address information specified by system administrators through the Mobile Devices view in the Communications Administration screen. This information is stored in the S_MBL_DVC and S_MBL_DVC_ADDR tables.
Mobile device, device address, and mobile alert information specified by end users through the Mobile screen. This information is stored in the S_MBL_DVC, S_MBL_DVC_ADDR, and S_MBL_ALERT tables. (The Mobile screen requires a license for either Siebel Wireless or Siebel Wireless Messaging.)
Predefined workflows that automate wireless messaging. For details, see Using One-Way Wireless Messaging Workflows.

Bookshelf Home | Contents | Index | Search | PDF