Problems in deploying the resource adapter

 

Failures in deploying the resource adapter are generally caused by not configuring JCA resources correctly. For example, a property of the ResourceAdapter object might not be specified correctly, or the deployment plan required by the application server might not be written correctly. Failures might also occur when the application server attempts to create objects from the definitions of JCA resources and bind the objects into the JNDI namespace, but certain properties are not specified correctly or the format of a resource definition is incorrect.

The resource adapter can also fail to deploy because it loaded incorrect versions of JCA or WebSphere MQ JMS classes from JAR files in the class path. This kind of failure can commonly occur on a system where WebSphere MQ is already installed. On such a system, the application server might find existing copies of the WebSphere MQ Java JAR files and load classes from them in preference to the classes supplied in the WebSphere MQ resource adapter RAR file. If the extended transactional client JAR file, com.ibm.mqetclient.jar, cannot be loaded when the resource adapter is deployed, a warning is written to the diagnostic trace, if enabled, but this does not cause deployment to fail.

uj40160_