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

DNR callback to fail on target

ProfessorX

OD 5.6 Win2k

I have a simple batch file on the target that I run after a successfull OD deployment.
This batch file could fail.
Can I do anthing to call back to tell the Deployment that the DNR failed?
Something like below:

BAT FILE BEFORE
REM copyfiles.bat
REM Batch script
REM Start

copy

\temp\filea.txt C:\temp\filea.txt
echo coppying

REM End

BAT FILE AFTER
REM copyfiles.bat
REM Batch script
REM Start

copy

\temp\filea.txt C:\temp\filea.txt
echo coppying

if not exist C:\temp\filea.txt (

echo <response code=-2/>

)

REM End

Or is this just not possible?

Thanks in advance!
The Professor-

Find more posts tagged with

Comments

Migrateduser

Printing

<response code="-2"/>\n

to STDOUT should do it. Be sure to check out the OD 5.6 Admin Guide (Nov 2003 edition) p. 184 for details about how OD will behave when the response code is returned at the various trigger points.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Adam Stoller

You might need double-quotes (" ") surrounding the <.../> string as DOS might be treating one or both of them as redirection directives. Also - I believe you need quotes (single should work) around the -2.

i.e. change:
echo <response code=-2/>
to
echo "<response code='-2'/>"

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

ProfessorX

Ran the following

<?xml version="1.0" encoding="ISO-8859-1" ?>

<deploymentConfiguration >

<localNode host="myhost"/>

<replicationFarmSet >
<replicationFarm name="WAS_SERVERS">
<nodeRef useNode="$wasnode^"/>
</replicationFarm>
</replicationFarmSet>

<definition name="wu_webfiles">
<source>
<sourceFilesystem area="c:\stuff" filelist="c:\morestuff\fillist.txt">
<pathSpecification >
<path name="."/>
</pathSpecification>
</sourceFilesystem>
</source>

<target useReplicationFarm="WAS_SERVERS">
<transferRules doDeletes="no"/>
<targetFilesystem area="c:\stuff">
</targetFilesystem>
<comparisonRules dateDifferent="yes">
</comparisonRules>
<permissionRules/>
</target>

</definition>

<deployment transactional="no" >
<execDeploymentTask useDefinition="wu_webfiles">

<deployNRun >
<dnrDeployment location="target" when="after" state="success">
<script cmd="C\dir\movedownloadables.cmd $atype^ $local^" as="D:\Interwoven\OpenDeployNG\tmp" where="" async="no" >
</script>
</dnrDeployment>
</deployNRun>

</execDeploymentTask>

</deployment>

<logRules maxBytes="23Mb" level="verbose"/>

</deploymentConfiguration>

In the movedownloadables.cmd all I tried
echo "<response code='-2'/>"
and
echo "<response code='-2'/>"

It still completed

Thanks in advance!
The Professor-

Adam Stoller

I tend to avoid DOS scripting as much as possible - if you have Perl on the machine, I'd suggest doing it in Perl...

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

PaulW

I have got the following code, done in Perl:

$exitval = "<response code=\"-2\"/>\n";
exit $exitval;

I call it like this:
<dnrDeployment location="source"
when="after"
state="success">
<script cmd="cmd..."
where="dir...."
async="no"
/>
</dnrDeployment>

My opendeploy still completes successfully. Does anyone have any idea about this?

Adam Stoller

It's not an exit value - it's a string you need to print to STDOUT before exiting (as a failure)....
if ($error_condition_is_true){
print "<response code='-2'/>\n";
exit(1);
}
# everything ok
exit(0);

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