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

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
timschotz
Contributor II
Contributor II

[resolved] Error on Runnable Process (Entity Action)

MDM 6.1.1
When defining an entity action process that calls a job, I am receiving the following error when executing from the MDM Web UI; 
ERROR Could not execute the tisCall transformer plugin for job
Steps to reproduce:

Create a new DI job using tMDMReceive component and context variable for the XML Record field. 
Deploy job on MDM server. Test execution of job from Studio works as expected.
Create a new Entity Action Process from the MDM perspective in Studio that uses the callJob plugin. Deploy this to the MDM Server.
Screen shots of job and all process step definitions are attached.

Full MDM Log Error:
2016-03-18 11:23:30,736 INFO Invoking job 'Runnable_MotorSystem_Main_0.1' 2016-03-18 11:23:30,736 ERROR Could not execute the tisCall transformer plugin for job Runnable_MotorSystem_Main in version 0.1com.amalto.core.jobox.util.JoboxException: java.lang.reflect.InvocationTa

To see the whole post, download it here
Labels (2)
1 Solution

Accepted Solutions
timschotz
Contributor II
Contributor II
Author

OK. Where can I find the job export (deployed on MDM)? 
I currently just right-click -> Deploy to MDM from the Studio. The dialog does not return any dependencies. What would I do differently to make sure the library is included when I export?
Thanks

View solution in original post

6 Replies
Anonymous
Not applicable

It seems you're depending onto a SAP library which is missing from the job execution:
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sap.conn.jco.JCo
at com.sap.conn.jco.JCoContext.end(JCoContext.java:89)
at local_project.runnable_motorsystem_main_0_1.Runnable_MotorSystem_Main.tSAPInput_1Process(Runnable_MotorSystem_Main.java:3244)
at local_project.runnable_motorsystem_main_0_1.Runnable_MotorSystem_Main.tMDMReceive_1_InProcess(Runnable_MotorSystem_Main.java:10875)
at local_project.runnable_motorsystem_main_0_1.Runnable_MotorSystem_Main.runJobInTOS(Runnable_MotorSystem_Main.java:28180)
at local_project.runnable_motorsystem_main_0_1.Runnable_MotorSystem_Main.runJob(Runnable_MotorSystem_Main.java:27956)
timschotz
Contributor II
Contributor II
Author

The SAP Jco modules are installed (from Studio) and the job executes without error. What else am I missing?
0683p000009MDdg.png
Anonymous
Not applicable

Is the library in the job export? It successfully executes within the studio but exported job might be missing that dependency.
timschotz
Contributor II
Contributor II
Author

OK. Where can I find the job export (deployed on MDM)? 
I currently just right-click -> Deploy to MDM from the Studio. The dialog does not return any dependencies. What would I do differently to make sure the library is included when I export?
Thanks
Anonymous
Not applicable

You can find the zip export into <MDM_SERVER_HOME>/jobox/deploy. The exploded version is in <MDM_SERVER_HOME>/jobox/work
timschotz
Contributor II
Contributor II
Author

Got it. I was able to verify that the jars were deployed with the job on the MDM server, but the issue was still present.
In researching the java.lang.NoClassDefFoundError error, I found that it was commonly caused by the ClassLoader. So, I restarted the MDM service and this fixed the issue from the web UI.
Thanks for your help.