WebSphere Sensor Events 7.0 | Software Interim Fix | APAR IC74503

• 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:

• IC74503: Solves a problem relating to some attributes not being retrieved from Maximo Asset Management.

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.

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.

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, IC74503.zip, to the C:\Program Files\IBM\WSE\maintenance directory. The .zip file contains these files:
   • IC74503\IBM_WSE_Admin_Console.ear
   • IC74503\IBM_WSE_Engine.ear
   • IC74503\IBM_WSE_Runtime.ear
   • IC74503\WSE70WBELocationProject.xml
   • IC74503\wseClient.jar
   • IC74503\alert_filter.xml
   • IC74503\IC74503-readme.html
   • IC74503\WebSphere_Sensor_Events.IC74503.fxtag
3. Create a folder named backup in the C:\Program Files\IBM\WSE\maintenance\IC74503 directory.
4. 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.handleAlertFilter
     • JNDI: eis/ibmse.handleAlertFilter.as
     • Destination Type: Topic
     • Destination JNDI Name: jms/ibmse
     • Message Selector: ibmse LIKE 'report/Asset/observation/location/alert/%' or ibmse LIKE 'report/asset/observation/location/zoneentry' or ibmse LIKE 'report/asset/observation/location/zoneexit'
     • Bus Name: ibmsensorevent
   • Click OK
   • Click Save
5. Back up the existing IBM_WSE_Admin_Console.ear, IBM_WSE_Engine.ear, and IBM_WSE_Runtime.ear to the C:\Program Files\IBM\WSE\maintenance\IC74503\backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
6. Apply this update to IBM_WSE_Admin_Console.ear, IBM_WSE_Engine.ear, and IBM_WSE_Runtime.ear as described in the technote, Updating EAR files for WebSphere Sensor Events.
7. Create a new cache instance:
   • Log on to WAS Admin Console
   • Navigate to Resources -> Cache instances -> Object cache instances
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Click New
   • Set the following values:
     • Name: Asset Management
     • JNDI Name: cache/assets
   • Click OK
   • Click Save
8. Modify AssetManagementAgent configuration:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration -> AssetManagementAgent
   • Click Add new Properties
   • Set the following values:
     • Name: cache.timeout
     • Value: timeout value is in second
   • Click Update PID
   • Click Update
9. Modify WBEAgent configuration:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration -> WBEAgent
   • Click Add new Properties
   • Set the following values:
     • Name: transform.userdata.for.wbe.rules
     • Value: true
   • Click Update PID
   • Click Update
10. Stop the WSE server.
11. Navigate to the C:\Program Files\IBM\WSE\lib directory and copy the wseClinet.jar file to the C:\Program Files\IBM\WSE\maintenance\IC74503\backup directory.
12. Navigate to the C:\Program Files\IBM\WSE\maintenance\IC74503 directory and copy the wseClinet.jar file to C:\Program Files\IBM\WSE\lib
13. Start the WSE server.
14. Import Alert Filter XML config:
    • Log on to WSE administrative console
    • Navigate to Data Capture Configuration -> Import Configuration
    • Click Choose File and select C:\Program Files\IBM\WSE\maintenance\IC74503\alert_filter.xml
    • Click Import
15. Re-deploy the WBE Rules and restart the WBE server.
16. Navigate to the C:\Program Files\IBM\WSE\maintenance\IC74503 and copy the WebSphere_Sensor_Events.IC74503.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, IC74503.zip, to the /opt/IBM/WSE/maintenance directory. The .zip file contains these files:
   • IC74503/IBM_WSE_Admin_Console.ear
   • IC74503/IBM_WSE_Engine.ear
   • IC74503/IBM_WSE_Runtime.ear
   • IC74503/WSE70WBELocationProject.xml
   • IC74503/wseClient.jar
   • IC74503/alert_filter.xml
   • IC74503/IC74503-readme.html
   • IC74503/WebSphere_Sensor_Events.IC74503.fxtag
3. Create a folder named backup in the /opt/IBM/WSE/maintenance/IC74503 directory.
4. 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.handleAlertFilter
     • JNDI: eis/ibmse.handleAlertFilter.as
     • Destination Type: Topic
     • Destination JNDI Name: jms/ibmse
     • Message Selector: ibmse LIKE 'report/Asset/observation/location/alert/%' or ibmse LIKE 'report/asset/observation/location/zoneentry' or ibmse LIKE 'report/asset/observation/location/zoneexit'
     • Bus Name: ibmsensorevent
   • Click OK
   • Click Save
5. Back up the existing IBM_WSE_Admin_Console.ear, IBM_WSE_Engine.ear, and IBM_WSE_Runtime.ear to the /opt/IBM/WSE/maintenance/IC74503/backup directory as described in the technote, Updating EAR files for WebSphere Sensor Events.
6. Apply this update to IBM_WSE_Admin_Console.ear, IBM_WSE_Engine.ear, and IBM_WSE_Runtime.ear as described in the technote, Updating EAR files for WebSphere Sensor Events.
7. Create a new cache instance:
   • Log on to WAS Admin Console
   • Navigate to Resources -> Cache instances -> Object cache instances
   • Set the Scope to Node=WSENode, Server=server1 if it is not already.
   • Click New
   • Set the following values:
     • Name: Asset Management
     • JNDI Name: cache/assets
   • Click OK
   • Click Save
8. Modify AssetManagementAgent configuration:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration -> AssetManagementAgent
   • Click Add new Properties
   • Set the following values:
     • Name: cache.timeout
     • Value: timeout value is in second
   • Click Update PID
   • Click Update
9. Modify WBEAgent configuration:
   • Log on to WSE Admin Console
   • Navigate to Data Capture Configuration -> Agent Configuration -> WBEAgent
   • Click Add new Properties
   • Set the following values:
     • Name: transform.userdata.for.wbe.rules
     • Value: true
   • Click Update PID
   • Click Update
10. Stop the WSE server.
11. Navigate to the /opt/IBM/WSE/lib directory and copy the wseClinet.jar file to the /opt/IBM/WSE/maintenance/IC74503/backup directory.
12. Navigate to the /opt/IBM/WSE/maintenance/IC74503 directory and copy the wseClinet.jar file to /opt/IBM/WSE/lib
13. Start the WSE server.
14. Import Alert Filter XML config:
    • Log on to WSE administrative console
    • Navigate to Data Capture Configuration -> Import Configuration
    • Click Choose File and select /opt/IBM/WSE/maintenance/IC74503/alert_filter.xml
    • Click Import
15. Re-deploy the WBE Rules and restart the WBE server.
16. Navigate to the /opt/IBM/WSE/maintenance/IC74503 and copy the WebSphere_Sensor_Events.IC74503.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_Admin_Console.ear, IBM_WSE_Engine.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 and re-deploy the origional WBE rules
4. Delete the WebSphere_Sensor_Events.IC74503.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_Admin_Console.ear, IBM_WSE_Engine.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 and re-deploy the origional WBE rules
4. Delete the WebSphere_Sensor_Events.IC74503.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 2010. All Rights Reserved. Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.