Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Sonic .jar files are needed by SOAtest to invoke SonicMQ JMS

LegacyForum
LegacyForum Posts: 1,664 ✭✭
in Progress Software
What is needed for testing SonicMQ JMS services using SOAtest
The following Sonic jar files need to be added to the SOAtest classpath
  • broker.jar
  • mfcontext.jar
  • sonic_Client.jar
  • xq_core.jar
They can be found under the Sonic MQ/ESB installation dirs lib and lib-mq.

To add a jar to SOAtest classpath, go to File --> Customize Preferences --> System Properties. jars and classes added there are usually loaded immediately, but restarting SOAtest will ensure that if necessary.

Once the jars are available, it becomes a matter of configuring SOAtest's "SOAP Client" or "Messaging Client" tools with the proper JNDI and queue data in order to send and receive messages. Sonic's "JMS Administered Objects" under the "Tools" menu in the Sonic Management Console may need to be configured so that SOAtest can make the JMS connection via JNDI.

At this point Sonic's multi-part messages are not supported, only standard JMS 1.0.1 and 1.1 API is.

Categories