Re:CLASSPATH of batch job on sysetem i

Dieter wrote:

Hi Gary,
there is a difference between using JNI call support of the RPG compiler

and a java application. A true Java application doesn't slip > into an
already running JVM, which could have been started with the wrong
environment. For ArdGate I recommend 3 alternatives:

- using the Tomcat Version: just copy the war file to the Install

directory and your additional driver jar files in the extension

directory of the newly created application and all is done
- if you only need connects to mysql, oracle and ms sql server (using

the jtds driver) the drivers are prepackaged with ArdGate and

you would only start the runnable jar (java -jar

myPath/AppServer4RPG.jar ) as described in the install instruction.

- for a customized version, I recommend setting the classpath with

calling the java Runtime, as I've described earlier in a posting

to your private mail

sbmjob JVAGATE cmd(qsh cmd('java -cp

.:AppServer4RPG.jar:commons-logging-1.1.1.jar:jt400Small.jar:jtds-1.2.5.jar:log4j-1.2.16.jar:sqljdbc.jar

de.bender_dv.jvagate.communication.Receiver'))

Thank you Dieter:

After installing ArdGate on our test partition and successfully running
queries
against Microsoft Sql Server using STRSQL, I am installing ArdGate
to our production partition.

Our network team has stated they do not want to support a Tomcat server,
so
I will work with the 2nd and 3rd options you describe.

I will also follow your suggestion and create a system i user profile with
home
directory set to JVAGATE (the ArdGate install directory) and use this
profile
to submit of the SQLGATE job.

Note: in the -cp of the sbmjob example above: if the Microsoft JDBC driver
is to be used, my testing shows the driver file must be: sqljdbc4.jar

Early ArdGate testing shows very good response time with the Microsoft
JDBC driver, but I will extend testing to include the jtds driver as I
have
received e-mail recommending the jtds driver for its speed.