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

Query on LSCS fanout deployments

Rohan_t1

Hi All,

We are on TS 6.7.2 SP1 and LSCS 7.1. We have LSCS fanout deployments working for all our higher environments. But for two lower environments we have two LSCS instances installed on the same box. This seems to be a roadblock for us since the

odAdapter [font=Arial]doesn't seem to take multiple ports as parameters.

[/font]

[font=Arial]For mutiple servers with independent instances it works fine:

[/font]

[PHP]

Where LSCSserver is the server name where the two instances are installed.
Looks like this is handled in LSCS 7.2 but not in 7.1. Any pointers/suggestions? I might have to debug into the class which takes these parameters but before doing that wanted to check if any one has faced this issue.

Find more posts tagged with

Comments

Rick Poulin

I haven't tested what I'm about to suggest so I don't know if there's negative ramifications, but there's technically nothing preventing you from adding another <odAdapter> node in the <odAdapterSet>, that calls the same things but with a hardcoded port number (or passed in via some parameter other than the OOTB ones) for your second instance. OD should be fine with that, but the LSCS adapter class itself may not be. First thing I'd try though.

Rohan_t1

Thanks Rick for your reply. I tested this with adding another instance with the required values but unfortunately this doesn't work. LSCS adapter class seems to not like it and just hangs. I want to get this confirmed from support however wanted to check if any one has any ideas on this.

If nothing works then the only workaround left would be to sequentially deploy for these select environments.

PaulW

Rohan, d you get an answer on this form support? I am trying to do the same thing. I have tried adding another definition, with some hardcoded values, but this causes the development deployment to fail, as dev only has one instance of lscs.

Rohan_t1

Rohan, d you get an answer on this form support? I am trying to do the same thing. I have tried adding another definition, with some hardcoded values, but this causes the development deployment to fail, as dev only has one instance of lscs.

Paul,
With numerous interactions from support we understood that this is a limitation with 7.1. So they suggested a redesign of authoring.xml and od configs for LSCS. Since we are moving to 7.3.1, we thought of taking it up in upgraded version.

We had this issue because we had two LSCS instance running on same server. Do you have similar case? If not then this should be achievable.

Crsb

Paul,

We had this issue because we had two LSCS instance running on same server. Do you have similar case? If not then this should be achievable.

I am curious to know why you had 2 lscs instances on same server, do you mind sharing/explaining why?

Rohan_t1

Well, it is our DEV environment and caters as DEV1 and DEV2 to our portal site. Consultants who designed it did the same for both LSCS and LSDS DEV environments.

We have separate servers for higher environments.

Crsb

that makes sense, so the consultants designed it but they didn't implement it or show you how to implement it Smiley Happy

Rohan_t1

They did..but left on us to improve the performance Smiley Tongue