Hi, I recently started developing for Tomcat, and now, having finished my application, was trying to deploy it, when... The application is a portal site, which - for safety reasons - I have split into 2 parts: admin site, and live site. I want to deploy them to the same Tomcat, into 2 directories below the webapps directory. Then I wanted to configure the Tomcat to allow access to the admin and live site on different ports (and to close the admin port on firewall in order not to allow access from outside). Apart from that, the other goal is that under their respective ports the applications should be roots (context path should be ""). I guess I should configure the tomcat.conf and server.xml files, but failed so far... Thanks in advance: Gyula Ps.: An addition, I am using Tomcat with Apache using WARP [ January 20, 2003: Message edited by: Gyula Klinszky ]
Sorry for not being clearer, this is my first post here As I wrote in the earlier post, I am using Tomcat with Apache through warp. What I wanted to accomplish is to have my 2 applications run on say ports 8008, and 8009, both being root contexts on their ports. I duplicated the server.xml Apache with Tomcat entry, changing the port from 8008 to 8009, keeping the same appBase in the Engine. Then I added WebAppConnection, and WebAppDeploy entries to tomcat.conf like this:
When I tried to start the servers, I got syntax error "Duplicate application specified for the same URL path". So this attempt failed, I guess the reason is that the 2 applications are on the same port. I tried to search on the web, and checked the jakarta tomcat page, but did not find any real information about the tomcat.conf settings. That is where I am stuck now. If anyone could help, I have 2 questions: 1.) Is it possible to separate them to be on different ports with warp, and if yes, how to do it ? 2.) If it is not possible, could you give me some directive how can I get solve this problem (2 applications on the same server, different ports, root context for both) ? Thanks in advance: -Gyula Klinszky
Hey! An easy one! I like it whenI can start like that, I'm new (here) too. Your problem is that both webapps are trying to use the same URL path. Remember, you have a web server out front of both of them, and it is connecting to those sockets, not the outside world directly. That path used is for Apache to decide which webapp to connect to, and they are both set to use the root "/" path. Make one different, and then use Apache's own permissions to block the outside world from the admin app. Cheers!
It's a beautiful day in this neighborhood - Fred Rogers. Tiny ad:
SKIP - a book about connecting industrious people with elderly land owners