Setting up a global cache

After migration of an integration node that is configured with a global cache, extra steps might be needed to complete the global cache configuration.

About this task

In IBM® App Connect Enterprise 13.0, the global cache configuration involves setting the cacheServerName parameter, which must be unique in your global cache system.

If the name of the target integration node is the same as the name of the source integration node, no further configuration is needed. However, if the name of the target integration node is different from the name of the source integration node, make the following changes to complete the configuration of the global cache.

By default, integration servers in IBM App Connect Enterprise 13.0 use Java 17, which does not support the global cache. To enable use of the global cache, you must configure your integration servers to use Java 8, by using the ibmint specify jre command.

Procedure

Define a unique cacheServerName in the server.conf.yaml files for the integration servers, and update the cacheServerName value in the catalogClusterEndPoints property.

Consider this example: if the node IB10NODE is migrated from IBM Integration Bus 10.0 to IBM App Connect Enterprise 13.0 with the name ACE12NODE, the value of catalogClusterEndPoints is IB10NODE_localhost_2800:localhost:2803:2801. After migration, specify a value of, for example, ACE12CatalogServer in cacheServerName and update the value in catalogClusterEndPoints to be ACE12CatalogServer:localhost:2803:2801, as shown in the following sample global cache stanza for a catalog server.

GlobalCache:
    cacheOn: true
    cacheServerName: 'ACE12CatalogServer'
    catalogClusterEndPoints: 'ACE12CatalogServer:localhost:2803:2801'
    catalogDomainName: 'WMB_IB10NODE_localhost_2800'
    catalogServiceEndPoints: 'localhost:2800'
    enableCatalogService: true
    enableContainerService: true
    enableJMX: true
    haManagerPort: 2801
    jmxServicePort: 2802
    listenerHost: 'localhost'
    listenerPort: 2800

Similarly, define a unique cacheServerName for the container server too. The value of catalogClusterEndPoints is the same for all the integration servers that participate in the global cache configuration. The global stanza for a container server, with a cacheServerName of ACE12ContainerServer2 looks like the following example:

GlobalCache:
    cacheOn: true
    cacheServerName: 'ACE12ContainerServer2'
    catalogClusterEndPoints: 'ACE12CatalogServer: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