WebSphere Sensor Events 7.0 | Software Interim Fix | APAR IC76222

• About this readme file
• Included in this interim fix
• Prerequisites
• Installation
• 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 Sensor Events 7.0.

Included in this interim fix

The following reported program defects are fixed in this update:

• IC76222: Maximo reflects incorrect location when moving directly between two zones.

Prerequisites

Prerequisites for Microsoft Windows^® operating systems

• You must have Administrator access to update the WebSphere Sensor Events server.
• It is assumed that the WebSphere Sensor Events server is already installed.
• It is assumed that WebSphere Sensor Events interim fix - IC74503 is already installed.
• It is assumed that WebSphere Sensor Events interim fix - IC75050 is already installed.

Prerequisites for Linux^® and AIX^® operating systems

• You must have root access to update the WebSphere Sensor Events server.
• It is assumed that the WebSphere Sensor Events server is already installed.
• It is assumed that WebSphere Sensor Events interim fix - IC74503 is already installed.
• It is assumed that WebSphere Sensor Events interim fix - IC75050 is already installed.

Installation

Installation procedure for Microsoft Windows operating systems

1. Create a folder named maintenance in the WebSphere Sensor Events server C:\Program Files\IBM\WSE directory.
2. Unpack the .zip file, IC76222.zip, to the C:\Program Files\IBM\WSE\maintenance directory. The .zip file contains these files:
   • IC76222\IBM_WSE_RTAL_Client.ear
   • IC76222\IBM_WSE_Runtime.ear
   • IC76222\wseClient.jar
   • IC76222\IC76222-readme.html
   • IC76222\WebSphere_Sensor_Events.IC76222.fxtag
3. Create a folder named backup in the C:\Program Files\IBM\WSE\maintenance\IC76222 directory.
4. Back up the existing IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear to the C:\Program Files\IBM\WSE\maintenance\IC76222\backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
5. Apply this update to IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear as described in the technote, Updating EAR files for WebSphere Sensor Events.
6. Create a new WSE task agent:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration
   • Click Create Agent
   • Set the following values:
     • Agent Name: MobileZoneFilterTaskAgent
     • Agent Type: TaskAgentType
     • Description: MobileZoneFilterTaskAgent
   • Click Add PIDs to the Agent
   • Click Add Property
   • Set the following values (PID and two properties):
     • PID: com.ibm.se.las.alert.ejb.mdb.MobileZoneFilterTaskAgent
     • Property 1 name: mobile.zone.filter.delay.secs
     • Property 1 value: 10
     • Property 1 description: the number of seconds to hold the event before deciding if it is still valid and forwarding it on to WBE
     • Property 2 name: mobile.zone.filter.numthreads
     • Property 2 value: 5
     • Property 2 description: the number of threads to be used by the new MDB to process the incoming events
   • Click Save
7. Create a new activation specification:
   • Log on to WAS Admin Console
   • Navigate to Resources -> JMS -> Activation Specifications
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Click New
   • Select Default messaging provider
   • Set the following values for the new configuration:
     • Name: ibmse.handleMobileZoneFilter
     • JNDI: eis/ibmse.handleMobileZoneFilter.as
     • Destination Type: Topic
     • Destination JNDI Name: jms/ibmse
     • Message Selector: ibmse LIKE 'report/asset/observation/location/mobilezoneentry' OR ibmse LIKE 'report/asset/observation/location/mobilezoneexit'
     • Bus Name: ibmsensorevent
   • Click OK
   • Click Save
8. Modify the WBE activation specification:
   • Log on to WAS Admin Console
   • Navigate to Resources -> JMS -> Activation Specifications
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Select ruc.wbe.as
   • Append the following to its message selector: OR ibmse LIKE 'report/asset/observation/location/mobilezoneentry/filtered' OR ibmse LIKE 'report/asset/observation/location/mobilezoneexit/filtered'
   • Click OK
   • Click Save
9. Stop the WSE server.
10. Navigate to the C:\Program Files\IBM\WSE\lib directory and copy the wseClient.jar file to the C:\Program Files\IBM\WSE\maintenance\IC76222\backup directory.
11. Navigate to the /opt/IBM/WSE/maintenance/IC76222 directory and copy the wseClient.jar file to /opt/IBM/WSE/lib
12. Start the WSE server.
13. Navigate to the C:\Program Files\IBM\WSE\maintenance\IC76222 and copy the WebSphere_Sensor_Events.IC76222.fxtag file to the C:\Program Files\IBM\WSE\properties\version directory.

Installation procedure for Linux and AIX operating systems

1. Create a folder named maintenance in the WebSphere Sensor Events server /opt/IBM/WSE directory.
2. Unpack the .zip file, IC76222.zip, to the /opt/IBM/WSE/maintenance directory. The .zip file contains these files:
   • IC76222/IBM_WSE_RTAL_Client.ear
   • IC76222/IBM_WSE_Runtime.ear
   • IC76222/wseClient.jar
   • IC76222/IC76222-readme.html
   • IC76222/WebSphere_Sensor_Events.IC76222.fxtag
3. Create a folder named backup in the /opt/IBM/WSE/maintenance/IC76222 directory.
4. Back up the existing IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear to the /opt/IBM/WSE/maintenance/IC76222/backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
5. Apply this update to IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear as described in the technote, Updating EAR files for WebSphere Sensor Events.
6. Create a new WSE task agent:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration
   • Click Create Agent
   • Set the following values:
     • Agent Name: MobileZoneFilterTaskAgent
     • Agent Type: TaskAgentType
     • Description: MobileZoneFilterTaskAgent
   • Click Add PIDs to the Agent
   • Click Add Property
   • Set the following values (PID and two properties):
     • PID: com.ibm.se.las.alert.ejb.mdb.MobileZoneFilterTaskAgent
     • Property 1 name: mobile.zone.filter.delay.secs
     • Property 1 value: 10
     • Property 1 description: the number of seconds to hold the event before deciding if it is still valid and forwarding it on to WBE
     • Property 2 name: mobile.zone.filter.numthreads
     • Property 2 value: 5
     • Property 2 description: the number of threads to be used by the new MDB to process the incoming events
   • Click Save
7. Create a new activation specification:
   • Log on to WAS Admin Console
   • Navigate to Resources -> JMS -> Activation Specifications
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Click New
   • Select Default messaging provider
   • Set the following values for the new configuration:
     • Name: ibmse.handleMobileZoneFilter
     • JNDI: eis/ibmse.handleMobileZoneFilter.as
     • Destination Type: Topic
     • Destination JNDI Name: jms/ibmse
     • Message Selector: ibmse LIKE 'report/asset/observation/location/mobilezoneentry' OR ibmse LIKE 'report/asset/observation/location/mobilezoneexit'
     • Bus Name: ibmsensorevent
   • Click OK
   • Click Save
8. Modify the WBE activation specification:
   • Log on to WAS Admin Console
   • Navigate to Resources -> JMS -> Activation Specifications
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Select ruc.wbe.as
   • Append the following to its message selector: OR ibmse LIKE 'report/asset/observation/location/mobilezoneentry/filtered' OR ibmse LIKE 'report/asset/observation/location/mobilezoneexit/filtered'
   • Click OK
   • Click Save
9. Stop the WSE server.
10. Navigate to the /opt/IBM/WSE/lib directory and copy the wseClinet.jar file to the /opt/IBM/WSE/maintenance/IC76222/backup directory.
11. Navigate to the /opt/IBM/WSE/maintenance/IC76222 directory and copy the wseClient.jar file to /opt/IBM/WSE/lib
12. Start the WSE server.
13. Navigate to the /opt/IBM/WSE/maintenance/IC76222 and copy the WebSphere_Sensor_Events.IC76222.fxtag file to the /opt/IBM/WSE/properties/version directory.

Installation procedure for WebSphere Sensor Events Toolkit

1. Follow the Windows install instructions above.

Uninstallation

Uninstallation procedure for Microsoft Windows operating systems

1. Reinstall the backup IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear files as described in the technote, Updating EAR files for WebSphere Sensor Events.
2. Copy the backup wseClinet.jar file to C:\Program Files\IBM\WSE\lib
3. Undo the configuration changes made in the WSE and WAS admin consoles
4. Delete the WebSphere_Sensor_Events.IC76222.fxtag file from the C:\Program Files\IBM\WSE\properties\version directory.
5. Restart WebSphere Application Server.

Uninstallation procedure for Linux and AIX operating systems

1. Reinstall the backup IBM_WSE_RTAL_Client.ear and IBM_WSE_Runtime.ear files as described in the technote, Updating EAR files for WebSphere Sensor Events.
2. Copy the backup wseClinet.jar file to /opt/IBM/WSE/lib
3. Undo the configuration changes made in the WSE and WAS admin consoles
4. Delete the WebSphere_Sensor_Events.IC76222.fxtag file from the /opt/IBM/WSE/properties/version directory.
5. Restart WebSphere Application Server.

Uninstallation procedure for WebSphere Sensor Event Toolkit

1. Follow the Windows uninstall instructions above.

Trademarks

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

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