The JBatch Example in my last post was ok for a prototype but when you have to write many batch jobs we would rather want to have to code less and have more ready-to-use components. This can be done very easily in only a few steps by putting these reusable components into a `batch.core` project which we can later declare as a depencency in your batch projects.
My last blog post was about batch processing on IBM i with Jakarta EE Batch implementation JBatch from IBM. I didn't get into too much detail in that post as it was only to provide a brief overview of Jakarta EE Batch. In this blog post I want to present and explain one of my JBatch example applications available on Bitbucket.
This whole blog has been very RPG centric so far. But some of you also know that I also do some Java programming (and also some Node.js+TypeScript from time to time). Lately I got involved into some Java projects which also include IBM i as a potential target platform.
In most IBM i shops SQL is the primary way of accessing data or is at least on its way to be it. And this is a good thing. But as ILEastic is a multi threaded framework we need to be aware of the fact that multiple threads may be using SQL transactions simultaneously.
Most people have probably assumed that the next blog post will again be about "ILEastic Tutorial : Tour of Champions". I will definitely continue this series but I had some time to work on the STOMP client again. And this time I have working STOMP service program which implements the STOMP specification 1.2.
This is a little update on the mini series "ILEastic Tutorial : Tour of Champions". Last time I covered plugins, those "special" procedures which are executed on the exit points of the ILEastic request handling workflow.