project defined Stats&Log to AS400 DB won't work

[bschwarz]

Hi,

Transitioning from a TOS7 to a Talend V8, I happen to experience troubles with the logging configuration.
We were used to logging into an AS400 DB, with a stats&log configuration defined at the project level.
When trying to apply the same scheme in the newly created V8 project I experience oddities for which I would need some help.

The project properties were copied from the working V7 project. As you can see in the first picture, we rely on a JDBC driver with a definition of the AS400JDBCDriver Class for accessing DB.

When running a simple job though, the application will express the impossibility to find that driver (see picture 2). Every attempt to log will then indeed fail. I later realized that adding a tAS400 component or a tRunJob on a subjob that opens an AS400 connection will allow the application to run smoothly. I guess adding a tLoadLibrary might have the same effect.

My guess is that adding "com.ibm.as400.access.AS400JDBCDriver" as a class name in the project properties isn't enough (anymore ?) to get the class imported. Is there a way to force project imports ?

Any help or insights are welcome.

--Ben

( Version: 8 Build id: 20260102_0846-patch on windows)

project defined stats and logs propertiesA simple toy job

[Greg_Taffer]

Adding com.ibm.as400.access.AS400JDBCDriver to project properties is often insufficient; you must manually import the jt400.jar into Talend’s modules view or ensure it is referenced in a configured JDBC driver connection to force the class loading. 

How to Force Driver Import in Talend:
 

• Modules View (Preferred): Open the Modules view, click the Import button, and manually import the jt400.jar file.
• JDBC Metadata: Create a new Metadata -> Db Connections -> JDBC entry. In the driver jar selection, import the jt400.jar and set the class to com.ibm.as400.access.AS400JDBCDriver.
• Restart Studio: After adding the JAR, restart Talend Studio to ensure the library is loaded into the classpath.
• Force Update: Go to the project settings, make a small dummy change to trigger a rebuild, or use the "Refresh" button in the Modules view. 

Ensure the jt400.jar itself is not corrupt, as this often causes silent failures.

[bschwarz]

Hi Greg, and thanks a lot for your answer.

Unfortunately, it didn't help me yet to solve my problems.

Module view : if I understand you well, you advise to manually fetch the jt400.jar file somewhere on the net, and then to import it through button (1) in the module view (see first picture).

I didn't do that yet though, because :

1. I wasn't sure this was what you meant. Manual fetching of libs doesn't seem "clean".
2. I am not sure such a manual install would be automatically transferred to the TMC or to my friends studio.
3. Provided that some tAS400 components are already installed in my studio, it seams I already have access to an implementation of the com.ibm.as400.access.AS400JDBCDriver class

JDBC Metadata : Never did that, and didn't really understand why I would need it here. I nonetheless complied, and created a JDBC DB connection as a metadata, using the jt400 jar shipped with the aforementioned tAS400 components. Everything seemed to work fine (class automatically detected), except that probing the connection failed (see second picture).

I still followed the remaining steps of your procedure, but the final result is unchanged :

• Running a simple job consisting in an empty tJava component, there will be warning messages
  java.lang.ClassNotFoundException: com.ibm.as400.access.AS400JDBCDriver
• adding a tWarn, the job doesn't crash, but obviously nothing is output to the DB and I have more warning messages at each attempt to write in the DB
• Adding a tAS400Connection, even at the end of the job, solves the problem.

 

 

[Greg_Taffer]

No problem. At this point, I would recommend opening a Support Case with our Support Team.