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

Deploying Externals to the RunTime environment

Bowker

We've created a few Externals and Controllers to use in LSDS and they work perfectly in the preview environment.

Can someone enlighten me on what gets moved to the runtime environment? Specifically what should be moved from he TeamSite server to the runtime server? (full path names would be most helpful)

If it's explained in Chapter 6 of the TeamSite SitePublisher Developers Guide, it's not clear to me.

Find more posts tagged with

Comments

santosh013

Hi,
you need to copy your lib containing your classes from the TS server location:iw-home\local\config\lib\content_center\livesite_customer_src\lib to LS Server location: iwov\LiveSite\runtime\web\WEB-INF\lib.
Also you need to copy the customer-resource-config.xml located at :iwov\iw-home \local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\resources to iwov\LiveSite\runtime\web\WEB-INF\conf\livesite_customer\resources.

Thanks.

interDev

We've created a few Externals and Controllers to use in LSDS and they work perfectly in the preview environment.

Can someone enlighten me on what gets moved to the runtime environment? Specifically what should be moved from he TeamSite server to the runtime server? (full path names would be most helpful)

If it's explained in Chapter 6 of the TeamSite SitePublisher Developers Guide, it's not clear to me.

Things moved to the runtime environment (by workflows) are the ones present in Teamsite branches. If you have externals and controllers residing at the backend, you will have to move them manually to the runtime environment. Similarly, if you are using some custom fixed layouts, you will have to move them separately to the runtime environment.

interDev

Hi,
you need to copy your lib containing your classes from the TS server location:iw-home\local\config\lib\content_center\livesite_customer_src\lib to LS Server location: iwov\LiveSite\runtime\web\WEB-INF\lib.

Thanks.

Classes present under home\local\config\lib\content_center\livesite_customer_src are zipped using build command and are them unzipped at the runtime.

DrillThroughDashboard.zip

santosh013

Classes present under home\local\config\lib\content_center\livesite_customer_src are zipped using build command and are them unzipped at the runtime.

There are several ways to do this.
We can make/maintain our own jar of concerned classes and then place that jar in the concerned lib folder of the runtime environment.
There is no need to unzip.

HTH.

Crsb

just copy your httpd/webapps/content_center.../lib/livesite_customer.jar to LiveSite\runtime\web\WEB-INF\lib and restart LSDS.

nipper

A better idea is put them on a branch and set OpenDeploy to push the jars out (as well as other config files). May be able to bounce the app server with a DNR as well (some, like WebLogics are done via GUI)

Faizi

Adding some points to nipper's reply:
[indent]Using a workflow you can define a process of deploying all the related code and configuration file to LSDS. Might be you associate a workflow with new job that will attach all the related files from livesite_customer_src location and deploy to LSDS.
You can also give a UI where user can select options for type of files needs to deploy to LSDS. Now you should have a deployment descriptor which perform the deployment activity.
[/indent]Its upto you how you will define the process.

Bowker

When I look in
iw-home\local\config\lib\content_center\livesite_cust omer_src\lib there's only one file, sqljdbc4.jar (dated 4/19/2010).

The file that appears to be the one I want is iwhome\locak\config\lib\content_center\livesite_cu stomer_out\livesite_customer.tk.war

The other question is, what do I put into (or where is it documented) customer-runtime-resource.xml?
The Class I'm starting with is "com.ntrs.livesite.external.Environment" and there are two methods: getEnvironment() and getParameters().

Rick Poulin

The posts above were a bit misleading. What you want to copy is any configuration files you've customized in livesite_customer_src, in addition to livesite_customer.jar (contains your compiled classes), which you should find in livesite_customer_out. You do not need to copy any .java or .class files. The .tk.war file is only used within TeamSite, so you want to leave that behind as well.

Again,
livesite_customer.jar from livesite_customer_out goes to your runtime's WEB-INF/lib, and
customized XML and .properties files from livesite_customer_src go to their corresponding directories under your runtime's WEB-INF folder.

The other question is, what do I put into (or where is it documented) customer-runtime-resource.xml?

This is a class for modifying the various Spring-loaded Java beans used by LiveSite, and for adding your own. LiveSite's configuration can be found in ApplicationContainer/server/default/deploy/iw-cc.war/WEB-INF/conf/livesite/**/*.xml or iw-home/httpd/webapps/content_center/WEB-INF/conf/livesite/**/*.xml (depending on your version), as well as in your runtime's WEB-INF/conf/livesite/**/*.xml.

The Class I'm starting with is "com.ntrs.livesite.external.Environment" and there are two methods: getEnvironment() and getParameters(). The Class I'm starting with is "com.ntrs.livesite.external.Environment" and there are two methods: getEnvironment() and getParameters().

How is this seemingly-custom class relevant to the thread?