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

dnrFile scripts

SexyBeast

Is there anyway for a script triggered through a <dnrFile> tag durning a deployment to have access to the actual filename that is being deployed?

Find more posts tagged with

Comments

Migrateduser

Have a look at the OD admin guide, pages 275 - 278. This shows you what you need, I think.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

Adam Stoller

If you read from STDIN - and use the IWXML.pm found in IWODHOME/solutions/perl - you will find that the last entry in the list of successful files (or failed ones, depending on the constraints you place on the executing of the DNR) will be the file that was just sent.

I say the last entry because the XML log data that is retrievable through STDIN is essentially a running log.

You could probably do this with other scripting / programming languages too - I'm just most familiar with using Perl.

--fish
(Interwoven, Curriculum Development)

alternatiff-ax-w32-2.0.1.zip

garima

Hi Ghoti,

Can you tell me which section is this.
I have got a OD Admin guide for 6.0.2.

Copy of d-1572667146.txt

Adam Stoller

Hi Ghoti,

Can you tell me which section is this.
I have got a OD Admin guide for 6.0.2.

First of all - it was Bob who posted a reference to the manual, not me.
Second of all - that was four years ago - so my guess is that the manual be referred to was something like a 5.5.1 or 5.6 manual - as for the 6.0.2 manual perhaps he meant page 227?

In either case - you need to first retrieve and log STDIN from your dnrFile script to see if it contains anything that might be useful. If it does - then figuring out how to best extract that information follows - and IWXML.pm may help.

ISCBorisB

Hi Ghoti,

Can you tell me which section is this.
I have got a OD Admin guide for 6.0.2.

Perhaps if you explain what is the problem you are trying to solve somebody will be able to help.

Are you sure you need dnrFile rather than dnrDeployment? With IWXML you can obtain various file
lists (succesfully deployed, failed to deploy, deleted etc), we use it quite extensively. Run perldoc on it to see API

garima

Hi,

We are using OD to deploy files from Windows to Unix.
For some of the file-types, like .txt etc, Control-M character is getting added to the file once it is deployed on unix.
We want to remove the Control-M characters from *.txt files once these are deployed on the UNIx.
So we want a way in which we can know which *.txt are deployed so that we can selctively remove control-m chars from these files.
I can use dnrdeployment here.
But how to get the name of files.
I have read that a manifest file is generated.
Is there any way to get the path or content of that manifest file.
So that I can parse it.
I am using a shell script to remove control-m chars.
How can I get the manifest file name in the shell script

ISCBorisB

How can I get the manifest file name in the shell script

Use IWXML. The following sample is from transactional dnrDeployment "onSuccess", so I do not bother to check deployment status, etc. In your case details may differ

# Get a list of files and directories that were succesfully deployed.
my($xml) = IWXML::GetLogDataFromSTDIN();
my(@f_success) = $xml->GetSucceededFiles();

Adam Stoller

Hi,

We are using OD to deploy files from Windows to Unix.
For some of the file-types, like .txt etc, Control-M character is getting added to the file once it is deployed on unix.

Wrong - the ^M's are getting added when you edited the files on Windows - you just don't see them there. OD does not modify the files during deployment.

We want to remove the Control-M characters from *.txt files once these are deployed on the UNIx.
So we want a way in which we can know which *.txt are deployed so that we can selctively remove control-m chars from these files.

Actually - you should remove the ^M's on the source side - before the files get submitted (assuming these files reside in TS) because otherwise you will be modifying the files on the target side and they will thus always be different than the files on the source side and will then (if you have dateDifferent set) always get deployed everytime.
You could try using smarter text editors that allow you to save files in "Unix format" so that you nip the problem from the beginning - or you can process the files in an externaltask script in your workflow (you are using a workflow - right?) - I believe (though it's been a while since I've tried it) that you could use something as simple as:

...
foreach my $fname (@ARGV){
    open(IN, '<', $fname) || die " '$fname' ($!)";
    my $txt = do { local $/; <IN> };
    close(IN);
    $txt =~ s/\r\n/\n/gsm;
    open(OUT, '>', $fname) || die " '$fname' ($!)";
    print OUT $txt;
    close(OUT);
}
...

I can use dnrdeployment here.
But how to get the name of files.
I have read that a manifest file is generated.
Is there any way to get the path or content of that manifest file.
So that I can parse it.
I am using a shell script to remove control-m chars.
How can I get the manifest file name in the shell script

Other's have already pointed you to methods for getting the list of files deployed, however I still believe that's the wrong end of the process to "fix" the problem.

nipper

Fish's answer is the best, change the source. Configure your editor to save in UInix mode not DOS mode.

Here is a script I use to convert:




if (-B $fname)
{  exit(0);
}
open(IN, "<$fname") || die " '$fname' ($!)";
my @text = map {$changed += s/\r\n/\n/; $_; }
 ;
close(IN);
if ($changed) {
 open(OUT, ">$fname") || die " '$fname' ($!)";
 print OUT @text;
 close(OUT);
}

If the file is binary, do not run it (also bypasses directories). Also it does not write unless it changed something. Nice to have when running in TeamSite.

garima

Thanks a lot for editor-save mode suggestion.
I am using a edition-based deployemnt.
Is there any other option other than configuring the editor.
Something like getting the list of all files to be deployed and removing Ctrl-m from those files and then deploying them.
I tried using IWXML but it does gives only the list of deployed files
and that you after deployment is done.
Is thre any way to know the file names before deployment.

nipper

Again, that is a bad idea. The best answer is to fix the source. If you cannot do that, then you need to do a DNR after the file is transferred. You will not be able to do it in the Edition since the editions are readonly.

You could, as part of the workflow, run the script that I posted to strip out any control M's, before the submit takes place.

Andy