One Star

Problem exporting SDI jobs. Please I need some help urgently.

I have recently started to use SDI plugin (4.1.0 installed in TOS 4.1.1) and SDI components in my jobs. Everything was fine running them in Talend but the big problem came when exporting them as Autonomous jobs.
These exported scripts seem to lack of ANY of the libraries needed by the SDI components, so they won't run (neither on Windows or Linux).
I don't know if its normal, a bug, or some configuration I missed or a bad installation of the SDI plugin.
I have looked in all the forum and bug tracker but nothing came up. It has to be only me who has this strange problem.
Some of the components I use are:
s2DPointReplacer
sProj
sShapeFileOutput
And some of the SDI libraries that should have been exported with the jobs and are not, so the jobs are throwing classNotFound are:
geoapi-2.2-M1.jar
gt-metadata-2.5-M3.jar
hsqldb-1.8.0.7.jar
jai_core-1.1.3.jar
gt-referencing-2.5-M3.jar
jscience.jar
gt-epsg-hsql-2.5-M3.jar
Some of them I had to download from internet because in the plugin libraries have another name and I don't know them.
Do I need to know which libraries are used and do a tLibraryLoad for all?
I need to export the jobs and give them so they can be launched as is, and I can't do that without doing lot of classpath and library searching.
Please, anyone can help me?

9 REPLIES
One Star Fxp
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Hi alex,
I can't reproduce the issue with tRowGenerator > s2DPointReplacer > sShapefileOutput.
After export all required lib are in the lib folder.
Could you check that in the modules tab, you have the jar file loaded (at least for sShapefileOutput and sGeoOutput).
Cheers.
Francois
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Hi alex,
I can't reproduce the issue with tRowGenerator > s2DPointReplacer > sShapefileOutput.
After export all required lib are in the lib folder.
Could you check that in the modules tab, you have the jar file loaded (at least for sShapefileOutput and sGeoOutput).
Cheers.
Francois

Can you post the list of libs after export?
The job launched as autonomous job fine then?
Trying to find out now which is the "modules tab" and which jar do you mean...
One Star Fxp
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Hi, the list of libs is based on the IMPORTS section of the component's configuration (see sGeoInput_java.xml for example).
For the module tab, menu Window>Show View>Other, search the module one.
HTH.
Francois
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Found the modules tab. Lot of jars loaded for the SDI components. But almost none of them are exported with the job.
Image of modules tab:



Lib folder of my exported job:
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

It's strange. In a job which only has s2DPointReplacer and sProj, all libs that shows in Modules tab are really exported. But the job fails to launch, with this:
java.lang.NoClassDefFoundError: org/opengis/referencing/FactoryException
It's the job that I showed the lib folder in the previous post.
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Now I exported a job with sProj and sShapeFileOutput and exported all libs and worked FINE.
So the problem are with jobs with s2DPointReplace and sProj only...
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

I'm starting to think that the bug is only with s2DPointReplacer and/or sProj. That uses jar that are not exported. If used with sShapeFileOutput they get the jars they need to work.
A job with only s2DPointReplacer and sProj will not export right to work as autonomous
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

Almost confirmed my point. After adding a sShapeFileOutput (that does nothing) to a job that only used sProj and wasnt working, so the libs of sShapeFileOutput are exported, and the job started working ok as autonomous.
The problem/bug/whatever has to be in the list of jars that sProj (or/and s2DReplacer) claim to need, that is not enough.
One Star

Re: Problem exporting SDI jobs. Please I need some help urgently.

So, if someone wants to try it:
THIS DOESN'T WORK WHEN EXPORTED:


THIS WORKS WHEN EXPORTED (but has 14MB more of libraries weight...):