IJ23791: TIVOLI MANAGEMENT AGENT FRAMEWORK: AGENT CONFIGURATION NOT UPDATED FROM CENTRAL CONFIGUARION SERVER

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 5 (6.3.0.7-TIV-ITM-SP0005)

APAR status

• Closed as program error.

Error description

• Environment:
  ITM 630 FP7 SP3
  
  >> Do you think the latest patch
  applied is involved? Yes
  
  Problem Description:
  
   When using
  ITM's Central Configuration Server technology to update an
  Agent's files, the Agent does not update its local
  configuration when changes are made to the configuration on the
  Central Configuration Server. This problem is seen when the
  Tivoli Management Agent Framework (TEMA) is updated to release
  630 FP7 or above.
  
   Detailed Recreation
  Procedure:
  =======================================
  - Install
  Tivoli Management Server 630 FP7
  - Install Tivoli Log File
  Agent 06.30.01.00
  - Install Apache Web Server (CCS)
  - Configure
  Tivoli Log File (KLO) Agent for one Instance
  - Configure Tivoli
  Log File Agent for CCS access.
  - Prepare .conf and .fmt files
  for Agent download from CCS
  - Start KLO Agent Instance
  - Edit
  configuration file on CCS
  - Restart KLO Agent and observe that
  the Agent does not download the configuration file.
  

Local fix

• WORKAROUND:
  ============
   Manually configure the environment
  variable IRA_SERVICE_INTERFACE_CONFIG_LOADLIST for each
  Instance to the default pathname
  $CANDLEHOME$/localconfig/lo/lo_cnfglist.xml
  ============
  

Problem summary

• Centralized configuration server configured with ITM no longer
  works with ITM 6.3.0.7 SP3 TEMA.  The default load list file
  name has changed -- it now includes the instance name but didn't
   used to.  As a result, files in the load list are no longer
  automatically downloaded from the server.
  
  
  APM and ICAM agents include the instance name in the load list
  file name, e.g.  lo_instance_cnfglist.xml, whereas ITM agents
  did not include the instance name in the file name, e.g.
  lo_cnfglist.xml.  When the central configuration functions were
  merged to form a unified agent code base, or possibly later when
  dual mode central configuration functions were implemented, the
  ITM default was inadvertently changed to the APM default.  As a
  result, the customer's existing load list file was no longer
  being processed.
  

Problem conclusion

• IRA_ConstructUtilityFileName had already been structured to have
   different names for various files by splitting a char * into an
   array of two char * elements (one for V6 ITM and one for V8 APM
   / ICAM).  The Load List file name filenameCnfg had just slipped
   through the cracks and was not converted from a single pointer
  to an array of two pointers.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0005
  

Temporary fix

• In the config directory of each agent, add the environment
  variable setting
  IRA_SERVICE_INTERFACE_CONFIG_LOADLIST=<original-loadlist-default
  -file-name> and restart the agent
  

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

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels