WMB Continuous Integration

13 min readOct 2, 2020

Install Apache Tomcat

Download the installable for Apache Tomcat from the following location — http://tomcat.apache.org/download-70.cgi .

We are using the 7.0.42 version for this and it can be downloaded from — http://mirror.cc.columbia.edu/pub/software/apache/tomcat/tomcat-7/v7.0.42/bin/apache-tomcat-7.0.42-windows-x64.zip

Extract the archive file and place it in local directory. In our case we have it in the ‘c:\IBM\’ directory.

To start apache tomcat java is needed. If java is not installed on the machine and you try to run ‘startup.bat’ from the bin directory it would give the following error.

Directory Structure

JAVA_HOME is not set up

Download and install java from the location — http://www.oracle.com/technetwork/java/javase/downloads/index.html . We have the JDK and JRE installed in ‘c:\java’ directory.

After java is installed create the JAVA_HOME variable pointing to c:\java\jdk directory as follows -

Set up the JAVA_HOME environment

Save it and now if you start apache tomcat it will work as follows.

Apache Tomcat started

Install Apache Ant

The next step would be to install Apache Ant that allows us to script creation and deployment of bar files. Download the installable for Apache Ant from the following location — http://ant.apache.org/ .

We are using the 1.9.2 version for this and it can be downloaded from — http://apache.mirrors.tds.net//ant/binaries/apache-ant-1.9.2-bin.zip

Extract the archive file and place it in local directory. In our case we have it in the ‘c:\IBM’ directory as shown in Fig.1

Create Ant Build File to create BAR file

Under the assumption that we have a WMB application project ‘MFA_TestAppln’ in the ‘c:\IBM\workspaces\IIB9’ workspace, create the XML file that would be the input to the ant executable for creation of the bar file. The XML describes below how to create and deploy a bar file for ‘MFA_TestAppln’.

<?xml version="1.0"?>
<project name="project" default="run">
<target name="run" description="">
<property name="toolkit.home" value="C:\IBM\IntegrationToolkit90" />
<property name="workspaces.dir" value="C:\IBM\workspaces\IIB9" />
<property name="runtime.dir" value="C:\IBM\MQSI\9.0.0.0\bin" />
<property name="appln.name" value="MFA_TestAppln" />
<property name="bar.name" value="${workspaces.dir}\${appln.name}\${appln.name}.bar" />
<antcall target="mqsideploybar" />
</target>
<! -- Target to build the broker archive using mqsicreatebar -->
<target name="mqsicreatebar.buildbar">
<echo message="Building Broker Archive file: ${bar.name} " />
<exec executable="${toolkit.home}\mqsicreatebar.exe" spawn="false">
<arg value="-data" />
<arg value="${workspaces.dir}" />
<arg value="-b" />
<arg value="${bar.name}" />
<arg value="-a" />
<arg value="MFA_TestAppln" />
</exec>
<echo message="Completed building Broker Archive file - ${bar.name} " />
</target>
<! - -Target to deploy the broker archive using mqsideploybar-->
<target name="mqsideploybar" depends="mqsicreatebar.buildbar">
<echo message="Deploying Broker Archive file: ${bar.name} " />
<exec executable="${runtime.dir}\mqsideployscript.bat" spawn="false">
<arg value="${Brokername}" />
<arg value="-e" />
<arg value="${execution.group}" />
<arg value="-a" />
<arg value="${workspaces.dir}\${appln.name}\${appln.name}.bar" />
</exec>
<echo message="Completed building Broker Archive file - ${bar.name} " />
</target>
</project>

We have the above script saved in following location — ‘C:\IBM\workspaces\IIB9\MFA_TestAppln\build.xml’ . Before we run this ant script we need to make a small change to ‘C:\IBM\MQSI\9.0.0.0\bin\mqsideployscript.bat’. Change the ‘call’ to ‘echo’ and add the second line and save the file.

– — — — — — — — -@echo mqsisetmqenv@call “C:\IBM\MQSI\9.0.0.0\bin\mqsiprofile.cmd”– — — — — — — — -

Run the above saved build.xml file by passing it to ant and passing the arguments as follows -

C:\IBM\apache-ant-1.9.2\bin>ant -buildfile C:\IBM\workspaces\IIB9\MFA_TestAppln\build.xml -DBrokername=WBRK9 -Dexecution.group=default -v

Where Brokername is the local broker on the machine and execution.group is the EG on the broker WBRK9. It would create a bar file ‘C:\IBM\workspaces\IIB9\MFA_TestAppln\MFA_TestAppln.bar’ and deploy to WBRK9 broker’s EG default.

Bar File deployed to Broker

Install Jenkins

Now that we have the Ant script ready the next step would be to run in using a web interface that allows automated deployment with just a click of a button without installing it locally. To do this we use Jenkins. Download the WAR file to run Jenkins from Apache Tomcat from the following location — http://mirrors.jenkins-ci.org/war/latest/jenkins.war

Copy the downloaded war file and place it in the webapps directory and re-start apache tomcat. This will load the jenkins in the servlet container. The command window will display the info when Jenkins is loaded -

Jenkins up and running

In the browser enter the URL -http://localhost:8080/jenkins/ — and you should be able to see the following screen -

Jenkins web interface

Click ‘Manage Jenkins’ on left hand top corner to configure Jenkins to use Ant and also Java. Next click the first option ‘Configure System’. Enter the details as shown below and save it.

Configure Jenkins with Ant and Java

Next click the ‘New Job’ link on the right hand top corner to open the interface to create a job to run the Ant Script. Give the job a name-in this scenario MFA_Test- and select the first option ‘Build a free-style software project ‘ and save.

In the build section, click on ‘Add build step’ and select ‘Invoke Ant’.

Specify the build step

Enter the details of the job for Build File and Properties. The build file is the same what we have used from the preceeding i.e. C:\IBM\workspaces\IIB9\MFA_TestAppln\build.xml and the properties are the values we supply to the build file.

Brokername=WBRK9

execution.group=default

Click to save the job.

Ant job properties

The interface would look like this -

Ant job overview

Click on ‘Build Now’ to initiate the building of bar file and deployment to the broker.

Ant job running

If the job runs successfully it will show a blue color beside the job run as well as the time at which it was run. Clicking it on the time will show the verbose details.

Console output indicating the job ran successfully

Securing Jenkins

It is imperative that Jenkins will be used by the developers to run tasks. To control the access setup security access by ‘Manage Jenkins’ and ‘Configure Global Security’. Select ‘Enable Security’ to show the options. In ‘Security Realm’ select ‘Jenkin’s own user database’ with the ‘Allow users to sign up’ checkbox selected. In ‘Authorization’ select ‘Matrix-based security’. Add a user with user id and give him the requisite permission and click ‘Save’.

Configure Global Security

As soon as you save it will bring you to login screen. Select the ‘Create an account’ and enter the details and click on ‘Sign up’. This will create the user and give him the permissions. Please be aware that once you click on save you will be thrown back to login and cant access. The only way out is reconfigure.

User sign up

Working with SVN as source repository

Before we start working with SVN we need to integrate our toolkit with a SVN Server using an Eclipse SVN plugin. To do so download the plugin for Eclipse by selecting ‘Help’, ‘Install New Software’. Click ‘Add’, give the location a name -in our case ‘SvnEclipse’- and point to the Location ‘http://subclipse.tigris.org/update_1.10.x ‘ and click ‘OK’.

Add the SubEclipse site

This will list the site to download the plugins. Select both the options and click ‘Next’. The download will begin.

Add the SubEclipse site

A confirmation of what we are downloading.

SubEclipse Install Details

Accept the license.

Download begins.

Software begins installation

Accept the warning for unsigned content download.

Accept security warning

Restart the toolkit.

After the restart of the toolkit you will see the following addition in your perspective list

SVN Repository Exploring Added to Perspective

Open the ‘SVN Repository Exploring’ perspective. Right click on white canvas and select ‘New’ and ‘Repository Location’ to add the repository location for the SVN Server versioning location.

Add the SubEclipse site

Enter the URL of the SVN repository and select finish.

Add the SVN Repository site

It will list the repository and the artifacts in the repository.

SVN repository listed

To share the project in SVN repository right click the project and then select ‘Team’ and then ‘Share Application’.

Share the project in SVN

It will pop up for the application to be shared in SVN. Select the Project/Application, ‘Team’ and ‘Share Project’

Share the project

Select ‘SVN’ and click ‘Next’.

SVN Repository

Select the existing repository and click ‘Next’.

Select SVN Repository

Select the existing repository and click ‘Next’.

Share Project with Project Name