This topic provides a reference for configuring SOAtest and VirtualizeSOAtestVirtualize for Virtualize for popular JMS providers.
Sections include:
...
To add the required jar files (listed in the tables below) to theSOAtest and VirtualizeSOAtestVirtualize classpathVirtualize classpath, complete the following:
...
For | Amazon Simple Queue Service (SQS) and other JMS providers where building JMS ConnectionFactory through JNDI lookup is difficult. |
---|---|
Minimum required JARs | Amazon SQS java client JARs (available on Maven Central at https://repo1.maven.org/maven2/com/amazonaws/):
Apache httpclient dependencies:
WSO2 carbon-jndi JAR (available on the WSO2 Maven repository at https://maven.wso2.org/nexus/content/repositories/releases/org/wso2/carbon/jndi/org.wso2.carbon.jndi/): org.wso2.carbon.jndi-<version>.jar |
Factory class | InMemoryInitialContextFactory from the WSO2 carbon-jndi project. See Creating the JMS ConnectionFactory Object. |
Connecting to AWS | Use I AM user roles for connecting to AWS. Refer to the following Amazon documentation for details: |
Learn more | https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/getting-started.html |
...
For | For the WebSphere MQ JMS provider | ||
---|---|---|---|
Minimum required JARs | For MQ 9You can find these under [WebSphere MQ installation directory]/java/lib:
For MQ 8You can find these under [WebSphere MQ installation directory]/java/lib:
For MQ 7.0You can find these under [WebSphere MQ installation directory]/java/lib:
You also need to download the following jar:
For MQ 6.0You can find these under [WebSphere MQ installation directory]/java/lib:
You also need to download the following jars:
MQ Client DownloadThe jars from [WebSphere MQ installation directory]/java/lib are also included in the MQ Client. The MQ 6 Client is no longer available from IBM. The MQ 7 Client is available at http://www-01.ibm.com/support/docview.wss?uid=swg24019253 | ||
Typical provider URL pattern | yourhostname:1414/SYSTEM.DEF.SVRCONN | ||
Factory class | WebSphere MQ JNDI Initial Context factory class - com.ibm.mq.jms.context.WMQInitialContextFactory | ||
SSL configuration | WebSphere JMS clients can achieve SSL connections by setting the appropriate properties in the initial context. Both WebSphere MQ and WebSphere JMS clients will set the same properties for SSL connectivity. | ||
JMS messaging without JNDI | Under the properties tab, define the following properties:
| ||
Additional information | IBM's JNDI provider authenticates itself with the Websphere MQ server by sending the user's login name. This is typically the user name that was provided when logging into the workstation before starting SOAtest/Virtualize. If the MQ server does not recognize the user name, then your tool will fail with the error "javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager". This error can be resolved by adding a Windows user account on the Websphere MQ server machine. This account should 1) have the same user name as the account on the local machine whereSOAtest and VirtualizeSOAtestVirtualizeis Virtualizeis running and 2) be a member of the "mqm" IBM WebSphere MQ Administration Group. Alternatively, use a different user name by changing the value of the user.name Java System property. This system property can be configured by startingSOAtest and VirtualizeSOAtestVirtualizeusing Virtualizeusing It is also possible to modify Java system properties during test suite execution by using an Extension Tool to call the java.lang.System.setProperty() method from Sun's Java API. For more details on this error, see http://www.mqseries.net/phpBB/view-topic.php?t=40640. | ||
Learn more | http://www-01.ibm.com/software/integration/wmq/library/ http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaw.doc/jm10320_.htm |
...