Under the properties tab, define the following properties:
Name: Value
provider:  WebSphere IBM MQ
queue.manager: [your queue manager name]
channel: [your channel name]
port:  [port number, the default WebSphere IBM MQ port is 1414]
With this configuration, SOAtest/Virtualize will create the connection factory using the provided parameters as follows:

  import com.ibm.mq.jms.*;
  ...
  MQConnectionFactory cf = new MQConnectionFactory();
  cf.setHostName(hostname);
  cf.setPort(port);
  cf.setQueueManager(queuemanager);
  cf.setChannel(channel);
  cf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);   
  cf.setFailIfQuiesce(JMSC.MQJMS_FIQ_YES);
  cf.setUseConnectionPooling(true);

IBM's JNDI provider authenticates itself with the Websphere IBM MQ server by sending the user's login name. This is typically the user name username that was provided when logging into the workstation before starting SOAtest/Virtualize.

If the MQ server does not recognize the user nameusername, 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 IBM MQ server machine. This account should 1) have the same username as the account on the local machine where SOAtest is running and 2) be a member of the "mqm" IBM WebSphere MQ Administration Group.Alternatively, use a different username by changing the value of the user.name Java System property. This system property can be configured by starting SOAtest using soatest.exe -J-Duser.name=username where username is the username you want to use. In some configurations using an empty username via soatest/virtualize.exe -J-Duser.name= will work. Using SYSTEM for the user.name property may also work in some configurations. 

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.