Multi-Tier Deployments and TeamSite EAs

Env. TS 7.2.1 (Solaris) to OD 7.3.2 (Solaris) to TS/OD 7.3.2 (Windows)

Due to a corporate security model we have a multi-tier deployment from a TeamSite server to a "liason" server (running OD base) then off to an externally hosted target TeamSite server.

I know that if I were deploying directly from the internal TeamSite server to the target TeamSite server - that I could use the applyExtAttrs attribute to send EAs.

Is it possible to use the recordExtAttrs feature (which stores the EAs in a manifest file) and use that file to transfer EAs? Or am I making this rocket science?

TIA

Find more posts tagged with

Comments

sheikh1

Yes, you can do this easily by writing a small script to read all EA's and write to a file and then set it at the target TeamSite using same file. I assume you are maintaining similar directory structure between source and target else you need manipulate the metadata(EA) file after reading it from source to match the target TeamSite directory structure.

ISCBorisB

Env. TS 7.2.1 (Solaris) to OD 7.3.2 (Solaris) to TS/OD 7.3.2 (Windows)

Due to a corporate security model we have a multi-tier deployment from a TeamSite server to a "liason" server (running OD base) then off to an externally hosted target TeamSite server.

I know that if I were deploying directly from the internal TeamSite server to the target TeamSite server - that I could use the applyExtAttrs attribute to send EAs.

Is it possible to use the recordExtAttrs feature (which stores the EAs in a manifest file) and use that file to transfer EAs? Or am I making this rocket science?

TIA

I do not think that there is anything in OD to transparently "transition" MD through a server that does not
have TS Virtual File system. One way or another, you'd have to code for it.

"recordExtAttr" will cause OD Base to promote EA manifest to OD Receiver, that's it. You can find/use this
manifest for any purpose whatever, including MD restoration on another tier - as long as you do it yourself.
Sure enough, you can use any other mechanism (like DD) to save/restore MD.

Test.rptdesign

ParameterDialogFragment.txt

81.JPG

Migrateduser

Perhaps some more context on your use case would help here.

The first leg of the deployment can go ahead with an applyExtAttrs as it lands up on another TeamSite filesystem.
You can trigger the second leg of multi-tier deployment from here, probably to a runtime instance using recordExtAttrs feature that writes to a maifest at your receiver directory. How you wish to utilize the manifest is up to you.

ISCBorisB

The first leg of the deployment can go ahead with an applyExtAttrs as it lands up on another TeamSite filesystem

His first leg deployment seems to be to liaison Server that does not have TS, only OD Base

Screenshot.jpg

Migrateduser

His first leg deployment seems to be to liaison Server that does not have TS, only OD Base

Thanks for pointing this out. My bad!
That being said, my take would be to use DD as a possible solution to insert and fetch the EA's.