[resolved] After export: ClassNotFoundException com.ibm.db2.jcc.DB2Driver

[Anonymous]

Hi,
my Talend jobs are structured as follows:
-job "RUN_ALL"
-job "RUN_SUBPROJECT1"
-job "RUN_SUBPROJECT2"
--sub project 1
---job x
---job y
--sub project 2
---job a
---job b
So, basically I have folders for several projects that contain several jobs. Furthermore, I have jobs that execute all jobs of a project, and on top of that a job that runs all jobs. That "RUN_ALL" job calls each "RUN_SUBPROJECTx" job.
Now I wanted to export RUN_ALL - so I can execute all jobs by executing one .bat. I checked everything in the export wizard and also included every file (in the file selection window on the left side). However, once I start the RUN_ALL.bat, it fails saying " ClassNotFoundException com.ibm.db2.jcc.DB2Driver".
When I export just the particular job at which the error occurs it runs fine. I also compared the export of the single job with the export of all jobs: It seems that there are some files missing in the "lib" folder in the export of all jobs. The export of the single job contains files like "db2.jcc.jar" and so on, which are missing in the "lib" folder of the export of all jobs.
I dont know....is it a problem that I nest the actual jobs? Because basically I call ALL_RUN which calls RUN_SUBPROJECTx which calls JOBx. So maybe when I export ALL_RUN it doesnt recognize the dependencies of the actual job files?
How can I solve the problem?
Best regards

[Anonymous]

Oh, just FYI: If I export RUN_SUBPROJECTx it works as well.
So basically the problem seems to be only in case of a "2nd-degree-dependency" (meaning "RUN_ALL" > "RUN_SUBPROJECTx" > "job x")

[Anonymous]

Hi
Which version of TOS are you using? Have you checked the box 'export dependencies' when export the job script?
Best regards
Shong

[Anonymous]

I'm running the latest version, as far as I know. v4.1.2.r53616 on "Windows XP Professional Version 2002 SP3".
Here's what I did:
1. Rightclick on the RUN_ALL job in the repository -> Export Job
2. Archive file location: Desktop; Job version "0.1" (the only available); Export type "autonomous job", checkbox "extract the zip file" NOT checked; Options: checked everything except "source files". Shell launcher is "all" and context scripts is "default"
3. Then I expanded the "items to export" frame on the left side and clicked "select all"
And then I hit "finish"

[Anonymous]

Wait.....now that you mention it....there is no checkbox "export dependencies" in that wizard. Am I using the right one?
I found "export dependencies" in that other export wizard ("export items") - but this wizard doesnt create executable .bat files, does it?

[Anonymous]

Hi
I don't understand why you do the step 3? All the dependency jobs will be included once the 'export dependencies' option is checked.
Best regards
Shong

[Anonymous]

Wait.....now that you mention it....there is no checkbox "export dependencies" in that wizard. Am I using the right one?
I found "export dependencies" in that other export wizard ("export items") - but this wizard doesnt create executable .bat files, does it?

Yes? You don't see the 'export dependencies' option?
Best regards
Shong

[Anonymous]

Ohhh wait. Now I'm confused. You're right, there is that box, but it's grey. Thats why I oversaw it.
The steps I described in my last posting were those I performed last time (after experimenting with several settings). I figured that I dont need the source files, so I unticked the checkbox.
Just to get everything straight, I just performed another export - and this time I checked every checkbox available. So, I also checked "export dependencies" and "source files".
Still, the required .jar doesnt appear in the export 😕

[Anonymous]

So, is it a bug or am I doing sth wrong?

[Anonymous]

Hi
If it is the case, it should be a bug, but I can't reproduce it. Please to do:
1. Simplify your jobs and export the job items.
2. Create a bug on our bugtracker and upload the job item.
And then, we will try to reproduce the problem with your job.
Best regards
Shong