What is IBM App Connect V12’s Global Cache?
Global Cache is used to store data that you want to reuse, regardless of the message flow, application, Integration server, or Integration node.
The global cache’s two primary components
Catalog server – The catalogue server manages data placement and keeps track of container server health. In your global cache, you must have at least one catalogue server.
Container server – A container server is an embedded component in the integration server that stores a fraction of cached data. There are up to three integration servers in the broker host container servers, excluding the catalogue server.
Cache Manager – The cache manager is an integration server resource that oversees the integration server’s cache components.
What are our options for interacting with Global Cache?
- To save and retrieve data from Global Cache, we use Java code.
- We can do this with the MbGlobalMap object, and we can also specify how long the data stays in the global cache before it is automatically erased.
- Ascertain that the java code is available on all integration servers that are part of the Global cache.
What is the definition of Default Topology?
- The default global cache topology operates within a single Integration node.
- Regardless of whether they are catalogue servers, container servers, or neither, all integration servers can communicate with the global cache.
- The first integration servers to be introduced are a catalogue server and a container server. Container servers will be used on the second, third, and fourth servers.
- If the integration server that contains the catalogue server is stopped, the global cache is unavailable. If you stop the second, third, or fourth integration server, the container server of the stopped integration server is allocated to the next integration server that starts.
What is Multi-Broker Topology?
- This topology we use when we want the global cache to be accessed by multiple Integration nodes.
- You’ll need to make a policy file. The cache manager will use this policy file, which will be an XML file, to connect various brokers. Set the cache policy to the policy file’s fully qualified name.
- In the policy file, specify the names of the brokers who will share the cache data, as well as the number of catalogue servers and the port range and listener host for each broker.
- A single broker hosts two catalog servers; if one dies, the global cache is switched to the other. Two brokers each have a catalog server; if one fails, the global cache switches to the other broker’s catalog server.
What are the advantages of using Global Cache in IBM App Connect?
- The main advantage of Global cache is we can save the data that we want to reuse in different applications running on the same or different Integration servers of the same or different brokers.
- We can save simple values or complete messages that we want to re-use.
What are the disadvantages of using Global Cache in IBM App Connect?
- We need to have java knowledge to work with Global Cache.
- Data saved will be lost in case of catalog server reload.
- Data will be lost in case of an Integration node restart.