Re: RPG, Java and Classpath practices

Bradley V. Stone wrote:

So, looking for ideas on handling this. In a nutshell, you have a
standalone app that uses Java inside of RPG and you want to ensure the
classpath is set properly when your application runs, no matter what else
they are running or if the JVM is already running for that job.

Brad:

FWIW, I'm not a big fan of invoking Java directly from RPG. I know it can be done but, for the same reasons you mention, I don't think it's a great idea.

Personally I would suggest you start the java process up in a daemon job and communicate to it with data queues. Simply have the java process monitor a queue for commands and have your RPG send the command requests through the queue.

That way you only have the JVM startup penalty once ... and the job is running in batch. Your RPG program suffers no performance impact because the data queue api is relatively light weight.

Obviously all ther java code would have to be in your daemon job's classpath.

JMO, obviously.... but I've been using this kind of technique for quite a while with great success (using sockets though, not data queues ... given a chance to rework the implementation, I would probably use a data queue).

david