Hi Eric
Were can I find more information about the WAR distribution model? What are the
advantages/disadvantages of using a WAR versus standalone? What do you
recommand for which purpose?
The WAR distribution and the standalone distribution is the same
'distribution'. To deploy as a WAR, you will extract the Zip, and point
your Tomcat or other JEE app server to load the "webapp" directory as an
expanded WAR. You may also need to edit the web.xml to suit the environment.
There is no advantage on running as a WAR as we do not use the JEE app
servers' servlet transport for messaging - but only to host the admin
console UI and to get the ESB started up via the StartupServlet. Thus I
would recommend using the standalone model, unless your IT department
forces you to deploy any/all applications on a JEE server of their
choice etc
We could also deploy a WAR-file inside a JBossAS, but I'm not sure about the
advantages. Does this change anything regarding JMX-usage or clustering
support? You probably still use or own implementations or am I wrong?
It work.. but there will be no advantages.. but a bit more configuration
and overheads (for JBoss etc), which I'm sure you will not require..
I understand the reasoning of your change, but modifying a properties file
inside of a JAR file is not a optimal solution. Do you expect your users to
repackage the JAR? Sorry, if I get something wrong here.
We do not support an archived WAR.. but only as an expanded WAR from the
file system. The tomcat.properties exists under tomcat/conf outside of
the WAR directory.. The conf files within the WAR are setup properly to
be loaded by the JEE server
And yes, I had to modify the wrapper.conf. I had to add entries like that for
the cluster management stuff
wrapper.java.additional.13=-Dcom.sun.management.jmxremote.port=14121
wrapper.java.additional.14=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.15=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.16=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true
You should no longer need to edit these.. as now with the ability to
shutdown and [re]start via the ESB JMX controls, you no longer need to
go to Tanuki wrapper MBeans
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
