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

How do I make my DNR use rcv manifest?

System

I have a deployment config where I have a DNR that I want to use the rcv manifest. However, I'm not having any luck making it use the rcv manifest. I can only get it to work using the src manifest.

This is the DNR that is causing me problems:
[html]

<script cmd="/usr/interwoven/od-home1/OpenDeployNG/conf/odscripts/ibm_HandleUpdates_to_www03.pl /usr/interwoven/od-home1/OpenDeployNG/tmp > /log/iw/deploy/updatedFiles03.log" as="stgweb" where="" async="no" >
</script>

[/html]
If I have location="source", it runs, but it is using the source manifest which doesn't have what I need. If I use location="target" as shown above, it doesn't work at all. The script doesn't even start up.

Thanks in advance for any insight,
Maria
P.S.
Here is my complete config XML:
[html]

<script cmd="/usr/interwoven/iw-home/custom/deploy/ibm_log_deletions.ipl" as="" where="" async="no" >
</script>

<script cmd="/usr/interwoven/od-home1/OpenDeployNG/conf/odscripts/ibm_HandleUpdates_to_www03.pl /usr/interwoven/od-home1/OpenDeployNG/tmp > /log/iw/deploy/updatedFiles03.log" as="stgweb" where="" async="no" >
</script>

<script cmd="/usr/interwoven/od-home1/OpenDeployNG/conf/odscripts/ibm_HandleDeletes_to_www03.pl /usr/interwoven/od-home1/OpenDeployNG/tmp 2>>/log/iw/deploy/ibm_HandleDeletes03.err" as="stgweb" where="" async="no" >
</script>

<script cmd="/usr/interwoven/iw-home/custom/bin/ibmsend_html_mail_generic.ipl -t sgtsadm@us.ibm.com -f sgtsadm@us.ibm.com -m "There has been a deployment error from the TeamSite servers branch. Please check the OpenDeploy logs on TEAMSITE01." -s "TeamSite servers branch Deployment Error"" as="" where="" async="no" >
</script>

[/html]

Find more posts tagged with

Comments

Migrateduser

Can you run the ibm_HandleUpdates_to_www03.pl script from the command line on your receiver?

Migrateduser

Yes, for this config my source and receiver are the same server.

Adam Stoller

You might have to specify a specific triggerPoint.
However - I don't believe the script uses the manifest file per se (unless you have code within the script that expicitly goes to find the right manifest file) - instead it uses in-memory XML-formatted log data.

The quickest way to verify what you're getting is to temporarily replace your DNR script with a simple script like this:

#!/path/to/iwperl
use strict;
use warnings;
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();
my $log = "$iwhome/tmp/od_dump.log";
if (open(OUT, '>', $log)){
   while (<STDIN>){
       print OUT;
   }
   close(OUT);
}
else {
   print qq|<response code="-2"/>\n|;
}
exit 0;

Try adjusting the DNR paramaters (before/after, source/target, and targetPoint) and see what, if anything, changes in the output file.