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; } } }

DataDeploy

summergs

Hello,

I have a datadeploy that is working great from the command line but does not work at all in the workflow. The workflow does not deploy nor does it transition to the END task. I have tried several types of syntax but nothing works (two of the types are below). Any Ideas????...I am stumped


<externaltask
name="Unlock"
owner="__TAG__('iw_user');"
description="Unlock submitted files."
>
<areavpath v="__INSERT__($areavpath);"/>
<successors>
<successorset description="Unlock Complete">
<succ v="Deployment"/>
</successorset>
</successors>
<command v='__INSERT__($externalcmd[1]);'/>
<activation>
<pred v="Submit"/>
</activation>
</externaltask>

<externaltask name="Deployment"
owner="__TAG__('iw_user');"
description="Initiating Deployment to Deploy files.">
<areavpath v="__INSERT__($areavpath);"/>
<successors>
<successorset description="onDeploySuccess">
<succ v="End"/>
</successorset>
</successors>

<command v="C:/PROGRA~1/INTERW~1/datadeploy/bin/iwdd.ipl cfg=C:/PROGRA~1/INTERW~1/datadeploy/conf/contractor_dd.cfg deployment=dcr_to_db area=/default/main/gov/internet/state/Projects/HO662_51/WORKAREA/workarea filename=templatedata/Project_Templates/Contractor/data/Contractor project=123 need-result=yes"/>

..............The other syntax:
<command v="__INSERT__('C:/PROGRA~1/INTERW~1/datadeploy/bin/iwdd.ipl cfg=C:/PROGRA~1/INTERW~1/datadeploy/conf/contractor_dd.cfg deployment=dcr_to_db area=/default/main/gov/internet/state/Projects/HO662_51/WORKAREA/workarea filename=templatedata/Project_Templates/Contractor/data/Contractor project=123 need-result=yes');"/>
.................................

<activation>
<pred v="Unlock" />
</activation>
</externaltask>

<endtask name="End">
<activation>
<or>
<pred v="Deployment"/>
<pred v="Review"/>
</or>
</activation>
</endtask>

Find more posts tagged with

Comments

Michael

Hi

I think you are going to need to put the call to your DataDeploy command in a perl script (or similar). As you are probably aware the external task needs to perform a call-back to the workflow to tell it to transition (and which successor to transition to). I don't think iwdd.ipl does this for you automagically...

In your script you might also like to do useful things like checking to see if the deployment was successful.

Another smaller thing -- I am not sure if need-result=yes is a valid parameter for iwdd.ipl. I can only see it referenced in the doco in relation to iwexecdascmd.

Hope this helps.

Cheers
Michael

Adam Stoller

Two things here:

on Windows (which you are clearly on) you need to provide the path to the interpreter for scripts like this because the file associations (e.g. use c:/.../iw-perl/bin/iwperl on anything that ends with ".ipl" doesn't work within the workflow engine) so you need to specify it explicitly.

Again - I suggest you follow the same advice I gave previously to gain a better understanding of this issue.

Once you've taken care of that, you should be able to fix the problem trivially.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

summergs

Thanks everyone!!

summergs

I have now constructed the external task as suggested, however, it still does not deploy. Can anyone see what I am doing wrong??

-- Thanks in advance!!


<externaltask name="Deployment"
owner="__TAG__('iw_user');"
description="Initiating Deployment to Deploy files.">
<areavpath v="__INSERT__($areavpath);"/>
<successors>
<successorset description="onDeploySuccess">
<succ v="End"/>
</successorset>
</successors>

__INSERT__("<command v='$iwhome/iw-perl/bin/iwperl $iwhome/local/bin/TEST_dataDeploy.ipl'/>");

<activation>
<pred v="Unlock" />
</activation>
</externaltask>
.............................................
.....TEST_dataDeploy.ipl ......
.............................................
#!d:\iw-home/iw-perl/bin/iwperl
use TeamSite::WFtask;
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();
my $area = $ARGV[2];
my $task = new TeamSite::WFtask($ARGV[1]);
my @files;
if ($task->IsValid())
{
$output = 'C:\\PROGRA~1\\INTERW~1\\datadeploy\\bin\\iwdd.ipl cfg=C:\\PROGRA~1\\INTERW~1\\datadeploy\\conf\\contractor_dd.cfg deployment=dcr_to_db area=\\default\\main\\state\\internet\\division\\Projects\\HO662_51\\WORKAREA\\workarea filename=templatedata\\Project_Templates\\Contractor\\data\\Contractor project=123 need-result=yes';
$task->CallBack(0, "Data Deployed Successful.");
}

Dwayne

Well, you've got the wrong quote marks around your command. You've got single quotes ('). I think you meant back-ticks (`) which will cause the command to execute.

That would explain why the data isn't deploying, but it doesn't explain why the task is hanging. Try running it from the command line, with the three arguments of JobID TaskID and Workarea, to look for any error message.

--

Current project: TS 5.5.2/6.1 W2K

Michael

Hi

It doesn't look like you are executing the command. You assign the command string to $output. You might have meant to use backticks (eg my $output = `command to execute`) instead of single quotes?

hth

cheers
Michael

Adam Stoller

I think you might also have incorrect quotes for the command - try changing it to be:<command v="__INSERT__($iwhome/iw-perl/bin/iwperl $iwhome/local/bin/TEST_dataDeploy.ipl);"/>Also try adding debugging statements to your script so you can verify that it actually gets run.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I'm guessing that for some reason when you instantiate the task object it's failing, thus your $task->IsValid is not returning true. That's the only possibility that jumps out at me, but I don't see why that would happen. Run it through the debugger and make sure that you have a good $task before that call executes.

Dwayne

<command v="__INSERT__($iwhome/iw-perl/bin/iwperl $iwhome/local/bin/TEST_dataDeploy.ipl);"/>

Are you sure about that, Fish? Doesn't what's inside the parens of __INSERT__ need to be a scalar value? You may be right - I've just never seen it used in that fashion.

I actually think that the original syntax was OK.

--

Current project: TS 5.5.2/6.1 W2K

summergs

I am using the ` (mistyped it in here) ..sorry
The workflow now ENDS (using the external ipl), but still no datadeployment. The datadeployment works great from the command line. I can pass variables into my TEST_dataDeploy.ipl sucessfully. Seems that the datadeployment command itself is not working??
Any ideas? Anyone ever done this (on TS5.5.2 Windows)??

Thanks a million!

Dwayne

I would suggest adding the perl interpreter explicity to the command line you're using to invoke DD from within the external task handler.

<anti-windows-rant>
Windows, being the brain-dead OS that it is, doesn't understand the concept of the #! syntax to control the interpreter to use for a given executable. It bases it solely on the extension of the file. Obviously, from the command line, your user account has .ipl "mapped" back to the TS perl interpreter. It seems likely that the SYSTEM user, which is the one running your task handler, does not.
</anti-windows-rant>

--

Current project: TS 5.5.2/6.1 W2K

Michael

You may also want to see what is in your $output variable. You could output it to a file so that you can investigate.

Cheers
Michael.

summergs

No luck. Does the owner of this external task need to be a Master?

Adam Stoller

Can you re-post the *current* version of the script (which we now know gets executed)?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

It shouldn't matter. Especially under windows, since all external tasks are run as the SYSTEM user anyway.

I think we're back to getting the value of your $output variable dumped into a file somewhere, to try to track down the problem.

You could also comment out the CallBack method use, so that even though the script runs, the task won't transition. You could then run the external task handler from the command line, so that you can see what error messages, if any, are being generated.

--

Current project: TS 5.5.2/6.1 W2K

summergs

$output is empty

summergs

<externaltask name="Deployment"
owner="__TAG__('iw_user');"
description="Initiating Deployment to Deploy files.">
<areavpath v="__INSERT__($areavpath);"/>
<successors>
<successorset description="onDeploySuccess">
<succ v="End"/>
</successorset>
</successors>

__INSERT__("<command v='$iwhome/iw-perl/bin/iwperl $iwhome/local/bin/TEST_dataDeploy.ipl $projBranch'/>");

<activation>
<pred v="Unlock" />
</activation>
</externaltask>

..................
Script.......
................
#!d:\iw-home/iw-perl/bin/iwperl
use TeamSite::WFtask;
use TeamSite::Config;

my $iwhome = TeamSite::Config::iwgethome();
my $branch = $ARGV[0];
my $area = $ARGV[1];
my $task = new TeamSite::WFtask($ARGV[2]);
my @files;

if ($task->IsValid())
{
$output = `C:\\PROGRA~1\\INTERW~1\\datadeploy\\bin\\iwdd.ipl cfg=C:\\PROGRA~1\\INTERW~1\\datadeploy\\conf\\contractor_dd.cfg deployment=dcr_to_db area=\\default\\main\\state\\internet\\division\\Projects\\HO662_51\\WORKAREA\\workarea filename=templatedata\\Project_Templates\\Contractor\\data\\Contractor project=123 need-result=yes`;

$task->CallBack(0, "Data Deployed Successful.");
}

Dwayne

That can't be the current version of the script:

1. You're grabbing the command line arguments in the wrong order. It's jobid taskid areavpath, not jobid areavpath taskid
2. You aren't putting the iwperl.exe in front of the command line like you said you did.

--

Current project: TS 5.5.2/6.1 W2K

summergs

After I verified the perl.exe was running I took it back out

Adam Stoller

Try changing it to look like this:

$output = `$iwhome\\iw-perl\\bin\iwperl C:\\PROGRA~1\\INTERW~1\\datadeploy\\bin\\iwdd.ipl cfg=C:\\PROGRA~1\\INTERW~1\\datadeploy\\conf\\contractor_dd.cfg deployment=dcr_to_db area=\\default\\main\\state\\internet\\division\\Projects\\HO662_51\\WORKAREA\\workarea filename=templatedata\\Project_Templates\\Contractor\\data\\Contractor project=123 need-result=yes);

As already suggested.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

Huh? How did you "verify that it was running"?

And that still doesn't explain the incorrect command line interpretation.

--

Current project: TS 5.5.2/6.1 W2K

summergs

Thanks for all the input. I found the problem to be an incorrect reference to in pathing.
Many many thanks!

$output = `$iwhome\\iw-perl\\bin\\iwperl C:\\PROGRA~1\\INTERW~1\\datadeploy\\bin\\iwdd.ipl cfg=C:\\PROGRA~1\\INTERW~1\\datadeploy\\conf\\contractor_dd.cfg deployment=dcr_to_db area=\\default\\main\\sha\\internet\\marylandroads\\Projects\\HO662_51\\WORKAREA\\workarea filename=templatedata\\Project_Templates\\Contractor\\data\\Contractor project=123 need-result=yes`;

Should have been:
$output = `$iwhome\\iw-perl\\bin\\iwperl C:\\PROGRA~1\\INTERW~1\\datadeploy\\bin\\iwdd.ipl cfg=C:\\PROGRA~1\\INTERW~1\\datadeploy\\conf\\contractor_dd.cfg deployment=dcr_to_db area=\\default\\main\\sha\\internet\\marylandroads\\Projects\\HO662_51\\WORKAREA\\workarea<b>\\</b> filename=templatedata\\Project_Templates\\Contractor\\data\\Contractor project=123 need-result=yes`;