WebSphere^(R) Everyplace^(R) Access Version 4.3.0 Fix Pack 5 Interim Fix 2
Readme

WebSphere Everyplace Access Version 4.3.0 Fix Pack 5 Interim Fix 2 includes fixes to customer reported problems and additional enhancements to product functionality. This document provides an overview of what is contained in the Interim Fix.

If you have applied test fixes to either Everyplace Client 4.3.0 Fix Pack 5 or WebSphere Everyplace Access 4.3.0 Fix Pack 5, you might need to reapply them after installing this Interim Fix.

This Readme includes:

• Interim Fix 2 contents
• What's included in this interim fix
• Prerequisites and corequisites
• Installing this interim fix
• Recommended configuration changes
• Uninstalling this interim fix
• Trademarks

Interim Fix 2 contents

The 4.3.0-WEB-WEA-IF0502.zip includes the following:

What's included in this interim fix

This interim fix includes fixes for Everyplace Synchronization Server. To correct some of these problems, client fixes are required. Refer to the Prerequisites and corequisites section for details. This interim fix includes corrections for the following problems:

Interim Fix 2

• APAR PQ81870 Synchronization Server hangs at the end of a synchronization session because the connections to the Domino servers are left in the CLOSE_WAIT state. This problem has been fixed.
  
  
• APAR PQ83059 An OutOfMemoryError occurs during synchronization. This problem has been fixed. If the SyncObj has a large number of exceptions and the logging levels are high, Synchronization Server can run out of memory. This error is most likely to happen when synchronizing multiple changes to a calendar event with a large number of invitees. A change has been made to reduce the number of exceptions that occur during these kinds of synchronizations. Administrators can also lower the logging levels.
  
  
• APAR PQ81890 Synchronization of calendar and contacts fails and the Synchronization Server is unresponsive. This problem has been fixed.
  
  
• APAR PQ82904 Synchronizing large e-mail attachments with Microsoft Exchange 5.5 is slow. This problem has been fixed.
  
  
• APAR PQ82961 Meeting invitations accepted on Pocket PC are converted to appointments when users synchronize their e-mail and calendar separately. This problem has been fixed.
  
  
• APAR PQ83123 Users and superuser unable to connect to the mail file because the login name is case sensitive. This problem has been fixed. The login names are no longer case sensitive.
  
  
• APAR PQ82816 When synchronizing the calendar, a NullPointerException occurs. This is caused by the data from the e-mail server having a null time stamp. This problem has been fixed.
  
  
• APAR PQ81861 If the Synchronization Server administrator doesn't have read/write access to the syncing user's database, the user is not able to synchronize. This problem has been fixed. The user can now synchronize if the administrator only has read access to the database.
  
  
• APAR PQ83471 The extensions in the attachments filter are case sensitive. This problem has been fixed. The extensions in the attachments filter are no longer case sensitive.
  
  
• APAR PQ84378 An occasional problem where a nullPointerException is thrown when synchronizing calendar entries has been fixed.
  
  
• APAR PQ85601 On Microsoft Exchange 5.5 server, if a user replies to an e-mail from an SMTP address using the display name format ("display name" ) or an address containing invalid characters or misspellings, the message cannot be delivered or synchronized properly. This problem can occur anytime an e-mail address does not resolve with the address book, and an SMTP address needs to be written to the TO: field. This problem has been fixed.
  
  
• Users are denied permission to synchronize with Lotus Domino databases because the access control level checks of groups are case sensitive. This has been fixed.
  
  
• APAR PQ81855 The following nullPointer exception that occurred in the appserver-stderr.log file has been fixed. It was an extraneous error message that did not cause any problems. With the fix, the message will no longer be written to the log.
  java.lang.NullPointerException at Com.Starfish.SyncMLServer.parser.WBXML.estimatedSerializedSize(WBXML.java:909)
  
  
• After an initial synchronization of a large amount of data, the subsequent synchronizations are slow synch. This problem has been fixed.
  
  
• APAR PQ83238 and PQ84749 Non-alphanumeric data may prevent a successful sync of Tasks which is indicated in the device sync log by error 500 with return code 31. This problem has been fixed.
  
  
• Synchronizing a task containing rich text causes tasks not to synchronize properly. This problem has been fixed.
  
  
• A problem where all-day events created on the server were not synchronizing to the P900 device has been fixed.
  
  
• When tasks are synchronized from the client to server, the status of the task is sometimes changed from Not Complete to In Progress. This problem has been fixed.
  
  
• APAR PQ85895 A problem where Synchronization Server was hanging and users could not log in has been fixed.
  
  
• APAR PQ80424 A problem where e-mails that were moved to a folder on the server were not synchronizing to the correct corresponding folders on the device has been fixed.
  
  
• APAR PQ84389 When synchronizing meeting invitations with a Microsoft Exchange 2000 server, invitee names that contain double-byte characters do not appear correctly on the device. This problem has been fixed.
  
  
• APAR PQ84393 After synchronizing invitation acceptance notices with Lotus Domino, the subject line is occasionally empty on the device. This problem has been fixed.
  
  
• APAR PQ86514 A problem where duplicate attachments appeared on the server when you synchronized attachments from the device has been fixed. This sometimes occurred with attachments with long names that contained spaces.
  
  
• When there is a conflict between the information on the server and the device, the information on the device is used regardless of the conflict resolution settings in the device profile. This problem has been fixed.
  
  
• When synchronizing with Microsoft Exchange 5.5, an occasional problem occurred when an instance of a repeating all-day event was deleted or changed. When users synchronize with the device, the date or time of the deleted or changed instance may be incorrect or a duplicate instance of the event is created. This problem has been fixed.
  
  
• When synchronizing recurring events from a device to Lotus Domino, a time zone-related problem occurred where the first date for the recurring event was missing from the calendar. This occurred when the server and device were set to a different time zone than Synchronization Server. This problem has been fixed.
  
  
• When synchronizing with Microsoft Exchange 5.5, a problem occurred where recurring event invitations that were synchronized to the device and then accepted did not contain the recurring event information. Instead of setting multiple dates on the calendar for the recurring event, the invitation only set a single event on the calendar. This problem has been fixed.
  
  

Prerequisites and corequisites

This interim fix requires:

1. IBM WebSphere Everyplace Access 4.3.0 Fix Pack 5
2. If using Microsoft Window 2000 Server, service pack 4 is required.

To download updates and fixes for additional WebSphere Everyplace Access components or clients that you may be using, visit the following location: http://www.ibm.com/software/pervasive/ws_everyplace_access/support/

Installing this interim fix

When you install this interim fix, the Domino MapDir.nsf databases are replaced with new mapping databases. However, the Domino MapDir.nsf databases are backed up during the install to the following location: <WebSphere>\IBMSyncServer\Fix\FixPack<yyyymmddhhmm>\Backup\Notes\Data\esm. The variable <yyyymmddhhmm> represents the interim fix number where yyyy represents the year, mm represents the month, dd represents the day, hh represents the hour, and mm represents the minutes.

The template/form mapping definitions have been changed to more easily manage custom mappings and updates to the standard mapping definitions. Previously, both the standard and custom mappings were contained in a single database: esm\mapDir.nsf. In this release, the custom mappings are located in esm\custom mapDir.nsf. Users who create custom PIM mapping databases (i.e. MemoMap.nsf, PersonMap.nsf) should now copy them into this new custom folder. Synchronization Server will read the custom database after it reads the standard mappings in esm\mapDir.nsf. All new mappings it finds are added to the existing list. Any mappings that are already in this list are replaced by the ones specified in the custom database. The standard mapping databases are now read only, and any custom mappings should be put in a custom database.

Note: If Everyplace Synchronization Server components, such as the server, database and portlets, are installed on different machines, the interim fix installation should only be run on the machine that contains the server component.

To install this interim fix, do the following:

1. Using the WebSphere Application Server Administrator's Console, stop the Everyplace Synchronization Server AppServer.
   1. Open the console and expand the Nodes folder, the host node and finally the Application Servers folder.
   2. Select the Everyplace Synchronization Server and click the Stop icon.
2. Shutdown the Everyplace Synchronization Server process if it is started. You can do this from the Windows Services panel or from Stop Local Server command in the Everyplace Synchronization Server program group.
   For AIX:
   
   1. Execute the command:
      <WebSphere>/IBMSyncServer/caf/bin/esscmd shutdown
   2. Verify that no other esscmd processes are running using the command:
      ps -aef|grep esscmd
   3. Verify that no Everyplace Synchronization Java processes are running using the command:
      ps -aef|grep caf.jar
3. If you have previously enabled SyncML traces on the server and renamed or removed either tss-server.jar or tss-server_debug.jar from the directory <WebSphere>\IBMSyncServer\app\ess.ear\ESSBase.war\WEB-INF\lib, then you need to restore those files before running the interim fix install.
4. From the temporary directory where you extracted the files, run the following command and follow the on-screen prompts:
   Windows:
   cd disk1
setup.exe
   
   AIX:
   Make sure all mounted file systems are accessible. Run df. If the installation seems to hang, enter Ctrl+C and unmount or fix the mount that is failing.
   > export WAS_HOME=/usr/<WebSphere>/AppServer
> export ESS_HOME=/usr/<WebSphere>/IBMSyncServer/caf
   Note: For the following two commands, make sure there is a space between the period "." and the forward slash "/".
   > . /home/<weainst>/sqllib/db2profile
   where <weainst> is the common instance in which the Everyplace Synchronization Server database is installed.
   > . /home/<weainst>/sqllib/java12/usejdbc2
env | grep DB2INST
   to verify that the commands completed successfully. The DB2 instance name should be echoed.
   cd disk1
> chmod +x setupAix.bin
> ./setupAix.bin

   If you receive a message during the installation that caf.jar is in use, reboot the machine and install the interim fix again.

5. If install is unsuccessful, see the Known Problems section of the Everyplace Synchronization Server Release Notes.
6. Start the Everyplace Synchronization Server application from the WebSphere Application Server Administrator's Console and the Everyplace Synchronization Server process.
7. Regen WebSphere Plugin configurations by following these steps:
   1. Open the WebSphere Application Server Administrator's Console.
   2. Expand the tree to the WebSphere Portal node.
   3. Right-click the node and select Regen WebSphere Plugin.

Recommended configuration changes

For information about recommended configuration changes and performance tuning procedures, see the Everyplace Synchronization Server Release Notes.

Uninstalling this interim fix

To uninstall this interim fix, do the following:

1. If you are using Windows, reboot the system.
2. Using the WebSphere Application Server Administrator's Console, stop the Everyplace Synchronization Server AppServer.
   1. Open the console, expand the Nodes folder, the host node and finally the Application Servers folder.
   2. Select the Everyplace Synchronization Server and click the Stop icon.
3. Shutdown the Everyplace Synchronization Server process if it is started. You can do this from the Windows Services panel or from Stop Local Server command in the Everyplace Synchronization Server program group.
   For AIX:
   
   1. Execute the command:
      <WebSphere>/IBMSyncServer/caf/bin/esscmd shutdown
   2. Verify that no other esscmd processes are running using the command:
      ps -aef|grep esscmd
   3. Verify that no Everyplace Synchronization Java processes are running using the command:
      Ps -aef|grep caf.jar
4. Run the following command:
   
   Windows
   <WebSphere>\IBMSyncServer\Fix\FixPack<yyyymmddhhmm>\_uninst\uninstaller.exe
   
   AIX:
   Make sure all mounted file systems are accessible. Run df. If the installation seems to hang, enter Ctrl+C and unmount or fix the mount that is failing.
   > export WAS_HOME=/usr/<WebSphere>/AppServer
> export ESS_HOME=/usr/<WebSphere>/IBMSyncServer/caf
   Note: For the following two commands, make sure there is a space between the period "." and the forward slash "/".
   > . /home/<weainst>/sqllib/db2profile
   where <weainst> is the common instance in which the Everyplace Synchronization Server database is installed.
   > . /home/<weainst>/sqllib/java12/usejdbc2
env | grep DB2INST
   to verify that the commands completed successfully. The DB2 instance name should be echoed.
   <WebSphere>/IBMSyncServer/Fix/FixPack<yyyymmddhhmm>/_uninst/uninstaller.bin

5. If you followed the instructions in Recommended configuration changes when you installed this interim fix, you must undo those changes. You must also reset any devices to their previous Everyplace Client version.

6. Start the Everyplace Synchronization Server application within WebSphere Application Server Administrator's Console and the Everyplace Synchronization Server process.

Trademarks

IBM, WebSphere, and Everyplace are registered trademarks of the IBM Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

(c) Copyright International Business Machines Corporation 2002, 2004. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.