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

Is it possible to add new runtime node in PLC?

kaleemS

TS 7.2.1 , OS Linux.

1# Is it possible to add runtime node in OOTB PLC?

If YES
2# Did anyone added new runtime node ( staging/preproduction) in OOTB Publish Livesite Content Workflow? so there will be three nodes like development, staging and production.
I tried to follow article no 60255 (attached) provided by autonomy to add new runtime node in PLC, However it doesn't work for me.

Please check the attached article and correct/update if required.

I am struggling from last 2 weeks, is there any angle who can help me?

Thank you.

Find more posts tagged with

Comments

nipper

In 7.2.1 there is a bug where you often would get an NPE if you try to deploy to a new node.

There is a serious pain in the a$$ patch you can install to make it work or you can upgrade to 7.3.1

HKN1104

TS 7.2.1 , OS Linux.

1# Is it possible to add runtime node in OOTB PLC?

If YES
2# Did anyone added new runtime node ( staging/preproduction) in OOTB Publish Livesite Content Workflow? so there will be three nodes like development, staging and production.
I tried to follow article no 60255 (attached) provided by autonomy to add new runtime node in PLC, However it doesn't work for me.

Please check the attached article and correct/update if required.

I am struggling from last 2 weeks, is there any angle who can help me?

Thank you.

This article works only for 6.7 & 7.1,

Raise a ticket with Autonomy, They have separate documentation for 7.2.1 and 7.3.1

Thanks

kaleemS

I had raised the support ticket with autonomy and they provided me the following attached document and updates for configuration files.

I updated configuration files as per document and found this document is incomplete.

After configuration I will have 2 LSCS and 2 LSDS.
1-- Production nodes:
LiveSiteProduction
LSCSRuntime

2-- Stating nodes
LiveSiteStating
LSCSRuntimeStaging

Issue Is:
Both deployment (production and stating) are publishing the files without any error, however the stating node is publishing the content on LSCSRuntime instead of LSCSRuntimeStaging.

i.e : if we publish the content using staging node:
then it will deploy to LiveSiteStating and LSCSRuntime (instead of LSCSRuntimeStaging)

Has anyone added the staging node in Ts 7.2.1 successfully?

HKN1104

I had raised the support ticket with autonomy and they provided me the following attached document and updates for configuration files.

I updated configuration files as per document and found this document is incomplete.

After configuration I will have 2 LSCS and 2 LSDS.
1-- Production nodes:
LiveSiteProduction
LSCSRuntime

2-- Stating nodes
LiveSiteStating
LSCSRuntimeStaging

Issue Is:
Both deployment (production and stating) are publishing the files without any error, however the stating node is publishing the content on LSCSRuntime instead of LSCSRuntimeStaging.

i.e : if we publish the content using staging node:
then it will deploy to LiveSiteStating and LSCSRuntime (instead of LSCSRuntimeStaging)

Has anyone added the staging node in Ts 7.2.1 successfully?

Can you share your teamsite-areadiff.xml and odnodes file in conf/lscs and in /etc folder. Check Hostname in that part.

Thanks