WebSphere eXtreme Scale grids

Use one or more external WebSphere® eXtreme Scale grids to store data that you want to reuse.

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® App Connect Enterprise global cache collaborate to act as a WebSphere eXtreme Scale grid.

For more information about the grid that is embedded in IBM App Connect Enterprise, 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 in IBM App Connect Enterprise (as the embedded global cache), 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 App Connect Enterprise 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 online.

You might have an existing WebSphere eXtreme Scale environment that uses a topology, such as one of the following examples:
  • Embedded WebSphere eXtreme Scale servers in WebSphere Application Server network deployment installations
  • A stand-alone WebSphere eXtreme Scale software grid

When you are connecting to an external grid, IBM App Connect Enterprise 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. An installation or appliance can host more than one grid.

To connect to an external grid, you need the following information:
  • The name of the grid
  • The host name and port of each catalog server for the grid
  • Optional: the object grid file that can be used to override WebSphere eXtreme Scale properties

By using a policy to specify the parameters, you can connect to an external WebSphere eXtreme Scale grid. IBM App Connect Enterprise 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 Mapping nodes or JavaCompute nodes to store and retrieve data in a map in the global cache. 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 more information, see Accessing the global cache by using a Mapping node or Accessing the global cache by using 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.