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

Filelist in Multitier deployments

System

Deployment start at point A (ODBase) goes to point B (ODBase), and then point B deploys the same list of files to point to C (ODReceiver). Question is how do I set up filelist(s) in multitier deployment scenario.
I know how to set up filelist deployments from A to point B, but I am not sure how do I get hold of the list of files at point B. How will I make the filelist be available at point B?

Your help appreciated.

Find more posts tagged with

Comments

ISCBorisB

Deployment start at point A (ODBase) goes to point B (ODBase), and then point B deploys the same list of files to point to C (ODReceiver). Question is how do I set up filelist(s) in multitier deployment scenario.
I know how to set up filelist deployments from A to point B, but I am not sure how do I get hold of the list of files at point B. How will I make the filelist be available at point B?

Your help appreciated.

You may want to take a look at [thread=37719]this thread[/thread]

Adam Stoller

You either want multi-tiered deployments or routed deployments - both are covered in the manuals.

Migrateduser

Thanks.

I implemented this using Routed deployments and it worked.

I didnt had to anything with filelist on point B. It took care of transferring files all the way.

Adam Stoller

Thanks.

I implemented this using Routed deployments and it worked.

I didnt had to anything with filelist on point B. It took care of transferring files all the way.

Yes, that's the way routed deployments were designed from the very beginning (when the entire thing was done in Perl using DNR scripts, and then packaged into the OD 5.5.1 release, and then re-implemented in one of the later releases)

In general (though certainly biased) - I think routed deployments are better than tiered deployments.

Migrateduser

Scenario 1 - Point A, Point B, and Point C are all windows. Meaning, all the tiers in this Open Deploy set up are on Windows OS. This set up works perfectly fine.

Scenario 2 - Point A and Point B are Windows. One of the receiver from Point B is Linux (RHEL 6.1). So, in this scenario Point C would be Open Deploy Receiver installed on Linux. A (Windows)-> B (Window)-> C (Linux).
This set up is not working becuase I couldnt figure a way to provide a destination/target directory on C different from that is on B. It is picking the target directory from the deployment descriptor XML on the origin (point A) server.

Question - Is Routed deployment supposed to work in scenario:
A (Windows)-> B (Window)-> C (Linux) scenario?

If it is suppose to work, how can I provide target directoty for point C?

If not, what options do I have?

Your help/dircection appreciated!

ISCBorisB

Scenario 1 - Point A, Point B, and Point C are all windows. Meaning, all the tiers in this Open Deploy set up are on Windows OS. This set up works perfectly fine.

Scenario 2 - Point A and Point B are Windows. One of the receiver from Point B is Linux (RHEL 6.1). So, in this scenario Point C would be Open Deploy Receiver installed on Linux. A (Windows)-> B (Window)-> C (Linux).
This set up is not working becuase I couldnt figure a way to provide a destination/target directory on C different from that is on B. It is picking the target directory from the deployment descriptor XML on the origin (point A) server.

Question - Is Routed deployment supposed to work in scenario:
A (Windows)-> B (Window)-> C (Linux) scenario?

If it is suppose to work, how can I provide target directoty for point C?

If not, what options do I have?

Your help/dircection appreciated!

OD Deployment Configuration Guide => Routed Deployments => Specifying Next-Tier File Locations

Basically, you will have to use "targetArea" Attribute of the Node(s) that you include into
corresponding route Segment(s). If you use this node for other Deployments and do not want
"targetArea" there, create a dedicated one with the unique name. Note that you can have as many
uniquely named nodes as you want pointing to the same DNS/IP address.

Migrateduser

The targetArea attribute didnt help.

I was playing with targetArea attribute (nodes.xml in the origin server - A) and value given here seem to serve as a source location of that given node, and not the target location. Example -

-- Attached snippet from odnodes.xml --

Here, "E:\targetArea" serves as a source location when routed deployment is running on point B.

The target location is read from the deployment descriptor XML located on the origin server (Point A).

-- Attached snippet from deployment xml --

And, this value is retained as a target location through out the routed path.

So, coming back to the problem,I have a mix of Operating systems in the routed deployment path. I cant have a common target folder location across the two operating systems.

Looks like routed deployment is not my option given the requirement that I want filelist deployments, across multi-tiered targets, with different operating systems in the routed path.

ISCBorisB

...And, this value is retained as a target location through out the routed path

Something is not right. Divide and conquer...

Play with simple 2 nodes Win-to-Win routed Deployment first. Use targetArea to specify
distinct Target location and make sure that your configuration works as expected.

If it works, expand it to more nodes.
If it does not and you want us to take a look, provide relevant Nodes, Route Segments
and complete deployment configuration.

Migrateduser

Thank you. After multiple attempts as trial and error, I was able to figure out the configuration set up for the routed scenario:

A Windows-> B Window-> C Linux

I appreciate your responses.

Adam Stoller

Thank you. After multiple attempts as trial and error, I was able to figure out the configuration set up for the routed scenario:

A Windows-> B Window-> C Linux

I appreciate your responses.

To be of use to those who might run into this problem later - you should post details about what files you needed to configure and the specific parts of those files you needed to adjust (and how) for this scenario to work.

Then you should close the thread.