WXSServer policy
Use a WXSServer policy to define how a connection to an external WebSphere® eXtreme Scale grid is established.
Changes to the property values in a WXSServer policy take effect immediately, without the need to restart the integration server. You must deploy this policy before the associated message flow is started.
To reference a remote cache server specified
by a WXSServer policy in a JCN, specify the policy details in the
format {policyProjectName}:PolicyName. For example, {myPolicyProject}:MyPolicy (the {} characters
are required).
| Property | Value |
|---|---|
catalogServiceEndPoints |
A comma-separated list of one or more catalog servers for the grid to which you are connecting. The format
of each endpoint is |
gridName |
The name of the grid to which you are connecting. |
overrideObjectGridFile |
The absolute path to an XML file on the local system. This XML file defines overrides for the WebSphere eXtreme Scale client connections that are associated with this policy. This property is optional. You might want to specify an override file to override certain properties, such as numberOfBuckets and timeToLive for WebSphere eXtreme Scale backing map definitions. For details about how to update the WebSphere eXtreme Scale object grid file, see WebSphere Extreme Scale product documentation online. |
securityIdentity |
The name of the security identity to use when connecting to a secure grid. This property is optional.
If the grid to which you are connecting is secure, you can create
a security identity that represents a user name and password for use
when connecting to the remote grid. When you use the mqsisetdbparms command to create
the security identity, it has the format For more information about email server security identity support, see Security identities for the integration server connecting to external systems. |