|
Oracle® Application Server Wireless Administrator's Guide
10g Release 2 (10.1.2) Part No. B13820-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Wireless Administrator's Guide
10g Release 2 (10.1.2) Part No. B13820-01 |
|
|
Previous |
Next |
This chapter describes how to configure OracleAS Wireless for voice and messaging communications through the following sections:
Section 9.1, "Configuring Wireless for Browser-Based Applications"
Section 9.3, "Configuring OracleAS Wireless for Async-Enabled Applications"
Section 9.4, "Configuring OracleAS Wireless for Notifications"
This section describes how to configure OracleAS Wireless for PocketPCS, Palm, and WAP phone applications. Topics include:
This section describes the procedures for configuring Oracle Application Server Wireless to PocketPCS. Topics include:
Section 9.1.1.2, "Accessing the Wireless Server Using Internet Explorer"
Section 9.1.1.3, "Setting Up the Internet Explorer Home Page"
To access the OracleAS Wirelesss server from your Pocket PC device, connect the device to the network. If the OracleAS Wireless server is on your corporate Intranet, then you must connect your device to your corporate Local Area Network (LAN). If the Wireless server is on the Internet, then you must connect to your Internet Service Provider (ISP). The other methods for connecting the Pocket PC device to a corporate LAN or ISP are documented in the Pocket PC Connection Manager tutorial at:
http://www.microsoft.com/mobile/pocketpc/tutorials/connectionmanager/default.asp
To access the OracleAS Wireless server using Internet Explorer:
Open Internet Explorer by clicking Start in the desktop, then by selecting Internet Explorer. (If you are already in Internet Explorer, go to Step 2).
Select View, and then Address Bar to display the Internet Explorer Address Bar (If the Internet Explorer Address Bar displays, go to Step 3.)
Enter the URL to the OracleAS Wireless server in the Address Bar and click the GO button (represented as a green arrow).
Once connected to the main page on the OracleAS Wireless server, you can make that page the Home Page for your Internet Explorer. Doing so saves from entering the URL every time.
While still displaying the OracleAS Wireless server main page select Tools, then Options....
Select the Use Current button in the Home page section.
Select OK.
There are two types of Palm devices for connecting to the Internet and Intranet:
Devices with built-in wireless Internet access (Palm i705)
Devices that require an Internet Service Provider (ISP) account and data-enabled phone or modem to access the Internet (Palm m515, Palm m505, Palm m500, Palm m130, Palm m125).
For a device with built-in wireless Internet access, you need only to activate the wireless service to connect the device to the Internet.
For devices that do not have built-in Internet access require an ISP account and either a data-enabled phone or a Palm modem. (A data-enabled phone or a Palm modem will suffice for the Palm i705l.)
To configure the connection method:
Open Preferences by clicking the Press icon.
Select Connection.
Select the connection method from the list of Available Connections.
To configure the ISP account.
Open Preferences by clicking the Press icon.
Select Network.
Select the service value from the drop down list.
Enter your user name.
Enter your password.
Select the connection type from the drop-down list.
Enter the phone number.
Click the Connect button to test the settings.
If your handheld device supports more than one-way to connect to the Internet, you may choose your preferred method.
Open Preferences by clicking the Prefs icon.
Select Web Clipping.
Select the connection name from the drop down list.
If you have a Palm device with built-in wireless Internet access and you have activated your wireless service, then you can use the Palm native web browser to access a wireless server.
Open MyPalm application by clicking the MyPalm icon.
Enter the URL to the wireless server and click the Go button.
To install PalmOne's Blazer browser:
Download the Blazer browser software from http://www.palmone.com
Follow the installation instructions provided at:
The OracleAS Wireless server does not directly not support the WAP protocol, which enables WAP devices to communicate. As a result, supporting WAP requires a WAP gateway to convert the WAP protocol to HTTP(S). If you can connect to the Internet through your wireless service provider, then the provider has already configured a WAP gateway for you. However, if you connect to the Internet (or Intranet) through a dial-up (PPP) connection, then you must install and configure a WAP gateway.
The WAP phone configuration is specific both to the phone model and to the wireless service provider. In general, the phone must be configured for a dial-up network connection (this is not applicable to GPRS phones), the WAP gateway, and the home URL for your WAP browser.
Generally, your phone is reconfigured by your wireless service provider to connect to their own WAP gateway. Some wireless service providers hide the phone settings to prevent the user from changing them. In most cases, you do not need to change the phone network settings; instead, to access the wireless server from a WAP phone, you need only enter the URL of the wireless server into the phone's WAP browser. (Refer to the phone's user's manual for instructions on opening the WAP browser.)
OracleAS Wireless serves requests from different devices, including Palm, Pocket PC, and WAP. These devices must be configured so that they can access the OracleAS Wireless server. Requests from these devices to the wireless server come through an HTTP(S) protocol transformation gateway may be used in some cases to convert the device native network protocol to HTTP(S).
|
Note: The URL to the OracleAS Wireless server must be configured for all devices. If the OracleAS Wireless server is installed on host host.domain, then the default URL for HTTP and HTTPS protocols are:
Consult with your OracleAS Wireless server administrator for the exact URL to your OracleAS Wireless server. |
After Wireless has been installed and configured, the Oracle-hosted voice gateway enables you to immediately access applications from voice devices. For more information, go to http://mservice.oracle.com.
This section provides information on configuring your own voice gateway using the VoiceGenie Developer Studio as an example.
To configure voice access to OracleAS Wireless, you must have access to an Oracle-accepted third-party VoiceXML gateway and the Voice.ear file (included with OracleAS Wireless). Wireless has been tested against a number of VoiceXML gateways. The list of accepted gateways is located at: http://otn.oracle.com/tech/wireless/integration/content.html
Follow the third-party provider's instructions to properly install and configure your VoiceXML gateway.
If you do not have access to a VoiceXML gateway, a number of gateway providers have hosted gateways for developers that can be used free of charge for development and testing purposes. For example, VoiceGenie maintains a developer studio at http://developer.voicegenie.com, where users can sign up for a development account that provides them with 10 extensions to a voice gateway. From this Web site, users configure each of their extensions to point to different URLs. To configure voice access to Wireless, you must set up an extension to point to the URL outlined in Section 9.2.2.
Setting up the Accounts
Obtain a VoiceGenie developer account by visiting http://developer.voicegenie.com.Follow directions at that site.
To enable voice access, provision a voice gateway phone number to the following URL:
<server-name>:<port>/ptg/rm?PAlogin=true&PAlocale=<locale>
Where the port is the WebCache listening port number 7777 (the default port number) and the port number range is 7777 to 7877.
You must specify the locale for a language other than English; if the locale is English, however, then you do not need the PAlocale attribute. Specify the locale using the two-letter Java locale format (the two-letter Java country code is optional). For example, to define the PAlocale attribute as French-Canadian, enter fr_CA (fr is the Java locale, CA is the country code).
This provisioning scheme contacts the voice login service for the OracleAS Wireless server. After users login, a main menu displays, which lists all of the applications that they can access.
|
Note: Users must provide their account numbers and PINs to access the portal. |
Use the PAoid=<oid> attribute to enable users to log into a particular application.
Asynchronous-enabled OracleAS Wireless applications can be accessed using such messaging devices as an SMS phone (two-way text message capable), two-way pagers and email. Async-related terms in OracleAS Wireless include the following:
Site address—The entry point to the Async Listener, which is similar to a Web site's URL. Users send messages to the address to invoke the target application. Wireless's Async supports includes email addresses and SMS phone numbers.
Service short name—A site-wide, unique name that identifies a OracleAS Wireless service. Device users send messages to the site address with service short names in the message body to invoke the corresponding service. For example a message is sent to site address ask@oraclemobile.com, with the short name stk. This invokes the stock service built on top of OracleAS Wireless (assuming a OracleAS Wireless service was given the short name stk and ask@oraclemobile.com was designated as a site address for messaging devices to access Wireless services).
Messaging Server—Built on top of the Wireless Messaging System, Async can support multiple transport protocols. To enable Async, you must configure the messaging capability of a particular network, and a messaging driver supporting such a protocol (with two-way capability) for the underlying Messaging Server.
To configure e-mail-based access:
Select one or more site-addresses as the Async email entry points to the site.
Add the site-addresses to the OracleAS Wireless system. For more information, see Section 3.3.1. The designated site addresses should be configured on the underlying Messaging Server. For example, to receive messages for a site-address such as foo@bar.com, you must know the mail server which hosts the account, the protocol used (IMAP or POP3), and the user name and password. You must then create and configure an email driver instance so that messages sent to foo@bar.com can be retrieved.
Acquire one or more SMS phone numbers from the SMS carrier or aggregator. They are used as the SMS entry points to the site.
Add the site-addresses to the OracleAS Wireless system as described in Section 3.3.1. The designated site addresses must be configured on the underlying Messaging Server to ensure the retrieval of messages addressed to the SMS phone number can be retrieved (as is done in email). Different drivers must be configured depending on the actual protocol of the SMS connectivity.
Each pre-configured Async-enabled application is assigned a short name so the service is addressable to device users. In other words, a shortname is the keyword that device users use to identify which service they intend to invoke.Use the Content Manager to create and edit short names. For more information, see Section 6.3.4. in Chapter 6, "Managing Content".
This section discuses configuring email, SMS, pagers, fax and voice for notifications.
OracleAS Wireless features a messaging component that handles sending and receiving messages to and from devices. Typically, OracleAS Wireless must be configured to connect to an external server to deliver messages (such as SMS or email).
Wireless is pre-configured to send SMS, Voice, Email and Fax messages without configuration, by connecting to and utilizing the Oracle-hosted online Push Service.
If you do not to use the Oracle-hosted online Push Service, you must set up the necessary communications channels. OracleAS Wireless includes a set of drivers that you can use to configure capability of the network (such as SMS, Voice, or email). Depending on the type of network, seting up the appropriate connection that enables the drivers to connect for message delivery may involve working with network providers (carriers).
The OracleAS Wireless messaging system is pre-configured to connect to the Oracle-hosted online Push Service, which is capable of sending messages to SMS phones, pagers, voice and faxes. No configuration is required. Once the pre-seeded Messaging Sever is started, you can send messages. The PushClient driver is configured to communicate with the Oracle-hosted online Push Service running at the following Push SOAP URL:
http://messenger.oracle.com/xms/webservices
If the OracleAS Wireless instance has been upgraded from the 9.0.2 to the 9.0.4 release, then the URL, http://messenger.oracle.com/push/webservices is valid (though the application will in fact be running the 9.0.2 code base). As such, this URL is intended for backward compatibility only; you should update the clients of the SOAP API to use the /xms/webservices URL.
|
Note: The OracleAS Wireless PushClient driver uses the HTTP protocol to communicate with the Oracle online Push Web Service; the HTTP proxy setting is needed if you run your application behind a firewall. Refer to Section 3.3.1 for steps on changing the proxy |
OracleAS Wireless ships with pre-built network drivers that support major protocols that have been accepted as industry standards. These pre-built drivers handle communications protocols such as SMS (short message for phone), email (paging or desktop), voice and fax.
To enable those network channels, you must configure the pre-built drivers to work with their corresponding network servers by:
Identifying the external server to which OracleAS Wireless connects (this includes acquiring this connectivity and the configuration values for the OracleAS Wireless drivers relevent to their particular protocols).
Adding the supported driver and configuring its messaging properties. This step is not required if you use the drivers that are packaged with the OracleAS Wireless Server.
Creating a Messaging Server or selecting an existing one. This step is not required if you use an existing Messaging Server.
Select the new Messaging Server (or select an existing Messaging Server) and create a driver instance for it. The driver instance properties must be configured to work with its corresponding external network connectivity.
Starting the Messaging Server. For details on driver configuration see Section 3.3.4.2.
|
Tip: If you add the driver instance to a pre-configured Messaging Server, then you can remove the pre-configured PushClient driver and its corresponding instances if it is not used. |
To configure the e-mail and paging services:
Set up an SMTP mail server for outgoing messages.
Optionally, set up an IMAP or POP3 mail server if message receiving is required.
Configure the email driver and driver instance as described in Section 3.6.2.5 and Section 3.3.4.2, respectively.
To deliver SMS messages to phones, set up a communication channel to the SMS carrier. To do this, you must contract with a carrier that has a network for sending and receiving SMS messages through the UCP or SMPP protocols.
Alternatively, you can use a network aggregator, such as Mobileway, who acts as an intermediary between the SMS carriers and the enterprise. (This may be beneficial when supporting messaging that requires multiple carriers.) Vendors whose protocols are certified to work with OracleAS Wireless are listed at:
http://otn.oracle.com/products/iaswe/integration/content.html
Configure the corresponding SMS drivers (for example: UCP, SMPP) and driver instances as described in described in Section 3.6.2.5 and Section 3.3.4.2, respectively.
For this release, RightFax (a product of Captaris, Inc.) is the supported product. Customers must acquire the RightFax product and follow its instructions to set up a fax server.
The location of client API .jar files from RightFax must be added to the classpath in ORACLE_HOME/wireless/sample/runpanamaserver.sh. Configure the fax driver and driver instance as described in Section 3.6.2.5 and Section 3.3.4.2, respectively.
The voice driver implements the outbound telephony calls through a VoiceGenie VoiceXML Gateway. To configure the voice driver, provide the URL to the VoiceGenie Outbound Call servlet. Peform the remaining configuration of the voice driver and driver instance as described in Section 3.6.2.5 and Section 3.3.4.2, respectively.
