See information about the latest product version
Connecting to a WebSphere eXtreme Scale grid
You can store data in a WebSphere® eXtreme Scale grid for use by other message flows.
- Read the concept information about external grids in WebSphere eXtreme Scale grids.
- Ask your WebSphere eXtreme
Scale administrator
for the following information about the external grid to which you
are connecting:
- 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
- To enable SSL for connections to external WebSphere eXtreme Scale grids, follow the instructions in Enabling SSL for external WebSphere eXtreme Scale grids.
After you create the WXSServer configurable service, you can interact with the external grid by using a JavaCompute node. (For detailed instructions, see Accessing the global cache with a JavaCompute node.) When you use a JavaCompute node to get a global map from an external grid, the getGlobalMap method makes the connection to the grid if one does not exist. To modify a flow that previously used the embedded cache to connect to an external grid instead, you must update your JavaCompute node by specifying the name of the map on the external grid and the name of the configurable service that is used to connect to the grid. You can work with multiple external grids, and the embedded grid, at the same time.
Statistics are recorded for the interactions between message flows and the external grid. The global cache activity log also provides a high-level overview of how WebSphere Message Broker interacts with the external grid. For more information, see Monitoring the global cache.