IBM Support

IT06859: LOCAL MULTI-INSTANCE INTEGRATION NODES ARE NOT SHOWN WITH CORRECT STATUS IN IBEXPLORER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When running an integration node in multi instance mode one
    instance will be active and the other in standby. If the active
    instance is a local integration node,  it's running status may
    be incorrectly displayed by Integration Explorer depending upon
    how it was initially started
    
    Additional Symptom(s) Search Keyword(s): Mulit-instance
    Integration node, Integration Explorer, incorrect status
    

Local fix

  • Connect to the integration node as if it were a remote node.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 using multi-instance
    integration nodes with a local explorer install.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using an IBM Integration Explorer (IBX) install against a
    multi-instance integration node, a local integration node can
    appear stopped in IBX when it is the active instance.  This is
    due to the "AdminAgentPID" file only being looked for in the
    local registry, although it will be written to the shared
    filesystem area when using HA.  This returns a PID of 0 to IBX,
    which then marks the node as stopped.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The location of the PID file changes depending upon how the
    broker was initially started.  If it was running standalone and
    was then made multi-instance, then the PID file appears in the
    local registry.  If it was always multi-instance, it appears in
    the shared filestore.  The product looks for the PID file in the
    local registry and the shared filestore.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.6
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06859

  • Reported component name

    IB EXPLORER

  • Reported component ID

    5724J0532

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-30

  • Closed date

    2016-08-02

  • Last modified date

    2016-08-02

  • 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

    IB EXPLORER

  • Fixed component ID

    5724J0532

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020