4
Configuring Mobile Services for 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 in order 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 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
• iFS
  • 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 Async-Enabled Mobile Services

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

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

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

4.2 Address Book

The address book enables users to manage their own address books and contacts as well as enabling call functions from wireless phones. The mobile address book integrates with the email mobile service to allow users to compose a messages' recipient list from their address book.

Once you find a contact, you can also edit the contact information or delete a contact. While deleting, nothing is returned to the caller.

4.2.1 Configuration Parameters

The mobile address book includes the following parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Oracle Internet Directory (OID) Server

  The server name where Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The Personal Address Book is stored on this server.

  • Valid values: any server name.
  • Default Value: localhost
  • Examples: adr-server-pc.company.com,localhost
• Oracle Internet Directory (OID) Server Port

  The server port where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The Personal Address Book is stored on this server.

  • Valid Values: init value
  • Default Value: empty
  • Examples: 389, 4032
• Oracle Internet Directory (OID) Username

  The administrator user name and account in the OID server.

  • Valid Values: string value
  • Default Value: orcladmin
  • Examples: administrator, addrbookadmin
• Oracle Internet Directory (OID) Administrator Password

  The password for the administrator account in the OID server.

  • Valid Values: string value
  • Default Value: empty
  • Examples: welcome1, password123
• Account Name

  The domain attached to the user account information. This is a free form field. If the Oracle9iAS Wireless instance supports multiple address book servers, then these address books must not have the same domain. Different PIM services with the same domain share the user account information.

  • Valid Values: String with domain name
  • Default Value: OraAddressBookDomain
  • Examples: MyDomain, ExchangeDomain
• Address Book Java Driver Class

  The driver class implementing the backend. Administrators cannot edit this parameter.

  • Default Value: oracle.panama.module.pim.addressbook.oracle.UMAddressBook
• Can user use different server settings?

  Should the end user be able to edit the server configuration?

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

4.2.1.1 Async-Specific Configuration Parameters

• Async Contact Separator

  The valid contact separators in Async mode. When in Async 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: list of chars
  • Default Value: *;,
  • Examples: *;,.:
• Async Query OID

  A query is performed in the end-user's address book when the end-user searches for contacts in Async 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: Boolean value
  • Default Value: true
  • Examples: true, false
• Async 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: int value
  • Default Value: 5
  • Examples: 5, 10, 19
• Async Translate Commands

  Enables (or disables) the translation of Async commands. If true, then the Async commands are translated from the current language of the end-users. Setting this parameter to true enables end-users to send Async 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
  • Default Value: true
  • Examples: true, false

    Note: The values set for the parameters Async Contact Separator, Async Query OID, Async Max Contacts Results, and Async Translate Commands affect all Async-enabled mobile services. These values do not affect the address book mobile service alone, but any Async-enabled mobile service.

4.3 Calendar

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

4.3.1 Configuration Parameters

The Calendar mobile service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Calendar server

  The host name and port of the Calendar server. This should point to the server when Oracle Calendar was installed during the Oracle Collaboration Suite setup.

  • Valid Values: any server
  • Default Value: localhost
  • Examples: localhost:5730, cal-server-pc.company.com:8057
• Account Name

  The account name for this service. Address book and calendar services with the same account name share the login information. The domain is attached to the user account information. This is a free-form field. If the Wireless instance supports multiple calendar servers, then these must not have the same domain. Different PIM services with the same domain share the user account information.

  • Valid Values: String with domain name
  • Default Value: OraCalDomain
  • Examples: MyDomain
• Calendar Java Driver class

  The Oracle calendar backend. Administrators cannot edit this parameter.

  • Default Value: oracle.panama.module.pim.calendar.star.StarCalendar Service
• Can user use different server settings?

  Should the end user be able to edit the server configuration?

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

4.4 Directory

The directory mobile service enables users to access Oracle Internet Directory servers from any mobile device. The directory mobile service is integrated with the mobile email mobile service, 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.

4.4.1 Configuration Parameters

All of the required .jar files are included with Wireless. The Mobile directory includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  Default Value: POST

• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Oracle Internet Directory (OID) Server

  The server name where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The Corporate Directory is stored on this server.

  • Valid Values: server name
  • Default Value: localhost
  • Examples: localhost, myserver.company.com
• Oracle Internet Directory (OID) Server Port

  The server port where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The Corporate Directory is stored here.

  • Valid Values: int value
  • Default Value: 389
  • Examples: 389,123
• Administrator Login Access to OID

  If false, then access to OID is through a guest account. If true, then both the OID administrator user name and password must be specified.

  • Valid Values: Boolean value
  • Default Value: false
  • Examples: true, false
• Oracle Internet Directory (OID) Administrator Username

  The user name for the administrator account in the OID server.

  • Valid Value: A string with a user name
  • Default Value: empty
  • Examples: guest, ldapadmin
• Oracle Internet Directory (OID) Password

  The password for the administrator account in the OID server.

  • Valid Value: string with 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: int value
  • Default Value: 200
  • Examples: 100, 200

    Note: The following values are predefined to perform a query in the corporate directory by name, email, and phone number. Administrators should not change these values.

• Query Names

  The system-assigned names to the internal queries.

  • Valid Value: string value
  • Default Value: Q1
  • Examples: Q1, Q2
• Query Title

  The caption that displays when queries are performed.

  • Valid Values: string value.
  • Default Value: Search
  • Examples: Search by Name, Search by Email
• Oracle Internet Directory (OID) Entry Point

  The entry point in OID where queries start.

  • Valid Values: string value
  • Default Value: empty
• 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.

  • Valid Values: string value
  • Default Value: SUBTREE
  • Examples: BASE, ONE, SUBTREE
• Query Visibility

  Defines if the query will be visible. Administrators cannot edit this parameter. Internal use only.

  • Valid Value: boolean value
  • Default Value: true
  • Examples: true, false
• Query Filter Attributes

  Defines the query attributes that will be used in the filter. Future use only.

  • Valid Value: string value.
  • Default Value: givenname,sn,orclmailemail,telephonenumber
• Query Filter Expression

  Defines the query filter expression.

  • Valid Values: string value
  • DefaultValue: (&(|(|(givenname=*?*)(sn=*?*))(|(orclmailemail=*?*)(telephonenumber=*?*)))(objectclass=orcluserv2))
• Query Filter Attribute Display Names

  Defines the query filter expression. This parameter is reserved for future use only.

  • Valid Values: string value
  • Default Value: Enter a name for search, Enter a email for search, Enter telephone number
• Query Result List Attributes

  Defines the query attributes that will be on the result list.

  • Valid Value: string value
  • Default Value: givenname,sn,mail,telephonenumber,homephone,facsimile,telephonenumber,mobile,street,l,st,postalcode,description,orclguid
• Query Result List Attribute Display Names

  Defines the query attributes display name that will be on the result list.

  • Valid Value: string value
  • Default Value: First Name,Last Name,Email,Work Phone,Home Phone,Fax,Mobile,Address,City,State,Zip,Notes,Oracle GUID
• Summary Results Attributes

  Attributes shown during the summary of returned results. Enter true or false for the attributes in "Query Result List Attribute Display Names" in the same order.

  • Valid Values: string value
  • Default Value: true,true,true,true,false,false,false,false,false,false,false,false,false
• Query Attributes Types

  Specifies the applications to which the listed attributes will be linked.

  • Valid Values: display, email, phone, fax, sms and hidden. display shows only the attribute, but does not link it. email links to the Email application. phone, fax and sms link to Short Messaging, with the respective delivery type. hidden does not display the attribute.
  • Default value: display,display,email,phone,phone,fax,phone,display,display,display,display,display,hidden
• Link Attributes on Result List

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

  • Valid Values: string value
  • Default Value: no,no,no,no,no,no,no,no,no,no,no,no,no
• Query Link Names

  The caption for the links on the result list.

  • Valid Values: LINK1 or nope
  • Default Value: nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope,nope
• Link Names

  System-assigned name to the internal links.

  • Valid Value: string value
  • Default Value: LINK1
• Query Link Name

  The query associated with the current link. Default to Q1.

  • Valid Values: string value
  • Default Value: Q1
• Link Refer Attribute

  Specifies a comma-separated list of result sub-attributes to be 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 will be used in the next linked query.

  • Valid Values: string value
  • Default Value: cn
• Link Bind Attribute

  Specifies a comma-separated 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 value: string value
  • Default value: cn
• Link Attributes Display Name

  A comma-separated list of the Query Result List Attributes to be displayed in the Link.

  • Valid Values: string value
  • Default Value: givenname, sn
• Max Records Per Page

  The maximum number of results shown per display page.

  • Valid Value: int value
  • Default Value: 10
  • Examples: 10, 9
• Merge Results?

  If true, then all other public attributes are included in the query results. If false, then only the Query Result List attributes display.

  • Valid Value: boolean value
  • Default Value: false
  • Examples: true, false

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 email or iFS 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 Mobile Service

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 RFJava_api.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 classpath.	7.2

Sample Cover Page

Since the fax mobile service uses customized cover sheet file, it is highly recommended that you use the provided sample cover page.

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/iaswv20/wireless/j2ee/applications/modules/modules-web/images/pim/fax/FCS.doc

On Windows NT installations, this cover page is located at:

%ORACLE_HOME%\iaswv20\wireless\j2ee\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 in which you installed your RightFax server.
2. Specify which cover sheet to use.
   • Run 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.
   • 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.

     Note: See the RightFax Administrator's Guide for detailed instructions on fax cover sheets.

4.5.1 Configuration Parameters

The fax mobile service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Fax server URL

  The URL of the fax server on the RightFax server. This HTTP server listens for fax requests. The Fax mobile service performs fax transactions through this server.

  • Valid Values: string value
  • Default Value: http://localhost
  • Example: http://144.25.172.183
• Fax sender account

  The RightFax user name associated with the fax transactions.

  • Valid values: string value
  • Default Value: Administrator
• Faxes kept per user

  The maximum number of fax history records kept in database for each user.

  • Valid values: a non-negative integer.
  • Default Value: 9
• Fax Items per WML page

  This parameter, which applies only the WML, specifies the number of faxes that display per screen in the Fax History.

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

  Whether to keep log information in the system log file.

  • Valid Values: Boolean value
  • Default Value: true
  • Examples: True, false
• Query OID (Oracle Internet Directory)

  Whether to enable the directory mobile service when searching for a recipient. Set to true only if the directory has fax number information.

  • Valid values: Boolean value
  • Default Value: false
  • Examples: False, True
• Download directory

  The directory on the server holding the fax application where fax documents are temporarily stored. Specify this location if documents are to be attached when faxing.

  • Valid values: path value
  • Default Value: /temp/fax
  • Examples: /tmp, /temp/fax, C:/temp
• Cover Page

  Cover page to use when sending faxes. The cover page file should be on the fax server's RightFax\FCS directory.

  • Valid values: file name.
  • Default Value: FCS.doc
  • Examples: FCS.doc

Implementing Dialing Rules

Dialing rules allow you to specify rules to control outbound faxing. For example, you can specify that a "9" is automatically added to all outbound faxes if dialing "9" is necessary to get an outside line.

To add, edit, or delete dialing rules:

Run Enterprise Fax manager on the fax server and click Dialing Rules.

• To add a new dialing rule: click Insert or select New from the Edit menu.
• To delete a dialing rule: click Delete or select Delete from the Edit menu.
• To edit a dialing rule: double click an existing dialing rule.

When creating a dialing rule, you specify the fax number (or, using wildcards, the number pattern) and then attach rules to faxes whose destination fax number matches the pattern. In case multiple dialing rules are matched, the fax server selects the rule with the greatest weight.

Dialing Rule Properties:

Pattern: This is the destination fax number or number pattern that the dialing rule will apply to. RightFax ignores any hyphens, parentheses, or spaces entered in the pattern string.

Number Adjustments Tab: the Prepend this and Append this options enable you to both add or remove digits from the beginning or end of the destination fax number. For example, If you want to automatically add a "1" to long distance calls and add a "9" to get an outside line. The dialing rules can be:

Rule 1: Matching=???-???-???? , Prepend this=91

Rule 2: Matching=+ , Prepend this=9

Under these rules, 123-4567 will be changed to 9123-4567, 650-123-4567 will be changed to 91650-123-4567, and1650-123-4567 will be changed to 91650-123-4567.

4.6 Online Files

The online files mobile service enables users to both attach and save files in their native formats. The online files mobile service 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 mobile service works with any file servers that comply to World Wide Web Distributed Authoring and Versioning (WebDAV).

Required Software

This online files mobile service requires the Java development kit for Oracle Internet File System.

4.6.1 Configuration Parameters

The online files mobile service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Service URLs

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

  • Valid values: URL values
  • Default Value: http://files.oraclecorp.com/content, http://webdav.mycompany.com/files
  • Examples: http://www.sharemation.com
• Download Directory

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

  • Valid values: path value
  • Default Value: /temp/ifs
  • Examples: /tmp/ifs, C:/temp
• Allow Navigation

  Whether the user is allowed to navigate to any WebDAV service URLs. If true, then the user can enter any URL when setting up the service.

  • Valid values: Boolean value
  • Default Value: True
  • Examples: True, False
• Proxy Host

  The HTTP proxy host. This parameter is used only if the Oracle Collaboration Suite server has been installed behind a firewall.

  • Valid values: server name
  • Default Value: (empty)
  • Examples: proxy.company.com
• Proxy Port

  The HTTP proxy port. This parameter is used only if the Oracle Collaboration Suite server has been installed behind a firewall.

  • Valid values: int value
  • Default Value: (empty)
  • Examples: 80, 8000
• Authorization Realms

  The HTTP authorization realms associated with each of the preceding service URLs. Separate multiple realms with a comma (,).

  • Valid values: string value
  • Default Value: Authorized_Users
  • Examples: http://www.sharemation.com

4.7 Instant Messaging

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

Required Software

The instant messaging mobile service, 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 Mobile Service

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

This mobile service does not require scripts.

4.7.1 Configuration Parameters

The instant messaging mobile service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Jabber Server Name

  The host name of the machine on which the Jabber Server is configured (for example, jabber.org).

  • Valid values: server name value
  • Default Value: localhost
  • Examples: localhost
• Yahoo! Messaging Transport

  The Yahoo! Instant Messaging transport, if any, configured on the Jabber Server used by the service (for example, yahoo.jabber.org).

  • Valid values: url value
  • Default Value: (empty)
  • Examples: yahoo.jabber.org
• Yahoo Group Name

  The initial group name to assign to users acquired through the Yahoo! transport, if any.

  • Valid Values: string value
  • Default value: Yahoo
  • Examples: Yahoo
• MSN Transport

  The MSN Instant Messaging transport, if any, configured on the Jabber Server used by the service. (for example, msn.jabber.org)

  • Valid Values: URL value
  • Default Value: (empty)
  • Examples: msn.jabber.org
• MSN Group

  The initial group name to assign to users acquired through the MSN transport, if any

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

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

  • Valid Values: int value
  • Default Value: 20000
  • Examples: 2000
• Log Length

  The maximum number of messages the service will display between you and another user.

  • Valid Values: int value
  • Default Value: 10

4.8 Mail

The mail mobile service enables users to access their email messages from any mobile device.

4.8.1 Configuration Parameters

The mail mobile service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Mail protocol

  The mail protocol to which the mail server is configured. For Oracle Unified Messaging (UM), the default protocol is IMAP. Administrators cannot edit this parameter.

  • Valid Values: mail protocol
  • Default value: IMAP
  • Examples: IMAP, POP3·

Note: To have Inbox Filters for the email application, the Oracle Internet Directory (OID) server and the port should be configured as Mail Server and Mail Server Port instead of the IMAP server and port. For more information, see the documentation for Oracle Unified Messaging.

• Oracle Internet Directory (OID) Server

  The server name where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The filtered user emails are retrieved from this server.

  • Valid Values: String value
  • Default value: localhost
  • Examples: localhost, 127.0.0.1
• Oracle Internet Directory (OID) Server Port

  The server port where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The filtered user emails are retrieved from here.

  • Valid Values: int value
  • Default value: 143
  • Examples: 4032, 3060
• Oracle Internet Directory (OID) Administrator Username

  The username for the administrator account on the OID server.

  • Valid Values: string value
  • Default Value: orcladmin
  • Examples: orcladmin, ldapadmin
• Oracle Internet Directory (OID) Administrator Password

  The password for the administrator user on the OID server.

  • Valid Values: string value
  • Default value: (empty)
  • Examples: welcome1
• Mail JDBC Driver Type

  The mail JDBC driver type specifies how the mail application will connect to the Oracle Internet Directory (OID) server in order to get the Inbox Filters information.

  • Valid Values: string value
  • Default Value: thin

Examples: thin, oci

• SMTP Server

  The host name of the SMTP Server. This should point to the server where SMTP was installed during the Oracle Collaboration Suite setup.

  • Valid Values: String value
  • Default Value: localhost
  • Examples: localhost, 127.0.0.1
• SMTP Server Port

  The port of the SMTP Server. This should point to the server where SMTP was installed during the Oracle Collaboration Suite setup.

  • Valid Values: int value
  • Default Value: 25
  • Examples: 25
• Auto domain for email addresses

  The domain used for recipients when no domain is present in their email address. It is also used to construct the sender's identity if it is not specified by the user.

  • Valid Values: string value
  • Default Value: localhost
  • Examples: localhost, @company.com
• Inbox name

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

  • Valid Values: string value
  • Default Value: INBOX
  • Examples: INBOX
• Sent folder name

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

  • Valid Values: string value
  • Default Value: Sent
  • Examples: Sent
• Max messages fetched

  The maximum number of messages that will be fetched from the server at each request.

  • Valid Values: int value
  • Default Value: 200
  • Examples: 200, 100
• Timeout

  The timeout limit (in milliseconds) to wait for a response from the mail server.

  • Valid Values: int value
  • Default Value: 2000
  • Examples: 2000, 1000
• Temporary directory

  The temporary directory where attachments are downloaded.

  • Valid Values: path value
  • Default Value: /temp
  • Examples: /tmp, c:/temp
• Audio Temporary directory

  You must specify this directory to allow voice access and to enable replying to an email with a voice attachment. This parameter specifies the temporary directory that stores the voice files in the server holding the email application.

  • Valid Values: path URL
  • Default Value: /modules/modules-web/pim/mail/audiotemp
  • Examples: /modules/modules-web/pim/mail/audiotemp
• Audio temporary directory url

  You must specify this parameter to allow voice access and enable replying to an email as a voice attachment. This parameter specifies the HTTP URL used to retrieve the audio files sent in the email.

  • Valid Values: URL value
  • Default Value: http://localhost/modules/pim/mail/audiotemp
  • Examples: http://localhost/modules/pim/mail/audiotemp
• Encoding

  The encoding used while sending an email.

  • Valid Values: string value
  • Default Value: UTF-8
  • Examples: UTF-8
• Can user define server settings?

  Whether the user can edit the settings for the server, domain, etc.

  • Valid Values: Boolean value
  • Default Value: false
  • Examples: true, false
• SMTP Login

  The default user name for SMTP authentication.

  • Valid Values: String value
  • Default value: (empty)
• Email Configuration Java Driver Class

  The Java driver class used to load the email driver configuration. The Administrator cannot edit this parameter.

  • Valid Values: class name
  • Default value: oracle.panama.module.pim.mail.util.Config

4.9 Short Messaging

The short messaging mobile service 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 mobile service does not require scripts.

4.9.1 Configuration Parameters

The short messaging service includes the following configuration parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Message Sender

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

  • Valid Values: string value
  • Default Value: [e-mail]
  • Examples: mycompany.mydomain.com, 1(650)555-8785
• Display All Delivery Types?

  Specifies whether all of the delivery types (email, fax, SMS, and voice) are displayed, even if they are not configured. Setting this parameter to false, then only the configured delivery types are visible to the user.

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

4.10 Business Directory

The business directory mobile service provides user with a complete business directory. This mobile service is built on the Wireless Location Application Component API.

This mobile service provides a "yellow pages" type interface to look for 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 mobile service, the location mobile service is invoked to obtain location data for the search.

This mobile service requires the Wireless business directory provider.

Table 4-3 Requirements for the Business Directory Mobile Service

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

4.10.1 Configuration Parameters

The Business Directory includes the following input parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Web URL

  The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use.

  • Valid Values: any URL
  • Default Value: localhost
  • Examples: localhost, http://www.oracle.com
• Records Per Page

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

  • Valid Values: int value
  • Default Value: 9
  • Examples: 2, 4, 9

4.11 Driving Directions

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

This mobile service is built upon the Wireless Location Application Component API.

This service requires the Wireless routing provider.

Table 4-4 Requirements for the Location Picker Mobile Service

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

4.11.1 Configuration Parameters

The driving directions mobile service includes the following input parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Web URL

  The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use only.

  • Valid Values: any URL
  • Default Value: localhost
  • Examples: localhost, http://www.oracle.com
• Records Per Page

  Items per page. Used to indicate how many steps are displayed per page. Administrators cannot edit this parameter.

  • Valid Values: init value
  • Default Value: 9
  • Examples: 2, 4, 9
• Path for Voice Files

  The absolute file path for the voice token file, a properties file that gives the mapping between recorded .wav files and voice outputs. This parameter is reserved for future use only.

  • Valid Values: path in the file system.
  • Default Value: current directory.
  • Examples: /tmp, C:\temp\voice

4.12 Location Picker

The Location Picker mobile service enables users to pick and manage their frequently accessed locations. Using this mobile service, a user can specify a location that can be used by another mobile service, such as the driving directions mobile service. 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 mobile service is used by other mobile services 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 mobile services include Driving Directions, Maps, and Business Directory. These mobile services 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 mobile services.

This mobile service 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 Mobile Service

Name	External Providers	From
Geocoding Provider	otn.oracle.com	2.0
Mobile positioning provider	otn.oracle.com	2.0

This mobile service does not require scripts.

4.12.1 Configuration Parameters

The Location Picker mobile service includes the following input parameters:

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8
• Web URL

  The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use only.

  • Valid Values: any URL
  • Default Value: localhost
  • Examples: localhost, http://www.oracle.com, etc
• History Stack Size

  The depth of the location history stack. When it reaches this depth, the least recent locations are replaced by new locations to keep the depth constant. Administrators cannot edit this parameter.

  • Valid Values: init value
  • Default Value: 72
  • Examples: 72, 30, 100
• Records Per Page

  This parameter, which applies only to WML devices, specifies the number of business categories and result items show per WML card.

  • Valid Values: init value
  • Default Value: 9
  • Examples: 2, 4, 9

4.13 Maps

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

4.13.1 Configuration Parameters

The maps mobile service includes the following input parameters.

• Application URL Address

  The absolute URL to the data source. Administrators cannot edit this parameter.

• Replace Relative URLs

  Whether the adapter should replace the relative URLs inside the result with the absolute URL.

  • Default Value: true
• HTTP Method

  The method used by the adapter to get the content from the URL.

  • Default Value: POST
• Input Encoding

  The encoding scheme of the remote Web server.

  • Default Value: UTF-8