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

PLC - Deploying to a Web Farm

PaulW

I have multiple web servers in my farm that I need to deploy to. Is there a simple way of configuring the OOTB PLC workflow to deploy to a farm rather than a single node?

I tried changing the targetNode attribute of customer-teamsite-resource-config.xml to point to a farm name instead of a node name, but this just raised a DeployFiles exception when trying to deploy.

Find more posts tagged with

Comments

Frederik

we have done something similar by editing the relevant xml file under ODHOME/conf/LiveSite/ (webroot something)

Replace the internal farm reference by an external farm reference - and set up the farm in odnodes.xml

As you can see, I left part of the exercise to you ;-)

PS: if you are also using a farm of LSCS, it's similar, but a bit more elaborate.

Crsb

Few people had some luck with the steps provided in the LS technical reference, but so far the best and easiest way to handle this was thru the traditional OD farms and filters in the deployment config file. you might have to create a separate deployment config files for runtime deployment vs the preview deployment. if you want to have fan out LSCS deployment, make sure to use localhost as your runtimehostname in the lsauthoring.xml.

PaulW

i tried changing the OD WebRoot to pass the targetNode variable as the external farm name. and then i created the farm in odnodes, and updated customer_teamsite_resource_config.xml and ran a build. But when I try and publish to production I get the following error: Error during task execution: Could not invoke method: deployFiles, reason: null

I dont want to hard code the target farm name, as I have a preproduction and a production environment, which will have different farm names. Thats why I can use the example in the lscs tech ref.

how would I create separate deployment configs for runtime vs preview? which config maps these?

PaulW

we have done something similar by editing the relevant xml file under ODHOME/conf/LiveSite/ (webroot something)

Replace the internal farm reference by an external farm reference - and set up the farm in odnodes.xml

As you can see, I left part of the exercise to you ;-)

PS: if you are also using a farm of LSCS, it's similar, but a bit more elaborate.

Frederick, have you hard coded this into the WebRoot? We have added another target environment (Pre-Production). So I don't want to hard code the OD config file. Is there a clever way of doing this? All the document seems to refer to LSCS fan-out. And it specifically is showing hard coding - which clearly wont work when there are multiple target environments.

PaulW

Even the documentation for doing a fan-out deployment to LSCS doesn't make sense. because those configs in conf/lscs are also used by the development deployment. So if I hardcode another node into the deploy configs, that extra node will try to be deployed to even when just selecting the target as development in the job instantiation screen.

Migrateduser

Got a solution from support and I think it retains the flexibility you mentioned. Hople it helps.

Rohan_t1

Got a solution from support and I think it retains the flexibility you mentioned. Hople it helps.

I tried this sometime back with TS 6.7.2 SP1 with LSCS and it didn't work. This seems to be valid for TS 7.x versions.