WebSphere Premises Server 6.1.0.1 | Software Interim Fix | APAR IC65622

• About this readme file
• Included in this interim fix
• Prerequisites
• Installation
• Optional Configuration
• Uninstallation
• Trademarks

About this readme file

This readme provides information about the patch available in this interim fix.

This fix can be installed on WebSphere Premises Server 6.1.0.1.

Included in this interim fix

The following reported program defects are fixed in this update:

• IC65622: missing events / extra messages in queues.

Prerequisites

Prerequisites for Microsoft Windows^® operating systems

• You must have Administrator access to update the WebSphere Premises server.
• It is assumed that the WebSphere Premises server is already installed.

Prerequisites for Linux^® operating systems

• You must have root access to update the WebSphere Premises server.
• It is assumed that the WebSphere Premises server is already installed.

Installation

Installation procedure for Microsoft Windows operating systems

1. Create a folder named maintenance in the WebSphere Premises server C:\Program Files\IBM\RFID directory.
2. Unpack the .zip file, IC65622.zip, to the C:\Program Files\IBM\RFID\maintenance directory. The .zip file contains these files:
   • IC65622\IBM_Premises_Server.ear
   • IC65622\IC65622-readme.html
3. Create a folder named backup in the C:\Program Files\IBM\RFID\maintenance\IC65622 directory.
4. Export the existing IBM_Premises_Server.ear to the C:\Program Files\IBM\RFID\maintenance\IC65622\backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
5. Apply this fix to the WebSphere Sensor Events server as described in the technote, Updating EAR files for WebSphere Premises Server.
6. Note: If running a custom application on the Premises server, custom EARs should have a startup value of 6 or higher so that they do not start before Premises.

Installation procedure for Linux operating systems

1. Create a folder named maintenance in the WebSphere Premises server /opt/IBM/RFID directory.
2. Unpack the .zip file, IC65622.zip, to the /opt/IBM/RFID/maintenance directory. The .zip file contains these files:
   • IC65622/IBM_Premises_Server.ear
   • IC65622/IC65622-readme.html
3. Create a folder named backup in the /opt/IBM/RFID/maintenance/IC65622 directory.
4. Export the existing IBM_Premises_Server.ear to the /opt/IBM/RFID/maintenance/IC65622/backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
5. Apply this fix to the WebSphere Sensor Events server as described in the technote, Updating EAR files for WebSphere Premises Server.
6. Note: If running a custom application on the Premises server, custom EARs should have a startup value of 6 or higher so that they do not start before Premises.

Installation procedure for WebSphere Premises Toolkit

1. Follow the instructions to install the toolkit and add the projects to a workspace.
2. Create a folder named maintenance in the RFID directory of the IBM project.
3. Unpack the .zip file, IC65622.zip, to the \IBM\RFID\maintenance directory. The .zip file contains these files:
   • IC65622\IBM_Premises_Server.ear
   • IC65622\IC65622-readme.html
4. Create a folder named backup in the \IBM\RFID\maintenance\IC65622 directory.
5. Follow the installation instructions for the Windows operating systems to install this fix in all WebSphere Application Server profiles used by the toolkit.

Optional Configuration

This APAR will now send an initialization event through the system on startup. If you want to monitor this event you can create a event template for it and set an expiration for it in WAS to remove it from the queue afterwards.

• To monitor the event follow these steps:
  • Create a new queue definition in WAS (e.g. premises.init.caches.q) and new output channel (e.g. premises.init.caches.channel).
  • Create a new Event Template */premises/command/initializeCache that points to the output channel (e.g. premises.init.caches.channel).
• To remove the messages automatically from the queue make the following change in the WAS admin console:
  • Go to WAS Admin -> Resources -> JMS ->Queues -> click on your target queue for your output channel.
  • Set the Expiry field to SPECIFIED
  • Go to Specified expiry
  • Enter a suitable value in milliseconds (e.g. If you want to keep the message around for 24 hours the value would be 86400000).

Uninstallation

Uninstallation procedure for Microsoft Windows operating systems

1. Reinstall the backup files as described in the technote, Updating EAR files for WebSphere Premises Server.

Uninstallation procedure for Linux operating systems

1. Reinstall the backup files as described in the technote, Updating EAR files for WebSphere Premises Server.

Trademarks

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

© Copyright IBM Corporation 2009. All Rights Reserved. Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.