Invoking datadeploy module as part of workflow

Before you ask someone else to do your QA work for you, why don't you test this and find if you have any problems. Then, after some tweaking on your part, if you're still having problems, update your post with specifics.

C:\Interwoven\OpenDeployNG\bin>iwodcmd start DDTutorial/ddconfig -k iwdd=deployment1

I tried to execute this command as part of the workflow, but it didn't execute.

my $dd1 = "C:/Interwoven/OpenDeployNG/bin/iwodcmd";
my $dd2 = "start";
my $dd3 = "DDTutorial/ddconfig";
my $dd4 = "-k";
my $dd5 = "iwdd=deployment1";

declare_task('datadeploy',
name => "datadeploy",
description => $localizer->format('deploy_task.description'),
type => "externaltask",
owner => $iw_areaowner,
timeout => "+000001", # 1 minute
areavpath => $iw_workarea,
unlock => TRUE,
command => "$dd1 $dd2 $dd3 $dd4 $dd5");

If my approach is not proper ,pls specify the correct approach.

Your approach is not proper.

Hope that helps.

Before you ask someone else to do your QA work for you, why don't you test this and find if you have any problems. Then, after some tweaking on your part, if you're still having problems, update your post with specifics.

Dave, there's nothing to QA here - the approach taken was based on good intentions with some QA (in terms of testing things on the command line first) but with a lack of understanding in how workflows, and specifically externaltasks, function.

While I think it would be great if everyone who developed wfts actually had some training - we both know that isn't going to happen - in this case, there was a demonstrated grasp of trying things out from the command line and taking the same command and putting (albeit crudely) into a WFconstructor-type WFT - just a lack of comprehension on how workflows and externaltasks (or cgitasks) work.

Adam,

Call me cranky on a Monday morning -- and that would be appropriate, by the way -- but "If my approach is not proper ,pls specify the correct approach." suggests to me that he didn't even bother with the documentation. We both know that the documentation is sorely lacking in some areas but is pretty decent in others, this being one of them. Not to mention, there are many workflow examples and a few datadeploy examples to go on.

So, it seems to me as though more effort could have been made as to this approach -- however, it's always nice to have very helpful people on DevNet (rarely myself, sometimes you, often Jeff, etc.) who will lend a guiding hand towards things which one can easily get on their own without barking an "RTFM" which has often been my battle cry as of late.

Dave

I had posted the problem after spending considerable amount of time on

it. If any one knows the solution to the problem please guide me.

Regards,
Sachin

jbonifaci

If any one knows the solution to the problem please guide me.

As Adam stated above, you can't call it directly. You need to create a wrapper script that calls OpenDeploy and also performs the needed callback. There should be many examples of externaltask scripts with callbacks around.

~Jeff

Instead of calling "iwodcmd start" from your wrapper script, you may prefer to call "iwperl /solutions/iwodstart.ipl". The latter provides more information as to the results of your deployment which you may want to parse in order to route your workflow appropriately. The usage is pretty much the same as "iwodcmd start" but you don't need "start" as an argument and should call it with iwperl. Okay, so I guess the usage is a bit different but only in those two cases.

I think iwodstart.ipl has been marked deprecated. Perhaps Mariam could confirm or deny that for us? It's still there, but it could go away in a future version without warning. Not a big deal either way as long as you are aware of it.

I've heard that, too -- do you know of a replacement script or executable for this that provides as much detail as iwodstart.ipl?

I'm afraid not.

I find the output of iwodcmd start sufficient for what I do in my OD script. All I do is check the output to see whether it Completed, Completed with error, Failed, or didn't return one of those. Unless it is just plain "Completed", I kick it off to my alternate transition and trust the admin to go look at the logs and figure out what went wrong.

I guess so... personally, I appreciate the "STATUS: 2", etc. Hmm, when I got up this morning I didn't think I would eventually reminisce about iwodstart.ipl. Strange how that happens.

I guess so... personally, I appreciate the "STATUS: 2", etc. Hmm, when I got up this morning I didn't think I would eventually reminisce about iwodstart.ipl. Strange how that happens.

The entire reason iwodstart.ipl was created was to provide better exit status handling for Windows where the original CLT "iwodstart" didn't seem to be able to return the proper exit status to the caller.

iwodcmd is a replacement for iwodstart (and all the other pre-iwodcmd CLTs) which, I believe, does return the correct exit status to the caller even on Windows - and if so (haven't verified this right now) - then there's little need for the iwodstart.ipl script to exist.

iwodcmd should be more efficient that iwodstart and iwodstart.ipl because it should be issuing commands through an already existing JVM process instead of launching a new one in which to run the desired command.

I was not able to invoke datadeploy from the workflow using the perl script as the wrapper.

I tried to invoke the datadeploy using the perl script as the wrapper.
This perl script further invoked the .bat file.
The .bat file is having the command to invoke datadeply.
And the perl script is invoked using external task within the workflow.

Attached are the perl script & .bat file.

Perl script is invoked from the workflow using the following syntax.

declare_task('datadeploy',
name => "datadeploy",
description => $localizer->format('deploy_task.description'),
type => "externaltask",
owner => $iw_areaowner,
timeout => "+000001", # 1 minute
areavpath => $iw_workarea,
unlock => TRUE,
command => "$iwperl $dd_script");

where :
my $dd_script = "$wft_dir/solutions/myWFDDfile.ipl";
my $myiwperl = "c:/Product/Interwoven/TeamSite/iw-perl/bin/iwperl";

Attached are the perl script(myWFDDfile) & .bat (MyFile) files.

Perl script is getting invoked, but the datadeploy is not getting invoked.

Regards,
Sachin

Perl script is invoked from the workflow using the following syntax.

declare_task('datadeploy',
name => "datadeploy",
description => $localizer->format('deploy_task.description'),
type => "externaltask",
owner => $iw_areaowner,
timeout => "+000001", # 1 minute
areavpath => $iw_workarea,
unlock => TRUE,
command => "$iwperl $dd_script");

where :
my $dd_script = "$wft_dir/solutions/myWFDDfile.ipl";
my $myiwperl = "c:/Product/Interwoven/TeamSite/iw-perl/bin/iwperl";

Before we spend any time looking over your code - could you please verify that you are either using $myiwperl as defined instead of $iwperl - or - that $iwperl as shown being used, is in fact correctly defined?

It was typing mistake.
I have the following declaration in the wft file.

my $iwperl = "$iwhome/iw-perl/bin/iwperl";

Regards,
Sachin

I tried to invoke the datadeploy using the perl script as the wrapper.
This perl script further invoked the .bat file.
The .bat file is having the command to invoke datadeply.
And the perl script is invoked using external task within the workflow.

Attached are the perl script & .bat file.

These are so small - it's pretty easy to figure out you don't know what you're doing here and really need to spend some time learning Perl:

Out of curiosity - did anything get written to c:/indus.txt ?I highly recommend you pick up a copy of O'Reilly's Programming Perl and spend some time with it (a couple of hours) and then try again.

Yes the debug statements are written to the indus.txt file.

Please can u provide me exact synatx i need to write in perl script.

I am basically a java programmer working on Interwoven for the first time.

I am having a hard time working on so many tools ( teamsite / datadeploy / opendeploy / workflow /form api) and reading the individual documentation for these.

Regards,

Sachin

Yes the debug statements are written to the indus.txt file.

Please can u provide me exact synatx i need to write in perl script.

I am basically a java programmer working on Interwoven for the first time.

I am having a hard time working on so many tools ( teamsite / datadeploy / opendeploy / workflow /form api) and reading the individual documentation for these.

Regards,

Sachin

I'm not going to write the script for you - sorry. I've pointed you at a very solid reference book (that reads nicely too) which, if you spend a couple of hours with it should get you about 90% there - the rest of it comes from looking at the perldoc's for TeamSite::WFtask and perhaps the workflow tutorial supplement (a bit old, but not too out-dated).

If you have specific questions about specific pieces of code - and you post your code - you'll very likely get an answer. But asking someone to write the code for you is bad form.

I know - you said "syntax" not "code" - but if you want the syntax for a built-in function in perl - run perldoc -f function_name, if you want documentation for a particular module (and its functions) - run perldoc module-name.

I have modified my perl script to have a callback for the task.Still the datadeploy did not get invoked.
But when i execute the same perl script from the command prompt, its working fine. Here is the perl code i have writte.

use TeamSite::WFtask;
use TeamSite::WFworkflow;
sub debug {
$data_file=" >> c:/indus.txt";
open(DAT, $data_file) || die("**Could not open file!");
#print DAT "@_\n";
print DAT "@_\n";
close(DAT);
}
debug('Invoking Batch File ----');
print 'Hello World 1111222';

my($jobid, $taskid, $area) = (@ARGV[0..2]);

debug($jobid);
debug($taskid);
debug($area);
my($task) = TeamSite::WFtask->new($taskid);
system('c:/MyFile.bat');
#this bat file has dos commands to invoke datadeploy
$task->CallBack(0, "Success");
debug('Invoked Batch File ----');
debug('Hello datadeploy----');
exit(0);

Also please provide me the syntax for invoking the datadeploy command from this script,instead of writing separate bat file.

Regards,
Sachin

I have been able to execute the datadeploy from my workflow.

Thanx for all the help provided.

Regards,
Sachin