IBM Support

IT47704: IBMINT EXTRACT NODE COMMAND NOT RECOGNISE INTEGRATION SERVERS ACTING AS GLOBAL CACHE COMPONENTS

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

  • During the migration of integration nodes to V13, the `ibmint
    extract node` command fails to recognize integration servers as
    cache components, preventing the cache component EGs from
    starting and connecting to the global cache grid, which leads to
    failures because the catalog and container servers are not
    running.
    Error:
    Jan 30 11:43:19 lxtib021 ACE[13546]: IBM App Connect Enterprise
    v13020 (IBAD02.POCORR) [Thread 13546] (Msg 1/1) BIP2153I: About
    to 'Start' an integration server.
    Jan 30 11:54:47 lxtib021 ACE[1032]: IBM App Connect Enterprise
    v13020 (IBAD02) [Thread 1725] (Msg 1/1) BIP2060W: The
    integration node has detected that the integration server
    POCORR, process ID 13546, has shutdown.
    

Local fix

  • Explicitly run ibmint specify jre command to change the Java
    level for the integration servers connecting to the global cache
    to use Java 8 as global cache is not supported on Java 17. Then
    restart the integration server.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All IBM App Connect Enterprise users who migrate to version 13
    by running the `ibmint extract` command on integration servers
    that have global cache enabled  and no deployed message flows.
    
    
    Platforms affected:
    LinuxPPCLE64, LinuxZ64, AIX, WinX64, LinuxX64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During the migration of integration nodes to V13, the `ibmint
    extract node` command fails to recognize integration servers
    which acts as cache components, preventing the cache component
    integration servers from starting and connecting to the global
    cache grid, which leads to failures because the catalog and
    container servers are not running.
    

Problem conclusion

  • The product has been updated so that, the `ibmint extract node`
    command now detects the global cache enabled integration servers
    and correctly updates the Java level to 8.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version   Maintenance Level
    v13.0      13.0.7.0
    
    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

    IT47704

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0570

  • Reported release

    D0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-02-12

  • Closed date

    2026-01-15

  • Last modified date

    2026-03-20

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0570

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"13.0.0","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
20 March 2026