nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

'iwodstart' in External Task

wild123

Hi

I want to run this command(CLT) in my WFM's external task ::

\Interwoven\OpenDeployNG\bin\iwodstart test.xml

It works fine when run from command prompt.But not through external task's command window.

I want to know how I can use JAVA for this external task for coding purpose. How can I give a CallBack? How can I directly use the clt above with iwcallback in the external task's command window?

Please provide any sample code available. I have attached the ipm . TestDeploy task is what I am having problem configuring.

Thanks in advance

Find more posts tagged with

Comments

Adam Stoller

Hi

I want to run this command(CLT) in my WFM's external task ::

\Interwoven\OpenDeployNG\bin\iwodstart test.xml

It works fine when run from command prompt.But not through external task's command window.

I want to know how I can use JAVA for this external task for coding purpose. How can I give a CallBack? How can I directly use the clt above with iwcallback in the external task's command window?

Please provide any sample code available. I have attached the ipm . TestDeploy task is what I am having problem configuring.

Thanks in advance

Unless you're using a very very old version of OD - you should use the CLT command

iwodcmd start test

- however, in either case - you need to capture the results of the command and then determine the proper callback to use.
The process of capturing the results is, in a nutshell:

my $command = qq(....);
my $results = qx($command 2>&1);
if ($?) {
    # a non-zero exit status - generally indicative of an error
    # handle the error and exit the program
    # $results will contain the text that normally appears in the shell
}
# Assuming you exited on error - this part of the code handles success

As for using Java - I believe you need to code for a web service using the Content Services for OpenDeploy (as documented in the OpenDeploy Developer's Guide) which uses SOAP. I've never had a need to do this, so I cannot offer any guidance beyond suggesting you read the manual and play with it.

wild123

Hi

I want to run this command(CLT) in my WFM's external task ::

\Interwoven\OpenDeployNG\bin\iwodstart test.xml

It works fine when run from command prompt.But not through external task's command window.

I want to know how I can use JAVA for this external task for coding purpose. How can I give a CallBack? How can I directly use the clt above with iwcallback in the external task's command window?

Please provide any sample code available. I have attached the ipm . TestDeploy task is what I am having problem configuring.

Thanks in advance

Hi

Any suggestions on how I can use java in my Script window of the external task and make a Callback to the workflow from the same JAVA code?

Please provide sample code and Scripts for this external task.

Ghoti, thanks for the help!

Adam Stoller

Hi

Any suggestions on how I can use java in my Script window of the external task and make a Callback to the workflow from the same JAVA code?

Please provide sample code and Scripts for this external task.

Ghoti, thanks for the help!

I'm not sure what you're asking - an externaltask runs a command; a command is generally a script or program; if you can figure out how to write the entire thing in Java - fine, if not, you can write most of it in Java and call the CLT from there, if not, you can write the script in Perl and call the CLT from there. Your script or program needs to perform the deployment, check the return status and perform the appropriate callback to your workflow.

If you're expecting someone here to write your script / program for you - think again. Many (most?) of us do this kind of thing for a living - and you're not paying us to write your code for you (for which you are getting paid).

If you search the forums you might find some bits and pieces of code to help you - otherwise the onus is on you.

If you write a program and it fails to work - then you can ask for help on fixing the program - but you still need to make an effort to do so yourself. In such cases - streamlining the code to focus on where the problem is will get better results in the forums than posting an entire script with no clear indication of where the problem is occurring.

Migrateduser

Perhaps you might want to look into using url external task. That way you will not have to worry about the callback and getting your own workflow id, task id, etc.... You'll be able to do most of the things in your java class file using cssdk instead.

Adam Stoller

Perhaps you might want to look into using url external task. That way you will not have to worry about the callback and getting your own workflow id, task id, etc.... You'll be able to do most of the things in your java class file using cssdk instead.

What makes you think that the use of a urltask does not require a callback?
That seems to be what you're saying (above).

vpatel

Agree with Adam, you'll still have to do some sort of callback even from CSSDK Java code for your external/URL task.

However, executing OD with web services (Java route) does provide you with a clear set of definitive return codes which, IMHO, are easier to work with than trying to figure out the exact error code with other mechanisms.

Adam Stoller

Agree with Adam, you'll still have to do some sort of callback even from CSSDK Java code for your external/URL task.

However, executing OD with web services (Java route) does provide you with a clear set of definitive return codes which, IMHO, are easier to work with than trying to figure out the exact error code with other mechanisms.

I've never found it that difficult to check the return status from iwodcmd using Perl code - but then again I'm very comfortable in Perl. Different strokes for different folks...

Migrateduser

I guess Interwoven are using different terminology for their ipl files and their java files. According to the sample_external_task.ipl file under iw-home/local/config/wft/examples, they have something like:


    my ($success, undef) = $task->CallBack($transition, $comment);

to do the callback or choose the transition to the next task.

In their java code, they have something like:

    
    task.chooseTransition(transitionName, transitionComment);

So maybe the chooseTransition method does the callback, but nothing specifically called "Callback" like in the ipl file.

What makes you think that the use of a urltask does not require a callback?
That seems to be what you're saying (above).

Adam Stoller

I guess Interwoven are using different terminology for their ipl files and their java files. According to the sample_external_task.ipl file under iw-home/local/config/wft/examples, they have something like:
    my ($success, undef) = $task->CallBack($transition, $comment);
to do the callback or choose the transition to the next task.

In their java code, they have something like:
    
    task.chooseTransition(transitionName, transitionComment);
So maybe the chooseTransition method does the callback, but nothing specifically called "Callback" like in the ipl file.

Both are (apparently) mechanisms for performing a callback / transition in the workflow - so as long as you do something like that you should be okay.