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 somewhere else

Mikowo

Hi,

Inherited an application that is deploying on a specific LCSC and LSDS using the publish workflow.

What file do I need to change to deploy somewhere else using that same workflow(OOB).

I know about odbase and odnodes but not sure for the database is it only database.properties?

Guidance would be appreciated, for
1. Teamsite files
2. OD Files
3. LSCS on the authoring side

DO I need to change the workflow.

MIchel

Find more posts tagged with

Comments

Mikowo

Is there any doc that would explain this?

Mikowo

Is it just changing the following file?

od/etc/livesite-database.xml to the proper Livesite display serivces.

IN this case how does livesite content service is getting updated?

Mikowo

Hi,

Finally got my answer so I will share this for the other to use.

Don't need the livesitedisplay service database, only need the content services DB to deploy content to livesite.

How to do this:
------- Teamsite side
1. ON Teamsite side edit Database.properties
change db.enable= false
This is telling him not to use Display servies database.

2.Make sure lscs-authoring.xml and odnode are setupu properly

------- Livesite runtime
1. Livesite display services edit database.properties
change db.enable= false
Don't need this DB

2. Make sure that livesiteCSRT\..\lscs-conf.properties is setup to the right Content servies DB.

ANd that's it, it will only use two port the usual 20014 and the one that content services uses. To find out which one content services uses look into lscs-authoring.xml file.

Hope this help anybody else,

Regards,