Service Virtualization

Hi All, I am getting below message when I start to create an MQ step ."Please note that the required IBM JMS jars are missing from the LISA CLASSPATH.  You will need some combination of: com.ibm.mqjms.jar, com.ibm.mqbind.jar, com.ibm.mq.pcf.jar, com.ibm.m

could you please provide these jar files . I am using LISA 7.5 .

To use LISA Solutions with various third-party applications , here its IBM MQ , you must make the respective JAR files from the third-party application available to LISA .

CA does not provide the third-party files , kindly request this from your MQ team  and place them in LISA CLASSPATH .

Regards,

Praveen

Hi RohanDoshi,

Please find the attached IBM MQ third party jars & place the same in lib folder and restart the registry and workstation.

Regards

Nandeesha

Rohan,

Get the jar files from where your MQ Server is installed.  The JAR files are available in the MQ_HOME/java/lib directory.

Below is a listing of jar files you need depending on the version of MQ you are using:

WebSphere MQ File Requirements

Copy the WebSphere MQ JAR files to the LISA_HOME/lib directory or define the LISA_POST_CLASSPATH variable. Do not copy the files to the LISA_HOME/hotDeploy directory.

Note: If the operating system is a Japanese version, use the files that are listed for WebSphere MQ 7.

The following JAR files are required for WebSphere MQ 5.2:

■ com.ibm.mqjms.jar

■ com.ibm.mqbind.jar

■ com.ibm.mq.pcf.jar

■ com.ibm.mq.jar

■ connector.jar

The following JAR files are required for WebSphere MQ 6:

■ com.ibm.mq.jar

■ com.ibm.mq.pcf.jar

■ com.ibm.mqjms.jar

■ connector.jar

■ dhbcore.jar

The following JAR files are required for WebSphere MQ 7:

■ com.ibm.mq.commonservices.jar

■ com.ibm.mq.headers.jar

■ com.ibm.mq.jar

■ com.ibm.mq.jmqi.jar

■ com.ibm.mq.pcf.jar

■ com.ibm.mqjms.jar

■ connector.jar

■ dhbcore.jar

Hope this helps.

Regards,

Marcy

Please note the correct answer is the one from Marcy Nunns.

You must always use the MQ Jars taken from your MQ installation, or you may encounter issues linked to use of JARs from different releases (sometimes connectivity may work, but other features like correlation may not)