WebSphere MQ custom properties

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

For instructions on how to create a new custom property, see Configuring custom properties for the WebSphere MQ messaging provider.

In WebSphere Application Server Version 6.1, the custom properties that you define are validated by the WebSphere MQ client jar files contained in WebSphere Application Server. In previous versions, this was done within WebSphere Application Server itself, and then by the WebSphere MQ client jar files. If you have defined a property that is not valid for WebSphere MQ, the WebSphere MQ client jar files create an exception, which is caught by WebSphere Application Server, and logged in the Systemout.log and SystemErr.log. 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 WebSphere Application Server installation, new MQ properties might be created that are not known to WebSphere Application Server. You can configure these as custom properties through WebSphere Application Server so that they are recognized by the WebSphere MQ client jars. You can also configure WebSphere Application Server to point to the WebSphere MQ client jars in the external JMS provider, as described in Installing WebSphere MQ to interoperate with WebSphere Application Server.

For information on valid values for WebSphere MQ properties, refer to WebSphere MQ Using Java or WebSphere MQ System Administration, which are available from the IBM Publications Center.

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

Mixed node scenario

In this scenario, a cell consists of a WebSphere Application Server, Version 6.1 deployment manager and four nodes. Two of the nodes are WebSphere Application Server, Version 6.1 and two are WebSphere Application Server, Version 6.0. If a WebSphere MQ connection factory is defined at cell level and has custom properties defined which exploit the new fields available in WebSphere MQ, Version 6, then the connection factory is only bound into the WebSphere Application Server cells that are at Version 6.1 level. The WebSphere Application Server, Version 6.0 nodes do not know about the new WebSphere MQ properties and do not bind into the JNDI. The enhancements made to WebSphere Application Server, Version 6.1 allow validation of the properties to be deferred to the WebSphere MQ client jars.
Figure 1. Mixed node scenario

Future version of WebSphere MQ scenario

In this scenario a cell consists of WebSphere Application Server, Version 6.1 deployment manager and nodes. The WebSphere MQ messaging provider is running at a level later than Version 6. WebSphere Application Server is using the default WebSphere MQ client jars shipped with WebSphere Application Server, which are Version 6. In this scenario the WebSphere MQ client jars are 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 WebSphere Application Server, Version 6.1 deployment manager and nodes. The WebSphere MQ messaging provider is running at a level later than Version 6. To successfully use the new WebSphere MQ properties it is necessary to configure the WebSphere Application Server to point to the WebSphere MQ client jars associated with the future version of WebSphere MQ.
Figure 3. Correctly configured scenario

Error message example

The following example shows the type of text that the exception created by the client jars contains:
[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.



Related tasks
Configuring custom properties for the WebSphere MQ messaging provider
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=cmm_customprops
File name: cmm_customprops.html