Oracle9iAS Wireless Administrator's Guide Release 9.0.3 Part Number B10042_01 |
|
|
In order for Collaboration Suite to work with wireless devices, communications to those devices must be enabled. This chapter includes instructions on enabling these devices. It includes the following sections:
Section 2.1, "Enabling Palm, Pocket PC and WAP Devices"
Section 2.4, "Enabling Messaging"
Wireless can serve requests from different devices, including Palm, Pocket PC, and WAP. These devices must be configured in order to access the Wireless server. Requests from these devices to the wireless server come through HTTP(S) protocol Protocol transformation gateway may be used in some cases to convert the device native network protocol to HTTP(S).
Setting the HTTP(S) URL depends on the type of device. The following sections describe a different device. These sections include:
There are two types of Palm devices when it comes to connecting to the Internet/Intranet:
If you have a device with built-in wireless Internet access, then the only thing that you need to do to connect your device to the Internet is to activate your wireless service. For more information about Wireless Connectivity with Palm.Net® Service see: http://www.palm.com/products/palmi705/wireless.html.
If your device does not have built-in Internet access then you will need either a data-enabled phone or a Palm modem. Also, you will need an ISP account. (You can use a a data-enabled phone or a Palm modem with Palm i705, too.)
If your handheld device supports more than one-way to connect to the Internet, you may choose your preferred method.
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.
There are different web browsers for Palm, but probably the most popular one is Blazer by Handspring.
http://www.handspring.com/software/how_to.jhtml. (General instructions about installing software on Palm devices is available here: http://software.palm.com/download.jsp)
To access the Wireless server from your Pocket PC device, connect the device to the network. If the 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). There are different ways to connect your Pocket PC device to your corporate LAN or to your ISP, and they are all documented in the Pocket PC Connection Manager tutorial at: http://www.microsoft.com/mobile/pocketpc/tutorials/connectionmanager/default.asp
Once connected to the main page on the Wireless server, you can make that page the Home Page for your Internet Explorer. Doing so saves you the efforts of entering the URL every time.
WAP devices use the WAP protocol for communication. The Wireless server does not support the WAP protocol directly. For this reason, you need a WAP gateway to convert the WAP protocol to HTTP(S). If you connect to the Internet through your Wireless service provider, then the carrier must have already configured a WAP gateway for you. However, if you connect to the Internet/Intranet through a dial-up (PPP connection), then you must install and configure a WAP gateway.
Ensure that the WAP gateway you plan to install is a certified WAP gateway. The certified WAP gateways are listed at: http://mobile.us.oracle.com/ompm/site/product/devices/certified/certified_gateways_wap.jsp. Follow the installation instructions provided by your WAP gateway vendor.
Some gateways (WAPLite for example) have a configuration parameter for the Default WML Home Page. You can set this parameter to the Wireless server main page to save your users the inconvenience of typing this over and over again.
The WAP phone configuration is specific to the phone model and wireless service provider. In general the phone must be configured for dial-up network connection (not applicable for GPRS phones), WAP gateway, and the home URL for your WAP browser. In most cases, your phone is reconfigured by your wireless service provider to connect to their own WAP gateway. Some wireless service providers even hide the phone settings so that they cannot be changed by the phone user. And in most cases you will not need to make any changes in the phone network settings. The only thing that you will need to access a wireless server from your WAP phone is the URL to that server. Open the WAP browser (see the phone user's manual how to do that) and type that URL.
You must perform the following configuration to enable voice access to the Collaboration Suite components. This section describes the configuration tasks using Nuance Voice Web Server as an example.
To enable wireless voice access, you must build a voice gateway. To build the gateway, you must establish two accounts, free of charge, before being able to download the evaluation software to build your development VoIP Voice Gateway. To establish the necessary accounts:
The Nuance Voice Web Server (VWS) Installation Guide specifies the configurations supported by Voice Web Server and lists the required hardware and software. Note that this release of Voice Web Server is supported with the Nuance software versions listed in this section. Later versions of Nuance software may be available from the download area of the Nuance Developer Network, but this release of VWS may not be supported on them.
Once you have downloaded all the above software and followed all the Nuance instructions on how to configure the Voice Web Server, you will be able to connect to your Voice Gateway by using the PingTel Softphone that you have downloaded.
marconi_voice.ear includes two applications:
The main .jsp is located in:
/marconi_voice/voicelogin/login.jsp
The audio files are located in:
/marconi_voice/voicelogin/audio/default/en
System: Welcome to the Oracle Collaboration Suite. Enter your account number or say help.
User: 1234
System: Enter your PIN.
User: 1234
System: Hold on for a second while I access your account.
Note: Users must provide account number and PIN to access the portal. See Section 9.3.4 for information on creating user accounts. |
The main JSP is located in /marconi_voice/mainmenu/myhome.jsp
The audio files are in /marconi_voice/mainmenu/audio/default/en
A top level service called "Voice Main Menu" is created on the webtool to access this .jsp.
The setup for this service should include the URL, /marconi_voice/mainmenu/myhome.jsp and all of the service parameters from the mail and calendar modules.
The voice login automatically forwards to this service on ptg/rm instantiation.
The main menu includes MailMessageInclude.jsp which counts the number of new email messages and CalendarAppointmentInclude.jsp which counts the number of calendar appointments.
System: Main Menu. You have two new email messages, one new voicemail message and no pending appointments. Your options are: mail, calendar, tasks, files, address book, directory, or my location.
User: Mail.
System: Oracle Email. Please wait while your email is fetched.
The Async Server Kernel (ASK) enables Wireless services to be accessed using such messaging devices as SMS phone (two-way text message capable), two-way pagers and email. Here are some ASK-related terms:
See the Oracle9iAS Developer's Guide for Oracle9iAS Wireless for more information on ASK features.
Each pre-configured ASK-enabled service 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. The name can be easily configured and changed through a GUI tool if desired.
Oracle9iAS Wireless features a messaging component that handles sending and receiving messages to and from devices. Typically, 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/Fax messages without configuration, by connecting to and utilizing the Oracle-hosted online Push Service.
If you choose not to use the Oracle-hosted online Push Service, you must set up the necessary communications channels. Wireless includes a set of drivers that you can use to configure your network capability (such as SMS, Voice, or email). This may involve dealing with network providers (carriers) depending on your network type, to set up the kind of connection the drivers can connect to for message delivery.
The Wireless messaging system is pre-configured to connect to the Oracle-hosted online Push Service 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 driver in this case is the PushClient driver; it is configured to communicate with the Oracle-hosted online Push Service running at URL http://messenger.oracle.com/push/webservices. Contact messenger_us@oracle.com for information, or to set up your own account for volume message delivery.
Wireless ships with pre-built network drivers that support major protocols that have been accepted as industry standards. The 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:
Also, the pre-configured PushClient driver and its corresponding instances should be removed if they are not to be used.
Here are tasks, specific to different network channels:
To enable the email and paging services:
In order to deliver SMS messages to phones, you must set up a communication channel to the SMS carrier. To do this, you must contract with a carrier having a network that you will use to enable the sending and receiving of SMS messages through UCP or SMPP protocol.
Alternatively, you can choose to use a network aggregator, such as Mobileway, who acts as an intermediary between the SMS carriers and the enterprise. This may save some effort when supporting messaging on which multiple carriers are required. See the following URL for vendors whose protocols are certified to work with Wireless:
http://otn.oracle.com/products/iaswe/integration/content.html
Configure the corresponding SMS drivers (for example: UCP, SMPP etc.) and driver instances as specified in the common tasks Section 12.2.3, "Configuring the Site Processes of the Messaging Server".
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 specified in the common tasks.
The voice driver implements the Out Bound Call protocol supported by VoiceGenie Technologies Inc. It has been certified to work with the VoiceGenie gateway. A gateway to be used by Wireless's Voice Driver must be identified.
Configure the voice driver and driver instance as described in the common tasks.