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

Publish LiveSite Content - Need help

pdasarat

All,

I'm just trying to understand the PLC lifecycle. We have a TS 7.3.1 server, with one LSCS Runtime server & one LSDS Runtime server.

If I understand this PLC lifecycle correctly, when I select "Production" on the workflow, does the workflow deploy the metadata into LSDS runtime DB & then deploy the .Page files into the LSDS server.

So the PLC flow is TeamSite -> LSCSRuntime (DB Datadeploy) -> LSDSRuntime (OpenDeploy) -> END

Is this assumption correct?

Then what does the "Development" option on the workflow mean?

Appreciate your response/help in this regard.

Pradeep

Find more posts tagged with

Comments

cute_guy

All,

I'm just trying to understand the PLC lifecycle. We have a TS 7.3.1 server, with one LSCS Runtime server & one LSDS Runtime server.

If I understand this PLC lifecycle correctly, when I select "Production" on the workflow, does the workflow deploy the metadata into LSDS runtime DB & then deploy the .Page files into the LSDS server.

So the PLC flow is TeamSite -> LSCSRuntime (DB Datadeploy) -> LSDSRuntime (OpenDeploy) -> END

Is this assumption correct?

Then what does the "Development" option on the workflow mean?

Appreciate your response/help in this regard.

Pradeep

"Development" option on the workflow mean
=> Deployment to Sitepublisher DB
=> to preview .page in TeamSite server

FooterImage.rptdesign

Rick Poulin

"Development" option on the workflow mean
=> Deployment to Sitepublisher DB
=> to preview .page in TeamSite server

Specifically, the "development" target node doesn't do anything unless you're using LSCS, and even then, only in 7.1 and 7.2. I don't believe it does anything in 7.3+ because of the change to LSCSAuth, but this provides a hook in the PLC's deployment descriptors so that you can add custom deployment steps for deploying to "preview".

PreetpalSingh

Teamsite -> LSCS Auth deployment (development Node) -> SitePublisher DB (development Node) -> LSDS Runtime Deployment (Production Node) -> LSCS Runtime (Production Node)

FooterImage.rptdesign

pdasarat

Teamsite -> LSCS Auth deployment (development Node) -> SitePublisher DB (development Node) -> LSDS Runtime Deployment (Production Node) -> LSCS Runtime (Production Node)

Thanks everyone. Is this the order in which the PLC deploys?

nipper

Thanks everyone. Is this the order in which the PLC deploys?

If you have Dev deployments configured, most people do not. OOTB, it is not set up.