IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

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

  • 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

  • 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.
    
    
    *** VERY IMPORTANT NOTE ***
    IV81199 is not to be abused by issuing SOAP requests other than
    READ type, i.e.  SQL SELECT.  Though IV81199 does not prevent
    user from being abusive to ITM, this enhancement is not for
    purposes of issuing any form of WRITE, UPDATE, DELETE SOAP
    requests to a Mirror hub monitoring enterprise server !
    
    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.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0007
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV81199

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-08

  • Closed date

    2016-04-25

  • Last modified date

    2017-01-06

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

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

    OA52181

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R630 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":""}]

Document Information

Modified date:
06 January 2017