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

Multiple run-time environments

System

Is it possible to have multiple LiveSite Run-Time environments for a single Development (Content Center) instance? Basically I am trying to set up a structure where users will be able to preview the site in an integrated "Staging" run-time environment prior to pushing code and content to "Production".

What is the best practice around setting up environments to support this type of integrated staging environment so that it can be pushed to as part of a single content creation workflow?

Find more posts tagged with

Comments

Frederik

possible, but you'll probably have to rework the OOTB Livesite submit workflow big time - or recreate one.

LiveSite version?

Online_Services_Cancellation.rptdesign

Migrateduser

I assumed that I would have to change the workflow, there are going to be significant business requirements that I will need to incorporate anyway, so that is expected. Are there any configuration issues with having 2 Runtime environments for a single Development environment?

This is for 3.0

dinaish20

I assumed that I would have to change the workflow, there are going to be significant business requirements that I will need to incorporate anyway, so that is expected. Are there any configuration issues with having 2 Runtime environments for a single Development environment?

This is for 3.0

Hi
did you find success in implementing this?
we are also trying to have 2 different runtime env (2 diff servers) but no success yet?
any input or pointer will be helpful...
LS3.0 TS6.7.1 Sol 10

thanks in advance.
dinaish

tec_iwov

there's some issues with this as Livesite has only single production and development configurations for targeting/ ootb user management. Development being within Teamsite. The Preview/Development functionality within Teamsite is designed to be as close to runtime as possible.

rajnikant

Hello,

Were you able to implement this successfully for multiple runtime? We have also similar situation. Please let me know if I make copy of OOB Livesite workflow then what all other config changes I need to point new workflow to another Livesite Runtime?

Appreciate any word!

Thanks
Raj

Faizi

Hello,

Were you able to implement this successfully for multiple runtime? We have also similar situation. Please let me know if I make copy of OOB Livesite workflow then what all other config changes I need to point new workflow to another Livesite Runtime?

Appreciate any word!

Thanks
Raj

To achieve this you need to do lots of things.

Save as this OOTB workflow with different name.
Open custom_instantiation.cfg file in config folder and add a new target node.
save and submit this file.
Add DataDeploy configuration in livesite-database.xml for new DB
Add OD deployment target for each node in odnodes.xml and also reciever's allowed directories in odbase.xml
Now to customize livesite:
ivesite_customer_src/etc/livesite_customer/resources/customer-teamsite-resource-config.xml
Add an extensible bean reference for the DeploymentTarget Map in this file. You may cross check this file with teamsite-resource-config.xml existing httpd's child folder (search n get).
Run iwreset-a
Publish your workflow and check the deployment with different target nodes.

Try it, if any issue then reply. HTH

buddha1

Hi,
In support site, you can find the KB article #60255
for adding a new traget node...that might help you

Thanks,
Kishore

rajnikant

Hi,

Thanks bunch for the reply.

I have one more query - If I want to use only one Livesite Run time but want to change deplyment target to some other folder then where and which file I need to change?

In LS3.0.0 user guide they have mentioned somthing on page 78 but I have not got exactly.

Regards,
Raj

Faizi

Hi,

Thanks bunch for the reply.

I have one more query - If I want to use only one Livesite Run time but want to change deplyment target to some other folder then where and which file I need to change?

In LS3.0.0 user guide they have mentioned somthing on page 78 but I have not got exactly.

Regards,
Raj

You need to change the opendeploy.properties file at this location:
\\iw-home\httpd\webapps\content_center\WEB-INF\conf\livesite_customer

You have to change this variable as required.
opendeploy.runtimeHome = your_path

After saving file run iwreset-a to get update.

HTH