Filelist based multi tier deployment

ShashankJain

Hi Guys,

I have a requirement to address : I am trying to run a multi tier deployment.

Teamsite : 7.4.1

Open Deploy : 7.4.1.0.0

Tier

Server A (OD_Base or Teamsite ) -> Server B (OD_Base or OD_Proxy) -> Server C (LSDS Runtime or OD_Reciever).

Steps Performed :

@Server A :

1. I have created a filelist with files to be deployed (D:\Interwoven\OpenDeployNG\tmp\testFilelist.txt) and passed the same in deploymnet descriptor using -k Parameter.

2. deployment descriptor has been configured with below item -

@Server B :

1. Placed testFilelist_PROD.xml in conf\EmergencyScipt folder with the replicant farm and nodeset.

2. Copied the same filelist to \Interwoven\OpenDeployNG\tmp\testFilelist.txt

It tries to copy files from server a to server B , then it fails stating error in definition at server B while reading the next tier deployment configuration.

QUESTION : By any chance can we run multi tier deployment on file list based operation instead of remote diff.

Also, my client does not want routed deployment to be configured.

Find more posts tagged with

Comments

Rick Poulin

Post the log that contained that message. Your one-line summary of the error message may be hiding the actual details that would help identify the issue.

Yes, filelist deployments should work just fine in multi-tier configuration, although they're obviously harder to get right.

Also, not that it matters much, but your statement about routed deployments is nonsensical. Tactically, routed deployments are a subset of multi-tiered deployments, except in how they're configured. They'd look the same to anybody on the network in this case. /just sayin'

Adam Stoller

rpoulin wrote:
[...]

Also, not that it matters much, but your statement about routed deployments is nonsensical. Tactically, routed deployments are a subset of multi-tiered deployments, except in how they're configured. They'd look the same to anybody on the network in this case. /just sayin'

I would argue that the two are different in that multi-tier deployments require that you place the next-tier deployment configuration on the next-tier server but that routed-deployments actually pass the deployment configuration from source-to-hub[-to-hub...] along with various other pieces of information.

The implementation of routed-deployments may now differ from its original implementation (back around 2000), but its primary purpose (when designed) was to support large global farms. Whether or not the OP / OP's customer wants to use routed deployments is, of course, up to them.

ShashankJain

rpoulin wrote:

Post the log that contained that message. Your one-line summary of the error message may be hiding the actual details that would help identify the issue.

Shashank : Please find attached the log for more details.

Yes, filelist deployments should work just fine in multi-tier configuration, although they're obviously harder to get right.

Shashank : Let me know how to configure filelist based deployment in multi-tier architecture.

Shashank : My client is well versed with the OD setups and configuration, he does not want us to configure routed depoyment due to his own limitations. Also, one more reason is PLC doesnot support routed deployment architecture and he wants all the workflows should follow same type of architecture/configuration. Hope this helps answering your thought.

Rick Poulin

I'm assuming G2WV125 is your middle-man.. any logs on that server that might shed some light on why the definition is bad? In particular, check whether the OD substitution vars are being passed in correctly, because an empty string as the value of $filelist could lead to this type of error.

Regarding the routed deployments, I did say I know the configuration approach is different (as explained by ghoti). I'm just saying that a [business user] client should not care about this type of implementation detail, as long as the requirement is satisfied. So basically I'm making a difference between OP saying "client doesn't want us to use routed" versus saying "we can't use routed for technical reasons". My bad for reading too much into it, I guess.

Adam Stoller

Another distinction between routed and tiered - and perhaps the crux of the matter - is that with tiered deployments you would have to deploy the filelist along with the other files from the original source to the "hub" - whereas in routed deployments this is handled for you.