Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Mastering Change Data Capture: Read Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Build Job as OSGI Bundle For ESB

Hi,

Im trying to build a .jar file of my job that will be used in a container in our server.
Unfortunately, after placing the .jar file in the container and checking the list of jobs, it shows as "Failure".

Am I missing any setting/s or file/s in my Talend Job export and/or container folders?

EDIT:
My Talend Job uses a .jar library that is called in a tLibraryLoad, as well as routines called in tJavaFlex components.

Best Regards,
0683p000009MGvO.png
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hello

maybe you're missing some dependencies (or TOS doesn't link them automatically). I suggest to deploy the bundle (with the failure result) and see the logs - log:display or content of the tesb.log, where you'll find the core reason

g.

View solution in original post

4 Replies
Anonymous
Not applicable
Author

Hi,

Did your current job work well on studio? Does this issue repro on your specific job or all jobs?

Best regards
Sabrina
Anonymous
Not applicable
Author

Hello,

Yes it works when I run it and use Postman to act as the REST caller.
Here is a sample screenshot of a test scenario running the job in Talend and using Postman (red highlighted sections show working functions):
0683p000009MGoi.png
Anonymous
Not applicable
Author

UPDATE:


I have tried deactivating some components 1 at a time and deploying the modified job to the container. I have found out that it fails when I activate back the tJavaFlex that calls the routine code. How can I place the routine code in the container?


Best Regards
Anonymous
Not applicable
Author

Hello

maybe you're missing some dependencies (or TOS doesn't link them automatically). I suggest to deploy the bundle (with the failure result) and see the logs - log:display or content of the tesb.log, where you'll find the core reason

g.