m-e-c as2 contains an embedded jetty which is started automatically. We will include an option into the next version to prevent this. Anyway in the current version you could modify the jetty/etc/jetty.xml of the embedded m-e-c as2 jetty to not listen to any port. Then deploy the mec_as2.war into your web server (it's necessary that your web server contains a servlet engine) and start the m-e-c as2 server on the same machine, thats all.
You guys are the best!. In fact I have a symlink between the two webapps and they still work fine. I have a tiny problem with the realm - monitor.jsp, but I should be able to figure that out. (No realm error in the server).
totalogistix,
m-e-c as2 contains an embedded jetty which is started automatically. We will include an option into the next version to prevent this. Anyway in the current version you could modify the jetty/etc/jetty.xml of the embedded m-e-c as2 jetty to not listen to any port. Then deploy the mec_as2.war into your web server (it's necessary that your web server contains a servlet engine) and start the m-e-c as2 server on the same machine, thats all.
Regards
Heller
Thanks for that. I will try that. I'm planning on using our existing Tomcat server. Is there a way to change the context path in the webserver?
totalogistix,
this could be changed in the context.xml of the war file.
Regards
Heller
You guys are the best!. In fact I have a symlink between the two webapps and they still work fine. I have a tiny problem with the realm - monitor.jsp, but I should be able to figure that out. (No realm error in the server).
totalogistix,
the realm is set up in the jetty.xml and referenced in the web.xml of the war.
Regards
Heller
thanks again for all the help.