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

Best possible way to Deploy EA from TS 7.1 to LS Runtime 7.1(Prod) without using DB?

Shiv_Agrawal

Environment and flow is - we have a teamsite server (Ts-Server-1), target server 1 (Target-Server-1), target server 2 (Target-Server-2), target server 3 (Target-Server-3).
User will open TeamSite (Ts-Server-1), go to new form entry, filled the form, press the finish button. In finish button , we have setup a particular workflow (invoked).

Flow of workflow is –
One instantiation form initially open, which have dropdown to choose a reviewer among available values (mandatory field); and then press the next button;
First it locked and submit this newly saved DCR to Teamsite Staging area;
By default workflow create and set one Metadata (EA) for this DCR, EA name is Approved and default value is No;
Then deploy the DCR (eventually xml file) to (Target-Server-1) and (Target-Server-2);
Mail goes to selected reviewer for approval;
Once it got approved by reviewer, in TeamSIte the Metadata value (EA value) for Approved will set to Yes for This DCR;
And finally this DCR (eventually xml file) deployed to (Target-Server-3);

Target-Server-3 is – Linux box, LiveSite Runtime 7.1.0 (LiveSite Display Service 7.1 and LiveSite Content Services 7.1)
Ts-Server-1 is – Linux box, TeamSite 7.1.0, Sitepublisher 7.1.0, LiveSite Content Service (authoring) 7.1.0

Finally LiveSite page (component) on Target-Server-3 read this DCR (eventually xml file) and display the content filled by user on production (Live) website.

Now the requirement is,

We need to read this Metadata value (EA value) also (as explain above, during worflow), on Target-Server-3;
I do not want to deploy this EA in database (I do not want to database come into the picture);
I want to deploy this EA (Approved – YES; or Approved – NO) on File system as DCR (eventually xml file) deployed.

What is the best possible way to achieve this, please suggest ?

How LiveSite Content Service Authoring and LiveSite Content Services Runtime will help me to achieve this requirement ?

Is there Out of the box (OOTB) functionality to achieve above requirement with the help of LSCS Authoring/Runtime ?

Many thanks..

Best
-Shiv

Find more posts tagged with

Comments

vpatel

Sounds like you need LSCS for your use case. However, keep in mind that under the cover LSCS will use a DB -- you just don't have to worry about deploying into that DB or the DB Schema or anything.

Rick Poulin

If you want OOTB, then LSCS is the only way.

The alternative if you insist on a pure file-based solution is to use workflow to inject your EA values into your XML file (as another element or attribute somewhere) right before deployment, assuming you're deploying a different rendering or copy of the DCR and not the DCR itself.

Shiv_Agrawal

@vpatel : Thanks, But As I understand, for deployment I no need to bother, LSCS will deploy the EA (name value pair) into the Database, but once it deployed , LiveSite Runtime (7.1) component (.page/ component) need to read this EA name value pair from Datbase (is this right understanding)? or again I no need to bother about reading this EA on Runtime also ?

Basically , In current architecture, for displaying promotion content on Live website, Component (.page) read the DCR (xml file) from file system (which is deployed through workflow), it didn't hit Database for anything, and now if I deployed this EA in DB (as I understand through LSCS), so on Runtime server, I need to connect to database (through programatically) and fetch/read the EA value from DB, right?

@Rick : Thanks, I am deploying the DCR itself only, no different rendering, no copy; "inject your EA values into your XML" this Idea seems good (and I am also thinking this only).

But, if I want to Go with LSCS (OOTB) , then what should be the possible steps which I need to perform? How this EA value goes from TeamSite to Runtime environment and where ? then how I read this value in .page (component) for performing some condition checks for rendering this DCR content on Live website?

Thanks.

Best
-Shiv

vpatel

@vpatel : Thanks, But As I understand, for deployment I no need to bother, LSCS will deploy the EA (name value pair) into the Database, but once it deployed , LiveSite Runtime (7.1) component (.page/ component) need to read this EA name value pair from Datbase (is this right understanding)? or again I no need to bother about reading this EA on Runtime also ?

.... it didn't hit Database for anything, and now if I deployed this EA in DB (as I understand through LSCS), so on Runtime server, I need to connect to database (through programatically) and fetch/read the EA value from DB, right?
.... ....

But, if I want to Go with LSCS (OOTB) , then what should be the possible steps which I need to perform? How this EA value goes from TeamSite to Runtime environment and where ? then how I read this value in .page (component) for performing some condition checks for rendering this DCR content on Live website?

With LSCS, when an asset (DCR) is deployed (assuming standard OOTB LSCS deployment) following happens:

1. DCR is deployed to the file system.
2. Metadata (EAs) get deployed to LSCS Database -- you do not need to worry about the schema / format of this DB.
3. LSCS will "index" metadata from this DB.
4. Now you can query (do look-ups) against this index using REST API (i.e. http://your-server Smiley Tongue

ort/lscs/v1/document$?q=TeamSite/Metadata/Location:Texas -- will return ALL assets tagged with "TeamSite/Metadata/Location" to "Texas").

Deployment is taken care of for you automatically OOTB. For retrieval you are making REST calls to get what you need on your live website. I would encourage you to read the LSCS documentation.

HTH!