Generic host name for lscs query

Hello there,

Teamsite OS -- Solaris 10
LSCS OS -- Linux RED HAT 6 - 64bit

We have a situation where we have a prod and a dr environment for Teamsite. Both the servers are a complete two physical servers with their own fqdn. We are pushing content from PROD environment (every night PROD and DR Teamsite are synched up) to LSCS servers and using LSCS rest based query we are fetching the content.

We see a problem, when the PROD goes down and we have to move to DR Teamsite server. Now from DR Teamsite server we deploy some new content.
Now if we have to make query, then for project or context parameter we have to pass the Teamsite server name also. If we have deployed some new content from DR server then is there a way to find out a generic way to make lscs query without substituting the host name. As the app server wouldn't know for which request should it use old Teamsite host name and for which one it should use the new one.

Is there a way during PLC to change the setting of the server name to some generic option? This way we can avoid changing the server name during our LSCS REST calls.

Or any other option one can suggest to avoid this situation will be helpful.

Find more posts tagged with

Comments

Adam Stoller

Are you using a single database server for both PROD and DR or distinct servers?

Do you use a DNS alias for accessing PROD, that gets switched to access DR when needed?

Migrateduser

We have 2 separate databases for each Teamsite instances.
We don't have any alias as of now to make a switch. Users will be using the new Teamsite servers fqdn to access DR server if PROD goes down.

Rajesh

Adam Stoller

I don't know for sure, but a DNS alias, especially if you ensure that all configuration file references to the hostname use the alias, on both boxes, might give you the seamless results from LSCS ... although it is possible that the system qualifies the hostname and ends up using the actual FQDN anyway... it's still worth a shot - and much more likely to fit within the "supported" concept than trying to change some internal code to use a "generic" name.

Rick Poulin

You can force specific branches to use a given LSCS project name in the <branchinfo> elements of lscs-authoring.xml

nipper

You can force specific branches to use a given LSCS project name in the <branchinfo> elements of lscs-authoring.xml

This is BY FAR the best practice. Having the TS server name in the project is a bad idea.

Migrateduser

So the recommendation I am hearing from everyone is to make an entry for project in lscs-authoring.xml to avoid issues with project to include the server name.

Thanks for the inputs.