Only caveats are the native libraries used by the Remedy Java api. These will need to be in the LD_LIBRARY_PATH when tomcat is started.
Deploying the mid-tier is just like deploying any other j2ee war/ear/directory/application. Mid-Tier will run as the user that Tomcat runs as. For this reason, the files deployed with the application should be owned by that user so that the mid-tier config page can update the config.properties located in the WEB-INF/classes directory. Not sure what you mean by 'mid-tier will be installed as yet another non-root user.' Axton Grams On Mon, Aug 17, 2009 at 10:51 AM, Rabi Tripathi <ars_l...@yahoo.com> wrote: > Hi, > I have Apache/Tomcat 2.2.8 in solaris already installed by sys admins. I'm > trying to install Midtier 7.1 on top of it. > > All the documentation seem to assume that you are either trying to install > mid-tier with the bundled apache/tomcat or that you already have another web > server/JSP engine (other than apache/tomcat) and you are trying to install > midtier only. > > Nothing on installing just Midtier when you already have apache/tomcat > running. Any caveats not mentioned in the documentation? > > About permissions, apache/tomcat is started by root and then runs as > non-root user (one httpd has root owner, others have web owner). Midtier > will be installed as yet another non-root user. Besides issues with writing > on httpd.config, any other issue I need to be aware of? > > TIA. > > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:rmisoluti...@verizon.net<sponsor%3armisoluti...@verizon.net>ARSlist: > "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
