Launch ODI scenario from PL/SQL

Question

I want to execute ODI scenario from PL/SQL procedure.
1. I have created the java method using oracle.odi.sdk.invocation.*
// Create the scenario command
OdiCommandScenario cmd = new OdiCommandScenario();
cmd.setScenName(pckName);
cmd.setScenVersion(pckVer);
cmd.setSyncMode(lSyncMode);
cmd.setLogLevel(lLogLevel);
cmd.setContext(lCtx);
cmd.setSessionName(sesName);
// Additional variables
if (parNames != null) {
for (int j=0; j<parNames.length;j++) {
cmd.addVariable(parNames [j], parValues[j]);
// Create the repository connection
OdiRepositoryConnection conn = new OdiRepositoryConnection();
conn.setOdiUser(lOdiUsr);
conn.setOdiPassword(lOdiPwd);
// Launch scenario (use Agent scheduler)
try
invocation = new OdiInvocation(lHostName,lPortNum);
catch (Exception e2) { throw new Exception ("open OdiInvocation="+e2.getMessage());}
OdiInvocationResult result = invocation.invokeCommand(cmd,conn);
if (!result.isOk())
{throw new Exception ("invokeCommand="+result.getErrorMessage());}
else
{sid = result.getSessionNumber();}
invocation.close();
rv = "OK"+sid;
catch (Exception e) { rv = "ERROR: "+e.getMessage(); }
finally
return rv;
// System.exit(0); // !!
2. I have created a PL/SQL wrapper for this java method
It is working satisfactory, an ODI scenario is launched, ID of ODI session is returned, but a java session is not finished, it stay to hang up.
I have got the same result if I try to execute java-method directly from command line - session is hang up.
I found only workaroud to use "System.exit(0)" to terminate session, but it is not a way I can use inside JVM.
(I can to resolve it by deploying java method as web-service and call this webservice from DB - it works OK ... but it seems uselessly complicated ... )
Version ODI: 10.1.3.5.3, JDK 5.0, Windows (but I've got the same result on the Linux)
Any suggestions? Thank you very much.

Answer 1

In your example you invoke ODI scenario using "startscen" command (using java method for launching OS command from PL/SQL).
Yes, I have also tried this workaround - but it is complicated to get back a session ID or ODI error message. In addition to I had a problem with calling ODI scen asynchrounously - but I didn´t investigate this possibility too properly ...
Thanks