Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Deploying LSCS webapp on new tomcat instance
jsankara
Anyone had luck installing LSCS on tomcat instance instead of using LSCS runtime's tomcat ?
Can I just copy the LSHOME/runtime/webapps/lscs to my tomcat's webapps folder ? will it be enough or do I need to copy some other files/folders ?
Find more posts tagged with
Comments
nipper
Is this a new server or one with an existing LSCS ?
If you do a new install it will ask for tomcat and you can install whatever one you want. Have it preinstalled and point to the tomcat install folder and it will continue.
jsankara
New tomcat instance without LSCS..
nipper
Install LSCS and point it to the existing Tomcat. Standard install.
jsankara
Thanks Andy..I will give it a try..
Migrateduser
Hi Guys,
I have similar scenario. Where can we point the LSCSRT to Tomcat because in my case after installing LSCSRT, when i hit the URL:
http://servername:1976/lscs/v1/admin/status
getting 404 error.
And under Tomcat Manager i do not see lscs folder deployed over there during installation does it miss it or it follows other way for deploying.
Can i put LSHOME/runtime/webapps/lscs in Tomcat and check?
TeamSite 7.1, LiveSite7.1, Solaris 5.10
Thanks,
Navid Khan.
Rick Poulin
Can i put LSHOME/runtime/webapps/lscs in Tomcat and check?
No, it's not that simple. There's a few configs that need adjusting in WEB-INF/classes, and you also need to copy+tweak some context.xml files. Do not attempt unless you're very familiar with Java webapp development, because even if I gave you detailed instructions, you're on your own for troubleshooting problems later.
BTW, might be a typo but you said port 1976 when it's actually 1876 by default.
Migrateduser
Yes it is not good way for that but what could be the solution or to debug this scenario where LSCSRT application is not present in the Tomcat Manager and it throws 404 error.
No, we have manually set the port to 1976 instead of 1876.