Network Deployment (Distributed operating systems), v8.0 > Applications > Messaging resources > Interoperation with WebSphere MQ > Interoperation using the WebSphere MQ messaging provider

WebSphere MQ custom properties

WAS supports the use of custom properties to define WebSphere MQ properties. This is useful because it enables WAS to work with later versions of WebSphere MQ that might have properties that are not exposed in the WAS administrative console.

For WAS v7.0 or later, the custom properties that you define are validated by the WebSphere MQ resource adapter contained in WAS. In earlier releases, this was done within WAS itself, and then by the WebSphere MQ client jar files. If we have defined a property that is not valid for WebSphere MQ, the WebSphere MQ resource adapter creates an exception, which is caught by WAS, and logged in the Systemout.log and SystemErr.log files. Examples of error messages are given at the end of this topic.

When a later version of WebSphere MQ is available that is supported by the WAS installation, new WebSphere MQ properties might be created that are not known to WAS. We can configure these as custom properties through WAS so that they are recognized by the WebSphere MQ resource adapter. We can also configure WAS to point to the WebSphere MQ resource adapter in the external JMS provider, as described in Configure the WebSphere MQ messaging provider with native libraries information.

For information on valid values for WebSphere MQ properties, refer to the Use Java and System Administration sections of the WebSphere MQ information center.

New feature: Beginning in WAS v8.0 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:

The following scenarios illustrate how different cell configurations might be affected.

Mixed node scenario

In this mixed node scenario, a cell consists of a WAS, v8.0 dmgr, two WAS, v6 nodes, and two WAS, v8.0 nodes. If a WebSphere MQ connection factory is defined at cell level and has custom properties defined that exploit the new fields available in WebSphere MQ, then the connection factory is only bound into the WAS cells that are at v8.0 level. The WAS, v6 nodes do not know about the new WebSphere MQ properties and do not bind into the Java Naming and Directory Interface (JNDI). The enhancements made to WAS, v8.0 allow validation of the properties to be deferred to the WebSphere MQ resource adapter.

Figure 1. Mixed node scenario

Future version of WebSphere MQ scenario

In this scenario a cell consists of WAS, v8.0 dmgr and nodes. The WebSphere MQ messaging provider is running at a level later than v6. WAS is using the default WebSphere MQ resource adapter shipped with WAS v8.0. In this scenario the WebSphere MQ resource adapter is not aware of the new WebSphere MQ properties so the validation fails and the connection factory does not bind into the JNDI.

Figure 2. Future version of WebSphere MQ scenario

Correctly configured scenario

In this scenario, which is similar to the previous one, a cell consists of WAS, v8.0 dmgr and nodes. The WebSphere MQ messaging provider is running at a level later than v6.

To successfully use the new WebSphere MQ properties it is necessary to configure the WAS to point to the WebSphere MQ resource adapter associated with the future version of WebSphere MQ.

Figure 3. Correctly configured scenario

Error message example

The exception created by the resource adapter contains error messages similar to the following example:

[09/02/06 15:40:06:377 GMT] 0000000a ContainerImpl E   WSVR0501E: Error creating
component null [class com.ibm.ws.runtime.component.ApplicationServerImpl]
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.runtime.component.binder.
ResourceBindingException: invalid configuration passed to resource binding logic.
REASON: Failed to create connection factory: Error raised constructing AdminObject, error code: XAQCF PropertyName : XAQCF PropertyName

where PropertyName is the name of the invalid property.
Interoperation using the WebSphere MQ messaging provider
Configure custom properties for WebSphere MQ messaging provider JMS resources
Configure custom properties for the WebSphere MQ resource adapter
Configure the WebSphere MQ messaging provider with native libraries information
Use HPEL to troubleshoot applications

Related

WebSphere MQ library Concept topic

+

Search Tips   |   Advanced Search