Issue with System Command in External Task(IPL)

Hi,
We are invoking a IPL file from Workflow as external Task.
In the IPL file we are invoking a Standalone "Java" program to perform certain task. The java command is not working, its not invoking the Java program.

But when we invoke the IPL file as standalone, Java program is invoked via SYSTEM command perfectly. Other commands like 'iwodcmd -h' are getting executed fine. Even when we try to PIPE the output of "java" command to text file, its not working. The text file is blank.

The functionality is working fine in our development environment but failing in Stage environment.

I would like to know is there any setting in Teamsite Server/Perl/System Environment, which prevents Invoking other programs like Java?

Sample Code in the IPL file:
--------------------------
$cmd = qq(java.exe -Xms128m -Xmx512m InsightsIndexer -d $env -h

\\Interwoven\\TeamSite\\local\\bin\\USRetail\\insights -a INSERT -f "$f_upd" -w $jobId -t $taskId -p "$area");

$failure_result = system($cmd);

Regards,
Reghu.

Find more posts tagged with

Comments

ISCBorisB

Hi,
We are invoking a IPL file from Workflow as external Task.
In the IPL file we are invoking a Standalone "Java" program to perform certain task. The java command is not working, its not invoking the Java program.

But when we invoke the IPL file as standalone, Java program is invoked via SYSTEM command perfectly. Other commands like 'iwodcmd -h' are getting executed fine. Even when we try to PIPE the output of "java" command to text file, its not working. The text file is blank.

The functionality is working fine in our development environment but failing in Stage environment.

I would like to know is there any setting in Teamsite Server/Perl/System Environment, which prevents Invoking other programs like Java?

Sample Code in the IPL file:
--------------------------
$cmd = qq(java.exe -Xms128m -Xmx512m InsightsIndexer -d $env -h \\Interwoven\\TeamSite\\local\\bin\\USRetail\\insights -a INSERT -f "$f_upd" -w $jobId -t $taskId -p "$area");

$failure_result = system($cmd);

Regards,
Reghu.

Chances are, your problem is that some Environment variables (JAVA_HOME? CLASSPATH?) were reset by Teamsite WF Engine.
If that's the case you would have to set them yourself within external task script. For starter, try to redirect STDERR to see what your issue is. Like that:

$failure_result = qx($cmd 2>&1);

Adam Stoller

Hi,
We are invoking a IPL file from Workflow as external Task.
In the IPL file we are invoking a Standalone "Java" program to perform certain task. The java command is not working, its not invoking the Java program.

But when we invoke the IPL file as standalone, Java program is invoked via SYSTEM command perfectly. Other commands like 'iwodcmd -h' are getting executed fine. Even when we try to PIPE the output of "java" command to text file, its not working. The text file is blank.

The functionality is working fine in our development environment but failing in Stage environment.

I would like to know is there any setting in Teamsite Server/Perl/System Environment, which prevents Invoking other programs like Java?

Sample Code in the IPL file:
--------------------------
$cmd = qq(java.exe -Xms128m -Xmx512m InsightsIndexer -d $env -h \\Interwoven\\TeamSite\\local\\bin\\USRetail\\insights -a INSERT -f "$f_upd" -w $jobId -t $taskId -p "$area");

$failure_result = system($cmd);

Regards,
Reghu.

Standard answer for questions that say: "it works when run from the command line but doesn't work from within TS"

In your case - I'm guessing things like CLASSPATH, LIBPATH, etc.

Reghunath

Thanks a lot for your suggestions.

We found that some JAVA process(java.exe) was hanging in the backend(donno which application). We killed the process manually and restarted teamsite. Now we are able to call the Java process.

Thanks for your time...

Cheers!
Reghu.

Reghunath

Yesterday we tried the same as mentioned below to PIPE the output.
$failure_result = qx($cmd 2>&1);

But the output was BLANK(nothing turned out)...
If the classpath/some environment is getting overwritten then the application will throw some error which can be caught in the output PIPE.

But here the situation was weird...Hence we checked any process that is hanging in the background and found one and killing the same resolved.

Cheers!
Reghu.