IZ73958: Add support for WAS 7.0 to the WebSphere ASM

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• The Websphere ASM does not support WAS 7. Changes need to be
  made for the subagent to work with WAS 7.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the websphere ASM with WAS 7.0 or later
  ****************************************************************
  PROBLEM DESCRIPTION:
  The WebSphere ASM that ships with SSM 4.0 does not support WAS
  7.0
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 10 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• Starting with WebSphere Fix 3 for SSM 4.0, the WebSphere ASM
  uses the built-in
  performance servlet that ships with WAS 7 (and 6). Also the
  legacy SSM ws*
  setup scripts are no longer used. Setup of the new performance
  servlet must
  by done manually by the user, using a few simple steps:
  
  1. In the Integrated Solutions Console go to:
  Monitoring and Tuning > Performance Monitoring Infrastructure
  (PMI)
  and click on your server.
  
  Ensure that "Enable Performance Monitoring Infrastructure
  (PMI)" is ticked
  and the "Currently monitored statistic set" is "Extended".
  
  You may need to restart WAS for the change to take effect.
  
  2. Deploy the servlet:
  WAS_HOME/installableApps/PerfServletApp.ear
  using the Integrated Solutions Console or whatever means you
  currently use
  to deploy applications.
  
  3. Start the servlet.
  
  4. Verify the servlet is running from the agent host using a web
  browser with
  address:
  http://hostname/wasPerfTool/servlet/perfservlet
  
  If you do not have an HTTP server installed then the servlet
  will be
  available on port 9080 by default:
  http://hostname:9080/wasPerfTool/servlet/perfservlet
  
  Do not continue until you can verify that the above page returns
  XML data.
  
  5. Once the servlet is verified to be running, the updated
  websphere subagent
  (build 1700 and later) will automatically find it and list the
  collection
  names in wsCollectionTable. Ensure that the websphere ASM is
  configured for
  the same hostname and port number used in step 4. Also pay close
  attention
  to the collection names and the counter names (shown in
  wsCounterTable when
  wsControlCounterMode is automatic) as most of the names have
  changed in the
  new servlet. A sample configuration script for WAS 7.0 is
  provided in:
  config/websphere7.cfg
  
  For further information about PerfServlet refer to:
  http://publib.boulder.ibm.com/infocenter/wasinfo/fep/topic/com.i
  bm.websphere.nd.multiplatform.doc/info/ae/ae/tprf_devprfservlet.
  html
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0010
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSN

     UP