2
Configuring Access Points

For the 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.2, "Enabling Voice"

Section 2.3, "Enabling ASK"

Section 2.4, "Enabling Messaging"

2.1 Enabling Palm, Pocket PC and WAP Devices

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).

Note: One of the parameters that must be configured for all devices is the URL to the Wireless server. If the Wireless server is installed on host host.domain, then the default URL for HTTP and HTTPS protocols are: http://host.domain:7777/ptg/rm https://host.domain:4443/ptg/rm Consult with your Wireless server administrator for the exact URL to your Wireless server.

Setting the HTTP(S) URL depends on the type of device. The following sections describe a different device. These sections include:

• Section 2.1.1, "Palm Devices"
• Section 2.1.2, "Pocket PC Devices"
• Section 2.1.3, "WAP Devices"

2.1.1 Palm Devices

2.1.1.1 Connecting to a Network

There are two types of Palm devices when it comes to connecting to the Internet/Intranet:

• Devices with built-in wireless Internet access (Palm.Net® ready) - 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

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.)

2.1.1.2 Configuring the Connection Method

1. Open Preferences by tapping the Prefs icon.
2. Select Connection.
3. Select the connection method from the list of Available Connections.

2.1.1.3 Configuring an ISP Account

1. Open Preferences by tapping the Prefs icon.
2. Select Network.
3. Select the Service value from the drop down list.
4. Enter your User Name.
5. Enter your Password.
6. Select the Connection type from the drop down list.
7. Enter Phone number.
8. Tap 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.

1. Open Preferences by tapping the Prefs icon.
2. Select Web Clipping.
3. Select the Connection name from the drop down list.

2.1.1.4 Accessing the Wireless Server Using MyPalm Application

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.

1. Open MyPalm application by tapping the MyPalm icon.
2. Enter the URL to the wireless server and tap the "Go" button.

2.1.1.5 Installing Blazer Web Browser

There are different web browsers for Palm, but probably the most popular one is Blazer by Handspring.

1. Download the Blazer browser software from http://blazer.handspring.com
2. Follow the installation instructions provided 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)

2.1.1.6 Accessing the Wireless Server Using Blazer

1. Open Blazer by tapping the Blazer icon.
2. Tap the Go to Web Page icon (the opened folder icon).
3. Enter the URL to the wireless server and tap the "OK" button.

   Tip: You can create a Bookmark so you do not need to repeatedly type the URL.

2.1.2 Pocket PC Devices

2.1.2.1 Connecting to the Network

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

2.1.2.2 Accessing the Wireless Server Using Internet Explorer

1. Open Internet Explorer by tapping Start, then Internet Explorer. (If you are already in Internet Explorer, go to step 2.)
2. Tap View, then Address Bar to display the Internet Explorer Address Bar (If the Internet Explorer Address Bar is already shown, go to step 3.)
3. Enter the URL to the Wireless server in the Address Bar and tap the "GO" button (the green arrow).

2.1.2.3 Setting Up the Internet Explorer Home Page

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.

1. While still displaying the Wireless server main page tap Tools, then Options...
2. Tap Use Current button in the Home page section.
3. Tap OK.

2.1.3 WAP Devices

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.

2.1.3.1 Installing and Configuring 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.

2.1.3.2 Configuring a WAP Phone

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.

2.2 Enabling Voice

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.

2.2.1 Prerequisites

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:

1. Obtain a Nuance Extranet Developer account free of charge by visiting http://extranet.nuance.com/developer/. Follow directions at that site.
2. Obtain a PingTel Developer account free of charge by visiting https://secure.pingtel.com/www/registration/registerUser.jsp. Follow directions at that site.

2.2.2 Platform requirements

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.

Note: This release of VWS is supported only on a special release of Nuance 8.0 which is available from the VWS download section of the Nuance extranet. The special release of Nuance 8.0 is intended only for use with this release of VWS. No other use is supported.

2.2.2.1 Hardware

• Pentium II or higher CPU.
• SoundBlaster audio hardware if using native audio or SIP desktop telephony.
• Dialogic or NMS telephony board, if applicable.

2.2.2.2 Operating System

• Windows 2000 with Service Pack 2.

2.2.2.3 Third-party Software

• Java 2 Standard Edition (J2SE) SDK 1.3.1
• Jakarta Tomcat 4.0.3 (recommended).
• Dialogic System Release 5.1 (if using Dialogic telephony boards).
• NMS Natural Access 2002-1 (if using NMS telephony boards).

2.2.2.4 Nuance software

• Nuance System 8.0 Release for VWS. This special release is available in the VWS download section of the Nuance extranet.
• Connectivity Pack 2.0.
  • Dialogic Connectivity Pack 2.0.4
  • SIP Connectivity Pack 2.1.1
  • NMS connectivity Pack 2.1.0
• Foundation Speech Objects 1.1.1
• Nuance Vocalizer 2.0 Service Pack 1 (Recommended)

  Note: See the Nuance Voice Web Server release notes for the most current information.

Once you have downloaded all the preceding 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.

2.2.3 marconi_voice.ear

marconi_voice.ear includes two applications:

• Voice Login
• Main Menu Service

2.2.4 Voice Login

The main .jsp is located in:

/marconi_voice/voicelogin/login.jsp

The audio files are located in:

/marconi_voice/voicelogin/audio/default/en

 

Note: This is the voice login .jsp that must be provisioned to a phone number. It is a voice XML script that goes through the voice login procedure and then forwards to ptg/rm with the login credentials and the OID of the main menu service. It has to be provisioned in the following way: http://<server-name>:<port>/marconi_voice/voicelogin/login.jsp?PAoid=<oid of the Voice Main Menu service>&language=<language code>&countrycode=<country code> Where the port is the WebCache listening port number. 7777 is the default port number, and the port number range is 7777 to 7877. To obtain the voice main menu_service OID, log in to the Webtool, click Content Manager and get the Object ID for the Voice Main Menu service. The Language code is in the standard 2-letter Java locale format (for example: "en" = English, "fr" = French). The Country code is also in a 2 letter Java format (for example: "US", "UK", "BR"). If English is the intended language, then you do not need the language and the country code attributes.

2.2.4.1 Sample Use Case for Voice Login

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.

2.2.5 Main Menu Service

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.

2.2.5.1 Sample user case for main menu

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.

2.3 Enabling ASK

2.3.1 Introduction

The Asynchronous 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:

• Site address--the entry point to the ASK server, akin to a URL to a Web site. Users send messages to the address to invoke the service of interest. Currently, ASK supports email addresses and SMS phone numbers.
• Service short name--site-wide unique name that identifies a 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 [e-mail], with the short name stk. This invokes the stock service built on top of Wireless (assuming a Wireless service was given the short name stk and [e-mail] was designated as a site address for messaging devices to access Wireless services).
• Messaging Server--built on top of the Wireless Messaging System, ASK is able to support multiple transport protocols. To enable ASK, 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.

See the Oracle9iAS Developer's Guide for Oracle9iAS Wireless for more information on ASK features.

2.3.2 Enabling Email-based (Two-Way Pager) Access

1. Choose one or more site-addresses as the ASK email entry points to the site.
2. Add the site-addresses onto the Wireless system. For more information, see Section 12.2.2. The designated site addresses should be configured on the underlying Messaging Server. For example, to receive messages for a site-address such as [e-mail], 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 [e-mail] can be retrieved. Set up and configuration tasks are listed in Enabling Messaging, Section 12.2.3, "Configuring the Site Processes of the Messaging Server".

2.3.3 Enabling SMS Phone Access

1. Acquire one or more SMS phone numbers from the SMS carrier or aggregator. They are used as the SMS entry points to the site.
2. Add the site-addresses onto the Wireless system as detailed in Section 12.2.2. 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. Set up and configuration tasks are listed in Enabling Messaging, Section 12.2.3, "Configuring the Site Processes of the Messaging Server".

2.3.3.1 Service Short Name Change

Each preconfigured 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.

2.4 Enabling Messaging

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 preconfigured 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.

2.4.1 Oracle-hosted Messaging Delivery

The Wireless messaging system is preconfigured 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 [e-mail] for information, or to set up your own account for volume message delivery.

Note: The 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. See this Guide for steps on proxy changes.

2.4.2 Non Oracle-hosted Messaging 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:

1. Identify to which external server to which Wireless will connect, including acquiring such connectivity and preparing for the values needed to configure the Wireless drivers depending on their particular protocols.
2. Add the supported driver and configure its messaging properties.
3. Create a Messaging Server or choose an already created Messaging Server.
4. Create a driver instance and associate it with the Messaging Server on which it will run. The driver instance properties must be configured to work with its corresponding external network connectivity.
5. Start the Messaging Server. For details on driver configuration see Section 12.1.2. For Messaging Server management, see Section 11.2.1.

Also, the preconfigured PushClient driver and its corresponding instances should be removed if they are not to be used.

Here are tasks, specific to different network channels:

2.4.2.1 Email-based Message Delivery

To enable the email and paging services:

1. Set up an SMTP mail server for outgoing messages.
2. Optionally, set up an IMAP or POP3 mail server if message receiving is required.
3. Configure the email driver and driver instance as described in the common tasks section.

2.4.2.2 SMS Phone Message Delivery

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) and driver instances as specified in the common tasks Section 12.2.3, "Configuring the Site Processes of the Messaging Server".

2.4.2.3 FAX Delivery

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.

2.4.2.4 Voice Delivery

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.