go to post Andrew Langley · Jan 18, 2024 Thanks - if I put the classpath into the Gateway definition, it fails; however, the code that is making the connection and trying to access those jar files belongs to a vendor and it's compiled. I'll feed this back to them but thanks for taking a look.
go to post Andrew Langley · Jan 18, 2024 Bearing in mind this is on a hp-ux system : That's how it set up in our UAT environment except UAT doesn't have an issue, it's only Live.
go to post Andrew Langley · Jan 18, 2024 Yes, all the files exist in the sub-directories in the wizard : Along with the other two files in the additional classpath section. The Java Gateway had been started before this, and the first time round it compiled over 100 classes. If I do this again, it says that nothing has changed, but the Java Gateway now works. Make sense ?
