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

pass manifest filename in DNR configuration

cmcc

Hi
I have a deploy-and-run configuration which triggers a perl script on the destination server. At present I'm passing the filelist filename to the script as a parameter but I need to pass the manifest filename instead. Is there any way of doing this?

<script cmd="D:\Perl\bin\perl.exe

\myscript.pl $filelist^" async="no" />

Find more posts tagged with

Comments

cmcc

My present DCR configuration is

<script cmd="D:\Perl\bin\perl.exe

\myscipt.pl $filelist^" async="no" />

g2svnit

Hi,

You can pass manifest file name in similar way as you are passing filename currently. Manifest name is always standard it is the combination of host name, target name, port and ints name (check documentation for details of name).
Is that what you are asking, if not please mentione your problem in details.

Regards,
g2

Adam Stoller

Why do you need to pass the manifest file?
Your DNR should be able to retrieve the manifest file information via STDIN in XML format - all you need to do is parse that to get the information you're probably looking for.
It's generally a lot easier than conjuring up the complete filename for the manifest file - which would require knowing all sorts of information:

Just write a simple DNR script that retrieves the contents of STDIN and dumps it into a temporary file. Look at the contents of the file, and then modify your DNR to parse that information directly from STDIN and output the information you believe you're looking for into the temporary file. Once you have that working, you can retrofit your real DNR script to parse the information and use it as you need (without needing to dump it to a temporary file).

ISCBorisB

Your DNR should be able to retrieve the manifest file information via STDIN in XML format...

In addition to what Ghoti mentioned, check /OD-HOME/solutions/perl directory, you *may* have
IWXML.pm Module there. If you do, run perldoc on it. Module performs manifest parsing for you
and provides methods like IWXML::GetSucceededFiles, IWXML::GetFailedFiles and so on.

There are also usage samples on the Forum, search with IWXML key.

Adam Stoller

In addition to what Ghoti mentioned, check /OD-HOME/solutions/perl directory, you *may* have
IWXML.pm Module there. If you do, run perldoc on it. Module performs manifest parsing for you
and provides methods like IWXML::GetSucceededFiles, IWXML::GetFailedFiles and so on.

There are also usage samples on the Forum, search with IWXML key.

While I thought the IWXML module was supposed to be able to handle manifest data processing, I believe it only works if you configure the servers to not use the manifest logging (I forget the actual setting right now - but it's in the manual and/or DTDs and such)

ISCBorisB

While I thought the IWXML module was supposed to be able to handle manifest data processing, I believe it only works if you configure the servers to not use the manifest logging (I forget the actual setting right now - but it's in the manual and/or DTDs and such)

Ah, yes... Two stream formats, "log" and newer "manifest". The setting is in odbase.xml
<dnrProperties allowDnrExecution="yes" infoStreamFormat="[log | manifest]"/>

Default is "manifest". If IWXML does not work with it, one can always switch to the older "log"
format or parse stream himself like you've proposed originally...

3 Data Set Join.rptdesign