PM73305: WAS TEMA DOESN'T HANDLE CTIRA_SUBSYSTEM_ID PROPERTY FROM YN.INI

7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5
7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6
7.1.0.3-TIV-ITCAMAD-IF0008: ITCAM for Application Diagnostics V7.1 FP3 IF8
IBM Tivoli Composite Application Manager for Application Diagnostics V7.1 fixes

APAR status

• Closed as program error.

Error description

• Users Affected:
  User of Agent for WebSphere in ITCAM for WebSphere V6.2 or
  ITCAM for Application Diagnostics 7.1 who set
  CTIRA_SUBSYSTEM_ID in ITM agent configuration file (yn.ini)
  
  ---------------------------------------------
  Problem Description:
  TEP workspaces are blank on agent level (for example
  Application Server Status workspace). This happens when
  value of CTIRA_SUBSYSTEM_ID property in yn.ini is different
  than agent node id set in agent configuration file
  (<ITM_HOME>/config/<hostname>_yn.cfg or
  <ITM_HOME>/config/<hostname>_yn.xml).
  

Local fix

• Local Fix/Workaround:
  Reconfigure agent to have exactly same node id
  as value in CTIRA_SUBSYSTEM_ID. Or manually set it
  in following files:
  - for 6.2 release: KYN_ALT_NODEID property in
    <ITM_HOME>/config/<hostname>_yn.cfg file
  - for 7.1 release: value in <altNodeId> tag in
    <ITM_HOME>/config/<hostname>_yn.xml file to new value
  <altNodeId>vrt0085</altNodeId> ).
  
  Restart the agent and verify TEP workspaces.
  

Problem summary

• ***************************************************************
  * USERS AFFECTED: Agent for WebSphere in ITCAM for WebSphere
  * V6.2 and ITCAM for Application Diagnostics 7.1 users who
  * set CTIRA_SUBSYSTEM_ID in agent configuration file.
  ***************************************************************
  * PROBLEM DESCRIPTION:
  * TEP workspaces are blank on agent level (for example
  * Application Server Status workspace). This happens when value
  * of CTIRA_SUBSYSTEM_ID property in yn.ini is different than
  * agent node id set in agent configuration file:
  * v6.2: <ITM_HOME>/config/<hostname>_yn.cfg,
  * v7.1: <ITM_HOME>/config/<hostname>_yn.xml.
  ***************************************************************
  * RECOMMENDATION: Use ITCAM for WebSphere 6.2 FP6, Interim
  * Fix 1, TEMA (6.2.0.6-TIV-ITCAM_WAS_TEMA-IF001) or newer
  * release which contains this fix to resolve this issue.
  ***************************************************************
  

Problem conclusion

• Setting CTIRA_SUBSYSTEM_ID causes registration on TEMS under
  Managed System Name like: <CTIRA_SUBSYSTEM_ID>:<hostname>:KYNA.
  However, TEMA has it's own setting for agent ID called
  'Alternative Node ID' which is stored in
  <ITM_HOME>/config/<hostname>_yn.cfg or
  <ITM_HOME>/config/<hostname>_yn.xml files. This value is
  used to build internal identification similar to Managed System
  Name.
  When CTIRA_SUBSYSTEM_ID is different than 'Alternative Node ID'
  then TEMA drops request from ITM as those request are for agent
  with CTIRA_SUBSYSTEM_ID name and TEMA identifies it's name as
  value of 'Alternative Node ID'.
  
  The fix for this APAR introduces the precedence of agent node ID
  configurations. If CTIRA_SUBSYSTEM_ID value is present in
  <ITM_HOME>/config/yn.ini file then it overrides value of
  'Alternative Node ID'.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | interim fix | 6.2.0.6-TIV-ITCAM_WAS_TEMA-IF001
    | interim fix | 7.1.0.3-TIV-ITCAMAD-IF0005
  

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

  ITCAM WAS DIST

• Fixed component ID

  5724L6200

Applicable component levels

• R610 PSY

     UP

• R710 PSY

     UP