4
Configuring Mobile Services for Voice and Wireless

This document describes the Wireless Mobile Services. The Wireless Mobile Services support wireless-enabling of the communications applications. Each section of this document presents a different topic. These sections include:

• Section 4.1, "What Must Be Configured?"
• Section 4.2, "Address Book"
• Section 4.3, "Calendar"
• Section 4.4, "Directory"
• Section 4.5, "Fax"
• Section 4.6, "Online Files"
• Section 4.7, "Instant Messaging"
• Section 4.8, "Mail"
• Section 4.9, "Short Messaging"
• Section 4.10, "Business Directory"
• Section 4.11, "Driving Directions"
• Section 4.12, "Location Picker"
• Section 4.13, "Maps"

4.1 What Must Be Configured?

You must configure Wireless mobile services to enable your communications applications for wireless access. The mobile services that must be configured depend on which of the Collaboration Suite applications you will deploy. All of the necessary libraries are shipped with Oracle Collaboration Suite. The following table lists the communications applications, and which of the wireless mobile services that support them. Here is a list of communications applications and their associated mobile services:

• Unified Messaging
  • fax
  • address book
  • directory
  • instant messaging
  • mail
  • short messaging
• Search
  • business directory
  • address book
  • directory
• Oracle 9iFS
  • document management
• Calendar
  • calendar

The voice and wireless components of the Oracle Collaboration Suite become fully functional after you configure the mobile services.

4.1.1 Configuring the Mobile Services Using the Content Manager

You use the edit functions of the Content Manager to configure the parameters of the mobile service. Some of the configuration parameters of a mobile service are read-only and therefore cannot be edited. See Section 8.2 for information relating to accessing the Content Manager. For information on editing services, see Section 8.3.2.2.

Figure 4-1 Editing the Configuration Parameters of a Mobile Service

Text description of the illustration mod_emsi.gif

4.1.2 Configuring Asynchronous-enabled Mobile Services

The address book mobile service includes four configuration parameters that pertain to all asynchronous-enabled mobile services:

• Asynchronous Contact Separator
• Asynchronous Query OID
• Asynchronous Max Contacts Results
• Asynchronous Translate Commands

The values set for these parameters affect all asynchronous-enabled services.

4.2 Address Book

The address book enables users to manage their own address books and contacts. It also enables call functions from wireless phones. The mobile address book integrates with the Mail application to allow users to compose a messages' recipient list from their address book.

Configuration Parameters

• Can user use different server settings?

  Determines if the current application settings can be edited by the user.

  • Valid Values: Boolean (true, false)
  • Default Value: false
• Address Book Java Driver class

  The java driver that implements the Oracle Address Book backend.

  • Valid Values:

    oracle.panama.module.pim.addressbook.oracle.UMAddressBook for Oracle Collaboration Suite

    oracle.panama.module.pim.addressbook.oracle.OracleAddressBook for Oracle Calendar Server

    oracle.panama.module.pim.addressbook.exchange.ExchangeAddressBook for Microsoft Exchange Server

    oracle.panama.module.pim.addressbook.omaddressbook.OMAddressBook for preset address book (the data is stored in the database tables in the Oracle9iAS Wireless schema)

  • Default Value: oracle.panama.module.pim.addressbook.oracle.UMAddressBook
• Address Book Server name

  The server name, or IP address, of the Address Book server.

  When connecting to the Oracle Collaboration Suite, enter the name or IP of the Oracle Internet Directory (OID)

  When connecting to the Oracle Calendar Server, enter the connect string to the Oracle Calendar Server database and is of the format:

  <username>:<password>:<hostname or IP>:<port where the database is listening>:<database SID>

  When connecting to the Microsoft Exchange server, enter the name or IP of the Exchange server

  • Default Value: localhost
  • Examples: oidserver.mycomp.com
• Address Book Server Port

  The port number for the Address Book server. For the Collaboration Suite, enter the port number for the OID server.

  • Valid Values: Any integer value
  • Default Value: empty
  • Examples: 4032, 389
• OID Administrator username

  User name for Administrator account on the OID Server. This is required for Oracle UM Address Book standalone configuration.

  • Valid Values: OID Administrator account username
  • Default Value: orcladmin
  • Examples: orcladmin
• OID Administrator Password

  Password for the OID administrator user (required for Oracle UM Address Book standalone configuration).

  • Valid Values: The password for OID administrator user
  • Default Value: Empty
  • Examples: welcome1
• Account Name

  If sharing login authentication information with the Calendar application, then specify the same string value as that used for the Account Name parameter for the Calendar application.

  • Valid Values: Any string
  • Default Value: OraAddressBookCalDomain
  • Examples: mydomain, sharedAccount
• Exchange Data URL

  This should point to the ASP page (AddressBook.asp) that fetches the data from the Exchange Server (required for MS Exchange configuration).

  • Valid Values: A URL pointing to AddressBook.asp on the MS IIS server
  • Default Value: empty
  • Examples:

    http://myiis.mycomp.com/oracle/AddressBook.asp, http://iis-server.abc.com/oracle/AddressBook.asp

• Path to ORACLE_HOME

  The complete system path to the ORACLE_HOME where the Wireless midtier is installed (required for Oracle UM integrated configuration).

  • Valid Values: A fully qualified path to ORACLE_HOME
  • Default Value: empty
  • Examples: /private/home/9ias-mid, C:\9iasmid
• Application Setup OMP URL

  The OMP reference used by the URL group.

  • Valid Values: The OMP URL to the "Application Setup"
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup, omp://oracle/applications/otherappsetup

Asynchronous-Specific Configuration Parameters

• Asynchronous Contact Separator

  The valid contact separators in asynchronous mode. When in asynchronous mode, the end user may query for more than one contact at the same time. To separate the contact names, the user may use such separator types, such as a comma (,), colon (:), or a semi-colon (;). For example: john,doe;Jeremy (three contacts).

  • Valid Values: A list of characters
  • Default Value: *;,
  • Examples: *;,.:
• Asynchronous Query OID

  A query is performed in the end-user's address book when the end-user searches for contacts in asynchronous mode. Setting this parameter to true enables the search to be performed in the Oracle Internet Directory (OID) as well as in the end-user's address book.

  • Valid Values: A boolean value (true, false)
  • Default Value: true
  • Examples: true, false
• Asynchronous Max Contacts Results

  This parameter indicates the maximum number of contacts that will be explicitly returned to the end-user if a contact search returns multiple values. If the query returns more than the value defined in this parameter (for example, 10 contacts returned from a query when only five contacts have been specified), then a message asking for the end-user to narrow the search is returned.

  • Valid Values: An integer value
  • Default Value: 5
  • Examples: 5, 10, 19
• Asynchronous Translate Commands

  Enables (or disables) the translation of asynchronous commands. If true, then the asynchronous commands are translated from the current language of the end-users. Setting this parameter to true enables end-users to send asynchronous commands in their current language. For example, users can enter the show command for the calendar, cal show, in Portugese (cal mostrar) or in French (cal montrer).

  • Valid Values: Boolean value (true, false)
  • Default Value: true
  • Examples: true, false

 

Note: The values set for the parameters Asynchronous Contact Separator, Asynchronous Query OID, Asynchronous Max Contacts Results, and Asynchronous Translate Commands affect all asynchronous-enabled mobile services. These values do not affect the address book mobile service alone, but any asynchronous-enabled mobile service. For the Address Book application to connect to MS Exchange Server, refer to Section 4.15.1.

4.3 Calendar

The calendar enables users to manage their schedule and tasks using mobile access to calendaring servers.

Configuration Parameters

• Can user use different server settings?

  Determines if the current application settings can be edited by the user.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
• Calendar Java Driver class

  The java driver class that implements the Oracle calendar backend.

  • Valid Values:

    oracle.panama.module.pim.calendar.star.StarCalendarService for Oracle Collaboration Server

    oracle.panama.module.pim.calendar.oracle.OracleCalendarService for Oracle Calendar Server

    oracle.panama.module.pim.calendar.exchange.ExchangeCalendarService for Microsoft Exchange Server

    oracle.panama.module.pim.calendar.domino.DominoCalendarService for Lotus Domino Server

  • Default Value: oracle.panama.module.pim.calendar.star.StarCalendarService
• Calendar Server

  Calendar server name and port.

  • Valid Values:

    In Oracle Collaboration Suite mode, enter the name and port of the Oracle Collaboration Suite Calendar server. Separate both these entries with a colon (:). The port is where the "unieng" TCP/IP service is running on the Wireless Calendar Mid-Tier. This can found in /etc/services file.

    In Oracle Calendar mode, this value designates the connect string to the Oracle Calendar Server database in the following format:

    <username>:<password>:<hostname or IP>:<port where the database is listening>:<database SID>

    In Exchange mode, enter the name or IP address of the Exchange server.

    In Lotus Domino mode, enter the name and port of the Lotus Domino server. Separate these names with a colon (:). The port is where the DIIOP and HTTP services are running on the Domino server.

  • Default Value: localhost:5730
  • Examples: cal-server.com:5730, oo_calsched:cal:myhost.mycompany.com:1521:mySID, exchg.mycomp.com, domino.abc.com
• Exchange Data URL

  This should point to the ASP page (Calendar.asp) that fetches the data from the Exchange Server (required for MS Exchange configuration).

  • Valid Values: A URL pointing to Calendar.asp on the MS IIS server
  • Default Value: /pim/Calendar.asp
  • Examples: http://mycomp.com/oracle/Calendar.asp, http://www.abc.com/oracle/Calendar.asp
• Application Setup OMPURL

  The OMP reference to used by the URL group.

  • Valid Values: The OMP URL to the "Application Setup"
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup, omp://oracle/applications/otherappsetup
• Account Name

  If sharing login authentication information with the Address Book application, specify the same string value as that used for the Account Name parameter of the Address Book application

  • Valid Values: Any string
  • Default Value: OraAddressBookCalDomain
  • Examples: mydomain, sharedAccount

 

Note: For the Calendar application to connect to MS Exchange or Lotus Domino Server, refer to Section 4.15.1.

4.4 Directory

The directory application enables users to access Oracle Internet Directory servers from any mobile device. The directory application is integrated with the mobile email application, enabling users to browse their corporate directory and then send an email to a particular contact, or to compose a recipient list from the directory.

Configuration Parameters

• Oracle Internet Directory (OID) Server

  OID Server name or an IP Address. For example, the server name could be ldap.mydomain.com.

  • Valid Values: The server name or IP address
  • Default Value: localhost
  • Examples: myLDAPserver.com, 123.123.1.1
• OID Server Port

  Port number for the OID server. For example, enter 389.

  • Valid Values: An integer value
  • Default Value: 389
  • Examples: 387, 390
• Administrator Login Access to OID

  If set to false, then access to OID is accomplished through a guest account. If true, then both the OID Administrator username and password must be specified.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true, false
• OID Administrator Username

  Username for Administrator account in the OID Server, such as orcladmin.

  • Valid Values: A string (username).
  • Default Value: empty
  • Examples: guest, ldapadmin
• OID Administrator Password

  Password for the OID administrator user. For example: welcome1.

  • Valid Values: A string (password).
  • Default Value: empty
  • Examples: welcome1, admin123
• Maximum Results Returned
  • The maximum results returned to the user regardless of the query result set size.
  • Valid Values: An integer value.
  • Default Value: 200
  • Examples: 100, 200
• Query Names

  The system-assigned name to Internal Queries.

  • Valid Values: A comma-delimited series of query names.
  • Default Value: Q1
  • Examples: Q1, myQuery
• Query Title

  The captions displayed when doing queries.

  • Valid Values: A comma-delimited series of query titles.
  • Default Value: Search
  • Examples: Search by Name, Search by Email
• OID Search Entry Point

  The entry point in OID where the queries start.

  • Valid Values: A string specifying the search entry point. For more information refer to RFC 2251.
  • Default Value: empty
  • Examples: dc=oracle, dc=com
• Search Scope
  • Defines the query search scope. The allowable scopes are BASE for a base object search, ONE for a one-level search, or SUBTREE for a subtree search. The base object used in relation to these search types that is specified as the OID Search Entry Point. For more information, refer to RFC 2251.
  • Valid Values: BASE, ONE, SUBTREE
  • Default Value: SUBTREE
  • Examples: BASE, ONE
• Query Visibility

  For internal use only. This value defaults to true.

  • Valid Values: Boolean value (true, false)
  • Default Value: true
  • Examples: false
• Query Filter Attributes

  Defines the query attributes that are used in the filter expression.

  • Valid Values: A comma-delimited string of attribute names
  • Default Value: givenname,sn,cn,orclmailemail,telephonenumber
  • Examples: givenname, sn, email
• Query Filter Expression

  Defines the query filter expression. Filter expressions should be built based on the specifications in RFC 2254.

  • Valid Values: A string filter expression.
  • Default Value: (&(|(|(|(givenname=*?*)(sn=*?*))(cn=*?*))(|(orclmailemail=*?*)(telephonenumber=*?*)))(objectclass=orcluserv2))
  • Examples: (cn=*?*)
• Query Filter Attribute Display Names

  Future Use Only

  • Valid Values: A comma-delimited string prompts for each of the filters.
  • Default Value: Enter a name for search, Enter a email for search, Enter telephone number
  • Examples: Enter an ID to search, Search
• Query Result List Attributes

  Defines the query attributes on the result list. Refer to Figure 4-2.

  • Valid Values: A comma-delimited string of attributes
  • Default Value:

    givenname,sn,telephonenumber,mail,homephone,facsimiletelephonenumber,mobile,street,l,st,postalcode,description,orclguid

  • Examples: givenname,sn,mail,telephonenumber
• Query Result List Attribute Display Names

  Defines the query attributes display name on the result list. Refer to the labels in Figure 4-2.

  • Valid Values: A comma-delimited string of attribute labels.
  • Default Value: First Name,Last Name,Work Phone,Email,Home Phone,Fax,Mobile,Address,City,State,Zip,Notes,Oracle GUID
  • Examples: First Name,Last Name,Email,Work Phone

 

Figure 4-2 The Details Page. The labels refer to Query List Attribute Display Names and the values are from Query Result List Attributes

Text description of the illustration mod_dtpg.gif

 

• Summary Results Attributes

  The attributes displayed during the summary of returned results. Enter true or false for the attributes in Query Result List Attribute Display Names in the same order. Refer to Figure 4-3.

  • Valid Values: A comma-delimited list of boolean values
  • Default Value: true,true,true,true,false,false,false,false,false,false,false,false,false
  • Examples: true, true, false, true

 

Figure 4-3 The Summary Results Page. The Summary Results Attributes define which values display

Text description of the illustration mod_smrp.gif

 

• Query Attributes Types

  Specifies the applications to which the listed attributes are linked.

   

  Note: display shows only the attribute, but does not link to it; email links to the Mail application. phone, fax and sms link to Short Messaging, with the respective delivery type. hidden does not display the attribute.

  • Valid Values: A comma-delimited string of the following values: display, email, phone, fax, sms and hidden.
  • Default Value: display,display,email,phone,fax,phone,display,display,display, display,display,hidden
  • Examples: display,display,email,phone
• Link Attributes on Result List

  Specifies the attributes that are linked in result query to perform further queries.

  • Valid Values: A comma-delimited list of yes and no values
  • Default Value: no,no,no,no,no,no,no,no,no,no,no,no,no
  • Examples: no, no, no, yes, yes
• Query Link Names

  A caption for the links on the result List. Possible values are LINK1 or nope.

  • Valid Values: A comma-delimited string of link names or nope
  • Default Value: nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope
  • Examples: nope, nope, nope, LINK1, LINK1
• Link Names
  • A system-assigned name to internal Links. Default to LINK1
  • Valid Values: String names. For example: LINK1
  • Default Value: LINK1
  • Examples: MANAGER, LINK2
• Query Link Name

  The query associated with current Link. Default to Q1.

  • Valid Values: String names of queries. For Example: Q1
  • Default Value: Q1
  • Examples: Q2, BYNAME
• Link Refer Attributes

  Specifies a comma-delimited list of result sub-attributes which are used in the linked query. For example, if the result returned is manager=cn=john/sn=doe and the Link Refer Attribute is cn, then the value john is used in the next linked query.

  • Valid Values: A comma-delimited string of attributes
  • Default Value: cn
  • Examples: cn,sn
• Link Bind Attributes

  Specifies comma-delimited list of filter attributes that the Link Refer Attributes are bound to. For example, if the Link Refer Attribute is cn and the Bind attribute is givenname, then the value for cn will be used for givenname.

  • Valid Values: A comma delimited String of attributes
  • Default Value: cn
  • Examples: givenname,sn
• Link Attributes Display Name

  A comma-delimited list of the Query Result List Attributes that are displayed in the link.

  • Valid Values: A comma-delimited string of attribute names
  • Default Value: givenname,sn
  • Examples: givenname, mail
• Max Records Per Page

  The maximum number of results displayed per page.

  • Valid Values: Integer values
  • Default Value: 10
  • Examples: 9, 15
• Merge Results

  If true, this includes all other public attributes in the result of the query. If false, then only the Query Result List Attributes are displayed.

  • Valid Values: Boolean value (true, false)
  • Default Value: false
  • Examples: true
• Application Setup OMP URL

  The OMP reference used by the URL group.

  • Valid Values: An OMP URL
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://mysetup/services/appsetup
• Use Voice LSS

  Whether to use the large scale search for voice.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true

 

4.5 Fax

The fax mobile service enables users to send a fax, check the status of a fax, forward or delete a fax from any wireless device. By combining with the Mail or Online Files services, it also supports faxing documents through mobile devices.

Requirements

This service requires third-party software components; it uses the RightFax Java API to connect to a RightFax server.

 

Table 4-1 Required Software for the Fax application

Name	Instructions	From Version(s)
RightFax Server (available from RightFax)	Install the RightFax server.	7.2
RightFax Integration Mobile Service (available from RightFax)	Install the Integration mobile service on fax server.	7.2
RightFax PFD mobile service (available from RightFax)	Install the PFD mobile service on the fax server.	7.2
RightFax Java API (available from RightFax)	Copy RFJavaInt.zip(Fax server's RightFax/Production/xml/java directory) to $ORACLE_ HOME/wireless/lib on Solaris, to %ORACLE_HOME%\wireless\lib on NT. Include this zip file in the OC4J classpath by adding the following line to %ORACLE_HOME%\j2ee\OC4J_Wireless\config\application.xml. <library path="../../../wireless/lib/RFJava_api.zip"/>	7.2

Sample Cover Page

Since the fax mobile service uses a customized cover sheet file, you should use the sample cover page which is provided with Oracle9iAS Wireless. To use this cover page, you must have Microsoft Word 2000 installed on your RightFax server for 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:

1. Copy the FCS.doc to the directory RightFax\FCS on the machine on which you installed your RightFax server.
2. Specify the cover sheet.
3. Restart Enterprise Fax Manager
4. 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.
5. Highlight Groups under the appropriate server and double-click the group ID Everyone. Click the Basic Information tab. Select the cover sheet file (FCS.doc) in the Cover Sheet Model field.
6. Restart Enterprise Fax Manager

 

Note: See the RightFax Administrator's Guide for detailed instructions on fax cover sheets. You can download the documentation from http://www.rightfax.com.

Configuration Parameters

• Fax server URL

  The fax server HTTP URL. The values for this parameter can an IP Address or a domain name address.

  • Valid Values: A string value
  • Default Value: http://localhost
  • Examples: http://111.11.111.11 or http://host.mydomain.com
• Fax sender account

  The name of the account on the Fax Server for sending faxes.

  • Valid Values: A string value
  • Default Value: Administrator
  • Examples: Administrator

  Faxes kept per user

  The number of recently sent faxes that are kept in the user's Fax History.

  • Valid Values: A non-negative integer
  • Default Value: 20
  • Examples: 20
• Fax Items per page

  The number of faxes sent that are shown per screen in the Fax History.

  • Valid Values: A non-negative integer
  • Default Value: 9
  • Examples: 9
• Debug

  If true, then the log messages are written to the Oracle9iAS Wireless log file.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true
• Query OID

  If true, then it enables the retrieval of a recipient addresses from the Oracle Internet Directory (OID).

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true
• Download directory

  The directory where fax documents are temporarily stored in the Oracle9iAS Wireless server. Specify this directory for sending faxes with attached documents.

  • Valid Values: A path value
  • Default Value: /temp/fax
  • Examples: c:\\temp or /tmp/var
• Cover Page

  A cover page used when sending faxes. Default value is FCS.doc. The cover page document path is relative to the FCS directory on the Fax Server.

  • Valid Values: A file name
  • Default Value: FCS.doc
  • Examples: FCS2.doc, Cover.doc
• Application Setup OMP URL

  The OMP reference used by the URL group.

  • Valid Values: An OMP URL
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup

4.6 Online Files

The Online Files application enables users to both attach and save files in their native formats. The Online Files application is also integrated with RightFax to enable document printing through faxes. Users can remotely select an attachment and send it by email to another mobile user, who can then view the document (Microsoft Office files) and print it to a nearby fax. This application works with any file servers that comply to World Wide Web Distributed Authoring and Versioning (WebDAV).

Configuration Parameters

• Allow Navigation

  Whether the user can navigate to any open service URLs. If true, then users can access any service URL that they want, as long as proper authentication credentials are presented. If false, then users can access only the service URLs which are specific for the parameter, Service URLs.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: false
• Service URLs

  The HTTP URLs to WebDav file systems where users can upload and download files. This parameter applies only if Allow Navigation has been set to false.

  • Valid Values: WEBDAV service URLs
  • Default Value: http://webdav.mycompany.com/files
  • Examples: http://www.mywebdavdomain.com/fileuser
• Download Directory

  Specifies directory used to hold files for download or attachment. The path is local to the server holding the Online Files application.

  • Valid Values: A path value
  • Default Value: /tmp
  • Examples: c:\\temp or /tmp/var
• Proxy Host

  Enter the HTTP Proxy Host. For example, enter proxy.mydomain.com

  • Valid Values: URLs
  • Default Value:
  • Examples: proxy.mydomain.com
• Proxy Port

  Enter the HTTP Proxy Port.

  • Valid Values: A port number
  • Default Value:
  • Examples: 80
• Authorization Realms

  The HTTP Authorization Realms associated with each of the preceding Service URLs. Separate each of the Authorization Realms values with a comma.

  • Valid Values: A string value
  • Default Value: Authorized_Users
  • Examples: Authorized_Users
• Show Service URL?

  This parameter enables the server name to be either hidden or displayed on the Online Files application.

  • Valid Values: yes, no
  • Default Value: no
  • Examples: no
• Application Setup OMP URL

  The OMP reference to the URL group.

  • Valid Values: OMP URLs
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup

4.7 Instant Messaging

The instant messaging application provides presence management, enabling employees to exchange instant messages from their mobile devices. This application is integrated with Jabber Instant Messaging server and the MSN and Yahoo networks.

Required Software

The instant messaging application, which uses the Jabberbeans classes to connect to a Jabber Instant Messaging Server, requires the following third-party software.

 

Table 4-2 Third-Party Software for the Instant Messaging Application

Name	Instructions	Version(s)
Jabber Beans	Copy the latest jabberbeans.jar to $ORACLE_HOME/wireless/lib on Solaris, to %ORACLE_HOME%\wireless\lib on NT.Examples of ORACLE_HOME values: Solaris: ORACLE_HOME=/u01/iaswv20NT: ORACLE_ HOME=d:\oracle\iaswv20	0.9.0-pre4
Jabber Server	Follow the Jabber server's installation guide.	1.4.1
Yahoo Transport Gateway	Optional. Follow the Jabber server's installation guide	0.8.0
MSN Transport Gateway	Optional. Follow the Jabber server's installation guide.	1.1.0

Configuration Parameters

• Jabber Server Name

  Server name where the Jabber Server is running.

  • Valid Values: The server name or IP address
  • Default Value: localhost
  • Examples: myJabber.company.org
• Yahoo! Messaging Transport

  The Yahoo! Instant Messaging transport, if any, configured on the Jabber Server used by the service.

  • Valid Values: A string identifier
  • Default Value: empty
  • Examples: yahoo.myJabber.company.org
• Yahoo Group Name

  The initial group name to assign to Yahoo! buddies which is acquired whenever the Yahoo! transport is configured.

  • Valid Values: A string value
  • Default Value: Yahoo
  • Examples: Yahoo Groups, Y!
• MSN Transport

  The MSN Instant Messaging transport, if any, configured on the Jabber Server used by the service.

  • Valid Values: A string identifier
  • Default Value: empty
  • Examples: msn.myJabber.company.org
• MSN Group

  The initial group name assigned to MSN buddies which are acquired whenever the MSN transport is configured.

  • Valid Values: A string value
  • Default Value: MSN
  • Examples: MSN Friends
• Refresh Time

  The refresh page timeout for some pages accessed by the service. This value is in milliseconds.

  • Valid Values: An integer value
  • Default Value: 20000
  • Examples: 50000
• Log Length

  The maximum number of messages displayed by the service.

  • Valid Values: An integer value
  • Default Value: 10
  • Examples: 5, 15

4.8 Mail

The Mail application enables users to access their email messages from any mobile device.

Configuration Parameters

• Can user use different server settings?

  Whether the a user can edit such settings as those for server and domain.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true, false

 

Note: For the Mail application to include inbox filters, enter the Oracle Internet Directory (OID) server and the port as Mail Server and Mail Server Port instead of the IMAP server and port. Also select esmail as the Mail protocol. For more information on Inbox Filters, see the documentation for Oracle Unified Messaging.

• Mail protocol

  The mail protocol supported by the mail server.

  • Valid Values: imap, pop3, esmail
  • Default Value: esmail
  • Examples: imap, pop3, esmail
• Incoming Mail Server Name

  Incoming email server name. If protocol is esmail, then this should point to the Oracle Internet Directory (OID) server.

  • Valid Values: A string value
  • Default Value: localhost
  • Examples: globalimap.mycomp.com, mailserver.foo.com
• Incoming Mail Server Port

  Incoming email server port. If the protocol is esmail, then this should point to the OID server.

  • Valid Values: An integer value
  • Default Value: 4032
  • Examples:143, 110, 4032. Usually, this value is 143 for imap, 110 for pop3 and 4032 for esmail.

 

• Outgoing Mail Server (SMTP)

  Outgoing Mail Server (SMTP) name or IP address.

  • Valid Values: A string value
  • Default Value: localhost
  • Examples: gsmtp.mycomp.com, 127.0.0.1
• Outgoing Mail Server (SMTP) Port

  Port number for the Outgoing Mail Server (SMTP).

  • Valid Values: A string value
  • Default Value: 25
  • Examples: 25
• OID Administrator username.

  The Username for the Administrator account in the OID Server. This parameter is only needed when the Mail application is being configured to connect to Oracle Internet Directory (OID) to retrieve Inbox Filters.

  • Valid Values: valid administrator account on the OID server
  • Default Value: orcladmin
  • Examples: orcladmin, administrator
• OID Administrator Password.

  The password for the OID administrator user. This parameter is only needed when the Mail application is being configured to connect to Oracle Internet Directory (OID) to retrieve Inbox Filters.

  • Valid Values: The password for the OID admin user
  • Default Value: empty value
  • Examples: welcome1, password
• Mail JDBC Driver Type

  Specify the Mail JDBC driver type to connect to the OID server. This parameter is only needed when the Mail application is being configured to connect to Oracle Internet Directory (OID) to retrieve Inbox Filters.

  • Valid Values: thin, oci
  • Default Value: thin
• Outgoing Mail Server (SMTP) Login

  When required, it specifies username for the outgoing server.

  • Valid Values: A string value
  • Default Value: empty
  • Examples: global.user, robert.smith
• Auto domain for email addresses

  Enter the domain that is used for the recipient when no domain is present in the recipient's email address. This parameter can construct the sender's identity if it is not specified by the user.

  • Valid Values: A string value
  • Default Value: localhost
  • Examples: mycomp.com, xyz.com
• Inbox name

  The primary folder for the user; usually it is INBOX.

  • Valid Values: Any valid folder name on the mail server.
  • Default Value: INBOX
  • Examples: INBOX
• Sent folder name

  The name of the folder where the sent messages are saved.

  • Valid Values: Any valid folder name on the mail server
  • Default Value: Sent
  • Examples: SentItems, Sent
• Max Messages Fetched

  Enter the maximum number of the messages that will be fetched, per request, from the server.

  • Valid Values: Any integer value
  • Default Value: 200
  • Examples: 9, 200
• Timeout

  The timeout connection limit to the Mail server. It is specified in milliseconds.

  • Valid Values: Any integer value
  • Default Value: 2000
  • Examples: 2000, 5000
• Email Configuration Java Driver Class

  A Java driver class used to load the email configuration. This parameter is provided only for backward compatibility.

  • Valid Values: A valid class name
  • Default Value: oracle.panama.module.pim.mail.util.Config
  • Examples: oracle.panama.module.pim.mail.util.Config
• Temporary directory
  • Enter the temporary directory where the attachments are downloaded.
  • Valid Values: Any valid folder on the Oracle9iAS Wireless mid-tier server.
  • Default Value: /tmp
  • Examples: /tmp, C:\Temp
• Audio Temporary directory

  Must be specified if allowing voice access and if replying to email as voice attachment. This directory needs to be accessible through the Web. It specifies the temporary directory where voice files are stored in the server holding the Email application. For convenience, specify the fully qualified path to the "audiotemp" directory on the Oracle9iAS Wireless mid-tier server.

  • Valid Values:

    $ORACLE_HOME/OC4J_Wireless/j2ee/applications/modules/modules-web/pim/mail/audiotemp. Replace

    $ORACLE_HOME with the actual value. Or any web-reachable folder.

  • Default Value: /modules/modules-web/pim/mail/audiotemp
  • Examples:

    /home/private/9iasmid/OC4J_Wireless/j2ee/applications/modules/modules-web/pim/mail/audiotemp

    C:\9iasmid\OC4J_Wireless\j2ee\applications\modules\modules-web\pim\mail\audiotemp

• Audio temporary directory URL

  This value is mandatory for voice access and for replying to an email as a voice attachment. It specifies the HTTP URL that retrieves audio files sent in the email and points to the Audio Temporary directory defined in Section 4.8. If the default for the Audio Temporary directory has not changed, then the value for this parameter does not have to change; otherwise specify the URL for the folder defined earlier.

  • Valid Values: A URL pointing to the "Audio Temporary directory".
  • Default Value: /modules/pim/mail/audiotemp
  • Examples: /modules/pim/mail/audiotemp
• Encoding

  Enter the encoding to be used while sending an email. Use IANA character set names. The list of names is published at:

  "http://www.iana.org/assignments/character-sets"

  If the value for this parameter is left blank (that is, no value has been entered), then the system's default encoding is used for outgoing messages. The user can override this setting in the Mail Application under Setup.

  • Valid Values: valid encoding
  • Default Value: UTF-8
  • Examples: UTF-8, ISO-8859-1
• Deleted messages folder name

  The name of the folder where the deleted messages need to be saved.

  • Valid Values: Any valid folder on the mail server
  • Default Value: empty
  • Examples: DeletedItems, Wastebasket
• Save the contents of the audio reply?

  Whether or not the contents of the audio reply should be saved in the Sent Folder.

  • Valid Values: A boolean value (true, false)
  • Default Value: true
• Application Setup OMP url

  The OMP URL of the Application Setup Modulable Application.

  • Valid Values: The OMP URL for the "Application Setup"
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup, omp://oracle/applications/myappsetup

4.9 Short Messaging

The short messaging application enables users to send messages through such mediums as voice, email, fax or SMS messaging. To send a short message, a user sends the service four parameters: the type of message to be sent (email, SMS, Voice, or Fax), the destination address of the message, the subject text, and the body text of the message. The subject and body text are translated into the medium appropriate to the message type and then sent to the destination. This service does not require any third-party software components. It relies on Oracle9iAS Wireless transports to be configured. The short messaging application does not require scripts.

Configuration Parameters

• Message Sender

  Specifies the identity used for anonymous users when they send short messages. This field is ignored for non-anonymous users.

  • Valid Values:
  • Default Value: [e-mail]
  • Examples: 'Anonymous User', '1(100)111-1111', '[e-mail]'
• Display All Delivery Types

  Specifies whether all the delivery types (Email, Fax, SMS and Voice) will be displayed regardless of whether or not they are configured. If set to false, then only configured delivery types will be shown to the user.

  • Valid Values: A boolean value (true, false)
  • Default Value: false
  • Examples: true
• Application Setup OMP URL

  The OMP reference for the URL group.

  • Valid Values: An OMP URL.
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://myCompany/services/appsetup

4.10 Business Directory

The business directory application provides users with a complete business directory. This application is built on the Wireless Location Application Component API.

This application provides a "yellow pages" type interface to locate the addresses and phone numbers of registered businesses in a given radius. It has search capabilities for business names or categories. Browsing through categories is also enabled. If no location parameters are passed to this application, then the location application is invoked to obtain location data for the search. This application requires the Wireless business directory provider.

 

Table 4-3 Requirements for the Business Directory Application

Name	External Provider(s)	From
Business Directory Provider	otn.oracle.com	2.0

Configuration Parameters

• Web URL

  Reserved for Future Use

  • Valid Values: A valid URL
  • Default Value: localhost
  • Examples: localhost
• Records per page

  Specifies the number of business categories and result items shown per WML card. This parameter applies to WML devices only.

  • Valid Values: non-negative integer
  • Default Value: 9
  • Examples: 9
• Application Setup OMP URL

  The OMP reference to the URL group.

  • Valid Values: An OMP URL
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup

4.11 Driving Directions

The driving directions application allows a mobile application to provide users with driving directions between an originating address and a destination address. It links to the Location Picker application to enable users to select originating and destination addresses not provided by Driving Directions. The Driving Directions application also links with the Maps application for enhanced routing.

This application is built upon the Wireless Location Application Component API.

 

Table 4-4 Requirements for the Location Picker Application

Name	External Provider(s)	From
Routing Provider	otn.oracle.com	2.0

Configuration Parameters

• Web URL

  Reserved for Future Use

  • Valid Values: A valid URL
  • Default Value: localhost
  • Examples: localhost
• Records per page
  • Specifies the number of business categories and result items shown per WML card. This parameter applies to WML devices only.
  • Valid Values: A non-negative integer
  • Default Value: 9
  • Examples: 9
• Path for voice files

  Reserved for Future Use

  • Valid Values:
  • Default Value:
  • Examples:
• Application Setup OMP URL

  The OMP reference used by the URL group.

  • Valid Values: Omp URLs
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup

4.12 Location Picker

The Location Picker application enables users to pick and manage their frequently accessed locations. Using this application, a user can specify a location that can be used by another application, such as the driving directions application. This location can be the user's default location, the current location (if mobile positioning is enabled), a Locationmark selected by the user, a recent location used by the user, or a new location to be entered by the user.

The Location Picker application is used by other applications to acquire a location from the user. When used directly by the user, Location Picker provides management of the user's locationmarks and allows the user to set his "preferred" location, which is either the user's current location (when mobile positioning is available and on) or the user's default locationmarks.

Other location applications include Driving Directions, Maps, and Business Directory. These applications use the Location Picker to acquire location(s) from the user if the user does not have a "preferred" location or if the user specifically wants to change the location used for those applications.

This application integrates with positioning servers when available and is built upon the Oracle9iAS Wireless Location Application Component API

This service requires the Wireless geocoding provider only when the geocoding of addresses is needed and the Wireless mobile positioning provider only when the positioning feature is needed. The geocoding and mobile positioning are optional features.

 

Table 4-5 Requirements for the Location Picker Application

Name	External Provider(s)	From
Geocoding Provider	otn.oracle.com	2.0
Mobile positioning provider	otn.oracle.com	2.0

Configuration Parameters

• Web URL

  Reserved for Future Use

  • Valid Values: A valid URL
  • Default Value: localhost
  • Examples: localhost
• History stack size

  Specifies the maximum number of locations kept in the user's location history.

  • Valid Values: A non-negative integer
  • Default Value: 72
  • Examples: 72
• Records per page

  Specifies the number of business categories and result items shown per WML card. This parameter applies to WML devices only.

  • Valid Values: A non-negative integer
  • Default Value: 9
  • Examples: 9

4.13 Maps

The maps application provides broad and detailed maps for a given location, supports map tiling and image map transformation for different devices. This application integrates with the Driving Directions application and is built upon the Wireless Location Application Component API.

Configuration Parameters

• Application Setup OMP URL

  The OMP reference to the URL group.

  • Valid Values: An OMP URL
  • Default Value: omp://oracle/applications/appsetup
  • Examples: omp://oracle/applications/appsetup

4.14 Applications Setup

Applications Setup defines how one application calls another. All of the Wireless and Voice applications can be uniquely identified by an attribute called the OMP URL. Each application uses an OMP URL to call a different application. Application Setup acts as a repository where each of the OMP URLs are registered. In turn, each application has a configuration parameter which tells the application where to find Applications Setup.

4.14.1 Registered URLs

The Application Setup includes the following OMP URLs.

• Address Book OMP URL

  Defines the address book OMP URL.

  • Valid Values: the OMP URL of the address book application
  • Default Value: omp://oracle/services/pim/addressbook
• Calendar OMP URL

  Defines the calendar OMP URL.

  • Valid Values: the OMP URL of the calendar application
  • Default Value: omp://oracle/services/pim/calendar
• Contact Rules OMP URL

  Defines the contact rules OMP URL.

  • Valid Values: the OMP URL of the contact rules application.
  • Default Value: omp://oracle/services/presence/switcher
• Directions OMP URL

  Defines the direction OMP URL

  • Valid Values: the OMP URL of the driving directions application
  • Default Value: omp://oracle/services/location/directions
• Directory OMP URL

  Defines the directory OMP URL.

  • Valid Values: the OMP URL of the directory application
  • Default Value: omp://oracle/services/pim/directory
• FormFiller OMP URL

  Defines the formfiller OMP URL.

  • Valid Values: the OMP URL of the formfiller application
  • Default Value: omp://oracle/services/commerce/formfiller
• Email OMP URL

  Defines the email OMP URL.

  • Valid Values: the OMP URL of the mail application
  • Default Value: omp://oracle/services/pim/mail
• Voice Main Menu OMP URL

  Defines the voice main menu OMP URL.

  • Valid Values: the OMP URL of the mainmenu application
  • Default Value: omp://oracle/services/voice/mainmenu
• Fax OMP URL

  Defines the fax OMP URL.

  • Valid Values: the OMP URL of the fax application
  • Default Value: omp://oracle/services/pim/fax
• Oracle 9iFS OMP URL
  • Defines Oracle 9iFS OMP URL.
  • Valid Values: the OMP URL of the Online Files (Oracle 9iFS) application
  • Default Value: omp://oracle/services/pim/ifs
• Instant Messaging OMP URL

  Defines the instant messaging OMP URL.

  • Valid Values: the OMP URL of the instant messaging application
  • Default Value: omp://oracle/services/pim/im
• Payment OMP URL

  Defines the Payment OMP URL.

  • Valid Values: the OMP URL of the payment application
  • Default Value: omp://oracle/services/commerce/payment
• Location Picker OMP URL

  Defines location picker OMP URL.

  • Valid Values: the OMP URL of the location picker application
  • Default Value: omp://oracle/services/location/picker
• Short Messaging OMP URL

  Defines the short messaging OMP URL.

  • Valid Values: the OMP URL of the short messaging application
  • Default Value: omp://oracle/services/pim/sm
• Tasks OMP URL

  Defines the tasks OMP URL.

  • Valid Values: the OMP URL of the tasks application
  • Default Value: omp://oracle/services/pim/tasks
• Translator OMP URL

  Defines the translator OMP URL.

  • Valid Values: the OMP URL of the translator application
  • Default Value: omp://oracle/services/commerce/translator
• Viewer OMP URL

  Defines the viewer OMP URL.

  • Valid Values: the OMP URL of the viewer application
  • Default Value: omp://oracle/services/pim/viewer
• Voice Mail OMP URL

  Defines the voice mail OMP URL

  • Valid Values: the OMP URL of the voice mail application
  • Default Value: omp://oracle/services/voice/mail
• Wallet OMP URL

  Defines the wallet OMP URL.

  • Valid Values: the OMP URL of the wallet application
  • Default Value: omp://oracle/services/commerce/wallet

4.15 Configuring the Oracle9iAS Wireless PIM Applications to Connect to Microsoft Exchange and Lotus Domino Server

The Address Book, Calendar and Tasks applications can connect to non-Oracle collaboration servers, such as the Microsoft Exchange and Lotus Domino server.

For Wireless and Voice Applications to properly run against these servers, some additional setup is required beyond configuring the application-specific parameters.

 

Note: The Mail application does not require additional software.

4.15.1 Configuring the Microsoft Exchange Server for Oracle9iAS Wireless PIM Applications

Configuring the Microsoft Exchange Server for Voice and Wireless PIM applications requires the following software:

Table 4-6 Required Software

Name	Instructions	From Version
Microsoft Exchange	Install the Microsoft Exchange Server.	5.5
MS IIS	Install the Microsoft Internet Information Server.	4.0
MS CDO Collaborative Data Objects	Available with the Microsoft Exchange SDK. The cdo.dll library must be installed on the IIS Server.	1.2.1

4.15.2 Configuring the 9ias Wireless PIM ASPs

To create the ASPs for the PIM Voice and Wireless applications:

1. Create a directory named oracle on the IIS server. For example, create C:\inetpub\oracle.
2. Copy the following files from Oracle9iAS Wireless mid-tier server to the oracle folder:

   $ORACLE_HOME/j2ee/OC4J_Wireless/applications/modules/modules-web/pim/addressbook/asp/*

   $ORACLE_HOME/j2ee/OC4J_Wireless/applications/modules/modules-web/pim/ calendar /asp/*

   $ORACLE_HOME/j2ee/OC4J_Wireless/applications/modules/modules-web/pim/tasks/asp/*

3. Start the IIS manager and then right-click the default Web site.
4. Add a new virtual directory.
5. Name this virtual directory oracle.
6. Using the Properties dialog box for this folder, grant Execute Permissions for Scripts and Executables.
7. Select Directory Security, and then click Edit in the Anonymous Access pane.
8. Set the following values:
   • Anonymous Access: unchecked
   • Basic authentication: checked
   • Integrated Windows authentication: checked

4.15.3 Configuring the Lotus Domino for Oracle9iAS Wireless PIM Applications

Configuring Lotus Domino for the Voice and Wireless applications requires the following software:

 

Table 4-7 Required Software for Configuring Lotus Domino for PIM Applications

Name	Instructions	From Version
Lotus Domino Server	Install the Lotus Domino Server	5.5
Lotus Java SDK	Install Lotus Java SDK	5.0.5

Installing the Lotus Domino Toolkit creates a DTJava directory on the file system.

To configure Lotus Domino:

1. Copy the DTJava/lib/NCSO.jar to $ORACLE_HOME/wireless/lib on Solaris, to %ORACLE_HOME%\wireless\lib on NT. Examples of Solaris and NT values for ORACLE_HOME are as follows:
   • For Solaris: ORACLE_HOME=/u01/iaswv904
   • For Windows NT: ORACLE_HOME=d:\oracle\iaswv904
2. Include this JAR file in the OC4J classpath by adding the following line to $ORACLE_HOME/j2ee/OC4J_Wireless/config/application.xml:

   <library path="../../../wireless/lib/NCSO.jar"/>

Ensure that you download Lotus Domino Toolkit for Java/CORBA Release 5.0.8 Update or Lotus Domino Toolkit for Java/CORBA Release 5.0.5 Update Shipping.

 

Note: Do not use version 2.x toolkit.

On the Domino server, the server tasks HTTP and DIIOP must be running. Ensure that the Domino server notes.ini file contains the following line:

ServerTasks=<other tasks>,http,diiop 5.0.5