doctorbatch.io is an API for developing batch applications in the Java programming language targetted for deployment to IBM’s WebSphere Batch or WebSphere Liberty Profile’s Java EE Batch runtime environments. The doctorbatch.io provides portability between the two runtimes by abstracting application development away from the runtime-specific API, and providing adapters for deployment.
Interested in getting started with Doctor Batch? Checkout the development lab that was hosted at IBM Interconnect 2016.
To get started with this lab, you must:
Clone the DoctorBatch.io GitHub repository
Import the following projects into an Eclipse workspace: bigbluebank-core, bigbluebank-jbatch, and bigbluebank-jbatch-war
Setup a local WebSphere Liberty Profile development server, and enable the “batchManagement-1.0” feature
To use doctorbatch.io, you’ll need to import several dependencies from IBM products into your local Maven repository. The dependencies are as follows:
The MVS components require IBM Java for z/OS Toolkitfrom your JDK 1.6 or later installation on z/OS, and marshall.jar from your WebSphere Application Server installation (on any platform).
The ODM components require the JRules RES Execution library from your Operational Decision Manager installation on any platform
The WebSphere components require the Batch Runtime library from your WebSphere Application Server installation on any platform
Note that doctorbatch.io-core and doctorbatch.io-javabatch may be built and used without and IBM dependencies.
Once you have imported the necessary prerequisuites, you are ready to use doctorbatch.io. doctorbatch.io is avaialble in Maven Central at the following coordinates:
The core library provides the API for the implementation of a doctorbatch.io application.
Batch Runtime Components
The batch runtime components provide bridges so that doctorbatch.io applications can be
executed in a provided batch runtime environment. At present, doctorbatch.io supports
JSR-352 compatible “Java Batch” containers, such as IBM WebSphere Liberty Profile, and
IBM WebSphere Application Server’s Batch Runtime (aka “Compute Grid”).
The MVS components provide drop-in support for reading and writing from z/OS DataSets using
the IBM JZOS library.
Operational Decision Manager Component
The Operational Decision Manager component provides drop-in capability to consume
business rules applications as the processing logic of your batch application.
Building doctorbatch.io From Source
Alternatively, you can build doctorbatch-io from source. Please note, by default, the
parent POM includes all submodules. If you do not have certain prerequisites available to
you, then you will need to comment out the affected modules.
Configuring WebSphere Liberty Profile
Below is a sample server configuration that will get you started quickly with JSR-352
and the Batch Management capabilities available in WebSphere Liberty Profile.