IBM Support

IT35129: POST-MIGRATION-TASK FOR GLOBAL CACHE IS MISSING IN V11 KNOWLEDGECENTER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • ACE V11 knowledgecenter need to be updated with the
    post-migration-task for Global cache as below:
    
    Edit and define
    the cacheServerName in the server.conf.yaml and update the
    catalogClusterEndPoints value accordingly
    OR
    Edit the
    cacheServerName in the catalogClusterEndPoints to match the
    format {V11NodeName}_{listenerHost}_{listenerPort}
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise V11 migrating global cache
    topology from previous version of IBM Integration Bus.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Post migration tasks for global cache is missing or incomplete
    in the product knowledge center.
    

Problem conclusion

  • <span style="font-family:arial,helvetica,sans-serif"><span
    style="font-size:11px">The product knowledge center is now
    updated with the post-migration tasks for global cache as below
    
    1) Updated the bh23520_.html  and added  one more bullet point
    link "Setting up Global Cache" under Procedure section
    2) New page bh23530_.html is added to describe the post
    migration tasks for global cache.
    
    Also, below listed additional changes will be done to the page
    bh23530_.html
    
    1)
    Currently the page shows :
    
    <span style="background-color:rgb(255, 255, 255);color:rgb(50,
    50, 50)">Define a unique cacheServerName in the server.conf.yaml
    files for the integration servers, and update the
    </span>cacheServerName<span style="background-color:rgb(255,
    255, 255);color:rgb(50, 50, 50)"> value in the </span><span
    style="background-color:rgb(255, 255, 255);color:rgb(50, 50,
    50)">catalogClusterEndPoints</span><span
    style="background-color:rgb(255, 255, 255);color:rgb(50, 50,
    50)"> property from </span>IB10NODE_localhost_2800<span
    style="background-color:rgb(255, 255, 255);color:rgb(50, 50,
    50)"> to the </span>cacheserverName<span
    style="background-color:rgb(255, 255, 255);color:rgb(50, 50,
    50)"> of the catalog servers. After modification, the global
    cache stanza for the server hosting catalog server will look
    like the stanza in the following example:
    
    Will be updated as : </span>
    
    Define a unique cacheServerName in the server.conf.yaml files
    for the integration servers, and update the cacheServerName
    value in the catalogClusterEndPoints property.
    
    Suppose if the node IB10NODE is migrated from V10 to V11 with
    name ACE11NODE, the value of catalogClusterEndPoints will be
    "IB10NODE_localhost_2800:localhost:2803:2801". So post
    migration, define cacheServerName, say for example
    "ACE11CatalogServer" and also update the catalogClusterEndPoints
    value to 'ACE11CatalogServer:localhost:2803:2801'  as shown in
    the below sample global cache stanza for a catalog server.
    
    <span style="background-color:rgb(255, 255, 255);color:rgb(50,
    50, 50)">2)
    
    Currently the page shows :</span></span></span>
    
    <span style="font-family:arial,helvetica,sans-serif"><span
    style="font-size:11px">The global cache stanza for the container
    server will look like the stanza in the following example:
    
    GlobalCache:
        cacheOn: true
        cacheServerName: 'ACE11ContainerServer2'
        catalogClusterEndPoints:
    'ACE11CatalogServer:localhost:2803:2801'
        catalogDomainName: 'WMB_IB10NODE_localhost_2800'
        catalogServiceEndPoints: 'localhost:2800'
        enableContainerService: true
        enableJMX: true
        haManagerPort: 2805
        jmxServicePort: 2806
        listenerHost: 'localhost'
        listenerPort: 2804
    
    <span style="background-color:rgb(255, 255, 255);color:rgb(50,
    50, 50)">Will be updated as :</span>
    
    Similarly, define a unique cacheServerName for container server
    as well. Please note that the catalogClusterEndPoints will be
    same for all the integration servers participating in the global
    cache configuration. The global stanza for a container server,
    with cacheServerName "ACE11ContainerServer2"  will looks like
    below :
    
    GlobalCache:
        cacheOn: true
        cacheServerName: 'ACE11ContainerServer2'
        catalogClusterEndPoints:
    'ACE11CatalogServer:localhost:2803:2801'
        catalogDomainName: 'WMB_IB10NODE_localhost_2800'
        catalogServiceEndPoints: 'localhost:2800'
        enableCatalogService: false
        enableContainerService: true
        enableJMX: true
        haManagerPort: 2805
        jmxServicePort: 2806
        listenerHost: 'localhost'
        listenerPort: 2804</span></span>
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT35129

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-02

  • Closed date

    2021-03-22

  • Last modified date

    2021-03-22

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

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

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
23 March 2021