Migrating global cache configuration settings

You can migrate your global cache settings by completing some additional configuration as part of your migration from IBM® Integration Bus V10 to IBM App Connect Enterprise V11.

When you migrate from IBM Integration Bus V10 to IBM App Connect Enterprise V11, you can migrate your global cache configuration settings by completing the following steps, in addition to those described in the Migrating section:

Migrating settings from your IBM Integration Bus cache policy XML files

In IBM Integration Bus V10, cache policy XML files were used to configure the global cache. In IBM App Connect Enterprise, the properties that were set in those files are now set in the server.conf.yaml configuration files instead.

The following example shows a policy XML file that is similar to the sample policy_two_brokers_ha.xml file that was provided with IBM Integration Bus Version 10:
<cachePolicy xmlns="http://www.ibm.com/xmlns/prod/websphere/messagebroker/globalcache/policy-1.0">
    <broker name="integrationNode1" listenerHost="localhost">
        <catalogs>1</catalogs>  
        <portRange>
            <startPort>2800</startPort>
            <endPort>2803</endPort>
        </portRange>
    </broker>

    <broker name="integrationNode2" listenerHost="localhost">
        <catalogs>1</catalogs>
        <portRange>
            <startPort>2804</startPort>
            <endPort>2815</endPort>
        </portRange>
    </broker>
</cachePolicy>
In IBM Integration Bus Version 10, if you applied the example cache policy XML file to two integration nodes called integrationNode1 and integrationNode2, which were running on the same host (in this example, localhost) with several integration servers, your integration nodes would have the following configuration as a result:
  • Integration Node 1:
    • Integration Server 1: one catalog server and one container server (taking ports 2800-2803)
    • Further integration servers would have no catalog servers or container servers
  • Integration Node 2:
    • Integration Server 2: one catalog server and one container server (taking ports 2804 - 2807)
    • Integration Server 3: container server (taking ports 2808 - 2811)
    • Integration Server 4: container server (taking ports 2812 - 2815)
    • Further integration servers would have no catalog or container servers

In IBM App Connect Enterprise, equivalent sample server.conf.yaml configuration files are provided under the sample directory basic_2_catalogs_4_containers, in which IntegrationServer1 would be under IntegrationNode1, and IntegrationServer2, IntegrationServer3, and IntegrationServer4 would be under IntegrationNode2.

This configuration is static and persists across integration server restarts, which means that an integration server that is configured as a catalog server will always be a catalog server, and you can tune your integration servers accordingly. For example, this might include giving container servers a larger JVM heap size, because this is where your cache is stored.

Migrating settings from your IBM Integration Bus objectgrid.xml and deployment.xml files

In IBM Integration Bus V10, the objectgrid.xml and deployment.xml files had to be copied into set locations beneath your integration node and integration server workpaths, before they would take effect. In IBM App Connect Enterprise, you set the objectGridCustomFile and deploymentPolicyCustomFile properties in the server.conf.yaml configuration file to point to these files. You can choose to put the files in the same workpath locations as in IBM Integration Bus V10, but, if you do so, you must specify the custom file properties in the server.conf.yaml file to point to this location.