IT32186: UPDATE KNOWLEDGE CENTER TO CLARIFY THE SUPPORT FOR GLOBAL CACHE CATALOG SERVER IN MULTI-INSTANCE INTEGRATION NODE CONFIGURATION.

APAR status

• Closed as documentation error.

Error description

• Following KC pages describe the Global cache configuration in
  multi-instance int node configuration.
  
  https://www.ibm.com/sup
  port/knowledgecenter/SSTTDS_11.0.0/com.ibm.etools.mft.doc/bn2379
  3_.html
  https://www.ibm.com/support/knowledgecenter/SSTTDS_11.0.
  0/com.ibm.etools.mft.doc/bn23780_.html
  
  There is a concern
  over following statement:
  
  "A multi-instance integration node
  cannot be used to host an integration server with a catalog
  server."
  
  As there are no qualifications on the statement as
  to when it applies. Additionally, this statement can be taken
  out of context as a blanket statement for support/functionality
  of global cache with multi-instance Int.Nodes.
  
  In the
  scenario where users do not intend to make cache highly
  available in a multi-instance Int node setup, then they can
  host catalog server on the multi-instance integration node with
  the awareness that when the multi-instance integration node
  fails over, the cache would be lost.
  
  The KC pages needs to be
  updated to reflect the scope of the statement:
  
  A
  multi-instance integration node cannot be used to host an
  integration server with a catalog server in this example.?
  
  In
  this scenario, a multi-instance integration node cannot be used
  to host an integration server with a catalog server.?
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of App Connect Enterprise V11.0 using Global Cache
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  In context of using Global Cache in a multi-instance integration
  node topology, the knowledge center states that
  "A multi-instance integration node cannot be used to host an
  integration server with a catalog  server."
  
  However, if an user does not intend to make the cache highly
  available and only needs to use the cache within
  the running integration node,  the catalog server can still be
  hosted on the multi-instance integration node. It is to be noted
  that when active integration node fails over to standby node,
  the cache would be lost and it will need to be reloaded on the
  failed over integration node.
  

Problem conclusion

• The product knowledge center topics   bn23780_ and   bn23793_
  have been updated to clarify the  context in which the catalog
  servers in multi-instance integration node topology are not
  recommended.
  

Temporary fix

Comments

APAR Information

• 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