|
Oracle® Application Server Wireless Administrator's Guide
10g Release 2 (10.1.2) B13820-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Wireless Administrator's Guide
10g Release 2 (10.1.2) B13820-02 |
|
|
Previous |
Next |
This chapter describes how to configure OracleAS Wireless for voice and messaging communications through the following sections:
Section 9.2, "Configuring OracleAS Wireless for Async-Enabled Applications"
Section 9.3, "Configuring OracleAS Wireless for Notifications"
Section 9.4, "Configuring Wireless for Browser-Based Applications"
Voice access is achieved through a VoiceXML gateway, a third-party server that connects to the telephony network on one side and OracleAS Wireless on the other. This voice gateway translates voice commands from the telephony line into HTTP requests which it sends to OracleAS Wireless. The voice gateway then renders the results as audio replies that are played back to the user.
After you install OracleAS Wireless, you can enable voice access. To do this, you must have the Voice.ear file (included with OracleAS Wireless) and obtain a third-party VoiceXML gateway that is approved by Oracle Corporation. OracleAS 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
Once you have selected a VoiceXML gateway provider, you then install and configure the gateway as instructed by the provider.
|
Tip: Seehttp://www.oracle.com/technology/products/iaswe/OracleAS_Wireless_Voice_Deployment.pdf for additional information on configuring and deploying voice access.
|
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 the developer studio 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.1.1.
|
Note: To use the VoiceGenie hosted VoiceXML gateway for testing, you must edit the VoiceGenie device by adding the VoiceGenie*NXP/7.* user agent. For more information, see Section 8.3. |
In addition to obtaining and configuring an approved VoiceXML gateway, you must do the following:
Configure a Messaging Server voice driver (if needed), create an instance of the voice driver, and then add the instance to a Messaging Server process.
Enter the number of the VoiceXML gateway as the value for the Voice Access Phone Number parameter in the Basic Site Configuration wizard (or in the Voice Access Phone Number parameter in the URL section of the HTTP, HTTPS configuration page of the System Manager). For more information, see Section 3.3.
Enter the URL of OracleAS Wireless in the VoiceXML start page slot.
To enable voice access, provision a VoiceXML 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 is 7777 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, they hear a main menu 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.
This section provides an overview of configuring the e-mail and SMS access points that enable users to retrieve content through Asynchronous short name commands (also known as ASK commands) For more information, see Section 3.3 and Section 3.10.2.
Sections include:
E-mail access to the OracleAS Wireless applications enables users to send an e-mail to a pre-defined address and then receive the requested content as a reply. In either the body or the subject line of this e-mail, the user enters a short name command to invoke one of the OracleAS Wireless applications, such as stk <ticker symbol> for information on a particular stock. OracleAS Wireless then replies with the requested data.
To enable e-mail access to wireless content:
Create an e-mail account for the incoming user requests.
Create site access point as described in Section 3.10.2.2.
Configure the appropriate Messaging Server driver instance. For example, to receive messages for a Async Listener e-mail 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 e-mail driver instance so that messages sent to foo@bar.com can be retrieved.
Add the driver instance to a Messaging Server process.
Restart the Messaging Server process.
Users retrieve content from the OracleAS Wireless applications by sending a text message containing the short name of the applications, such as stk <ticker symbol> described in Section 9.2.1. OracleAS Wireless replies with the requested content in a text message.
To deliver SMS messages, set up a communication channel to the SMS carrier that forwards the SMS content to OracleAS Wireless. You must contract with a carrier that has a network for sending and receiving SMS messages through the UCP or SMPP protocols and obtain SMS phone numbers as well. Alternatively, you can use an SMS aggregator, such as Mobile 365, which acts as an intermediary between the SMS carriers and the enterprise. (This may be beneficial when supporting messaging that requires multiple carriers.)
|
Tip: For global SMS delivery, you must obtain an SLA from an SMS aggregator with a reasonable success rate in delivering messages worldwide. Unlike a single carrier, an SMS aggregator can offer expanded reach and coverage because of peering relationships and roaming partnerships. The SMS aggregator must be able to receive messages from global carriers and then communicate with OracleAS Wireless. A list of certified aggregators is located at:http://otn.oracle.com/products/iaswe/integration/content.html You also must create a driver that communicates with the aggregator's infrastructure. |
To create an SMS access point:
Set up a telecom bridge that enables SMS delivery to the OracleAS Wireless over the wireless network. To do this, you must create a driver that communicates with an SMS aggregator's infrastructure. Before you contract with an aggregator, refer to the list of certified SMS aggregators located at:
http://otn.oracle.com/products/iaswe/integration/content.html
Alternatively, you can use one of the pre-built Messaging Server drivers that Support SMS or you can build a driver. If you build a driver, you must consult with the SMS aggregator and follow the OracleAS Wireless SDK. For more information on developing drivers, see to Oracle Application Server Wireless Developer's Guide.
Once you have built a driver, you must add an instance of that driver to a Messaging Server process. For more information on creating driver instances based on Messaging Server drivers, see Section 3.10.3.1.
Create access points for the driver instance as described in Section 3.10.2.2. Enter a name for the access point, enter the SMS phone number as the address, select SMS as the delivery type, and select Allowed to Access All Applications.
Notifications are delivered through different channels (SMS, e-mail, voice, or fax) and alert users to specific messaging events.
OracleAS Wireless ships with its Messaging Server component already configured to use the Oracle-hosted messaging gateway (http://messenger.oracle.com/xms/webservices). The Messaging Server communicates with hosted messaging gateway using the default Messaging Server driver, PushDriver.
|
Notes:
|
OracleAS Wireless ships with an account that enables 1000 units of notifications for SMS, voice, e-mail and fax messages. Because this account provides a limited number of notifications, you must obtain a certified messaging gateway provider, such as MutliMode, Inc., and then build a push driver appropriate to the messaging gateway provider. To contract with a certified messaging gateway provider, refer to
http://otn.oracle.com/products/iaswe/integration/content.html
Alternatively, you can configure the appropriate delivery channel for one of the OracleAS Wireless Messaging Server drivers that ship withOracleAS Wireless. OracleAS Wireless ships with 15 pre-built network drivers that support protocols that are accepted as industry standards. These drivers handle such communications protocols as SMS (short message for phone), e-mail (paging or desktop), voice and fax. To enable those network channels, you must configure the 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 Messaging Server drivers relevant to their particular protocols).
If you build a custom driver, you must consult with the service provider and follow the OracleAS Wireless SDK. For more information on developing drivers, see to Oracle Application Server Wireless Developer's Guide.
To enable those network channels, you must configure the pre-built drivers to work with their corresponding network servers. To do this:
Identify the external server to which OracleAS Wireless connects (this includes acquiring this connectivity and the configuration values for the OracleAS Wireless drivers relevant to their particular protocols).
Add 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 process or selecting an existing one. This step is not required if you use an existing Messaging Server process.
Select the new Messaging Server process (or select an existing Messaging Server process) and create a driver instance for it. The driver instance properties must be configured to work with its corresponding external network connectivity. For details on driver configuration see Section 3.6.2.1
Re-starting the Messaging Server process. For more information on the Messaging Server process, see Section 3.6.2.
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 e-mail driver and driver instance as described in Section 3.6.2.2.1 and Section 3.6.2.2.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 Mobile 365, which 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.2.1 and Section 3.6.2.2.2, respectively.
For OracleAS Wireless Release 10g Release 2 (10.1.2.02), RightFax (a product of Captaris, Inc.) is the supported product for the delivery of fax messages. To enable delivery through the fax channel, you must acquire the RightFax product and follow its instructions to set up a fax server (described in Table 9-1). You must also use the Content Manager to edit the input parameters of the Fax mobile application. For information on editing applications (also known as application links), see Section 6.3.5.
Table 9-1 Required Software for the Fax Mobile Application
| Name | Instructions | From Version |
|---|---|---|
|
RightFaxServer (available from RightFax) |
Install the RightFax server. |
7.2 |
|
RightFax Integration Application (available from RightFax) |
Install the Integration Application on the Fax server. |
7.2 |
|
RightFax PFD application (available from RightFax) |
Install the PFD Application on the Fax server. |
7.2 |
|
RightFax Java API (available from RightFax) |
On Windows NT, copy
On Solaris, copy
Include this .
|
7.2 |
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.2.1 and Section 3.6.2.2.2, respectively.
Sample Cover Page
Although the Fax mobile application uses a customized cover page file, you can use the sample cover page provided by OracleAS Wireless. To use this cover page, Microsoft Word 2000 must be installed on the RightFax server to enable server-side application conversion.
On Solaris installations, this cover page is located at:
ORACLE_HOME/j2ee/OC4J_Wireless/applications/modules/modules-web/images/pim/fax/FCS.doc
On Windows NT installations, this cover page is located at:
ORACLE_HOME\j2ee\OC4J_Wireless\applications\modules\modules-web\images\pim\fax\FCS.doc
To use the provided fax cover page:
Copy FCS.doc to the directory called RightFax\FCS, which is located on the machine on which you installed the RightFax server.
Specify the cover sheet.
Restart Enterprise Fax Manager.
Highlight Users under the appropriate server and double-click the user ID Administrator. Click the Default Cover Sheets tab. In the Cover Sheet Defaults group box, check Send Cover Sheets and select the cover sheet file (FCS.doc) in the Cover Sheet Model field.
Under the appropriate server, highlight Groups and then double-click the group ID Everyone. Click the Basic Information tab. Select the cover sheet file (FCS.doc) in the Cover Sheet Model field.
Restart Enterprise Fax Manager
|
Notes:
|
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. Perform the remaining configuration of the voice driver and driver instance as described in Section 3.6.2.2.1 and Section 3.6.2.2.2, respectively.
|
Note: You must integrate with a VoiceGenie VoiceXML gateway for voice notifications. Provide the application URL to the VoiceGenie outbound call servlet (the required value for thevoicegenie.outbound.servlet.uri parameter) by first selecting VoiceGenieDriver from the Drivers page and then by clicking Edit. From the Driver Class and Parameters section of the Properties page for VoiceGenieDriver, enter the URL for the voicegenie.outbound.servlet.uri parameter.
|
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.4.1.2, "Accessing the OracleAS Wireless Server Using Internet Explorer"
Section 9.4.1.3, "Setting Up the Internet Explorer Home Page"
To access the OracleAS Wirelesss server from a Pocket PC device, connect the device to the network. If the OracleAS Wireless server is on a corporate Intranet, then you must connect the device to the corporate Local Area Network (LAN). If the Wireless server is on the Internet, then you must connect to the 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 Internet Explorer so that you do not have to repeatedly enter the URL to OracleAS Wireless.
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 the user name.
Enter the password.
Select the connection type from the drop-down list.
Enter the phone number.
Click the Connect button to test the settings.
If the handheld device supports more than one-way to connect to the Internet, you can use any 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 the 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 the 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 does not apply to GPRS phones), the WAP gateway, and the home URL for the WAP browser.
Generally, the phone is configured by the 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 the host (host.domain), then the default URL for HTTP and HTTPS protocols are:
Consult with an OracleAS Wireless server administrator for the exact URL to the OracleAS Wireless server. |
