WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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.

Before you start:
  • 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.
The following steps describe how to connect to a WebSphere eXtreme Scale grid by using a configurable service.
  1. Optional: If you are connecting to a secure grid, use the mqsisetdbparms command to create a security identity, as shown in the following example.
    mqsisetdbparms MB8BROKER -n wxs::id1 -u userId -p password

    For more information, see mqsisetdbparms command.

  2. Create a WXSServer configurable service by using the mqsicreateconfigurableservice command or WebSphere Message Broker Explorer.

    For more information, see mqsicreateconfigurableservice command or Creating a new configurable service.

  3. Use the values provided by your WebSphere eXtreme Scale administrator to configure the connection to the external grid, as shown in the following example. For an explanation of the parameters of the configurable service, see Configurable services properties.
    mqsicreateconfigurableservice MB8BROKER -c WXSServer -o xc10 
    -n catalogServiceEndPoints,gridName,overrideObjectGridFile,securityIdentity 
    -v "server.ibm.com:2809","myGrid","C:\Brokers\WebSphere_eXtreme_Scale\xc10\xc10Client.xml","id1"
    As you can see from this example, when you specify the security identity, you omit the prefix (wxs::) that you used when creating the security identity with the mqsisetdbparms command.

    If the object grid file is on a shared drive on Windows, you must use the \\hostname\directory path syntax to the shared drive, instead of a mapped drive letter. The WebSphere Message Broker user ID that is used to access the \\hostname\directory path must have read access to the file system and must use the same password that is required to access the shared drive.

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.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:19


Task topicTask topic | Version 8.0.0.7 | bn23788_