I'm currently working on a WCG proof of concept. I have to say, I'm quite impressed with the "container" side of the product, but the "framework" side is another story. We've had good success proving out Java Batch as a viable go forward approach, but I'm having reservations about the development side of it.
Given that JSR-352 just went to draft (congrats!!), it's probably going to be a year or so before the framework is mature and integrated into the WebSphere and Rational products. I'm looking for recommendations on getting started "the right way" from a development perspective, using currently available tools.
I've built a few jobs using the Rational tooling, and it seems to be a step or two behind the WCG product. Plus I'm concerned about the portability of it, like being able to build/test the code during continuous integration builds.
The "POJO method" is quite appealing, and seems like a very natural development experience, but the batch jars seem to be distributed via forum posts and obscure links. This makes me concerned about version incompatibilities between dev and runtime.
Another question is how to build/test jobs using the PJM. Neither Rational nor the POJO framework jar include things like the "parameterizer".
So... what is the "right way" to start building batch jobs now, without shooting ourselves in the foot with a bunch of rework once JSR-352 matures?
Thanks for any guidance you can provide.
sspavan 060000R0AA60 Posts
Re: Development tooling story2012-05-16T17:04:13ZThis is the accepted answer. This is the accepted answer.Hi,
If you are looking for some sample PJM jobs, I have attached them here. We can use BuiltInParameterizer or have a custom Parameterizer.
We are using WCG for few months and I see testing is a challenging task. Per IBM documentation they had something called BatchSimulator for previous WCG version-6 but not for current version and from forums I understand they are planning on it.
Re: Development tooling story2012-05-16T17:26:36ZThis is the accepted answer. This is the accepted answer.
- sspavan 060000R0AA
sajan 0100003PRR42 Posts
Re: Development tooling story2012-05-16T22:45:58ZThis is the accepted answer. This is the accepted answer.Jon,
You are correct. RAD was a couple of steps behind the full WCG product and they are trying to catch up with the latest fix pack RAD 220.127.116.11. This fix pack should support the development of parallel (PJM) APIs and the xJCL (like the <run> element).
And regarding your concern about incompatibilities between the BDS framework jars in the forum and the product, I would recommend using the framework jar from the WCG v8 product and its service.
And finally, the RecordProcessor model in the BDS framework is very close to the reader-processor-writer pattern in the JSR-352. This would provide the best migration going forward.