The mobile mail application is an email client that works in conjunction with the address book. Like the calendar and address book applications, mail is accessed through the main menu on the mobile desktop. The mail option provides access to the mail channel, which provides an option to launch the mail application.
Control passes to the mail home page, which is presented by the summary.jsp file. This display page summarizes the messages, and provides options for managing Inbox, composing a new message, and accessing other folders. This page can also provide the option for messages to be collected from a POP server if the Collections option has been properly configured. The possible options for the email home page appear as follows:
Inbox contains a From line at the top of the screen indicating the range of messages that are currently viewable. If Inbox contains more messages, an option labeled More appears at the bottom of the page. When users select that option, the current page is reloaded and the From line is updated to reflect the new range of messages that are then viewable.
The range is updated on screen because, in the code, the start index value for the new range is set to increase by an increment of 1 over the end index value displayed in the previous range. This process loads the next set (page) of messages.
Within Inbox or other mailboxes—though Inbox is the most common mailbox within which to set views—users see the messages that are visible depending upon which view, if any, Inbox is set to. If one or more views have been configured, the View option becomes available.
When the View option is available, the option that by default is labeled MailHm changes to a menu option; therefore, the option no longer brings users to the mail home page, but instead offers users different view options. When users select the menu option, they see the “All messages” option and they see an option for each view that they have configured.
Views are pre-configured rules that determine which messages are visible on screen.
Users perform the following steps:
Log in to the standard Portal Desktop with an HTML browser
Scroll to the Mail communication channel
Select Edit Mail (the pencil icon)
Click the Mobile Mail button.
Under the Mobile Mail Views heading, configure the Views using the following options:
Rules Configuration
Views Configuration
Device Views
Users first configure a rule (Rules Configuration). Then they add the rule to a view (View Configuration). Finally, they apply the view to their specific mobile devices (Device Views). Once users have finished editing the mobile mail preferences page, they return to their mobile devices, navigate to the Views option, and select the view they want. The Views option appears only if users have already configured a view.
Each email message is summarized to show the sender’s address and message subject. To view a message, users select the desired option, which passes control from the current page to the getmsg.jsp file, which fetches the message data from the server and forwards requests to the message.jsp file, which displays the subject and body of the message as well as the applicable options.
The possible options are the “List attachment(s)”, Next, and Previous. When available, these options appear at the bottom of the message body. The options Next, Previous, or both appear when next and previous messages are available to view. When users select one of these options, the respective message (next or previous) is loaded.
The “List attachment(s)” option appears when one or more attachments are attached to the message. When users select this option, control is passed to the attach.jsp file, and users are presented with a list of available attachments as links.
Users can click the link to view the attachment provided the attached file format is supported by the mobile device’s browser. If the file format is not supported by the mobile device browser, users will be prompted to download the file and view the downloaded attachment with suitable software.
After users have opened a message, they have a menu of other options available to them. This menu option is linked to the menu.jsp file. When users select this menu option, the menu page appears on their browsers. This page provides users with the following options: Reply, Delete, Forward, Move To, Copy To, View header, Mailbox, and Fax.
The Reply option provides users with a dialog for replying to the sender’s message. When users select this option control passes to the reply.jsp file, which asks users if the reply should go only to the sender, or to everyone included in the original email. To answer this question, users select To Sender or To All, both of which pass control to the compose.jsp file. This action brings up the compose page on users’ browsers, where they can compose a message (see Compose).
The Delete option deletes the message. Control passes from the current page (the menu.jsp file) to the delete.jsp file, and then back to Inbox.
The Forward option sends the message already received to another recipient, which passes control to the pickaddr.jsp file. Users are then able to select a recipient from the list of stored contacts. Users select the recipients to include, which passes control to the compose.jsp file. If no address book channel is configured, control passes to the compose.jsp file directly. For details about the compose page, see Compose.
The Move To option moves the message to a specified folder, deleting the message from Inbox in the process. When users select this option, control passes to the getfolders.jsp file, which fetches the folder names from the server, then forwards users to the folders.jsp file, which displays the available list of folders. A New Folder option also appears, enabling users to create a new folder if desired (see Folders).
The Copy To option behaves exactly as Move To, except that the original message is left in Inbox after the operation.
The View header option links to the header.jsp file, and displays the following email header fields: from, date, subject, and to. This screen simply displays information. Users are not presented with additional choices.
The Mailbox option returns users to the currently selected mailbox. In this case, when users select this option, control returns to Inbox.
The fax feature enables the hand held device users to send a document to a fax machine. The fax machine can be any where, including a local fax machine where the user wants the document in a printed form. In this release, we address one feature where the user can fax one or more documents that are available as a received email attachment(s).
The compose page (the compose.jsp file), is where users compose a new email message. The Compose option is available in the mail home page, which is presented by the summary.jsp file:
When users select this option, control is first passed to the pickaddr.jsp file, (even when an address book communication channel has not been configured), then control is passed to the compose.jsp file. The compose page prompts users for standard email fields, such as: to, cc, subject, and message body. The interface is intuitive; users simply supply the requested fields, submit the message, and return to Inbox.
An email message composed on a mobile device can be time-consuming; therefore, users are allowed to define up to nine preset messages. These predefined replies can be selected for inclusion at the beginning of the compose screen. You can create a predefined reply using the Portal Server 7.1 CLI. For more information on creating a predefined reply using a CLI, see the Sun Java System Portal Server 7.1 Command Line Reference guide.
Follow the procedure, to create a predefined reply using the Portal Server 7.1 administration console.
Log in to the standard Portal Server 7.1 with an HTML browser
Scroll to the Mail channel
Click Edit Mail (the pencil icon)
Click the Mobile Mail button.
Predefined replies have a 30-character maximum limit.
After users click the Folders option in the mail home page— which is presented by the summary.jsp file—they are able to view or create a specific folder. When users select the Folders option, control is passed to the getfolders.jsp file, which fetches the folder names from the server and forwards requests to the folders.jsp file, which then displays the available list of folders. A New Folder option also appears, allowing users to create a new folder if needed.
When users select the New folder option, control passes from the current page (the folders.jsp file), to the newFd.jsp file, which prompts users for the name of the folder. Control then passes to the doNewFd.jsp file, which creates the new folder. Users then return to the folders page by following the Folders option that appears after the new folder has been created.
When users select an existing folder, control passes to the folderMenu.jsp file, which provides users with three options from which to select: Open, Rename, or Delete.
The Open option reloads Inbox screen (passing control to the doInbox.jsp file), substituting the selected folder data for Inbox data.
The Rename option passes control to the renameFd.jsp file, which prompts users to enter a new name for the folder.
The Delete option passes control to the delFd.jsp file, which deletes the folder.
All three links eventually present users with a Folders option that returns control to the folders.jsp file.
The Collections option can be made available in the mail home page, which is presented by the summary.jsp file. The Collections option allows users to view mail on their mobile devices that was collected from a POP mail server.
Users perform the following steps:
Log in to the standard Portal Desktop with an HTML browser.
Scroll to the Mail channel.
Click Edit Mail (the pencil icon).
Click the Mobile Mail button.
Under the Mobile Mail POP Collections heading, select Add.
Populate the fields of the POP Information box with the details for the POP server to which users want to connect.
Click Finished.
Once users have finished editing the mobile mail preferences page, they return to their mobile devices where they see the Collections option in the mail home page.
Mobile Access includes functionality to convert images into forms that can be displayed on mobile devices. However, large images are not displayed.
For example, images can be converted from .png format to .wbmp format if the target device supports only .wbmp. The image transcoding component can read .gif, .jpeg, .bmp, .wbmp, and .png image types and convert them into .jpeg, .bmp, .wbmp, and .png target types.
The image transcoding component can also scale images to fit the mobile device screen. Content developers can pass their images through the image transcoding servlet which is deployed along with the portal application. It takes the following parameters:
1. Image source - This could be an URL to an image within the portal application, or a complete URL to an image in some other location.
2. ScaleX - The horizontal width to which the image must be scaled.
3. ScaleY - The vertical width to which the image must be scaled.
Examples:
In XHTML files:
<img src="transcode?src=/images/logo.gif&scalex=100&scaley=150">
In AML files:
<AmlImage src="transcode?src=/images/logo.gif&scalex=100&scaley=150">