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

LSDS on JBOSS

Amanpreet

Hi,

TeamSite 7.2.1
JBOSS 5.2
We have deployed LSDS as an exploded (unzip) ear on JBOSS and we are deploying our content inside it /deploy/iw-runtime.ear/iw-runtime.war

I wanted to know how to configure/which file I need to update , so that we don’t have to explode ear and it picks up content/custom code from specified location.

I checked KB for JBOSS installation steps and in this article also ear is exploded, however this article is very old (2009). Is this the standard approach?

Find more posts tagged with

Comments

Rick Poulin

I wanted to know how to configure/which file I need to update , so that we don’t have to explode ear and it picks up content/custom code from specified location.

If by "code" you mean JavaScript, SitePub layouts and that sort of thing, then there's nothing to configure. The caching on these files, if any, is a function of the LSDS application and has nothing to do with your servlet container. Updating these files (via deployment or whatever mechanism) should have an immediate effect on the rendering of the pages. Note that the root of the workarea(s) should map (deploy) to your iw-runtime.war folder, such that folders "sites" and "iwov-resources" sit as siblings of "WEB-INF".

If, however, you meant being able to dynamically reload Java class files as you drop them in, that is very much a function of the servlet container which has nothing to do with LSDS, and you'd be better off asking the question on a JBoss forum.

Amanpreet

Rpoulin,

What I want to know is , that do we have to explode iw-runtime ear and deploy content (deploy/iw-runtime.ear/iw-runtime.war ) inside it. Can’t we keep it as .ear file (not exploded) and point it to pick data from some other location (e.g /data/LiveSite).

My question is related to exploding or not exploding LSDS ear.

Rick Poulin

There's a spring-loaded configuration variable in resource-config.xml that you might be able to change with the UITK to get this working, but I haven't come across anything that even remotely suggests that this would be a supported deployment. The documented approach for deploying LSDS into enterprise application servers has always been to deploy into the exploded webapp.