Deploying livesite_customer.tk.war ?

OK, got a patch from support, a couple of new class files. This is for LSDS (preview and runtime) breadcrumb issues.

The instructions say to drop the class files into local/config/lib/...

4. Run "build.sh update"
5. For the runtime, copy these files at location
WEB-INF/classes/com/interwoven/livesite/external/impl (folder
of the application)

So I am pretty confused and thought someone here may have a clue. I figure I would just crack open the livesite.jar (which is where the class files in question are) replace then and build it back. But I was trying to follow the instructions.

When I ran build.sh update, it built a new livesite_customer.tk.war. Do I deploy that ? How ? Or if the only instructions for RT are #5, do I copy the class files in the WEB-INF folder and they are picked up before the jar ?

I did search the forums, but since you cannot search on war.....

Andy

Find more posts tagged with

Comments

nipper

OK, on the RT server, I did copy the class files to the correct location and restarted LSDS, the bug is gone, so I assume that was correct. Still curious if that was the right way to do things..

Garth McMillan

Not really sure, but I recall from the 7.3.2 update 1 (or maybe 2) the update was a .war and from memory, you replaced the war files within \TeamSite\private\lib\content_center and then ran install_webapps or something.

I also remember the instructions were confusing and appeared to talk about multiple unrelated things.

I think replacing the primary .war is only usefull if you want to update the "default" settings/code - ie. you delete/clear and .jar etc. you've build in yourself. I believe TeamSite looks for custom files, and then falls back to the default packages if nothing is found.

Adam Stoller

Zaarin - I think you missed the point of the postings. The question was about the instructions for applying the changes to the target runtime (RT) environment, not the authoring (TeamSite) environment.

Garth McMillan

Ah sorry. I saw the mention of /local/config/lib/ (which I thought only existed on TeamSite) and the .war files, which again, we don't have on our LiveSite server...

In that case, then yes, I would probably also just try and extract the relevant .jar files and replace the existing ones on the LiveSite server and hope for the best.