Wednesday, October 14, 2015

SOAPUI Test Automation using Maven and Jenkins

In this article I will explain how to run SOAPUI tests in headless mode. We will use Maven and Jenkins for automation. There is soapui-maven-plugin available to do the job. I assume that you know how to create SOAPUI project and create Test suits/cases. You can refer to SOAPUI tutorial if need help in creating projects/test suits/test cases.

Here I will take a simple example of Functional test; however you can scale it up for load test as well.

Environment:
                   SOAPUI 5.0.0 (free version)
                   Maven 3.3.3
                   Jenkins 1.633

If you want to know how to configure Maven and Jenkins, pls refer to my post :
http://anandawasthitech.blogspot.com/2015/10/iib-continuousintegration-maven-jenkins.html

Step1: Create SOAPUI Project:

                 Create a SOAPUI project and create a Test Suit. Add a Test case in this Test Suit. You can configure project properties to pass the values dynamically in your request. You can pass the property value using the syntax "${#Project#PropertyName}" See the below example:

Click on the project and click on '+' button under 'Custom Properties'. Add a property name and value. In the soap request, supply this property. Refer to below screen-shot:

Further you can set assertions to validate the response. All this depends on your requirement, you can configure it accordingly.

Let us save the soapui project.

Step2: Update Maven settings.xml:
      Add below plugin repository in settings.xml for Maven:
<pluginRepositories>
    <pluginRepository>
        <id>smartbear-sweden-plugin-repository</id>
        <url>http://www.soapui.org/repository/maven2/</url>
    </pluginRepository>
</pluginRepositories>

For this example, I have added it to my POM.xml; however ideally you should add these repositories in settings.xml.

Step3: Create POM.xml for SOAPUI project:

Below is the sample POM.xml for my SOAPUI project.

<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>

   <name>Enterprise Quote Clearance</name>
   <groupId>com.esb.soapui</groupId>
   <artifactId>EnterpriseQClearance</artifactId>
   <version>1.0-SNAPSHOT</version>
   <packaging>jar</packaging>
   <description>Enterprise Quote Clearance</description>  

<pluginRepositories>
<pluginRepository>
        <id>smartbear-sweden-plugin-repository</id>
        <url>http://www.soapui.org/repository/maven2/</url>
    </pluginRepository>
</pluginRepositories>   
   <build>
      <plugins>            
         <plugin>
            <groupId>com.smartbear.soapui</groupId>
<artifactId>soapui-maven-plugin</artifactId>
<version>4.6.1</version>
            <executions>
               <execution>
                  <id>QClearanceTest</id>
                  <goals>
                     <goal>test</goal> 
                  </goals>
                  <phase>test</phase>           
               </execution>
            </executions>                       
            <configuration>
               <projectFile>C:\Anand\DevOps\QClearance\src\test\soapui\EnterpriseClearanceService-soapui-project.xml</projectFile>
  <testSuite>TestSuite 1</testSuite>
  <testCase>DCItems</testCase>
  <endpoint>http://esbserver.com:7800/EntClearanceService/EnterpriseClearanceService</endpoint>               
               <outputFolder>${project.build.directory}/surefire-reports</outputFolder>
               <junitReport>true</junitReport>
               <printReport>false</printReport>
               <projectProperties>
                  <projectProperty>NameInsured=IBM</projectProperty>
               </projectProperties>
  <settingsFile>C:\Anand\DevOps\QClearance\src\test\soapui\soapui-settings.xml</settingsFile>
            </configuration>
         </plugin>   
      </plugins>
   </build>          
</project>

You need to update the values for elements in 'Configuration' per your project. If you want to execute all the Test cases inside a Test Suit, simple 'testCase' element. Similarly if you want to execute all the Test Suites in the project, simly remove testSuit element as well.
Note that I have supplied the value for 'projectProperty' (NameInsured=IBM) that we had set in soapui project.
Note the element 'settingsFile'. We can use this file to configure the SOAPUI properties for my test. Here I am overwriting socket timeout to 200 seconds using 'soapui-settings.xml'. Give the absolute path for this file.
Below is the content of 'soapui-settings.xml':

<con:soapui-settings xmlns:con="http://eviware.com/soapui/config">
   <con:setting id="HttpSettings@socket_timeout">200000</con:setting>
</con:soapui-settings>

Jenkins will use this timeout value. By default Jenkins uses 60 seconds socket timeout, so I have increased it to 200 seconds for requests that take long time to come back.

You can refer to smartbear website to get the information about the variables that you can set. You can configure those as per your requirement.

http://www.soapui.org/test-automation/maven/maven-2-x.html


Save the POM.xml at the same location where you saved the soapui project.

Step 4: Create Jenkins Job:
Click on New Item and select 'Maven project' and give it a name:

You can do Source control configuration; however for this example to keep it simple we will just use a local project.

In 'Build', supply absolute path for POM.xml of soapui project and provide goal & options. You can give custom workspace also for jenkins.


Save the Job.
Now you are all set to run SOAPUI test Jenkins job. I ran my test and got the below result:

Started by user anonymous
Building in workspace C:\Anand\DevOps\QClearance\src\test\soapui
Parsing POMs
Established TCP socket on 50629
[soapui] $ "C:\Program Files\Java\jdk1.7.0_79/bin/java" -Xms1024m -Xmx4096m -XX:PermSize=1024m -cp "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.7.jar;C:\Anand\DevOps\apache-maven-3.3.3\boot\plexus-classworlds-2.5.2.jar;C:\Anand\DevOps\apache-maven-3.3.3/conf/logging" jenkins.maven3.agent.Maven32Main C:\Anand\DevOps\apache-maven-3.3.3 "C:\Program Files (x86)\Jenkins\war\WEB-INF\lib\remoting-2.52.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.7.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.7.jar" 50629
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven:  -B -f C:\Anand\DevOps\QClearance\src\test\soapui\pom.xml -s C:\Anand\DevOps\apache-maven-3.3.3\conf\settings.xml -gs C:\Anand\DevOps\apache-maven-3.3.3\conf\settings.xml clean test
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Enterprise Quote Clearance 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ EnterpriseQClearance ---
[INFO] Deleting C:\Anand\DevOps\QClearance\src\test\soapui\target
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ EnterpriseQClearance ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Anand\DevOps\QClearance\src\test\soapui\src\main\resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ EnterpriseQClearance ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ EnterpriseQClearance ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Anand\DevOps\QClearance\src\test\soapui\src\test\resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ EnterpriseQClearance ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ EnterpriseQClearance ---
[INFO] No tests to run.
[JENKINS] Recording test results
[INFO] 
[INFO] --- soapui-maven-plugin:4.6.1:test (QClearanceTest) @ EnterpriseQClearance ---
SoapUI 4.6.1 Maven2 TestCase Runner
06:54:11,965 WARN  [SoapUI] Missing folder [C:\Anand\DevOps\QClearance\src\test\soapui\.\ext] for external libraries
06:54:12,461 INFO  [DefaultSoapUICore] initialized soapui-settings from [C:\Anand\DevOps\QClearance\src\test\soapui\soapui-settings.xml]
06:54:13,913 INFO  [WsdlProject] Loaded project from [file:/C:/Anand/DevOps/QClearance/src/test/soapui/EnterpriseClearanceService-soapui-project.xml]
06:54:13,914 WARN  [WsdlProject] Project 'EnterpriseClearanceService' is from a newer version (5.0.0) of SoapUI than this (4.6.1) and parts of it may be incompatible or incorrect. Saving this project with this version of SoapUI may cause it to function differently.
06:54:14,613 INFO  [SoapUITestCaseRunner] Setting project property [NameInsured] to [IBM]
06:54:14,638 INFO  [SoapUITestCaseRunner] Running SoapUI tests in project [EnterpriseClearanceService]
06:54:14,639 INFO  [SoapUITestCaseRunner] Running TestCase [DCItems]
06:54:14,713 INFO  [SoapUITestCaseRunner] Running SoapUI testcase [DCItems]
06:54:14,738 INFO  [SoapUITestCaseRunner] running step [GetDCItemsForClearance - Request 1]
06:54:15,291 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request
06:54:15,292 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: POST /EntClearanceService/EnterpriseClearanceService HTTP/1.1
06:55:18,840 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Receiving response: HTTP/1.1 200 OK
06:55:18,850 DEBUG [HttpClientSupport$SoapUIHttpClient] Connection can be kept alive indefinitely
06:55:20,154 INFO  [SoapUITestCaseRunner] Assertion [SOAP Response] has status VALID
06:55:20,155 INFO  [SoapUITestCaseRunner] Assertion [Not SOAP Fault] has status VALID
06:55:20,158 INFO  [SoapUITestCaseRunner] Finished running SoapUI testcase [DCItems], time taken: 65403ms, status: FINISHED
06:55:20,159 INFO  [SoapUITestCaseRunner] TestCase [DCItems] finished with status [FINISHED] in 65403ms
[JENKINS] Recording test results
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:17 min
[INFO] Finished at: 2015-10-14T06:55:23-04:00
[INFO] Final Memory: 27M/982M
[INFO] ------------------------------------------------------------------------
[JENKINS] Archiving C:\Anand\DevOps\QClearance\src\test\soapui\pom.xml to com.endur.esb.soapui/EnterpriseQClearance/1.0-SNAPSHOT/EnterpriseQClearance-1.0-SNAPSHOT.pom
channel stopped
Finished: SUCCESS

Tuesday, October 13, 2015

WMQ High Availability (Multi-Instance) Setup

In this article I will describe how to setup HA Queue Managers using Multi-Instance feature in RHEL. Please note that multi-instance support was added starting WMQ v7, so it is not applicable for lower MQ versions. Also, both the MQ machines participating in HA configuration must be running same MQ versions.

Environment:
                  Operating System:  RedHat Linux 6
                  Shared Storage:     NFS v4
                  WMQ:                     v 7.5


Note that you must have 'root' level access to perform the steps.

Assumption:
                We have two WMQ servers (mq.server1 and mq.server2) and one NFS server (nfs.server). We will use id 'mqm' for MQ administration purpose.

Now let us make sure that all the servers (NFS server and MQ servers) have correct configuration.

1) Verify NFS Server:
      Lets us assume that the drive 'nfsshare' has been mounted on NFS server and we will use /nfsshare/MQ for storing data and logs of our Queue Managers.

Log-on to NFS server with root access.
Run the command:
cat  /etc/exports

It must display below result
/nfsshare *(rw,no_root_squash,sync,no_wdelay)

If not, update the /etc/exports to have above entry.
Run the command “showmount –e”. It should display below result (hostname will be your virtual machine):
If user mqm doesn't exist on NFS server, you can use below commands to set this up and set adequate permissions (as you are logged-on as root):
chmod -R 775 /nfsshare            
groupadd -g 501 mqm
useradd -g 501 -d /home/mqm -s /bin/bash -u 495 mqm

* Here I have choosesn groupid 501 for group mqm and userid 495 for user mqm. You can have different vlaues, but they should be in sync with corresponding mqm user and groups on NFS client machines (MQ Servers).

Set the appropriate password using 'passwd' command.

Make sure that /nfsshare/MQ/data and /nfsshare/MQ/log directories exist and have correct ownership.
mkdir  /nfsshare/MQ
mkdir  /nfsshare/MQ/data
mkdir  /nfsshare/MQ/log
chown -R mqm:mqm /nfsshare/MQ

Run the command “id mqm”. Verify that below output is displayed.


Now disable IPv4 filters:
service iptables stop
chkconfig iptables off

Add NFS4 domain:
echo "Domain = local.domain" >> /etc/idmapd.conf

Run below commands as well:
chkconfig nfs on
service rpcidmapd restart
chkconfig rpcidmapd on
service nfs start

Run the command “chkconfig --list iptables”. Below result should be displayed:
Run the command “cat /etc/idmapd.conf” and verify that below entry is present in the output:
Run the command “chkconfig --list rpcidmapd”. Below output should be displayed:
Run the command “service rpcidmapd status”. Below output should be displayed

Run the command “chkconfig --list nfs”. It should display below result:

  Run the command “service nfs status” or “/etc/init.d/nfs status”. It should display below results:

Verify that /nfsshare has below permissions & ownership set:
Verify that ‘data’ and ‘log’ directories have been created inside ‘MQ’ directory and have below permission 775 and mqm:mqm ownership.

If all the above tests are positive, nfs server virtual machine is correctly setup for WMQ. Now reboot the machine using below command:

/sbin/shutdown –r 0

After nfs server is rebooted, it’s ready to use.

2) Verify MQ Servers (NFS Clients):
Make sure that /nfsshare/MQ from NFS server is mounted on /MQ at WMQ server properly and adequate permissions have been setup.
Login as root on MQ. Validate below stuffs on both WMQ servers and correct the configuration is any issue.

Run the command “id mqm”. Verify that below results are displayed:
Make sure that you have directory '/MQ' on WMQ servers and mount /nfsshare/MQ on it. You can do it by adding it in /etc/fstab.
mkdir /MQ

Also, run below commands:
service iptables stop
chkconfig iptables off 
service netfs stop
chkconfig netfs on
echo "umask 0002" >> /var/mqm/.bashrc 
chown -R mqm:mqm /var/mqm   

Run the command “cat /etc/fstab”. Verify that nfs mount entry is present there as below, if not then make this entry:
Make sure that netfs is started and restart rpcidmapd and nfslock after adding domain in /etc/idmapd.conf
service netfs start 
echo "Domain = local.domain" >> /etc/idmapd.conf
service rpcidmapd restart
service nfslock restart


Run the command “df –k”. Verify that it displays the nfs mount (/MQ) as below:
Check the ownership and permissions of MQ. It should be as below:
Verify that ‘data’ and ‘log’ directories are displayed in MQ and have permissions 775 and ownership mqm:mqm.

You can see the mount information using the command mount -v

Run the command “chkconfig --list iptables”. Below should be the output:


Run the command “chkconfig --list netfs”. Below should be the output:
Run the command “service netfs status” or “/etc/init.d/netfs status”. Below output should be displayed:
Run the command “cat /var/mqm/.bashrc”. Below should be output (note the umask 0002):
Run the command “cat /etc/idmapd.conf”. It should have below entry:
Run the command “chkconfig –list rpcidmapd”. Below should be the output:
Run the command “service rpcidmapd status” or “/etc/init.d/rpcidmapd status”. Below should be the output
If all these tests are positive, your WMQ virtual machines is setup correctly to use the nfs mount. 



3) Create HA Queue Managers:
 Now you can simply create Queue Managers and give data & log path to Shared storage.

On mq.server1:
                 crtmqm -ld /MQ/log -md /MQ/data TEST_QM

dspmqinf -o command TEST_QM
Copy the output of the above command to Notepad. The output will be in the following format:
addmqinf -s QueueManager -v Name=TEST_QM -v Directory=TEST_QM -v Prefix=/var/mqm -v  
    DataPath=...

On mq.server2:
Paste the output of the command was saved in Notepad in Step 4:
# addmqinf -s QueueManager -v Name=TEST_QM -v Directory=TEST_QM -v Prefix=/var
/mqm -v DataPath=...
WebSphere MQ configuration information added.
#

Now you can start the multi-instance queue manager using -x option on both the servers. Whichever instance is started first, will become active and the other one will be standby.
strmqm -x TEST_QM

You can switch the state using the supplied commands. Please see WMQ infocenter for more information.

Thursday, October 8, 2015

IIB (v9 & v10)-ContinuousIntegration-Maven-Jenkins

[UPDATE]:- This article has been updated on 08/24/2018 to support build of IIB 10 projects. Wherever is mentioned v9 only, read it as v9 & v10. .
V10 plugin allows you to make Shared libraries as maven projects & build them independently. Note that the plugin code has been updated to make sure that shared libraries are not included in the bar files of referring projects to avoid unplanned changes in shared library going into runtime.

You can leave your comment or reach out to me at anand.awasthi@gmail.com if need help



In this article I will explain how to build an IIB (IBM Integration Bus v9 & v10) project and deploy the bar file to target Integration Server using Maven and Jenkins. I have not found very useful information around this, so thought to put it together. Here I will take a basic scenario and will explain all steps. You should be able to use this information to build the CI infrastructure for IIB in your enterprise.

Scenario:
             -- Build IIB (v9 & v10) projects
            -- Create BAR file with all referenced libraries/projects/jars
            -- Overwrite BAR file Node properties and User Defined Properties using Properties file
            -- Deploy this BAR file on target Integration Server

Environment:
                   IIB v9,v10
                   Maven 3.3.3
                   Jenkins 1.632
                   IIB-Maven-Plugin (from github)
                   Maven Eclipse Plugin (m2e) v1.4.1
                   TFS (Team Foundation Server) 2012
Operation System:
                  Windows 7

Step 1: Make sure that IIB v9 runtime and Toolkit are installed on your Build server. I assume this is already in place.

Step 2: Install Maven 3.3.3 or latest version. I have used version 3.3.3 here. If you are new to Maven, don't worry. It's a very simple installation. Below are steps to do it:
   -- Download Maven 3.3.3 Binary Zip archive from https://maven.apache.org/download.cgi
   -- Extract distribution archive in any directory
   -- Ensure JAVA_HOME environment variable is set and points to your JDK installation
   -- Add the bin directory of the created directory apache-maven-3.3.3 to the PATH environment variable
   -- Confirm with mvn -v in a new shell. The result should look similar to

-- Optionally you can change the local repository location in maven settings.xml . You can find settings.xml in 'conf' directory inside your maven installation directory.



Step 3:
          Install IIB-Maven-Plugin:        
Below is the v9 plugin source code:
v9 plugin

Below is v10 plugin source code:

v10 plugin

After you download this plugin, unzip the file in any directory. You can install this plugin in central repository of your enterprise. Here we will install it locally.
Open command prompt and go to the directory where you extracted it. Navigate to the directory where POM file is present and run the command "mvn clean install"
This will install the iib-maven-plugin in your local repository. If installed successfully, you will see 'BUILD SUCCESS' message as below:


Step 4:
    Convert IIB Project to Maven Project: IIB projects are nothing but Eclipse projects. You can convert them to maven project using command line or you can use m2e plugin to use IIB toolkit for project conversion.We will use here m2e plugin. Follow below steps to install m2e plugin on your IIB toolkit:
          -- Go to Help --> Install New Software
          -- If not already there, add the site http://download.eclipse.org/technology/m2e/releases
          -- Make sure you uncheck the check-box 'Show only the latest versions of software available'. Install m2e-Maven Integration for Eclipse 1.4.1 and m2e-slf4j over logback logging v 1.4.1



Complete the installation and restart IIB toolkit.

Now change settings in your toolkit to refer to custom maven installation instead of Embedded installation. Go to Window-->Preferences-->Maven-->Installations. Add the maven installation directory.



Now checkout the IIB project into your IIB toolkit. Right click on the project --> Configure --> Convert to Maven project.

Provide the groupId, artifcatId and Version and select packaging as 'pom'.

Click on Finish.

Now we need to make configurations in POM file. Here I have put central repository info in POM; ideally we should put it in settings.xml. Below is a complete sample POM for the project I created:
Sample POM

Note that I have changed packaging to 'iib-bar'.
<groupId>com.endur.esb.dummy</groupId>
<artifactId>GeniusStatus_Dummy_App</artifactId>
<version>1.0</version>
<packaging>iib-bar</packaging>

You can update the central repository info or remove it. By default it will go to internet.

Now look at the Configuration block.
toolkitInstallDir: Path of the IIB toolkit installation directory
barName: Absolute path for bar file
workspace: Absolute path for workspace
versionString: Will be appended to Application name in bar file
cleanBuild: default value is 'true'
deployAsSource: default value is 'true'
esql21: default value is false. If you are compiling mqsi2.1 esql file then it should be set to true.
applicationName: Name of applications to be included in bar file separated by space
configPropFileDirectory: Absolute path for properties file to override bar file (UDPs and Node properties)
defaultPropertiesFile: Absolute path for properties file where the plugin dumps all the properties for internal use
debugWorkspace: Make this 'true'

Keep other settings same as that of in the sample POM.
Now your IIB Maven project is ready to compile. Make sure that the referenced projects are present in 'workspace'.

Step 5:
    Setup Jenkins:
Now let us setup Jenkins and trigger IIB Build from Jenkins.
You can just download the Jenkins WAR and use it with Tomcat or any other server. Here I will use Windows installer and setup Jenkins as Windows service.
Download the Windows installer from below url:

http://jenkins-ci.org/content/thank-you-downloading-windows-installer

It's installation is straightforward. Once installation is complete, you can access jenkins using below url:
http://localhost:8080
You can do access configuration in Jenkins using LDAP or AD server or local access setup. This part is not in scope of this article. We can continue without doing this access setup.

Go to 'Manage Jenkins' --> Configure System
Set the Maven Configuration.

Give the path to settings.xml

Save it and exit.

Step 6:
   Setup Jenkins job to build and deploy IIB bar:
Click on 'New Item' and give name to item. Select the check-box 'maven-project' and click 'Ok'

Now the Configuration page is open. We need to provide the configuration here. Please note that here I am setting to check-out only main project from TFS assuming that previous jobs will do a 'checkout only' of referenced projects in workspace. Provide the project paths and credential to checkout from TFS:

Select the appropriate Build Trigger.
Provide the absolute path for ROOT POM of the project.
Set the Goals and Options
Set the deployment command or batch file having deployment command.

Save the configuration.
You can do all other additional configurations as per your requirement.
Now you are all set to trigger your build.

I triggered the jenkins job and it built the bar file, overridden a node property using properties file and deployed this new bar file to target integration server. Attached is the sample properties files:
sample properties file

Below is the output of the build:


Getting version 'C89878' to 'C:\Anand\jenkins\workspace\GeniusStatus_Dummy_App'...
Finished getting version 'C89878'.
Parsing POMs
Established TCP socket on 52558
[GeniusStatus_Dummy_App] $ "C:\Program Files\Java\jdk1.7.0_79/bin/java" -Xms1024m -Xmx4096m -XX:PermSize=1024m -cp "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.7.jar;C:\Anand\DevOps\apache-maven-3.3.3\boot\plexus-classworlds-2.5.2.jar;C:\Anand\DevOps\apache-maven-3.3.3/conf/logging" jenkins.maven3.agent.Maven32Main C:\Anand\DevOps\apache-maven-3.3.3 "C:\Program Files (x86)\Jenkins\war\WEB-INF\lib\remoting-2.52.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.7.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.7.jar" 52558
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven:  -B -f C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\pom.xml -s C:\Anand\DevOps\apache-maven-3.3.3\conf\settings.xml -gs C:\Anand\DevOps\apache-maven-3.3.3\conf\settings.xml clean package
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building GeniusStatusDummy 1.0
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ GeniusStatus_Dummy_App ---
[INFO] Deleting C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:prepare-bar-build-workspace (default-prepare-bar-build-workspace) @ GeniusStatus_Dummy_App ---
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:validate-bar-build-workspace (default-validate-bar-build-workspace) @ GeniusStatus_Dummy_App ---
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:create-bar (default-create-bar) @ GeniusStatus_Dummy_App ---
[INFO] Creating bar file: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\GeniusDummy.bar
[INFO] executeMqsiCreateBar command:  "C:\Program Files (x86)\IBM\IntegrationToolkit90\mqsicreatebar" -data C:\Anand\jenkins\workspace -b C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\GeniusDummy.bar -cleanBuild -version 1.0 -a GeniusStatus_Dummy_App -deployAsSource -trace -v C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\createbartrace.txt
[INFO] 
[INFO] C:\Anand\jenkins\workspace>"C:\Program Files (x86)\IBM\IntegrationToolkit90\mqsicreatebar" -data C:\Anand\jenkins\workspace -b C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\GeniusDummy.bar -cleanBuild -version 1.0 -a GeniusStatus_Dummy_App -deployAsSource -trace -v C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\createbartrace.txt 
[INFO] Command log file is set to: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\createbartrace.txt
[INFO] BIP0986I Command completed successfully.
[INFO] 
[INFO] 
[INFO] 
[INFO] 
[INFO] Classloaders are not in use. The following jars will be removed from the bar file: **/javacompute_**.jar,**/jplugin2_**.jar
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:validate-configurable-properties (default-validate-configurable-properties) @ GeniusStatus_Dummy_App ---
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\src\main\resources
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. build is platform dependent!
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\src\test\resources
[INFO] Reading bar file: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\GeniusDummy.bar
[INFO] mqsireadbar complete
[INFO] Writing configurable properties to: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\default.properties
[INFO] Validating properties files
[INFO]   C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.properties
[INFO] Applying properties files as bar file overrides
[INFO]   C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.properties
[INFO] 
[INFO] C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App>"C:\Program Files (x86)\IBM\IntegrationToolkit90\mqsiapplybaroverride" -b C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\GeniusDummy.bar -o C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.bar -p C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.properties -k GeniusStatus_Dummy_App_1.0 -r -v C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\applybaroverridetrace-Genius.txt 
[INFO] BIP1137I: Applying overrides using toolkit mqsiapplybaroverride...
[INFO] BIP1140I: Overriding property GeniusStatus_DummyService_Flow#HTTP Input.URLSpecifier with '/Anand/DataArea/StatusService' in 'GeniusStatus_Dummy_App_1.0.appzip/META-INF/broker.xml' ...
[INFO] BIP1143I: Saving Bar file C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.bar...
[INFO] 
[INFO] BIP8071I: Successful command completion.
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:clean-bar-build-workspace (default-clean-bar-build-workspace) @ GeniusStatus_Dummy_App ---
[INFO] debugWorkspace enabled - workspace will not be cleaned
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:validate-classloader-approach (default-validate-classloader-approach) @ GeniusStatus_Dummy_App ---
[INFO] Reading configurable properties from: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\iib\default.properties
[INFO] 
[INFO] --- iib-maven-plugin:2.1-SNAPSHOT:package-iib-bar (default-package-iib-bar) @ GeniusStatus_Dummy_App ---
[INFO] Building zip: C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\GeniusStatus_Dummy_App-1.0.zip
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:31 min
[INFO] Finished at: 2015-10-08T08:52:11-04:00
[INFO] Final Memory: 25M/982M
[INFO] ------------------------------------------------------------------------
[JENKINS] Archiving C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\pom.xml to com.endur.esb.dummy/GeniusStatus_Dummy_App/1.0/GeniusStatus_Dummy_App-1.0.pom
[JENKINS] Archiving C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\target\GeniusStatus_Dummy_App-1.0.zip to com.endur.esb.dummy/GeniusStatus_Dummy_App/1.0/GeniusStatus_Dummy_App-1.0.zip
channel stopped
[GeniusStatus_Dummy_App] $ cmd /c call C:\WINDOWS\TEMP\hudson9075319975353138395.bat

C:\Anand\jenkins\workspace\GeniusStatus_Dummy_App>C:\"Program Files"\IBM\MQSI\9.0.0.3\bin\mqsiprofile   && mqsideploy -i hostname -p port -q QMHM1DEV3 -e ClaimsServices -a C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.bar -w 180 

MQSI 9.0.0.3
C:\Program Files\IBM\MQSI\9.0.0.3

BIP1044I: Connecting to the queue manager...
BIP1060I: Connecting to the broker...
BIP1115I: Connected to the broker 'IBHM1DEV3'.
BIP1039I: Deploying BAR file 'C:\Anand\SourceCode\EA.Integration\ClaimsFeedService\GeniusStatus_Dummy_App\Genius.bar' to broker 'IBHM1DEV3' (execution group 'ClaimsServices') ...
BIP1092I: The broker successfully processed the deployment request.
Finished: SUCCESS