Exporting Test Plan from SoapUI

We recently had a need to export the test plan from SoapUI since there was no test plan available on the project and we only had test data.

For export, we created a groovy script in the SoapUI project and with that we were able to export the Test plan.

def dir = "C:\\TEMP" def fileDirectory = new File(dir) def fileName = dir + "\\" + testRunner.testCase.testSuite.project.name + " - Test Plan Export.csv" if ( !fileDirectory.exists() ){ log.error " !ERROR!! Directory does not exists" log.error " Test plan cannot be created" return 1 } try { log.info " Test Plan exported to : ${fileName}" file = new File(fileName) file.write "TestSuite;TestCase;TestStep" testRunner.testCase.testSuite.project.testSuiteList.each{ testSuite -> testSuite.testCaseList.each{ testCase -> testCase.testStepList.each{ testStep -> file.append "\n" + testSuite.name + ";" + testCase.name + ";" + testStep.name } } } } catch(Exception ex) { log.error " ERROR! Cannot export CSV file" log.error ex return 1 } 

SoapUI: Performing Actions on Linux Machine

Automation brings many challenges which need different solutions. We also came to a situation where we had to execute a command on a Linux platform, or, read a file/log from the Linux platform.

We created a groovy script to achieve the same. We had a lot of help from several blogs and sites and I thought it would be interesting to put the result as a complete solution at once place.

import java.io.InputStream; import java.io.InputStreamReader; import java.io.PipedInputStream; import java.io.PipedOutputStream; import java.io.PrintStream; import java.io.Reader; import java.util.Properties; import com.jcraft.jsch.Channel; import com.jcraft.jsch.ChannelExec; import com.jcraft.jsch.ChannelSftp; import com.jcraft.jsch.JSch; import com.jcraft.jsch.Session; class serviceManagement { // Define variable to be used in the function /* * ---------------------------------------------------------------------------------------------------------------------------------------------- * Funtion fetchFile definition * Description : Read file supplied from the server and return the content as String * Parameters : * host : IP * Cmd : File to read * usrPrim : Primary user account to connect * pwdPrim : Primary user account password */ public fetchFile(String host, String Cmd, String usrPrim, String pwdPrim) { JSch jsch = new JSch(); Session session = jsch.getSession(usrPrim, host, 22); session.setConfig("StrictHostKeyChecking", "no"); session.setPassword(pwdPrim); session.connect(); // Define variable to read into def fileContent="" Channel channel = session.openChannel("sftp"); channel.connect(); ChannelSftp sftpChannel = (ChannelSftp) channel; InputStream stream = sftpChannel.get(Cmd); try{ BufferedReader br = new BufferedReader(new InputStreamReader(stream)); String line; while ((line = br.readLine()) != null) { fileContent = line + fileContent } } catch (Exception e) { log.error ("Exception occurred during reading file from SFTP server due to " + e.getMessage()); } return fileContent } // Define variable to be used in the function /* * ---------------------------------------------------------------------------------------------------------------------------------------------- * Funtion executeCmd definition * Description : executes a given command on the linux platform * Parameters : * host : IP * Cmd : File to read * usrPrim : Primary user account to connect * pwdPrim : Primary user account password * executedBySecondary : "true/false" based on whether the command to be launched as secondary user(root) or not * usrSecond : secondary user account to connect * pwdSecond : secondary user account password */ public void executeCmd(String host, String Cmd, String usrPrim, String pwdPrim, boolean executedBySecondary, String usrSecond, String pwdSecond) { JSch jsch = new JSch(); // verify if the command has to be executed by secondary user or by the primary login Session session = jsch.getSession(usrPrim, host, 22); session.setConfig("StrictHostKeyChecking", "no"); session.setPassword(pwdPrim); session.connect(); Channel channel = session.openChannel("shell"); OutputStream chlInputStream = channel.getOutputStream(); InputStream chlOutStream = channel.getInputStream(); InputStream chlErrStream = channel.getExtInputStream(); BufferedReader br = new BufferedReader(new InputStreamReader(chlOutStream)); String line; PrintStream cmderShell = new PrintStream(chlInputStream, true); channel.connect(); byte[] tmp = new byte[1024]; String stdOut = ""; String stdErr = ""; int i; if (executedBySecondary) { log.info " Log in as " + usrSecond + " with password : " + pwdSecond cmderShell.println("su - " + usrSecond + "\n"); while(true){ if(chlErrStream.available() > 0){ i = chlErrStream.read(tmp, 0, tmp.length); if (i < 0) exit(1) stdErr += new String(tmp, 0, i); log.info (" Read from Standard Error stream : " + stdErr); } if(chlOutStream.available() > 0){ i = chlOutStream.read(tmp, 0, tmp.length); if (i < 0) exit(1) stdOut += new String(tmp, 0, i); log.info (" Read from Standard Output stream : " + stdOut); } if (stdOut.contains("assword")) break; Thread.sleep(1000); } cmderShell.println(pwdSecond + "\n"); cmderShell.println("id"); cmderShell.println(Cmd); cmderShell.println("exit"); } else cmderShell.println(Cmd); cmderShell.println("exit"); cmderShell.close(); while((line = br.readLine()) != null) log.info line channel.disconnect(); session.disconnect(); } }

SoapUI : Maven Integration Error AutoImportMethodFactory

I have had an upgrade of my OS from Windows 7 to Windows 10. This led me to reconfigure my maven integration settings.

While launching a few of the tests that used to work perfectly before with the same configuration, I saw some new errors

10:39:11,310 ERROR [SoapUI] An error occurred [com.eviware.soapui.plugins.auto.factories.AutoDiscoveryMethodFactory], see error log for details
java.lang.ClassNotFoundException: com.eviware.soapui.plugins.auto.factories.AutoDiscoveryMethodFactory
        at java.lang.Class.forNameImpl(Native Method)
        at java.lang.Class.forName(Class.java:333)
        at com.eviware.soapui.plugins.LoaderBase.loadAutoFactories(LoaderBase.java:96)
        at com.eviware.soapui.plugins.LoaderBase.loadFactories(LoaderBase.java:64)
        at com.eviware.soapui.plugins.PluginLoader.loadPluginFactories(PluginLoader.java:129)
        at com.eviware.soapui.plugins.PluginLoader.loadPlugin(PluginLoader.java:92)
        at com.eviware.soapui.plugins.PluginLoader.loadPlugin(PluginLoader.java:42)
        at com.eviware.soapui.plugins.PluginManager.doInstallPlugin(PluginManager.java:136)
        at com.eviware.soapui.plugins.PluginManager.access$600(PluginManager.java:38)
        at com.eviware.soapui.plugins.PluginManager$LoadPluginsTask.computeSequentially(PluginManager.java:415)
        at com.eviware.soapui.plugins.PluginManager$LoadPluginsTask.compute(PluginManager.java:372)

Although these errors did not impact my tests, they did impact how the console logs were looking and hence a fix was needed.

After some google around, the fix appears to be very easy.

https://community.smartbear.com/t5/SoapUI-Open-Source/AutoDiscoveryMethodFactory-ClassNotFoundException-when-executing/td-p/105397

If the SoapUI version is 5.2.1 (I use this and found the same problem), the problem ties to the default plugins installed under "C:\Users\<user name>\.soapuios\plugin".

For SoapUI 5.2.1, there are 4 default plugins installed under this directory:

1. readyapi-swaggerhub-plugin-1.0.jar
2. ready-mqtt-plugin-dist.jar
3. ready-uxm-plugin-1.0.1-dist.jar
4. soapui-swagger-plugin-2.2-dist.jar

Just rename the original folder 'plugins' to 'plugins_NOTinUse' (or something else), so that default plugins could be forced hidden during runtime. The problem then disappeared.

It works like a charm :)

SSL Handshake Overview

Reference : https://support.f5.com/csp/article/K15292

SSL Handshake Overview

SSL communication consists of a series of messages exchanged between two parties (client and server). The SSL handshake between a client and server consists of nine steps, and appears as follows.

The SSL messages determine the parameters of the encrypted communication channel that the two parties will use. It is important that the client and server agree on the message details, such as the protocol version, cipher suites, secure renegotiation, or client certificate requests. Otherwise the handshake will fail. The SSL handshake has the following messaging components:

ClientHello

When a client first attempts to connect to an SSL server, it initiates the session by sending a ClientHello message to the server. The ClientHello message starts the SSL communication between the two systems. The ClientHello message contains some of the following components:

• Version: The version field contains the highest SSL version that the client supports.
• Random: A random number generated by the client.
• Session ID: An arbitrary sequence of bytes chosen by the server; it identifies a particular SSL session. The client may attempt to resume a previously established session by sending a non-zero session ID.
• Cipher suites: Identifies the list of ciphers suites that the client supports.
• Compression: Identifies the list of compression methods that the client supports.

ServerHello

If the server is able to find an acceptable set of algorithms, it responds to the ClientHello message with a ServerHello message. The server may use the ServerHello message to allow a resumed session. The ServerHello message contains some of the following components:

• Version: The version field contains the highest SSL version supported by both the client and server.
• Random: A random number generated by the server.
• Session ID: Identifies a particular SSL session. If the client sends a non-zero session ID and the server locates a match in its cache, the server will attempt to respond with the same value as was supplied by the client, and resume the session using the same cipher suite.
• Cipher suites: Identifies the cipher suite chosen by the server from the list of ciphers that the client supports.
• Compression: Identifies the compression method chosen by the server from the list that the client supports.

Certificate

The server sends its Certificate message containing the server's certificate or list of (chain) certificates, depending on the selected cipher suite.

Note: The server may send a ServerKeyExchange message when the server Certificate message does not contain enough data to allow the client to exchange a premaster secret. This is true of some ciphers such as DHE-DSS.

ServerHelloDone

After sending its certificate, the server sends a ServerHelloDone message, indicating it is done with handshake negotiation.

ClientKeyExchange

The client sends the ClientKeyExchange message containing the PreMasterSecret. The PreMasterSecret is sent encrypted using the public key of the server.

ChangeCipherSpec

Both the client and server send the ChangeCipherSpec message after the security parameters have been determined. The ChangeCipherSpec message activates the negotiated SSL options for the session. From this point forward, all messages are authenticated and encrypted. This stage is significant as it indicates that subsequent records will be protected under the newly negotiated CipherSpec and keys.

Finished

Each party sends a Finished message under the new algorithm, keys and secrets. The Finished message indicates that the handshake is complete, and the parties may begin to exchange application layer data.

Resumed SSL sessions

A resumed SSL session implements session identifier (session ID) to re-establish a previously negotiated session. When an SSL handshake is resumed, the client presents the session ID from the previously negotiated session. If the server finds the session ID in its cache and accepts the resumed session, it sends back the same session ID and the parties skip the public key operation. If the server does not accept the resumed session, it issues a new session ID and implements the full SSL handshake. The resumed SSL handshake between a client and server consists of the following steps.

  

 

Testing SSL connections (using s_client)

After you enable SSL debug logging on the BIG-IP system, you should test SSL connections for the virtual server using a web browser or other utility, such as the OpenSSL utility, s_client, or cURL. Using the s_client utility may provide additional debugging information that you can use to troubleshoot the issue. After making several requests to the virtual server, you can review and analyze the debug log files on the BIG-IP system.

Impact of procedure: Performing the following procedure should not have a negative impact on your system.

1. Log in to the command line of a Linux host (with a current version of OpenSSL) that can access the SSL virtual server.
   
2. To test SSL connections for the virtual server, use the following command syntax:
   
   openssl s_client -connect <virtual_server>:<port> -msg
   
   For example:
   

   openssl s_client -connect 10.12.23.115:443 -msg
   openssl s_client -connect https://<url_of_website> -msg

3. If the handshake attempt fails, take note of SSL errors returned by the s_client utility.
   
4. If the handshake succeeds, type the following at the prompt:
   
   GET / HTTP/1.0
   
5. Press Enter twice.
   
   The HTML page should display.
   

SoapUI : Websphere MQ Test Integration with Groovy

MQ Injection and reception of messages using groovy is rather easy than setting up with HermesJMS and far more stable.

Below is a simple example :

  import com.ibm.msg.client.wmq.*; import com.ibm.mq.jms.*; import javax.jms.*; // Initialize connection variables def mq_ip = context.expand('${#Project#mq_ip}') int mq_port = context.expand('${#Project#mq_port}') as Integer def mq_user = context.expand('${#Project#mq_user}') def mq_pass = context.expand('${#Project#mq_pass}') def mq_qmgr = context.expand('${#Project#mq_qmgr}') def mq_in_q = context.expand('${#Project#mq_in_q}') def mq_out_q = context.expand('${#Project#mq_out_q}') // Get XML Request from the previous Step //testRunner.testCase.testSteps["Order 1"].testRequest.response.getRequestContent() MQQueueConnectionFactory qcf = new MQQueueConnectionFactory(); // Host and port settings qcf.setHostName (mq_ip); qcf.setPort (mq_port); // Queue manager and channel — the W-MQ administrator should supply these qcf.setQueueManager (mq_qmgr); qcf.setChannel ("SYSTEM.ADMIN.SVRCONN"); // Although there are many possible values of transport type, // only 'client' and 'bindings' work in a Java client. Bindings // is a kind of in-memory transport and only works when the client // and the queue manager are on the same physical host. In most // cases, we need 'client'. //qcf.setTransportType (WMQConstants.WMQ_CM_BINDINGS); qcf .setTransportType (WMQConstants.WMQ_CM_CLIENT); QueueConnection qc = qcf.createQueueConnection (mq_user,mq_pass); //set credentials // QueueConnection qc = qcf.createQueueConnection (); // if authenticaiton is disabled qc.start(); // Create a queue and a session Queue in = new MQQueue (mq_in_q); Queue out = new MQQueue (mq_out_q); QueueSession s = qc.createQueueSession (false, Session.AUTO_ACKNOWLEDGE); // Create and send a TextMessage QueueSender qs = s.createSender (in); Message m = s.createTextMessage ("Your message text"); qs.send (m); qs.close(); // Receive a TextMessage QueueReceiver qr = s.createReceiver(out); TextMessage message = (TextMessage) qr.receive(); log.info message.getText() qr.close() // Stop and close Connection qc.stop(); qc.close();

While integrating with maven, you will have to ensure that you have included the following dependencies in your pom file.

<dependencies> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.jms</artifactId> <version>8.0.0.3</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.mq.allclient</artifactId> <version>8.0.0.5</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.mq.jmqi</artifactId> <version>7.1.0.1</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.mq</artifactId> <version>7.1.0.1</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.mqbind</artifactId> <version>5.3</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>com.ibm.mqjms</artifactId> <version>7.1.0.1</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>dhbcore</artifactId> <version>7.1.0.1</version> </dependency> <dependency> <groupid>com.ibm.mq</groupId> <artifactid>mqconnector</artifactId> <version>6.0.2.4</version> </dependency> </dependencies>

Creating Multi-Module Pom Project

In one of my previous posts, I've written about creating maven project for simple purpose. Of course maven can be used for more complex projects as well and the structure defined by maven becomes really useful.

While working on a project you'd realize it has more complex needs, you would need a system where you can develop different independent components and that leads to the scenario we are going to cover in this post. We will be creating a project with maven which will serve as parent, or you can say binding element for the build of the other sub-projects or modules. Maven has a feature which allows you to create multi module project. We are going to see how.

To create a multi module project, we will have to start with a simple project about which you can learn from my previous post Creating a simple Maven Project.

# mvn archetype:generate -DgroupId=myProject.myCompany.com -DartifactId=myProject -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

Once done, you  would see that a directory with name "myProject" as per the artifactId defined earlier is created. Now move into this directory where you would see the pom.xml file created by maven the pom file may appear as below :

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelversion>4.0.0</modelVersion> <groupid>myProject.myCompany.com</groupId> <artifactid>myProject</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>myProject</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupid>junit</groupId> <artifactid>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> </project>

Before we move to creation of the modules, we need to do some changes in the parent pom file which was stated above. Locate and modify the lines as given below.
<packaging>pom</packaging>
Modify the parameter packaging from "jar" to "pom". Now using the below command, you can create the modules.

# mvn archetype:generate -DgroupId=myProject.myCompany.com -DartifactId=myModule1 -DinteractiveMode=false

You will notice that a new directory is created in the parent directory, open the pom file inside which would appear as below

<?xml version="1.0"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelversion>4.0.0</modelVersion> <parent> <groupid>myProject.myCompany.com</groupId> <artifactid>myProject</artifactId> <version>1.0-SNAPSHOT</version> </parent> <groupid>myProject.myCompany.com</groupId> <artifactid>myModule1</artifactId> <version>1.0-SNAPSHOT</version> <name>myModule1</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupid>junit</groupId> <artifactid>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> </project>
You will also notice that there are few extra lines added in the main project pom file as below <modules> <module>myModule1</module> </modules> Every new module created will have similar to above line added to the main pom.xml file. So that was quick update about creating a multi module pom project, hope you enjoyed and it was helpful.

Update
If you are running a latest version of maven, you would realize that the build is failing with rather strange error as below

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project myModule1: Compilation failure: Compilation failure:

[ERROR] Source option 5 is no longer supported. Use 6 or later.

[ERROR] Target option 1.5 is no longer supported. Use 1.6 or later.

If you have the above error while build, you might need to  add below lines in the main project's (parent) pom file under "project" head.

<properties> <maven.compiler.source>1.6</maven.compiler.source> <maven.compiler.target>1.6</maven.compiler.target> </properties>
With above changes, you should be able to build your project successfully using the command

# mvn clean install

SoapUI, HermesJMS, IBM Websphere MQ automation with Maven

I was working on the project where I need to automate tests with interact with IBM websphere MQ queues. I have been able to achieve it from SoapUI and HermesJMS (I have already talked about the steps in my old post here) soon to face the next challenge to integrate with Jenkins and run the tests with scheduled builds. 
In my hope to find an existing solution on net, I looked for it on google. Unfortunately it didn't help that much as the solutions available did not help me but they gave me an idea about how to achieve the same. I am using maven for integration of my solution here.

Step 1 : HeremesJMS Configuration File

I would suggest to simplify the HermesJMS configuration file which was created in the steps performed in exercise earlier. Remove all the unnecessary elements and keep only those that you would need for your test.  Here below is my configuration file which I've used

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <config lastEditedByUser="BFDB8245" lastEditedByHermesVersion="v1.14" maxThreadPoolSize="5" auditDirectory="C:\temp" messageFilesDir="C:\.hermes\.\messages" maxMessagesInBrowserPane="1000" copyJMSProviderProperties="true" copyJMSCorrelationID="true" copyJMSType="true" copyJMSExpiration="true" copyJMSReplyTo="true" copyJMSPriority="true" displayFactoryAdmin="true" maxColumnsInStatisticsTable="10" autoBrowseRefreshRate="10" correctDropSemantics="false" selectorImpl="hermes.selector.JAMSELMessageSelectorFactory" queueBrowseConsumerTimeout="0" enableJython="true" lookAndFeel="com.sun.java.swing.plaf.windows.WindowsLookAndFeel" scrollMessagesDuringBrowse="true" base64EncodeMessages="true" showDestinationsInMessageStore="false"> <classpathgroup id="WebSphere"> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.allclient.jar" noFactories="false" factories="com.ibm.mq.jms.Cleanup,com.ibm.mq.jms.MQConnectionFactory,com.ibm.mq.jms.MQQueueConnectionFactory,com.ibm.mq.jms.MQRRSConnectionFactory,com.ibm.mq.jms.MQRRSQueueConnectionFactory,com.ibm.mq.jms.MQRRSTopicConnectionFactory,com.ibm.mq.jms.MQTopicConnectionFactory,com.ibm.mq.jms.MQXAConnectionFactory,com.ibm.mq.jms.MQXAQueueConnectionFactory,com.ibm.mq.jms.MQXATopicConnectionFactory,com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsJndiConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsJndiXAConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsXAConnectionFactoryImpl,com.ibm.msg.client.mqlight.factories.MQBMConnectionFactory"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.axis2.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.commonservices.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.defaultconfig.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.headers.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.jmqi.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.jms.Nojndi.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.pcf.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.postcard.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.soap.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.tools.ras.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mq.traceControl.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONcom.ibm.mqjms.jar" noFactories="false" factories="com.ibm.mq.jms.Cleanup,com.ibm.mq.jms.MQConnectionFactory,com.ibm.mq.jms.MQQueueConnectionFactory,com.ibm.mq.jms.MQRRSConnectionFactory,com.ibm.mq.jms.MQRRSQueueConnectionFactory,com.ibm.mq.jms.MQRRSTopicConnectionFactory,com.ibm.mq.jms.MQTopicConnectionFactory,com.ibm.mq.jms.MQXAConnectionFactory,com.ibm.mq.jms.MQXAQueueConnectionFactory,com.ibm.mq.jms.MQXATopicConnectionFactory,com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsJndiConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsJndiXAConnectionFactoryImpl,com.ibm.msg.client.jms.admin.JmsXAConnectionFactoryImpl,com.ibm.msg.client.mqlight.factories.MQBMConnectionFactory"/> <library jar="MQ_LIB_LOCATIONfscontext.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONjms.jar" noFactories="true"/> <library jar="MQ_LIB_LOCATIONproviderutil.jar" noFactories="true"/> </classpathGroup> <renderer className="hermes.renderers.DefaultMessageRenderer"> <properties> <property name="bytesIsString" value="false"/> <property name="bytesIsObject" value="false"/> <property name="active" value="true"/> <property name="messageCache" value="100"/> <property name="bytesIsObjectBufferSize" value="65536"/> <property name="toStringOnObjectMessage" value="false"/> </properties> </renderer> <renderer className="hermes.renderers.DefaultMessageHeaderRenderer"> <properties> <property name="active" value="true"/> </properties> </renderer> <renderer className="hermes.renderers.ToStringMessageRenderer"> <properties> <property name="active" value="true"/> </properties> </renderer> <renderer className="hermes.renderers.HexMessageRenderer"> <properties> <property name="active" value="true"/> </properties> </renderer> <renderer className="hermes.renderers.XMLMessageRenderer"> <properties> <property name="active" value="true"/> </properties> </renderer> <renderer className="hermes.renderers.fix.FIXMessageRenderer"> <properties> <property name="displayValueWithEnum" value="true"/> <property name="active" value="true"/> <property name="messageCache" value="100"/> <property name="displayHeaderAndTrailer" value="true"/> </properties> </renderer> <renderer className="hermes.renderers.EBCDICMessageRenderer"> <properties> <property name="rowLength" value="16"/> <property name="undisplayableChar" value="."/> <property name="active" value="true"/> <property name="maxMessageSize" value="5242880"/> </properties> </renderer> <factory classpathId="System"> <provider className="hermes.providers.file.FileConnectionFactory"> <properties> <property name="baseDirectory" value="${hermes.home}/bin/messages"/> </properties> </provider> <connection clientID="" connectionPerThread="false"> <session id="Files" reconnects="0" audit="false" useConsumerForQueueBrowse="false"/> </connection> <destination name="examples.xml" domain="1"/> <destination name="fix.xml" domain="1" durable="false" useLocalRenderer="true"/> <extension className="hermes.ext.DefaultHermesAdminFactory"> <properties/> </extension> </factory> <factory classpathId="WebSphere"> <provider className="com.ibm.mq.jms.MQQueueConnectionFactory"> <properties> <property name="channel" value="SYSTEM.ADMIN.SVRCONN"/> <property name="hostName" value="192.168.0.101"/> <property name="port" value="1414"/> <property name="transportType" value="1"/> <property name="queueManager" value="MYQMGR"/> </properties> </provider> <connection clientID="" connectionPerThread="false"> <session id="MYQMGR" reconnects="0" transacted="true" audit="false" useConsumerForQueueBrowse="false"/> </connection> <destination name="alias.response.queue" domain="1"/> <destination name="response.queue" domain="1"/> <extension className="hermes.ext.mq.MQSeriesAdminFactory"> <properties/> </extension> </factory> <factory classpathId="WebSphere"> <provider className="com.ibm.mq.jms.MQQueueConnectionFactory"> <properties> <property name="channel" value="SYSTEM.ADMIN.SVRCONN"/> <property name="hostName" value="192.168.0.102"/> <property name="port" value="1441"/> <property name="queueManager" value="APPQMGR"/> <property name="transportType" value="1"/> </properties> </provider> <connection clientID="" connectionPerThread="false"> <session id="APPQMGR" reconnects="0" transacted="true" audit="false" checkSize="false" checkSizePeriod="1000" useConsumerForQueueBrowse="false"/> </connection> <destination name="alias.request.queue" domain="1"/> <destination name="request.queue" domain="1"/> <extension className="hermes.ext.mq.MQSeriesAdminFactory"> <properties/> </extension> </factory> <quickfix cacheSize="1024" filterSessionMsgTypes="false"/> </config>

You would notice that I've used a keyword "MQ_LIB_LOCATION" while providing the path of the IBM websphere MQ dependency jar files which are used by HermesJMS in order to create connection. While my experiment I realized that in order to be able to run my build I'll have to keep my hermes configuration file autonomous. Hence, I needed to update the file dynamically with help of "com.google.code.maven-replacer-plugin" of maven. With help of this plugin I change the path of the libraries used by HermesJMS.

Step 2 : Create Maven Project skeleton

As explained above we will have to update the Hermes configuration files dynamically, hence a separate maven project module would be needed for achieving this and another module will be used to execute the SoapUI project.

Create the master project using below command and then the modules under the master project

mvn archetype:generate -DgroupId=myorg.com -DartifactId=myapp -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

This command will create a directory "myapp" with the master project, now edit the pom file and change "packaging" parameter from "jar" to "pom" and remove the directory "src" from the master project as you will not be using it.
Once done, you can create the modules. Go to the master project directory and create the two modules with below commands

mvn archetype:generate -DgroupId=myorg.com -DartifactId=SoapProject -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

mvn archetype:generate -DgroupId=myorg.com -DartifactId=UpdateHermesJMS -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false

Now the two projects are ready, you can update the pom file to meet your need. We will start with the project to update the Hermes configuration.

Step 3 : Module UpdateHermesJMS

Now is the time to setup your module to update the hermesJMS configuration to be able to run in any environment. For this add a "com.google.code.maven-replacer-plugin" plugin to the project. I have created a folder "resources" under "src/main/" where I have put the folder for hermes configuration "hermes", the package of hermes "HermesJMS" and the library files for IBM Websphere MQ which is needed by HermesJMS for connecting to websphere MQ.
Below is example from my project : 
<build> <plugins> <plugin> <groupid>com.google.code.maven-replacer-plugin</groupId> <artifactid>replacer</artifactId> <version>1.5.3</version> <executions> <execution> <phase>prepare-package</phase> <goals> <goal>replace</goal> </goals> <configuration> <file>${basedir}/src/main/resources/hermes/hermes-config.xml</file> <replacements> <replacement> <token>MQ_LIB_LOCATION</token> <value>${basedir}/src/main/resources/mq-lib/</value> </replacement> <replacement> <token>AUDITDIR</token> <value>/tmp</value> </replacement> </replacements> </configuration> </execution> </executions> </plugin> </plugins> </build>

Step 4 : Module SoapProject

You are now set to work on the final module which is going to execute the SoapUI tests. There are few elements you should focus on and we will discuss about them one by one. 

Dependencies : Since the module UpdateHermesJMS should be executed before the SoapProject in order to have your configuration ready, this project needs to be prioritized. For that we need to define this module as dependency in the SoapProject module

<dependency> <groupid>myorg</groupId> <artifactid>updateHermesConf</artifactId> <version>1.0-SNAPSHOT</version> </dependency>

Another level of dependencies has to be defined at plugin level for HermesJMS and websphere MQ library. 

<dependencies> <dependency> <groupid>com.oracle</groupId> <artifactid>ojdbc14</artifactId> <version>10.2.0.4.0</version> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mq</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mq.jar</systemPath> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mq.jms.Nojndi</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mq.jms.Nojndi.jar</systemPath> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mq.commonservices</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mq.commonservices.jar</systemPath> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mq.jmqi</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mq.jmqi.jar</systemPath> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mq.headers</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mq.headers.jar</systemPath> </dependency> <dependency> <groupid>com.ibm</groupId> <artifactid>com.ibm.mqjms</artifactId> <version>8.0</version> <scope>system</scope> <systempath>${basedir}/../updateHermesConf/src/main/resources/mq-lib/com.ibm.mqjms.jar</systemPath> </dependency> <dependency> <groupid>hermesjms</groupId> <artifactid>hermes</artifactId> <version>1.14</version> </dependency> </dependencies>

I hope you are already aware of the SoapUI project execution and related plugin. The only thing extra you may have to do is to define two additional global variable for your project that will be used by SoapUI to configure HermesJMS

<globalProperties>
    <value>HERMES_JMS=${basedir}/../updateHermesConf/src/main/resources/HermesJMS</value>
    <value>hermesConfig=${basedir}/../updateHermesConf/src/main/resources/hermes</value>
</globalProperties>

Step 5 : Project LoadScript

Your maven project should be ready, however your project still needs one more tweeks in order to be able to use the right HermesJMS and corresponding configuration file.
Open your SoapUI workspace, right click on the project click on "Show Project View" and go on "Load Script" on the window of the project and insert the below script to configure HermesJMS and its configuration from the variables we have defined in previous step.

import com.eviware.soapui.SoapUI; import com.eviware.soapui.settings.ToolsSettings; import com.eviware.soapui.support.Tools; def hermesHome = SoapUI.globalProperties.getPropertyValue("HERMES_JMS"); def hermesConfig = SoapUI.globalProperties.getPropertyValue("hermesConfig"); log.info "************************************************************************************"; log.info " Current Hermes Tool : " + SoapUI.getSettings().getString( ToolsSettings.HERMES_JMS, null ); log.info " Curremt Hermes Config : " + project.getHermesConfig(); log.info ""; log.info " Updating Hermes Tool with : $hermesHome . . ."; SoapUI.getSettings().setString( ToolsSettings.HERMES_JMS, hermesHome ); log.info " Updating HermesConfig location : $hermesConfig . . . "; project.setHermesConfig(hermesConfig); log.info " New Hermes Tool : " + SoapUI.getSettings().getString( ToolsSettings.HERMES_JMS, null ); log.info " New Hermes Config : " + project.getHermesConfig(); log.info "************************************************************************************";

Now you are all set with the project and you can integrate your maven project on Jenkins with a simple maven build.