OA52181: RFE 83142 ENHANCEMENT TO ALLOW SOAP REQUESTS TO SECONDARY HUB TEMS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Customer is requesting "read only" access to Secondary HUB TEMS
  via SOAP client scripts.  Customer does not require tacmd CLI
  access to Secondary HUB TEMS.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TEMS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: IN A FTO HUB MONITORING ENTERPRISE      *
  *                      SERVER CONFIGURATION, SOAP REQUESTS     *
  *                      SUBMITTED TO THE MIRROR (STANDBY) HUB   *
  *                      MONITORING ENTERPRISE SERVER ARE        *
  *                      REJECTED.                               *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  In a FTO environment, the Acting hub monitoring enterprise
  server is always enabled for receiving and processing SOAP
  requests.  Submitting SOAP requests to a Mirror hub
  monitoring enterprise server is not permitted; this
  restriction is a safeguard to prevent Mirror hub monitoring
  enterprise server from getting out of sync with the Acting
  hub monitoring enterprise server in an FTO environment.
  

Problem conclusion

Temporary fix

Comments

• A new hub monitoring enterprise server Environment Variable
  named KMS_CHECK_FTO_ROLE has been added.  Declaring
  KMS_CHECK_FTO_ROLE=N in Mirror hub monitoring enterprise
  server configuration file will override the default
  behavior, thus enabling user to submit SOAP requests to a
  Mirror hub monitoring enterprise server.
  For more details on the new Environment Variable see
  "Install Actions" section, at end of this Problem Conclusion
  section.
  
  Install Actions:
  
  On the Acting hub monitoring enterprise server, declaring
  KMS_CHECK_FTO_ROLE=Y or KMS_CHECK_FTO_ROLE=N has no effect
  on the Acting hub monitoring enterprise server. However,
  given the very nature of an FTO hub monitoring enterprise
  server environment, at any time for whatever reason, the
  current Acting hub monitoring enterprise server and the
  Mirror hub monitoring enterprise server may switch roles.
  So what does this mean with respect to KMS_CHECK_FTO_ROLE
  environmnent variable ?
  
  It simply means this ...  if user wants Mirror hub
  monitoring enterprise server to receive and process SOAP
  requests then user will declare KMS_CHECK_FTO_ROLE=N per
  Mirror hub monitoring enterprise server configuration file.
  User should also make same KMS_CHECK_FTO_ROLE=N declaration
  in the Acting hub monitoring enterprise server configuration
  file, since at some point the Acting hub monitoring
  enterprise server may become the Mirror hub monitoring
  enterprise server.
  
  Adding same declaration of KMS_CHECK_FTO_ROLE=N to both
  Acting and Mirror hub monitoring enterprise servers will
  assure consistent enablement for Mirror hub monitoring
  enterprise server to receive and process SOAP requests.
  

APAR Information

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

  IV81199

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

Modules/Macros

•    KDSMAIN
  

Fix information

• Fixed component name

  MGMT SERVER DS

• Fixed component ID

  5608A2800

Applicable component levels

• R630 PSY UA91244

     UP17/03/13 P F703

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.