sun.com | 1-800-123-4000 | How To Buy | My Sun | Worldwide Sites |  |  |  |  |

Table of Contents
Features Overview Pre-installation Considerations Installation Information Template Modifications Required Tips for Customizing Templates Known Issues |
#### Features Overview ##### Features New to Second Quaterly update for Client Devices Database ##### Features Inherited from Prior Patch Consolidations First Quaterly Update for Client Device Database Fixes to incorporate latest version of FEDI binaries Fixes for I18N release Miscellaneous Fixes on top of Mobile Access 6.2 This patch has been tested against the phones and simulators Mobile Access 6.2 was ceritified. It has not been tested against all the devices which a customer might be using. Different devices may need to some extra settings to work properly. Please refer to the documents for Mobile Access 6.2 at Mobile Access Documents for more information on how to make different devices work with Mobile Access 6.2 For a list of patches that are obsoleted by refer to the included patch is not a standalone installation and does not include Portal Server : Mobile Access 6.2. Portal Server : Mobile Access 6.2 I18N bits. Portal Server: Mobile Access 6.2 must be installed prior to upgrading to or installing the patch. I18N bits needs to be installed separately and can be installed before or after installing the patch. . Back to top
#### Pre-installation Considerations In addition to the profile and flatfile changes listed in the Template Modifications Required section of the this document, there are also internal changes made that may directly affect how you use, test, or evaluate the product. As such, it is important that this patch, as with any other, be test thoroughly on a development or QA system prior to being put in to production. Additionally, because of the nature of Mobile Access 6x distribution and the customization requirements for the product, special attention should be given to JSP files that must be modified by the patch installer in order to fix defects, and/or for the product to continue functioning normally. There are some known issues with the patch too and the section of Known Issues must be reffered for the workaround. Back to top
#### Installation Information These installation instructions provide steps to install System Requirements This section describes the system requirements for
System Requirements for Mobile Access
Component | Description
Operating Environment | updates Portal Server : Mobile Access 6.2 software, and runs in the Solaris™ 8 and Solaris™ 9 operating environments.
Memory | Each Portal component should have a minimum of 1GB of main memory. This minimum requirement applies to proof of concepts (POCs), demo/test environments, and production systems alike.
OS Patches | No OS patches besides those required by the Portal Server Mobile Access base install are needed by
Installation Overview Please familiarize yourself completely with the release notes prior to attempting either installation of, or upgrade to, The following directories and files are included in `` : NOTE: The release notes are now stored in the patch directory itself so that they are able to be included with the rest of the patch on SunSolve. Installation Instructions NOTES: If the Portal Server : Mobile Access installation contains both a server node and one or more platform nodes, then `` must be applied on the server node first, then each additional platform node as well. must have the following releases applied prior to patch installation: Portal Server : Mobile Access 6.2 STEPS: In a terminal window, become root. Be sure the server and platform nodes on which you are currently installing are running and use the Solaris[tm] patchadd command to apply the patch.
# root@ps-server: /etc/init.d/amserver startall
starting auth helpers ... done. checking for directory server ... directory server already running done starting web server ... iPlanet-WebServer-Enterprise/6.0SP5 B10/31/2002 16:22 [LS ls1] http://ps-server.int.sun.com, port 80 ready to accept requests startup: server started successfully iPlanet-WebServer-Enterprise/6.0SP5 B10/31/2002 16:22 [LS ls1] http://ps-server.int.sun.com, port 8088 ready to accept requests startup: server started successfully done.
# root@ps-server: patchadd

- Apply the patch using `patchadd` to other installed nodes on separate machines.

Back to top

#### Template Modifications Required

Every attempt is made by the patch installer to both preserve customized template information and automate the update of that information. Any modified template files are backed up in the same directory as their updated counterparts with the patch name postfixed to the template name. For example, `/etc/opt/SUNWps/desktop/default/MyFrontPageTabPanelContainer \ /Netlet/display.template` might be backed up to `/etc/opt/SUNWps/desktop/default/MyFrontPageTabPanelContainer/ \ /Netlet/display.template.pre
` . However some of the template files are overwritten by the patch because the changes are to complicated to be done in postpatch scripts.This patch modifies the following JSPs.

SUNWps/web-src/jsp/default/mail/aml/compose.jsp
SUNWps/web-src/jsp/default/mail/wml/compose.jsp
SUNWps/web-src/jsp/default/mail/wml/composegui.jsp
SUNWps/web-src/jsp/default/mail/wml/reply.jsp
SUNWps/web-src/jsp/default/ab/aml/changeGroup.jsp
SUNWam/web-apps/services/config/auth/default/aml/register.jsp
SUNWam/web-apps/services/config/auth/default/wml/register.jsp

If these JSPs have been customized before applying the patch, please keep a backup copy for these JSPs BEFORE applying the patch and then redo your customization.

Back to top

#### Tips for Customizing Templates

Because the Portal Server: Mobile Access itself is so customizable, you should follow some precautions to insure that any customizations made to the Portal Server: Mobile Access are preserved after a product upgrade. First, set up a customized template directory if you have not already done so. While this directory could be an entire subset of the default template directory, it is advisable to only copy over those template files that you will be customizing. This particular scheme would then use the default directory as a 'base' for all templates and would help insure that customized templates are not accidentally overwritten when the default templates are modified.
NOTE: Files in the default template directory should should never be customized.

As a general rule of thumb, avoid modifying templates that have only a functional purpose rather than a look and feel purpose. One example of a template that should not need modifications is the `NetletProvider/display.template` . This template contains only JavaScript necessary for the launching of the Netlet. The contents of the Netlet Pop-up window should instead be customized by modifying the associated `.properties` file. The reason for this is that there could be a functional change in the product that would overwrite a customization done specifically to that particular template file. This example also exhibits why it is important to only keep customized files in the customized template directory.

Back to top

#### Known Issues

Bug# 4981013:

Issue: After Login into portal from IE on Win2K, Some Japanese and Chinese character are displayed as ?

WorkAround: login to amconsole->Service configuration->GLobalization Settings. Select the language and click edit. Add UTF-8 to Supported Charsets, click Ok. Save The Globalization settings.

Bug# 5016588:

Issue: If we add/change contents on Mail Application or Calender application for Japanese locale using phones like D503i, P503i the contents get corrupted.

WorkAround: None Avaliable. Working on fixing the problem.

Bug# 5016717:

Issue: If we login to portal using JHTML phones in cookie less mode it gives server error.

WorkAround: None Avaliable. Working on fixing the problem

Back to top

Company Info | Contact | Terms of Use | Privacy | Copyright 1994-2003 Sun Microsystems