18
Mobile PIM and eMail

Each section of the chapter describes a module and its configuration. The sections of this chapter include:

• Section 18.1.1, "Mobile Email"

• Section 18.1.2, "Mobile Directory"

• Section 18.1.3, "Mobile Address Book"

• Section 18.1.4, "Calendar"

• Section 18.1.5, "Instant Messaging"

• Section 18.1.6, "Short Messaging"

• Section 18.1.7, "Document Management"

• Section 18.1.8, "Fax Module"

• Section 18.1.9, "Tasks"

Figure 18-1 The Mobile PIM and Email

Text description of the illustration feature7.gif

18.1 Mobile PIM and eMail Overview

Oracle9i Application Server Personal Information Management (PIM) Service enables customers to integrate corporate email, directory, address book, calendaring and instant messaging applications into their mobile enterprise portals.

Each of these applications is built as a module that can be called either directly by mobile users from their devices, or by other applications. These mobile PIM and email applications are fully integrated within one another, enabling a user to access such features as an address book-based recipient selection or a directory when composing email messages.

Oracle9i Application Server customers can leverage the Personal Information Management Service modules into their own or third-party applications to add communication features to these services, to retrieve corporate directory information, or to add and manage appointments for users such as travel or dining reservations.

18.1.1 Mobile Email

The email module enables users to access their email messages from any mobile device. Mobile Email integrates with any IMAP or POP3 server (including Microsoft Exchange and Lotus Domino servers).

18.1.1.1 Configuring an Email Service

All the necessary .jar files are shipped with Oracle9iAS Wireless. The are no scripts.

Table 18-1 Email Module Parameters

Parameter	Description	Default Value	Example
ORACLE_SERVICES_PIM_MAIL_PROTOCOL	The mail protocol.	pop3	imap, pop3
ORACLE_SERVICES_PIM_MAIL_SERVER_NAME	Full hostname of the Mail server.	localhost	mailserver.mycompany.com
ORACLE_SERVICES_PIM_MAIL_SERVER_PORT	Port number of the Mail server on the host.	110	Typically 143 for imap and 110 for pop3.
ORACLE_SERVICES_PIM_MAIL_SMTP_SERVER_NAME	Full hostname of the SMTP server.	localhost	mysmtp.mycomp.com
ORACLE_SERVICES_PIM_MAIL_SMTP_SERVER_PORT	Port number of the SMTP server on the host.	25	25, 45
ORACLE_SERVICES_PIM_MAIL_SMTP_SERVER_LOGIN	The login name of the SMTP server. If login for SMTP is not required, then this value should be null or empty # string (""), otherwise, the value will be used for SMTP login. The format is <login name>@<domain>. If domain is not specified here, the value of the property ORACLE_SERVICES_PIM_MAIL_AUTODOMAIN will be appended. If that is not specified also, the property ORACLE_SERVICES_PIM_MAIL_DEFAULT_EMAILDOMAIN will be used.	none	john.doe@mycomp.com
ORACLE_SERVICES_PIM_MAIL_AUTODOMAIN	When composing email, if email address does not have a domain, this domain will be automatically appended.	localhost	mycomp.com
ORACLE_SERVICES_PIM_MAIL_FOLDER_INBOX	The name of the Inbox folder on the mail server.	INBOX	INBOX, Inbox
ORACLE_SERVICES_PIM_MAIL_FOLDER_SENT	The name of the Sent folder on the mail server.	Sent	Sent, SentItems
ORACLE_SERVICES_PIM_MAIL_DEFAULT_EMAILDOMAIN	The default email domain for sending emails. When sending emails, if the email domain is not specified, then the default email domain will be appended to the username. For example, if the default domain is oraclemobile.com, and a user sends an email to the user "john.doe", the email will be sent to john.doe@mycomp.com	localhost	mycomp.com
ORACLE_SERVICES_PIM_MAIL_MSGFETCH_SETSIZE	The maximum number of messages fetched for one request. This is the maximum number of messages return for one request. For example, if a folder has 300 messages, only the first 200 will be returned at the first time.	200	200, 300
ORACLE_SERVICES_PIM_MAIL_SERVER_CONNECT_TIMEOUT	The connection timeout in milliseconds.	2000	2000, 3000
ORACLE_SERVICES_PIM_MAIL_CONFIG_CLASS	The configuration class. Users can provide their own configuration classes, enabling them to perform advanced configuration such as selecting a mail server host name based on runtime information.	oracle.panama.module.pim.mail.util.Config	oracle.panama.module.pim.mail.util.Config mycomp.mail.config.MailConfig
ORACLE_SERVICES_PIM_MAIL_TEMP_DIR	The temporary directory for downloading a message or attachments.	/temp	/home/9iasuser/temp, D:\9iasuser\temp
ORACLE_SERVICES_PIM_MAIL_AUDIO_TMP_DIR	The temporary directory that stores the temporary audio files. This directory holds the .wav files that are generated when a user replies to an email in the voice version of the application. This directory should be web accessible.	/modules/modules-web/pim/mail/audiotemp	/home/9iasuser/iaswv20/modules/modules-web/pim/mail/audiotemp
ORACLE_SERVICES_PIM_MAIL_AUDIO_TMP_URL	The url for the temporary audio files directory.	http://localhost/modules/pim/mail/audiotemp	http://localhost/modules/pim/mail/audiotemp
ORACLE_SERVICES_PIM_MAIL_MESSAGE_ENCODING	The encoding that is used while sending an email. If this field is empty, then the default system encoding is used.	UTF-8	UTF-8, Shift_JIS, Big5

18.1.1.2 Linking to a Email Service

You can link to an email service using the following virtual URL:

omp://oracle/services/pim/mail

Input Call Parameters

The input call parameters of the email module include the following:

action

The action the email module should perform. This is a mandatory input parameter.

Table 18-2 Input Parameters for Action

Valid Value	Description	Requirement
messageto	Send an email message.	Requires mailto.
messagecc	CC an email message.	Requires mailto.
sendasattachment	Send an attachment	Requires attach.

mailto

The email address to which the message is sent. This is an optional input parameter. The value must be a string. For example:

• mailto=oraclemobile@oracle.com

• mailto=john.smith@mycompany.com

attach

The fully-qualified path of the local file that is sent as an attachment to the email. the value must be a string. For example:

• attach=/home/9iasuser/temp/presentation.ppt

• attach=D:\9iasuser\temp\instructions.txt

Output Parameters (Examples)

To send an email to Scott Tiger, you configure the action and mailto parameters as follows:

• action=messageto

• mailto=scott.tiger@oracle.com

To send the picture (a .jpeg)of your new home, you configure the action and attach parameters as follows:

• action=sendasattachment

• attach=/private/9iasuser/temp/my1MilDolHome.jpg

18.1.2 Mobile Directory

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

18.1.2.1 Configuring the Mobile Directory

All of the required .jar files are included with Oracle9iAS Wireless. This module requires no scripts.

The Mobile directory includes the following configuration parameters:

Table 18-3 Configuration Parameters for the Mobile Directory

Parameters	Description	Default Value	Examples
ORACLE_SERVICES_PIM_DIRECTORY_HOST	The LDAP server hostname.	localhost Valid value: myldapserver.cycompany.com
ORACLE_SERVICES_PIM_DIRECTORY_PORT	The LDAP server port number	389	389,345
ORACLE_SERVICES_PIM_DIRECTORY_LOGIN	Is Login required or not?	The valid value is 'false'.	true, false
ORACLE_SERVICES_PIM_DIRECTORY_USERNAME	If a LDAP login is required, then a default username and password can be specified. Set ORACLE_SERVICES_PIM_DIRECTORY_LOGIN to true.	my user	User 1234
ORACLE_SERVICES_PIM_DIRECTORY_PASSWORD	If a LDAP login is required then a default username and password can be specified. Set ORACLE_SERVICES_PIM_DIRECTORY_LOGIN to true.	1234	55 hello 27478
ORACLE_SERVICES_PIM_DIRECTORY_MAX_RESULT_COUNT	Maximum results returned from a query.	1000	1000, 1200
ORACLE_SERVICES_PIM_DIRECTOR_QUERY_NAMES	The list of IDs for each type of query to be defined. For each one defined, other parameters with the ID need must be created as specified below. The parameters with the ID "BYNAME" must be created for each query.	None	BYNAME, BYEMAIL
ORACLE_SERVICES_PIM_DIRECTORY_MAX_REC_PAGE	The maximum results displayed on a screen.	9	9, 10
ORACLE_SERVICES_PIM_DIRECTORY_MERGE_RESULTS	Whether to display other attributes returned by a query but not specified in the filter.		true, false
ORACLE_SERVICES_PIM_DIRECTORY_HOTLINK_NAMES	The list of hotlink names. You must define corresponding parameters for each hotlink you define. The parameters with the ID "MANAGER" are required for each hotlink.		MANAGER
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_DISPLAY	The display name for this query, which is displayed to the user.		Search by Name.
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_SEARCHBASE	Identifies the location from which the search begins.		Examples (dc=oracle,dc=com)
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_SEARCHSCOPE	Identifies the scope of the search.		BASE, ONE, SUBTREE
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_VISIBLE	Whether a query is visible as a choice to the user.		true, false
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_FILTER	The filter attributes for the query.		cn, sn, email
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_FILTER_EXPRESSION	The Filter expression for the query, which is RFC 2254 - compliant.		(!(cn=Scott Tiger)), cn=*?*
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_FILTER_DISPLAY	A prompt for the input values of the filter.		Enter a name to search:, Enter an area to search
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST	The list of attributes that you want from the query.
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST_DISPLAY	The display names for the attributes that are retrieved.	.	First Name, Last Name, Email Address
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST_TYPE	The type of link (made from the results).		display, phone, fax, email, link, SMS
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST_HOTLINK	Specifies if the result attribute is a hotlink. Set to false if the result attribute is not a hotlink; otherwise, any other value will suffice.		false, MANAGER, GROUP
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_HOTLINK_NAMES	The names for the hotlink of an attribute. If the corresponding attribute in the list is not a hotlink, enter "nope"	.	nope, MANAGER,
ORACLE_SERVICES_PIM_DIRECTORY_HOTLINK_MANAGER_QUERY	The query name used by the hotlink.
ORACLE_SERVICES_PIM_DIRECTORY_HOTLINK_MANAGER_COLUMN_REFER	The column values to use from the current result set.		cn, sn
ORACLE_SERVICES_PIM_DIRECTORY_HOTLINK_MANAGER_COLUMN_BIND	The attribute names to bind the referenced values.		cn, sn
ORACLE_SERVICES_PIM_DIRECTORY_HOTLINK_MANAGER_COLUMN_DISPLAY	The attribute values that are displayed. These values are delimited by a space in the display.		givenname, sn
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST_SHORTLIST	Comma-delimited series of tokens, either "true" or "false", and is of the same length as the parameter ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST. The value of the token specifies whether that particular member of the result list will be displayed in the short list mode (value = true) or if the member of the result list will only be displayed in the detailed view (value = false).

18.1.2.2 Linking to the Directory Module

You can link to the directory module through the following virtual URL:

omp://oracle/services/pim/directory

You can configure each element of this service; clicking any field after getting the details of a result returns the field value to the caller as the parameter mailto.

Output Parameters

The output parameters for the mobile directory service include the following:

mailto

The value of the field that the user clicks. For example:

• mailto=oraclemobile@oracle.com

• mailto=John

• mailto=Smith

• mailto=(650)999-9999

There are no restrictions for this parameter.

Examples

To return a first name, configure the mailto parameter as follows:

mailto=john

To return an email address, cofeature the mailto parameter as follows:

mailto=john.smith@mycompany.com

18.1.3 Mobile Address Book

The Mobile 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 Mobile Email Module 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.

18.1.3.1 Configuring the Mobile Address Book

This service implements two distinct modes, both with the same user experience but different back-ends. In its Oracle9iAS Wireless 2.0 mode, it does not require any third-party software and uses Oracle9iAS Wireless 2.0 storage. In its Microsoft Exchange Mode, it fully integrates with a Microsoft Exchange server to mobile enable Exchange users

Required Software

The mobile address book requires the following third-party software:

Required Third-Party Software for the Mobile Address Book

Name	Instructions	Version(s)
MS Exchange	[Exchange Mode] Install the Microsoft Exchange Server.	5.5
MS IIS	[Exchange Mode] Install the Microsoft Internet Information Server.	4.0
MS CDO	[Exchange Mode] Collaborative Data Objects. Available with Exchange SDK. The cdo.dll library must be installed on the IIS Server.	1.2.1
Oracle9iAS Wireless 2.0 Exchange ASP (Shipped with Oracle9iAS Wireless 2.0)	[Exchange Mode] Create any directory on the IIS server. Copy all the files in $ORACLE_HOME/iaswv20/wireless/j2ee/applications/modules/modules-web/pim/addressbook/asp/ for a Solaris install, %ORACLE_HOME%\iaswv20\wireless\j2ee\applications\modules\modules-web\pim\addressbook\asp\ for an NT install to the just created directory on the IIS server. Invoke the properties dialog box for this directory. Choose the Directory tab. Click the "Edit" button for the "Anonymous Access and Authentication Control". Set as follows: Allow Anonymous Access - unchecked Basic Authentication - checked Windows NT Challenge/Response - checked

Configuration Parameters

The mobile address book includes the following parameters:

• ORACLE_SERVICES_PIM_ADDRESSBOOK_CLASS
  • Description: The service implementation class. Determines whether the Oracle9iAS or Exchange mode is used.

  • Default Value: oracle.panama.module.pim.addressbook.omaddressbook.OMAddressBook

  • Valid Values: oracle.panama.module.pim.addressbook.omaddressbook.OMAddressBook, oracle.panama.module.pim.addressbook.exchange.ExchangeAddressBook.

• ORACLE_SERVICES_PIM_ADDRESSBOOK_SERVER_NAME
  • Description: If Exchange mode is selected, designates the Exchange server host name or IP address. It should not contain a value in the Wireless 2.0 mode.

  • Default Value: localhost

  • Valid Values: exchange.mycompany.com, email-serv.mycompany.com.

• ORACLE_SERVICES_PIM_ADDRESSBOOK_SERVER_DATA_WEB_LINK
  • Description: If Exchange mode is selected, this is the URL pointing to the Oracle9iAS Wireless Exchange Address Book ASP (AddressBook.asp) running on IIS. It should have no value in the Wireless 2.0 mode.

  • Default Value: None

  • Examples: http://iis.mycompany.com/Oracle9iASW20/exchange/AddressBook.asp

• ORACLE_SERVICES_PIM_ADDRESSBOOK_DOMAIN
  • Description: 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.

  • Default Value: LOCALDOMAIN

  • Examples: LOCALDOMAIN for the Oracle9iAS Wireless Mode, ExchangeDomain for Exchange.

18.1.3.2 Linking to the Mobile Address Book

You can link to the mobile address book using the following virtual URL:

omp://oracle/services/pim/addressbook

The mobile address book includes the following call parameters:

Table 18-4 Input Call Parameters of the Mobile Address Book

Parameter Name	Mandatory	Description	Valid Value
screen	No	The function performed by the Addressbook.	0 (Displays the list of contacts); 51 (Makes the Addressbook service add the contact with the provided data to this database of contacts. This parameter requires SERIALIZED_CONTACT if the value is 51.)
srchstr	No	Makes the Addressbook perform a search for the specified string among all of the contacts.	The string to search for. Requires screen := {0 empty}

SERIALIZED_CONTACT

The SERIALIZED_CONTACT group contains the parameters for each element of a contact, such as contact name, contact work phone, and contact work address. The elements described in this optional group are returned when the user clicks done in the screen with a contact detail.

The SERIALIZED_CONTACT group includes the following parameters:

Table 18-5 Parameters of the Serialized Contact Group for Addressbook

Parameter Name	Mandatory	Description	Valid Value
NAME	Yes	The name of this contact.	For example, NAME=John Smith.
WORKPH	No	The work phone number of this contact. Restriction: white-spaces, special characters, are encoded.	WORKPH=650-123-4567
MOBILEPH	No	The mobile phone number of this contact.
HOMEPH	No	The home phone of this contact. Restriction: white-spaces, special characters, are encoded.
WORKFAX	No	The business fax number of this contact. Restriction: white-spaces, special characters, are encoded.
EMAIL1	No	The email (or the first email) address of this contact. Restriction: white-spaces, special characters, are encoded.	An email address, for example, EMAIL1=scott.tiger@oralce.com
EMAIL2	No	The second email address of this contact. Restriction: white-spaces, special characters, are encoded.	An email address, for example, EMAIL2=scott.tiger@homemail.com
WADDRLINE1	No	The first (or only) line of the Work address of this contact. Restriction: white-spaces, special characters, are encoded.	The first line of a street address. For example: WADDRLINE1=123 Main Street
WADDRCITY	No	The city or Work address of this contact. Restriction: white-spaces, special characters, are encoded.	A city; for example, WADDRCITY = Boston
WADDRSTATE	No	The state (or federal region) of the WORK address of this contact. Restriction: white-spaces, special characters, are encoded.	A state (or federal region); for example, WADDRSTATE = CA WADDRSTATE = Massa chusetts
WADDRZIP	No	The ZIP or postal code of the work address of this contact.	A ZIP or postal code. For example, WADDRZIP=02142 WADDRZIP=D-80333
WADDRCOUNTRY	No	The country of the work address of this contact.	The name of a country, for example: WADDRCOUNTRY=U.S.A.
HADDRLINE1	No	The first (or only) street line of the home address of this contact. Restriction: white-spaces, special characters, are encoded.	The first line of a street address, for example: HADDRLINE1 = 2901 Armstrong Dr.
HADDRCITY	No	The city of the home address of the person in the contact.	The name of a city, for example: HADDRCITY=Boston
HADDRSTATE	No	The state (or federal region) of the home address of the person in this contact.	The full name or abbreviation of the state. For example: HADDRSTATE=Massachusetts HADDRSTATE=CA
HADDRZIP	No	The ZIP or postal code of this contact.	The ZIP or postal code. For example: HADDRZIP=90210 HADDRZIP=D-80333
HADDRCOUNTRY	No	The country of the home address of this contact.	A name of a country, for example: HADDRCOUNTRY=U.S.A.
NOTES	Yes	Text notes describing this contact. Restriction: white-spaces, special characters, are encoded.	A short description of the person in the contact, for example: NOTES=This the chief-of-staff in CCC Co.

Output Parameters

The output parameters for the Addressbook include the following:

Table 18-6 Output Parameters of the Addressbook

Parameter Name	Mandatory	Description
mailto	No.	An email address of a contact. This must be an email address. For example: mailto=scott.tiger@orcale.com

smPhone

smphone is a phone number of a contact, returned with additional parameters used by the Short Messaging module (usually when the user clicks on a phone number in the Addressbook).

This group includes the following parameters:

Table 18-7 Parameters of smPhone

Parameter Name	Mandatory	Description	Valid Value
type	Yes	The type of short messaging service desired.	VOICE, FAX
destinationAddress	Yes	The recipient number of address for the short message (usually a phone number).	A phone number, for example: destinationAddress=650-555-5000.

faxNumber

faxNumber is the fax number of a contact, returned with additional parameters used by the FAX or Short-Messaging modules (usually when the user clicks on a fax number in the Addressbook). The faxNumber group includes the following parameters:

Table 18-8 Parameters of faxnumber

Parameter Name	Mandatory	Description	Valid Value
type	Yes	The type of short messaging service needed.	FAX
destinationAddress	Yes	The fax number of the recipient used in the short messaging module.	A fax number, for example, destinationAddress=650-123-4567
FAXTODO	Yes	The function that the fax module perform.	NEWFAX
RNAME	Yes	The name of the recipient of the fax.	A name, for example: RNAME=Scott Tiger
RPHONE	Yes	The phone number of the recipient of the fax.	a phone number, for example: RPHONE=650-555-5000.
RFAX	Yes	The fax number to which the fax is sent.	a fax number, for example, RFAX=650-555-1234

SERIALIZED_CONTACT

The SERIALIZED_CONTACT group contains the parameters for each element of a contact, such as contact name, contact work phone, and contact work address. The elements described in this optional group are returned when the user clicks done in the screen with a contact detail.

The parameters of the SERIALIZED CONTACT group are as follows:

Table 18-9 Parameters of the SERIALIZED_CONTACT Group

Parameter Name	Mandatory	Description	Valid Value
NAME	Yes	The name of this contact. Restriction: the white-spaces, special characters, are encoded.	A name. For example, NAME=John Smith.
WORKPH	No	The work phone number of this contact. Restriction: the white-spaces, special characters, are encoded.	A phone number, for example: WORKPH=650-123-4567
HOMEPH	No	The home phone number of this contact. Restriction: the white-spaces, special characters, are encoded.	A phone number, for example: HOMEPH=650-555-5000
MOBILEPH	No	The mobile phone number of this contact. Restriction: the white-spaces, special characters, are encoded.	A phone number, for example: MOBILEPH=650-555-5000
WORKFAX	No	The business fax number of this contact. Restriction: the white-spaces, special characters, are encoded.	Example: WORKFAX=
EMAIL1	No	The e-mail (or the first email) address of this contact. Restriction: the white-spaces, special characters, are encoded.	An email address, for example, EMAIL1=scott.tiger@oralce.com
EMAIL2	No	The second email address of this contact. Restriction: the white-spaces, special characters, are encoded.	An email address, for example, EMAIL2=scott.tiger@homemail.com
WADDRLINE1	No	The first (or only) line of the Work address of this contact. Restriction: the white-spaces, special characters, are encoded.	The first line of a street address. For example: WADDRLINE1=123 Main Street
WADDRCITY	No	The city or work address of this contact. Restriction: the white-spaces, special characters, are encoded.	A city; for example, WADDRCITY = Boston
WADDRSTATE	No	The state (or federal region) of the WORK address of this contact. Restriction: the white-spaces, special characters, are encoded.	A state (or federal region); for example, WADDRSTATE = CA WADDRSTATE = Massachusetts
WADDRZIP	No	The ZIP or postal code of the work address for this contact.	A ZIP or postal code. For example, WADDRZIP=02142 WADDRZIP=D-80333
WADDRCOUNTRY	No	The country of the work address of this contact.	The name of a country, for example: WADDRCOUNTRY=U.S.A.
HADDRLINE1	No	The first (or only) street line of the home address of this contact. Restriction: the white-spaces, special characters, are encoded.	The first line of a street address, for example: HADDRLINE1 = 2901 Armstrong Dr.
HADDRCITY	No	The city of the home address of the person in the contact.	The name of a city, for example: HADDRCITY=Boston
HADDRSTATE	No	The state (or federal region) of the home address of the person in this contact.	The full name or abbreviation of the state. For example: HADDRSTATE=Massachusetts HADDRSTATE=CA
HADDRZIP	No	The ZIP or postal code of this contact.	The ZIP or postal code. For example: HADDRZIP=90210 HADDRZIP=D-80333
HADDRCOUNTRY	No	The country of the home address of this contact.	A name of a country, for example: HADDRCOUNTRY=U.S.A.
NOTES	Yes	Text notes describing the person this contact. Restriction: the white-spaces, special characters, are encoded.	A short description of the person in the contact, for example: NOTES=This the chief-of-staff in CCC Co.

18.1.4 Calendar

The calendar enables users to manage their schedule and tasks via mobile access to calendaring servers, such as Microsoft Exchange and Lotus Domino.

18.1.4.1 Configuring the Calendar Module

This service implements two distinct modes, both with the same user experience but with different back-ends. In its Lotus Domino mode, it fully integrates with a Lotus Domino server to mobile enable Domino users. In its Microsoft Exchange Mode, it fully integrates with a Microsoft Exchange server to mobile enable Exchange users.

Required Third-Party Software

The calendar module requires the following third-party software:

Table 18-10 Software Requirements for the Calendar Module

Name	Instruction	Version(s)
MS Exchange	Exchange mode: Install the Microsoft Exchange Server.	5.5
MS IIS	Exchange mode: Install the Microsoft Internet Information Server.	4.0
MS CDO	Exchange mode: Collaborative Data Objects. Available with Exchange SDK. The cdo.dll library must be installed on the IIS Server.	1.2.1
Oracle9iAS Wireless (Exchange ASP Shipped with Oracle9iAS Wireless 2.0)	Exchange mode: Create any directory on the IIS server. Copy all the files in $ORACLE_HOME/iaswv20/wireless/j2ee/applications/modules/modules-web/pim/calendar/asp/ for a Solaris install, %ORACLE_HOME%\iaswv20\wireless\j2ee\applications\modules\modules-web\pim\calendar\asp\ for an NT install to just created directory on the IIS server. Invoke the properties dialog box for this directory. Choose the Directory tab. Click the "Edit" button for the "Anonymous Access and Authentication Control", make sure the following check boxes are set as follows: Allow Anonymous Access - unchecked Basic Authentication - checked Windows NT Challenge/Response-checked
Lotus Java SDK	Domino Mode: Install the Lotus Domino Toolkit for Java/CORBA, and add NCSO.jar to the classpath for Oracle9iAS Wireless 2.0. Installing the toolkit creates "DTJava" directory on the file system. Copy the DTJava/lib/NCSO.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 Ensure 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". 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	R5

Configuration Parameters

The Calendar module includes the following configuration parameters:

• ORACLE_SERVICES_PIM_CALENDAR_CLASS
  • Description: The service implementation class, which determines whether the Domino or Exchange mode is used.

  • Default Value: None

  • Valid Values: oracle.panama.module.pim.calendar.domino.DominoCalendarService, oracle.panama.module.pim.calendar.exchange.ExchangeCalendarService.

• ORACLE_SERVICES_PIM_CALENDAR_SERVER_NAME
  • Description: Designates the Exchange server or Domino server host name.

  • Default Value: None

  • Examples: exchange.mycompany.com, domino-server.mycompany.com

• ORACLE_SERVICES_PIM_CALENDAR_SERVER_DATA_WEB_LINK
  • Description: If the Exchange mode is selected, this is the URL pointing to the Oracle9iAS Wireless 2.0 Exchange Calendar ASP (Calendar.asp) running on IIS.

  • Default Value: None

  • Examples: http://iis.mycompany.com/Oracle9iASW20/exchange/Calendar.asp

• ORACLE_SERVICES_PIM_CALENDAR_DOMAIN
  • Description: 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.

  • Default Value: None

  • Examples: DominoDomain for the Domino Mode, ExchangeDomain for Exchange.

18.1.4.2 Linking to the Calendar Module

You can link to the calendar module using the following virtual URL:

omp://oracle/services/pim/calendar

Input Call Parameters for the Calendar Module

The input call parameters of the calendar module include the getApptDetails group. This optional group includes the following input call parameters:

Table 18-11 Parameters of ID

Parameter Name	Mandatory	Description	Valid Value
ID	Yes	The input ID required to retrieve appointment details.	A string. For example, ID=1324.

Table 18-12 Parameters of addAppt

Parameter Name	Mandatory	Description	Valid Value
TITLE	Yes	The title of the appointment.	A string. For example, TITLE=Dinner at Joe's.
DATE	Yes	The date of the appointment.	A string. For example, DATE=December 31, 2001
TIME	Yes	The time of the appointment.	A string. For example, TIME= 8:00 p.m.
DURATION	Yes	The duration of the appointment.	A string. For example, DURATION=1 hour.
NOTES	Yes	The notes for the appointment.	A string. For example, NOTES=Remember the brief.
TYPE	Yes	The type of appointment, either personal or business.	A string. For example, TYPE=Business.
LOCATION	Yes	The location of an appointment.	A string. For example, LOCATION=Home.
REMIND	Yes	The time interval before the event reminder occurs.	A string. For example, REMIND=1 hour.
SHARING	Yes	A flag that enables or disables the sharing of an appointment. If True, the appointment is shared; if FALSE, then the appointment is not shared.	For example, SHARING=TRUE.

The Calendar module also includes the deleteAppt group. The deleteAppt group includes the following parameter:

Table 18-13 Parameter of deleteAppt

Parameter Name	Mandatory	Description	Valid Value
ID	Yes	The input ID required to select an appointment.	A string. For example, ID=1324.

Output Parameters of the Calendar Module

The calendar module includes the following output parameters:

The output parameters of the calendar module include the getApptDetailsRresponse group. This optional group contains the following parameters:

Table 18-14 The Output Parameters of the getApptDetailsResponse Group

Parameter Name	Mandatory	Description	Valid Value
TITLE	Yes	The title of the appointment.	A string. For example, TITLE=Dinner at Joe's.
DATE	Yes	The date of the appointment.	A string. For example, DATE=December 31, 2001
TIME	Yes	The time of the appointment.	A string. For example, TIME= 8:00 p.m.
DURATION	Yes	The duration of the appointment.	A string. For example, DURATION=1 hour.
NOTES	Yes	The notes for the appointment.	A string. For example, NOTES=Remember the brief.
TYPE	Yes	The type of appointment, either personal or business.	A string. For example, TYPE=Business.
LOCATION	Yes	The location of an appointment.	A string. For example, LOCATION=Home.
REMIND	Yes	The time interval before the event reminder occurs.	A string. For example, REMIND=1 hour.
SHARING	Yes	A flag that enables or disables the sharing of an appointment. If True, the appointment is shared; if FALSE, then the appointment is not shared.	For example, SHARING=TRUE.

apptResponse

The apptResponse group (an optional group) includes the following parameters:

Table 18-15 The Output Parameters of the addApptResponse Group

Parameter Name	Mandatory	Description	Valid Value
TITLE	Yes	The title of the appointment.	A string. For example, TITLE=Dinner at Joe's.
DATE	Yes	The date of the appointment.	A string. For example, DATE=December 31, 2001
TIME	Yes	The time of the appointment.	A string. For example, TIME= 8:00 p.m.
DURATION	Yes	The duration of the appointment.	A string. For example, DURATION=1 hour.
NOTES	Yes	The notes for the appointment.	A string. For example, NOTES=Remember the brief.
TYPE	Yes	The type of appointment, either personal or business.	A string. For example, TYPE=Business.
LOCATION	Yes	The location of an appointment.	A string. For example, LOCATION=Home.
REMIND	Yes	The time interval before the event reminder occurs.	A string. For example, REMIND=1 hour.
SHARING	Yes	A flag that enables or disables the sharing of an appointment. If True, the appointment is shared; if FALSE, then the appointment is not shared.	For example, SHARING=TRUE.

deleteApptResponse

The deleteApptResponse group (an optional group) includes the following parameters:

Table 18-16 Parameters of the deleteApptResponse group

Parameter Name	Mandatory	Description	Valid Value
TITLE	Yes	The title of the appointment.	A string. For example, TITLE=Dinner at Joe's.
DATE	Yes	The date of the appointment.	A string. For example, DATE=December 31, 2001
TIME	Yes	The time of the appointment.	A string. For example, TIME= 8:00 p.m.
DURATION	Yes	The duration of the appointment.	A string. For example, DURATION=1 hour.
NOTES	Yes	The notes for the appointment.	A string. For example, NOTES=Remember the brief.
TYPE	Yes	The type of appointment, either personal or business.	A string. For example, TYPE=Business.
LOCATION	Yes	The location of an appointment.	A string. For example, LOCATION=Home.
REMIND	Yes	The time interval before the event reminder occurs.	A string. For example, REMIND=1 hour.
SHARING	Yes	A flag that enables or disables the sharing of an appointment. If True, the the appointment is shared; if FALSE, then the appointment is not shared.	For example, SHARING=TRUE.

18.1.5 Instant Messaging

The instant messaging module 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.

18.1.5.1 Configuring the Instant Messaging Module

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

Table 18-17 Third-Party Software for the Instant Messaging Module

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 module does not require scripts.

Configuration Parameters of the Instant Messaging Module

The instant messaging module includes the following configuration parameters:

Table 18-18 Instant Messaging Module Parameters

Parameter	Description	Default Value	Valid Values
ORACLE_SERVICES_PIM_IM_PROXY_SET	Determines whether the service uses an HTTP proxy to access the Jabber Server.	false	true, false
ORACLE_SERVICES_PIM_IM_PROXY_HOST	The host name of the HTTP proxy, if any, used to connect to the Jabber Server.	none	www-proxy.mycompany.com, http-proxy.mycompany.com
ORACLE_SERVICES_PIM_IM_PROXY_PORT	The port number of the HTTP proxy, if any, used to connect to the Jabber Server.	80	Any valid TCP port number on which the HTTP proxy is listening (8080, etc).
ORACLE_SERVICES_PIM_IM_SERVER_NAME	The host name of the machine on which the Jabber Server is configured.	localhost	jabber.mycompany.com, corporate-jabber.mycompany.com
ORACLE_SERVICES_PIM_IM_USER_DIRECTORY	The name of the user directory service configured on the Jabber Server accessed by the service.	None	Jud.jabber.mycompany.com directory.jabber.mycompany.com. This name should be set to the value of the jid attribute of the service element of type jud in the active Jabber server's jabber.xml configuration file: <service type="jud" jid="jud.jabber.mycompany.com" name="Dir"> <ns>jabber:iq:search</ns> <ns>jabber:iq:register</ns> </service>
ORACLE_SERVICES_PIM_IM_YAHOO	The Yahoo! Instant Messaging transport, if any, configured on the Jabber Server used by the service.	None	yahoo.jabber.mycompany.com yahoo-im.jabber.mycompany.com This name should be set to the value of the jid attribute of the service element of type yahoo in the active Jabber server's jabber.xml configuration file: <service type="yahoo" jid="yahoo.jabber.mycompany.com" name="Y"> <ns>jabber:iq:gateway</ns> <ns>jabber:iq:register</ns> </service>
ORACLE_SERVICES_PIM_IM_YAHOO_KEY	The initial group name to assign to users acquired through the Yahoo! transport, if any.	Yahoo	Yahoo Users, Yahoo!
ORACLE_SERVICES_PIM_IM_MSN	The MSN Instant Messaging transport, if any, configured on the Jabber Server used by the service.	None	msn.jabber.mycompany.com, msn-im.jabber.mycompany.com This name should be set to the value of the jid attribute of the service element of type msn in the active Jabber server's jabber.xml configuration file <service type="msn" jid="msn.jabber.mycompany.com" name="MSN"> <ns>jabber:iq:gateway</ns> <ns>jabber:iq:register</ns> </service>
ORACLE_SERVICES_PIM_IM_MSN_KEY	The initial group name to assign to users acquired through the MSN transport, if any.	MSN	MSN Users, MSN
ORACLE_SERVICES_PIM_IM_CONFERENCE	The name of the conference service configured on the Jabber Server accessed by the service, if any.	None	conference.jabber.mycompany.com, conf.mycompany.com This name should be set to the value of the jid attribute of the conference element in the active Jabber server's jabber.xml configuration file: <conference type="private" jid="conference.jabber.mycompany.com" name="Private Conferencing"/>
ORACLE_SERVICES_PIM_IM_REFRESH_TIME	The refresh rate for some pages accessed by the service. This value is in milliseconds.	20000	30000 - for 30 seconds 60000 - for 60 seconds

18.1.5.2 Linking to the Instant Messaging Module

You can link to the instant messaging module using the following virtual URL:

omp://oracle/services/pim/instantmessaging

Input Call Parameters of the Instant Messaging Module

The input call parameters of the instant messaging module includes the IMMessage parameter.

Table 18-19 The IMMessage Parameter

Parameter Name	Mandatory	Description	Valid Value
IMMessage	No	The text of a message that is sent through the service.	A string. For example: IMMESSAGE=How are you doing today? IMMESSAGE=I am sending you this message through IM

Output Parameters

An example of the IMMessage output parameter is calling the module to send a simple message. For example:

Input Parameter: IMMessage=Do you want to go see a movie?

18.1.6 Short Messaging

The short messaging module 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 email. The subject and body text are translated into the medium appropriate to the message type and then sent to the destination.

18.1.6.1 Configuring the Short Messaging Module

This service does not require any third-party software components. It relies on Oracle9iAS Wireless transports to be configured. The short messaging modules does not require scripts.

Configuration Parameters

The short messaging service includes the following configuration parameters:

• ORACLE_SERVICES_PIM_SM_FROM_ADDRESS
  • The default address used as sender information for guest or anonymous users.

  • None

  • anonymous@mycompany.com, Company Name, (800)123-4567

18.1.6.2 Linking to the Short Messaging Module

You can link to a short messaging module using the following virtual URL:

omp://oracle/services/pim/sm

Input Call Parameters

The short messaging module includes the following input call parameters:

Table 18-20 Input Call Parameters of the Short Messaging Module

Parameter Name	Mandatory	Description	Valid Value
type	No	The type of medium through which the message is sent.	The values include: EMAIL (for sending email messages) SMS (for sending a SMS message) VOICE (for sending a message through a phone). FAX (for sending a message through a facsimile)
destinationAddress	No	The address to which the message is sent.	A string. For example: destinationAddress=6505551234 destinationAddress=oraclemobile@oracle.com
subjectText	No	The subject of a message to be sent.	A String. For example: subjectText=Hi There! subjectText=Tomorrow Night
bodyText	No	The body text of a message to be sent.	A String. For example: bodyText=Don't forget to pick up the children on the way home. And buy dinner, too.
sendMessage	No	Specifies whether the service should attempt to send the message with the given information. The service does not send the message unless it has been instructed to do so.	Specify Yes if the service should send the message. Specify No if the service should not send the message.

Output Parameters (Examples)

An example of the short message output parameters is sending a simple message. For example:

Sending an Email

To send an email configure the input parameters as follows:

type=EMAIL

destinationAddress=friend@oracle.com

subjectText=Hey there!

bodyText=How's it going?

sendMessage=yes

Sending a Voice Message

To send a voice message, configure the input parameters as follows:

type=Voice

destinationAddress=9095551234

18.1.7 Document Management

The Oracle Internet File System (iFS) module enables users to both upload files to, or download files from, an Oracle IFS server. The iFs module is integrated with other modules, such as the email module and the fax module.

18.1.7.1 Configuring the iFS Module

The Oracle iFS module enables users to both attach and save files in their native formats. The Oracle iFS module 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 modules does not require scripts.

Required Software

This iFS Module requires the Java development kit for Oracle Internet File System.

Table 18-21 Required Software for the iFS Module

Name	Instructions	Version
Java development kit for Oracle Internet File System	Copy the latest adk.jar, email.jar, release.jar, repos.jar, utils.jar to $ORACLE_HOME/wireless/lib on Solaris, to %ORACLE_HOME%\wireless\lib on NT. Examples of ORACLE_HOME values: Solaris: ORACLE_HOME=/u01/iaswv20 NT: ORACLE_HOME=d:\oracle\iaswv20	1.1.6 or higher
Oracle Internet File System	Follow the Oracle IFS installation guide.	1.1.6 or higher
Server instance properties file (from the Oracle IFS server instance)	For each IFS server instance, its properties file is needed on the iASW 2.0 server. Copy the properties file (for example: oracle.ifs.server.properties.IfsDefault.properties) so it's included in the OC4J classpath. Example: %ORACLE_HOME/wireless/server/classes	N/A

Configuration Parameters

The iFS module includes the following configuration parameters:

• ORACLE_SERVICES_PIM_IFS_SERVICES
  • Description: A list of IFS service names (they are simply aliases and are up to the user to name), separated by commas.

  • Default Value: ifsserver1, ifsserver2

  • Examples: myifs.oracle.com, myifs2.oracle.com

• ORACLE_SERVICES_PIM_IFS_SERVICENAMES
  • Description: A list of IFS server names, separated by commas. A server name is used when the IFS Java API looks up the client side properties for the IFS server. Therefore, these names must match the names of the properties files.

  • Default Value: Ifs1, Ifs2

  • Examples: IfsDefault1, IfsDefault2 (so the Java API will look for IfsDefault1.properties and IfsDefault2.properties)

• ORACLE_SERVICES_PIM_IFS_SERVICEPASSWORDS
  • Description: A list of IFS schema password (one for each server), separated by commas.

  • Default Value: ifspassword1,ifspassword2

  • Examples: welcome, manager

• ORACLE_SERVICES_PIM_IFS_DOWNLOADDIR
  • Description: The absolute path for the local directory that is used for temporarily storing downloaded IFS files.

  • Default Value: /temp/ifs

  • Examples: d:\temp\ifs

18.1.7.2 Linking to the iFS Module

You can link to the iFS Module using the following virtual URL:

omp://oracle/services/pim/ifs

Input Call Parameters

The iFS module includes the following call parameters and parameter groups:

Table 18-22 The IFSAction Input Parameter

Parameter Name	Mandatory	Description	Valid Value
IFSAction	Yes	The type of action to be performed.	UPLOAD (for uploading a file to the IFS server.) DOWNLOAD (for downloading a filed to the IFS server.) If the value is UPLOAD, then IFSAction requires uploadIfsRequest. If the value is DOWNLOAD, then the downloadIfsRequest output is triggered.

uploadIfsRequest

This optional group includes the following parameters:

Table 18-23 Parameters of the uploadIfsRequest Group

Parameter Name	Mandatory	Description	Valid Value
LOCALPATH	Yes	The absolute local path of the file to be uploaded to the iFS Server.	A string. For example: LOCALPATH=/private/joe docs/file.doc LOCALPATH=c:\TEMP\RESUME.PDF
OBJNAME	No	Enables the user to rename the uploaded file rather than keeping the file name given in LOCALPATH. Note: This name must conform to the UNIX file system convention. For example, it cannot contain the back-slash (\).	A string. For example, OBJNAME=Renamed File.doc

Output Parameters

The Oracle iFS module includes the following output parameters:

downloadIfsInfo

This optional group specifies such information about the downloaded file as the size of the downloaded file, its location, and its original name.

The downloadIFsInfo group includes the following parameters:

Table 18-24 Parameters of the IFsInfo Group

Parameter Name	Mandatory	Description	Valid Value
IFSPATH	Yes	The absolute path of the downloaded file.	A string, for example: IFSPATH=/private/joe/download/file.doc IFSPATH=C:\TEMP\RESUME.PDF
IFSORIGPATH	Yes	The original IFS path of the downloaded file.	A string, for example: IFSORIGPATH=/ifshome/joe/file.doc
IFSNAME	Yes	The original name of the downloaded filed. This name is provided for display in the user interface.	A string, for example: IFSNAME=file.doc IFSNAME=RESUME.PDF
IFSSIZE	Yes	The size (in kilobytes) of the downloaded file.	Double. For example: IFSSIZE=12.4

Examples

To upload, files.doc, from the directory/private/joe/docs and save it as newfile.doc, you must configure the parameters as follows:

IFSACTION=UPLOAD

LOCALPATH=/private/joe/docs/file.doc

OBJNAME=newfile.doc

To download files.doc from the Oracle iFS Server, configure the parameters as follows:

IFSACTION=DOWNLOAD

IFSPATH=/private/joe/download/file.doc

IFSNAME=file.doc

Output Parameter: IFSORIGPATH=ifshome/joe/file.doc

Output Parameter: IFSSIZE=15.0

18.1.8 Fax Module

The fax module 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 18-25 Required Software for the Fax Module

Name	Instructions	From Version(s)
RightFax Server (available from RightFax)	Install the RightFax server.	7.2
RightFax Integration Module (available from RightFax)	Install the Integration module on fax server.	7.2
RightFax PFD module (available from RightFax)	Install the PFD module 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

This module does not require scripts.

Sample Cover Page

Since the fax module 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.

Configuring the Fax Module

The fax module includes the following configuration parameters:

• ORACLE_SERVICES_PIM_FAX_HOST
  • Description: Fax server URL. The Fax module performs fax transactions through this server.

  • Default Value: http://localhost

  • Example: http://144.25.172.183

• ORACLE_SERVICES_PIM_FAX_SENDER
  • Description: The default user to be used when submitting fax transactions to fax server.

  • Default Value: Administrator

  • Valid Values: registered user account in designated fax server

• ORACLE_SERVICES_PIM_FAX_RECORDS_PER_USER
  • Description: The maximum number of fax history records kept in database for each user.

  • Default Value: 20

  • Valid Values: non-negative integers

• ORACLE_SERVICES_PIM_FAX_ITEMS_PER_PAGE
  • Description: The maximum number of fax history records displayed in a page.

  • Default Value: 9

  • Valid Values: non-negative integer

• ORACLE_SERVICES_PIM_FAX_DEBUG
  • Description: Whether to keep log information in the system log file.

  • Default Value: false

  • Valid Values: true, false

• ORACLE_SERVICES_PIM_FAX_LDAP_ENABLED
  • Description: Whether to enable Directory module in searching recipient. Generally set to true only if Directory has fax number information.

  • Default Value: false

  • Valid Values: true, false

• ORACLE_SERVICES_PIM_FAX_DOWNLOADDIR
  • Description: The absolute path for the local directory that is used for temporarily storing downloaded files.

  • Default Value: /temp/fax

  • Valid Values: /private/joe/temp/fax

18.1.8.1 Linking to the Fax Module

You can link to the fax module using the following virtual URL:

omp://oracle/services/pim/fax

The fax module has one input call parameter, FAXTODO. This parameter describes the type of actions to be performed. This mandatory input parameter includes the following values:

Table 18-26 Values of the FAXTODO Input Parameter

Value	Requirement	Triggers Output
NEWFAX	SendNewFax	SendNewFaxResult.
STATUS	faxID	CheckFaxStatusResult
DELETE	faxID	deleteFaxResult
FWD	forwardFax	forwardFaxResult

sendNewFax

The FAXTODO parameter includes sendNewFax group. This mandatory group of parameters specify the information about the fax to be sent.

Table 18-27 Parameters of the sendNewFax Group

Parameter Name	Mandatory	Description	Valid Value
SENDER_NAME	No	Sender name.	A string. For example: SENDER_NAME=Joe Smith
SENDER_CORP	No	Sender company.	A string. For example: SENDER_CORP=Oracle Corp.
SENDER_PHONE	No	Sender phone number.	A string. For example: SENDER_PHONE=1(650)123-4567
SENDER_FAX	No	Sender fax number.	A string. For example: SENDER_FAX=1(650)123-4567
SENDER_ADDRESS	No	Sender address.	A string. For example: SENDER_ADDRESS=Home address
SENDER_NOTES	No	Other sender information not listed above.	A string. For example: SENDER_NOTES=email: joe.smith@oracle.com
RECIPIENT_NAME	No	Recipient name.	A string. For example: RECIPIENT_NAME=John White
RECIPIENT_CORP	Yes	Recipient company.	A string. For example: RECIPIENT_CORP=1(650)123-4567
RECIPIENT_PHONE	No	Recipient phone number.	A string. For example: RECIPIENT_PHONE=1(650)987-6543
RECIPIENT_FAX	Yes	Recipient fax number.	A string. For example: RECIPIENT_FAX=1(650)123-4567
RECIPIENT_ADDRESS	No	Recipient address.	A string. For example: RECIPIENT_ADDRESS=Work address
MESSAGE	No	Short message to be written on cover page.	A string. For example: MESSAGE=An awesome resume!
ATTACHMENT	No	Attachment to be faxed.	A string. For example: ATTACHMENT=mydoc/resume.pdf

forwardFax

The FAXTODO parameter includes the forwardFax group. This mandatory group includes the following parameters:

Table 18-28 Parameters of the forwardFax Group

Parameter Name	Mandatory	Description	Valid Value
FAXID	Yes	The unique id of the fax to be forwarded.	A string. For example: FAXID=12345
RECIPIENT_FAX	Yes	The destination fax number.	A string. For example: Example: RECIPIENT_FAX=1(650)123-4576

Output Parameters

The Fax module includes the following output parameters:

Table 18-29 Output Parameters of the Fax Module

Parameter	Mandatory	Description	Valid Value
sendNewFaxResult	Yes	Whether the fax was successfully sent or not.	A string. For example: sendNewFaxResult=Fax has been successfully submitted for sending.
checkFaxStatusResult	Yes	The fax status.	A string. For example: checkFaxStatusResult=Sending(50%)
deleteFaxResult	Yes	Whether the fax was successfully deleted or not.	A string. For example: deleteFaxResult=Fax successfully deleted.
forwardFaxResult	Yes	Whether the fax was successfully forwarded or not.	A string. For example: forwardFaxResult=Fax has been successfully submitted for forwarding.

Examples

To send a fax, you configure the FAXTODO parameters as follows:

FAXTODO = NEWFAX

RECIPIENT_FAX = 1(650)987-6543

MESSAGE = Hello world!

sendNewFaxResult = Fax has been successfully submitted for sending.

To check the status of a fax you configure the FAXTODO parameters as follows:

FAXTODO = STATUS

faxID = 16543

checkFaxStatusResult = OK

18.1.9 Tasks

The tasks module enables users and applications to schedule and manage tasks. This module integrates with Lotus and Exchange servers.

Requirements

This service implements two distinct modes, both with the same user experience but with different back-ends. In its Lotus Domino mode, it fully integrates with a Lotus Domino server to enable mobile Domino users. In its Microsoft Exchange Mode, it fully integrates with a Microsoft Exchange server to mobile enable Exchange users.

The Tasks module requires the following third-party software:

Table 18-30 Software Required for the Tasks Module

Name	Instructions	From Version
MS Exchange	[Exchange Mode] Install the Microsoft Exchange Server.	5.5
MS IIS	{Exchange Mode] Install the Microsoft Internet Information Server.	4.0
MS CDO	{Exchange Mode] Collaborative Data Objects. Available with Exchange SDK. The cdo.dll library must be installed on the IIS Server.	1.2.1
Oracle9iAS Wireless 2.0 Exchange ASP(Shipped with Oracle9iAS Wireless)	[Exchange Mode] Create any directory on the IIS server. Copy all the files in $ORACLE_HOME/iaswv20/wireless/j2ee/applications/modules/modules-web/pim/tasks/asp/ for a Solaris install, %ORACLE_HOME%\iaswv20\wireless\j2ee\applications\modules\modules-web\pim\tasks\asp\ for an NT install to just created directory on the IIS server. Invoke the properties dialog box for this directory. Choose the Directory tab. Click the "Edit" button for the "Anonymous Access and Authentication Control", make sure the following check boxes are set as follows: Allow Anonymous Access - unchecked Basic Authentication - checked Windows NT Challenge/Response - checked
Lotus Java SDK	[Domino Mode] Install the Lotus Domino Toolkit for Java/CORBA, add NCSO.jar to the classpath for Oracle9iAS Wireless 2.0. Installing the toolkit creates a "DTJava" directory on the file systemCopy the DTJava/lib/NCSO.jar to $ORACLE_HOME/wireless/lib on Solaris, to %ORACLE_HOME%\wireless\lib on NT. Examples of ORAClLE_HOME values: Solaris: ORACLE_HOME=/u01/iaswv20 Windows NT: ORACLE_HOME=d:\oracle\iaswv20 Ensure 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". 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	R5

This module does not require scripts.

Configuring the Task Module

The Task Module includes the following configuration parameters:

• ORACLE_SERVICES_PIM_TASKS_CLASS
  • Description: The service implementation class, which determines whether the Domino or Exchange mode is used.

  • Default Value: None

  • Valid Values: oracle.panama.module.pim.tasks.exchange.ExchangeTaskService for Exchange server
    
    oracle.panama.module.pim.tasks.domino.DominoTasksService for Lotus Domino server.

• ORACLE_SERVICES_PIM_TASKS_SERVER_NAME
  • Description: Designates the Exchange server or Domino server host name.

  • Default Value: None

  • Valid Values: exchange.mycompany.com
    domino-server.mycompany.com

• ORACLE_SERVICES_PIM_TASKS_SERVER_DATA_WEB_LINK
  • Description: If Exchange mode is selected, this is the URL pointing to the Oracle9iAS Wireless Exchange Tasks ASP (Tasks.asp) running on IIS.

  • Default Value: None

  • Valid Values: http://iis.mycompany.com/Oracle9iASW20/exchange/Tasks.asp

• ORACLE_SERVICES_PIM_TASKS_DOMAIN
  • Description: The domain attached to the user account information. This is free form field. If the Oracle9iAS Wireless instance supports multiple tasks servers, then these must have the same domain. Different PIM services with the same domain share the user account information.

  • Default Value: None

  • Valid Values: DominoDomain for the Domino Mode
    ExchangeDomain for Exchange.

18.1.9.1 Linking to the Task Module

You can link to the task module using the following virtual URL:

omp://oracle/services/pim/tasks