Java is well-served in its two most popular build systems, Gradle and Maven. Their power and ubiquity mean that most Java applications get built by either one or the other of them, and that can include Java applications that are intended to be installed into IBM CICS Transaction Server.
Deploying Java applications to CICS can be achieved in a number of ways, but using CICS bundles to package those applications gives the advantage of being able to control that application in standard CICS ways.
You can easily extend an existing Gradle or Maven build of a Java application to also build a CICS bundle. Let’s take a look at how to do that.
Let’s assume you already have a Java application that has been built using Gradle or Maven. I’m going to start from the sample getting started application supplied by the Open Liberty team and extend that, as it’s already set up with a build for both Gradle and Maven.
There’s a branch in my fork of the sample for each of the build systems — Maven and Gradle — showing how I changed the project compared to the original. Each step is a commit, so you can follow along with the workflow. As I go through each step, I’ll link to a comparison between each commit and its prior state.
It should take you about 20 minutes to complete this tutorial.
Ready to get started? Check out the README file in this repo for detailed instructions on how to:
- Take a sample application, or your own.
- Modify the build to create a CICS bundle, wrapping up the application. The README shows you how to do this with either Maven or Gradle.
- Find out how to easily deploy the CICS bundle to CICS Transaction Server.
That’s it! Converting an existing Java application’s build to generate a CICS bundle is very easy and only takes a couple of steps, whether you use Maven or Gradle.