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

Retrieving Manifest File Name From DnR?

mstradling

Hi,
Does anyone know of any tricks for retrieving the OD manifest file name, or the elements such as deployment config and instance names from a DnR?

I'm running a TeamSite->TeamSite deployment with "recordExtAttr=yes" to generate a manifest file containing all the EAs in the target server's log folder and need to access this file from a DnR script an take some actions based on the EAs.

IWXML::GetLogDataFromFile() can actually parse the EA manifest file but unfortunately IWXML::GetLogDataFromSTDIN() only gets passed the file manifest, not the EA one too.

Potentially I could hard-code the basic info like OD config name as DnR parameters in the OD config but the deployment really needs to be run with a unique instance name. Does anyone know if the instance name is available as a default variable in the OD config that I can pass to the DnR?

Thanks

Find more posts tagged with

Comments

ISCBorisB

Hi,
Does anyone know of any tricks for retrieving the OD manifest file name, or the elements such as deployment config and instance names from a DnR?

I'm running a TeamSite->TeamSite deployment with "recordExtAttr=yes" to generate a manifest file containing all the EAs in the target server's log folder and need to access this file from a DnR script an take some actions based on the EAs.

IWXML::GetLogDataFromFile() can actually parse the EA manifest file but unfortunately IWXML::GetLogDataFromSTDIN() only gets passed the file manifest, not the EA one too.

Potentially I could hard-code the basic info like OD config name as DnR parameters in the OD config but the deployment really needs to be run with a unique instance name. Does anyone know if the instance name is available as a default variable in the OD config that I can pass to the DnR?

Thanks

Search for the manifests with the extension *.eamf within your od-home/log/deployment_group Directory.
Deployment Configuration Guide describes naming convention, Guide's paragraph is "Writing Extended Attributes
to a Manifest File".

As far as I know, DnR's STDIN Stream that you can parse with (or without) IWXML contains neither Files' Extended
Attributes nor for that matter Files content, just Files' Path/Names.

mstradling

Thanks but unfortunately that doesn't really move things forward.

I'm well aware of where the files are written and the naming structure of the manifest files - including the fact that the filename will include the deployment instance name. The question is how can I get either the full manifest name or the deployment instance name so I can construct the file name?

Adam Stoller

Temporarily, modify your DNR to dump the complete contents of STDIN into a file (e.g.: /tmp/foo.xml) - and then examine the contents to see if there is anything within that output that contains the information you want. If so - it should be an easy matter to parse that information from STDIN within your "real" DNR script.

ISCBorisB

Thanks but unfortunately that doesn't really move things forward.

I'm well aware of where the files are written and the naming structure of the manifest files - including the fact that the filename will include the deployment instance name. The question is how can I get either the full manifest name or the deployment instance name so I can construct the file name?

Tough luck. AFAIK instance ID is not reported anywhere, Manifests, Environment Variables, whatever.

Perhaps you can provide it from some place upstream? Some process (like WF Task) creates Deployment Instance Id.
If you can modify this code you may perhaps pass an Id as DNR Parameter through OD -k Flag.

mstradling

Yea, nothing useful in the manifest file, environment variables, etc.

Had a feeling this was going to be a dead-end.

ISCBorisB

Yea, nothing useful in the manifest file, environment variables, etc.

Had a feeling this was going to be a dead-end.

In addition to the "pass ID from upstream" proposal, another possible approach may be to
ignore EA Manifest altogether and simply use STDIN Stream to get deployed File List. Your
code then will obtain/process Attributes from Files, on the source side if needed.

With the large number of Files performance may deteriorate quickly though...