Oracle9iAS Wireless Administrator's Guide Release 9.0.3 Part Number B10042_01 |
|
|
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:
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:
The voice and wireless components of the Oracle Collaboration Suite become fully functional after you configure the mobile services.
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.
The address book mobile service includes four configuration parameters that pertain to all Aysnc-enabled mobile services:
The values set for these parameters affect all Async-enabled services.
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.
The mobile address book includes the following parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web 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.
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.
The administrator user name and account in the OID server.
The password for the administrator account in the OID server.
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.
The driver class implementing the backend. Administrators cannot edit this parameter.
Should the end user be able to edit the server configuration?
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).
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.
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.
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).
The calendar enables users to manage their schedule and tasks via mobile access to calendaring servers.
The Calendar mobile service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web 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.
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.
The Oracle calendar backend. Administrators cannot edit this parameter.
Should the end user be able to edit the server configuration?
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.
All of the required .jar files are included with Wireless. The Mobile directory includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
Default Value: POST
The encoding scheme of the remote Web 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.
The server port where the Oracle Internet Directory (OID) was installed during the Oracle Collaboration Suite setup. The Corporate Directory is stored here.
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.
The user name for the administrator account in the OID server.
The password for the administrator account in the OID server.
The maximum results returned to the user regardless of the Query Result set size.
The system-assigned names to the internal queries.
The caption that displays when queries are performed.
The entry point in OID where queries start.
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.
Defines if the query will be visible. Administrators cannot edit this parameter. Internal use only.
Defines the query attributes that will be used in the filter. Future use only.
Defines the query filter expression.
Defines the query filter expression. This parameter is reserved for future use only.
Defines the query attributes that will be on the result list.
Defines the query attributes display name that will be on the result list.
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.
Specifies the applications to which the listed attributes will be linked.
Specifies attributes that are linked in the result query to perform further queries.
The caption for the links on the result list.
System-assigned name to the internal links.
The query associated with the current link. Default to Q1.
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.
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.
A comma-separated list of the Query Result List Attributes to be displayed in the Link.
The maximum number of results shown per display page.
If true, then all other public attributes are included in the query results. If false, then only the Query Result List attributes display.
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.
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 ServiceSince 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:
On Windows NT installations, this cover page is located at:
To use the provided fax cover page:
The fax mobile service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
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.
The RightFax user name associated with the fax transactions.
The maximum number of fax history records kept in database for each user.
This parameter, which applies only the WML, specifies the number of faxes that display per screen in the Fax History.
Whether to keep log information in the system log file.
Whether to enable the directory mobile service when searching for a recipient. Set to true only if the directory has fax number information.
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.
Cover page to use when sending faxes. The cover page file should be on the fax server's RightFax\FCS directory.
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:
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.
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.
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).
This online files mobile service requires the Java development kit for Oracle Internet File System.
The online files mobile service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
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.
Specifies the directory used to hold files for download or for attachments. This path is local to the server holding the Online Files application.
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.
The HTTP proxy host. This parameter is used only if the Oracle Collaboration Suite server has been installed behind a firewall.
The HTTP proxy port. This parameter is used only if the Oracle Collaboration Suite server has been installed behind a firewall.
The HTTP authorization realms associated with each of the preceding service URLs. Separate multiple realms with a comma (,).
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.
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 ServiceThis mobile service does not require scripts.
The instant messaging mobile service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
The host name of the machine on which the Jabber Server is configured (for example, jabber.org).
The Yahoo! Instant Messaging transport, if any, configured on the Jabber Server used by the service (for example, yahoo.jabber.org).
The initial group name to assign to users acquired through the Yahoo! transport, if any.
The MSN Instant Messaging transport, if any, configured on the Jabber Server used by the service. (for example, msn.jabber.org)
The initial group name to assign to users acquired through the MSN transport, if any
The refresh page timeout for some pages accessed by the service. This value is in milliseconds
The maximum number of messages the service will display between you and another user.
The mail mobile service enables users to access their email messages from any mobile device.
The mail mobile service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
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.
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.
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.
The username for the administrator account on the OID server.
The password for the administrator user on the OID server.
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.
Examples: thin, oci
The host name of the SMTP Server. This should point to the server where SMTP was installed during the Oracle Collaboration Suite setup.
The port of the SMTP Server. This should point to the server where SMTP was installed during the Oracle Collaboration Suite setup.
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.
The primary folder for the user; usually it is "INBOX".
The name of the folder where the sent messages need to be saved.
The maximum number of messages that will be fetched from the server at each request.
The timeout limit (in milliseconds) to wait for a response from the mail server.
The temporary directory where attachments are downloaded.
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.
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.
The encoding used while sending an email.
Whether the user can edit the settings for the server, domain, etc.
The default user name for SMTP authentication.
The Java driver class used to load the email driver configuration. The Administrator cannot edit this parameter.
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.
The short messaging service includes the following configuration parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
Specifies the identity used for anonymous users when they send short messages. This parameter is ignored for non-anonymous users.
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.
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.
Name | External Provider(s) | From |
---|---|---|
Business Directory Provider |
otn.oracle.com |
2.0 |
The Business Directory includes the following input parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use.
This parameter, which applies only to WML devices, specifies the number of business categories and result items shown per WML card.
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.
Name | External Provider(s) | From |
---|---|---|
Routing Provider |
otn.oracle.com |
2.0 |
The driving directions mobile service includes the following input parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use only.
Items per page. Used to indicate how many steps are displayed per page. Administrators cannot edit this parameter.
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.
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.
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.
The Location Picker mobile service includes the following input parameters:
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.
The URL for resources used by this service. Administrators cannot edit this parameter. This parameter is reserved for future use only.
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.
This parameter, which applies only to WML devices, specifies the number of business categories and result items show per WML card.
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.
The maps mobile service includes the following input parameters.
The absolute URL to the data source. Administrators cannot edit this parameter.
Whether the adapter should replace the relative URLs inside the result with the absolute URL.
The method used by the adapter to get the content from the URL.
The encoding scheme of the remote Web server.