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 Site on a Single LSDS Runtime

AakarshC

Is it possible to have multiple Sites on a single Runtime Instance mapping to different webroot folders ?

We are using Livesite 7.1, Teamiste 7.2.1 with Site Publisher and IIS. We need two websites to be run on same LSDS Runtime and they don't share common resources or fixed layouts. Is this possible has anyone done this before.

Find more posts tagged with

Comments

Ranveer

Is it possible to have multiple Sites on a single Runtime Instance mapping to different webroot folders ?

We are using Livesite 7.1, Teamiste 7.2.1 with Site Publisher and IIS. We need two websites to be run on same LSDS Runtime and they don't share common resources or fixed layouts. Is this possible has anyone done this before.

yes it is possible and we are doing. in this case each site will have deffrent folder which carry sitemap.

Rick Poulin

Is it possible to have multiple Sites on a single Runtime Instance mapping to different webroot folders ?

We are using Livesite 7.1, Teamiste 7.2.1 with Site Publisher and IIS. We need two websites to be run on same LSDS Runtime and they don't share common resources or fixed layouts. Is this possible has anyone done this before.

The short answer is yes, I've done it too and in many different ways. I think rather than multiple sites in the same webroot as implied by Ranveer's suggestion, it sounds like you're asking to completely separate the webroot folders? The way to do that is to have a second instance of the whole LSDS webapp run on a different port (you can then mask the ports with a web server that maps domains / virtual servers to the appropriate IPs). How you do that is specific to your servlet container. If you're using the default Tomcat, the magic is all in the server.xml.

AakarshC

The short answer is yes, I've done it too and in many different ways. I think rather than multiple sites in the same webroot as implied by Ranveer's suggestion, it sounds like you're asking to completely separate the webroot folders? The way to do that is to have a second instance of the whole LSDS webapp run on a different port (you can then mask the ports with a web server that maps domains / virtual servers to the appropriate IPs). How you do that is specific to your servlet container. If you're using the default Tomcat, the magic is all in the server.xml.

Yes this is exactly what we are trying to do, have a separate webroot folder for a different site, just to avoid the resources overlap for each site and mask the separate instance using an IIS webserver. Can you mention what changes needed to be done in the tomcat server.xml ?

Thanks

Rick Poulin

Should be fairly obvious from looking at that config file. You just need to create a whole new copy of the <Service> node, changing all the ports, folders and log filenames to new values.

Migrateduser

Hi Akarsh,

If i understand well, you are using the OOTB LSDS and not LSDS as part of an enterprise archive deployed on WAS,Weblogic etc. (This would have been a cakewalk as Enterprise Application servers are very user Friendly...but costly)

for the OOTB LSDS, I agree with Rick. Perhaps you can check out the Tomcat docs : /webapps/docs/config/service.html

mishravik

Can we use PLC for multiple site hosted on multiple instance of Tomcat?

With PLC, so we need to go for separate Branch?
How we can map PLC for branch?

Rick Poulin

Can we use PLC for multiple site hosted on multiple instance of Tomcat?

With PLC, so we need to go for separate Branch?
How we can map PLC for branch?

Have you read the SitePublisher Dev Guide?

mishravik

We want to deploy two site on separate LSDS server using PLC workflow.

Have completed creating new Tomcat instance for LSDS service.

Has started with modifying deployment descriptor file "customer-teamsite-resource-config.xml" for new targetNode.

Not sure what need to be modified into PLC workflow for configuing new targetNode for particular branch. We do not want to use default.site RuntimeConfiguration settings.

Topic_40180__Table_Sort_change via getListProperty.rptdesign

Rick Poulin

Has started with modifying deployment descriptor file "customer-teamsite-resource-config.xml" for new targetNode.

Did this step not work for you?

We do not want to use default.site RuntimeConfiguration settings

That's fine. You would only need this if your sites had different targets but sat in the same branch (which would normally be a bad idea anyway).

Garth McMillan

We do it a different way than what has been mentioned above. I'll mention it in case it helps someone else looking to do something similar. Our set up uses IIS on Windows though, so not for everyone.

We have multiple websites (served over different domains) running on the same LiveSite/Tomcat instance.

In our case we use IIS to "separate" the sites and only use Tomcat to generate the .page content.

We created the separate sites in IIS, with virtual directories to the relevant assets (documents/images etc.), then use a reverse proxy (via the URL rewrite module in IIS7+ or ISAPI Jakarta connecter for IIS6) to Tomcat for the actual pages.

URL rewrite (http://www.iis.net/downloads/microsoft/url-rewrite) is much better than the old Jakarta connector, as far as configuring, so hopefully you're able to use it.

mishravik

Rick

We are using https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/60255.html

for added new node into PLC workflow.

We are not getting any error, workflow is showing that content has been publish sucessfully.

It is not publishing to LiveSite runtime node...

If I modify custom_instantiation.cfg of PLC config workflow
var productionFlag = selection == "newnode";

It's still publishing to production environment, still of "newnode" defined.

newnode is not getting mapping... into PLC workflow.

mishravik

Replaced "production" node from PLC config and workflow file by new node.

Also, modified "lscs-authoring.xml" for add "new node" refernce.

It's working for me.

sumitk

I was going through this post and found out that the same thing we would like to implement.

Could you please explain how to do this as we would like to share the resources?

TeamSite/LiveSite: 7.4.1

Environment: Windows/.NET

What we have is following directory structure:

C:\Interwoven\LiveSiteDisplayServices\webroot\iw\*

C:\Interwoven\LiveSiteDisplayServices\webroot\iwov-resources\*

C:\Interwoven\LiveSiteDisplayServices\webroot\sites\<site-1> : mapped to www.site1.com

C:\Interwoven\LiveSiteDisplayServices\webroot\sites\<site-2> : how to map it to www.site2.com in IIS.?

Any pointers would be helpful.

Thanks,

Sumit

Garth McMillan

To share the same resource folders you could either use IIS virtual folders (if you're using IIS) or symlinks (if you want Windows to do it, ie. should work with any web server - Tomcat etc).

shameem

I have exact similar requirement of deploying multiple livesite sites on lsds instance. But we have a requirement of multiple sites maintained in different branches needs to be deployed to LSDS.

1. Is this possible being iw, templatedate not shared/common across different sites.

2. Do we have to install separate LSDS app seaprately for each website.

3. If #2 is yes, is every instance of LSDS licensed separately. (considering all LSDS pointing to Same LSCS instance)