WebSphere eXtreme Scale grids

WebSphere eXtreme Scale provides a scalable, in-memory data grid. The data grid dynamically caches, partitions, replicates, and manages data across multiple servers. The catalog servers and container servers for the IBM® Integration Bus global cache collaborate to act as a WebSphere eXtreme Scale grid. For more information about the grid that is embedded in the broker, see Embedded global cache. To find out more about the differences between the embedded cache and the external grid, see Differences between the embedded global cache and an external WebSphere eXtreme Scale grid.

In addition to the grid that is available (as the embedded global cache) within IBM Integration Bus, you can integrate with WebSphere eXtreme Scale grids that are running elsewhere. You can work with multiple external grids, and the embedded grid, at the same time. For a diagram that shows how IBM Integration Bus message flows interact with an external WebSphere eXtreme Scale grid, and for definitions of the terms that are associated with a grid, see Data caching terminology. For more information about grids, see WebSphere eXtreme Scale product documentation.

When you are connecting to an external grid, IBM Integration Bus hosts the WebSphere eXtreme Scale client, but the cache is hosted on an external grid. Therefore, a separate WebSphere eXtreme Scale installation or appliance is required, such as a DataPower XC10 device. An installation or appliance can host more than one grid.

By using a configurable service to specify the parameters, you can connect to an external WebSphere eXtreme Scale grid. IBM Integration Bus message flows can then access and modify data that is stored in the external grid. If you are connecting to a secure grid, you can create a security identity by using the mqsisetdbparms command. To connect to an external grid, follow the instructions in Connecting to a WebSphere eXtreme Scale grid.

You can enable SSL for client connections to external WebSphere eXtreme Scale grids by setting up a public key infrastructure, then enabling SSL for an integration server. For more details, see Enabling SSL for external WebSphere eXtreme Scale grids.

You can use JavaCompute nodes to store and retrieve data in a map in the external grid. When you get a global map from an external grid, the getGlobalMap method makes a connection to the grid if one does not exist. For instructions, see Accessing the global cache with a JavaCompute node.

You can monitor the external grid by viewing the activity log and resource statistics. For more information, see Monitoring the global cache.

To enable new function that is available in fix packs, you use the -f parameter on the mqsichangebroker command. Running this command also enables the specification of domain names. In previous versions of IBM Integration Bus, the domain name for all WebSphere eXtreme Scale servers in all embedded caches was an empty string. Servers in different domains cannot collaborate in the same grid. Therefore, for a cache that spans more than one broker, you must enable the new capability for these brokers at the same time.