WAS v8.5 > WebSphere applications > Messaging resources > Interoperation with WebSphere MQ > Interoperation using the WebSphere MQ messaging providerWebSphere MQ custom properties
WebSphere Application Server 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 available in the dmgr console.
For WAS v7.0 or later, the custom properties defined 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 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 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.
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
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 PropertyNamewhere PropertyName is the name of the invalid property.
Related
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
Troubleshoot applications with HPEL
Reference: