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

OD Manifest

bturns

Hi,

OD 6.2.1

I'm running a file list deployment which is also sending EA's of the files. Right now the EA's are written to a file in the log directory with the name.

rcv..log0.eamf

Our plan is to feed this file to search so that search can index the EA's as well as the files.

We are running parallel deployments to avoid a large deployment queue. My concern is that if two deployments run at the same time then one deployment will overwrite the EA file of the other.

I've thought of two ways to solve this:

1) Use a DNR to try and copy the EA log file to a new name/location
2) use a DNR to try and grab the STDIN.

Has anyone tried to use an approach like this? Has anyone found out how to get the EA's from the STDIN?

Thanks,

Brian

Find more posts tagged with

Comments

Adam Stoller

Our plan is to feed this file to search so that search can index the EA's as well as the files.

Are you talking about TS Search - or some web site search engine?
If you have EAs on the files and configure TS search appropriately, you shouldn't have to do anything with regard to deployments for search.

bturns

not TS search. This is for a seperate web related search engine.

Adam Stoller

not TS search. This is for a seperate web related search engine.

I'm a bit confused then - EA deployments with OD only work between TeamSite servers (and then, only when the target area is a workarea) - so I'm not sure how this would be generated and then fed into your web related search engine.

If you want to get EAs on STDOUT you can use iwextattr or use the CSSDK equivalent within some Java code.

It sounds to me like what you want to do is create a deployment wrapper process that produces the manifest file you want and then deploys it (either as a separate process or combined with deploying the actual file assets)