Hi Eric
from a users perspective the current configuration approach is somehow
confusing. The configuration is scattered in different configuration
files.
This is party due to the fact that we want to support a WAR distribution
model along with the standalone.. Since in the standalone model, we
start an embedded Tomcat instance (using the shell scripts, bat files,
and wrapper etc), we want to initialize the ESB the same way for both
distributions - i.e. using the startup servlet. This would guarantee
that we do not break the WAR model as well. During the startup of
Tomcat, we do not want anything related to Synapse or ESB in the
classpath, but everything has to be loaded from the WAR class loader.
Thus the reason to move the Tomcat startup into a separate JAR. Since we
cannot move the logic that earlier parsed the server.xml into this, I
had to introduce the tomcat.properties
webapp\WEB-INF\classes\conf\axis2.xml
HttpCoreNIOListener Port
HttpCoreNIOSSLListener Port
If we think about the axis2.xml, thats where all transports will be
configured.. I think the solution to this is to give better
documentation, and educate the users on how things can be changed - like
a how-to guide maybe?
webapp\WEB-INF\classes\conf\server.xml
RMI-JMX-Port
HTTPPort --> since a few weeks also redundantly here (see above)
HTTPSPort --> since a few weeks also redundantly here (see above)
DerbyPort --> rundundantly within the same file (also in the JDBC-URL)
We will review the redundant declarations, and see if we can improve
these..
AdminConsolePort --> since Asanhkas commit on Friday moved to:
tomcat\lib\wso2-esb-startup-SNAPSHOT.jar\tomcat.properties
which from a configuration point of view makes things even worse.
How can we now change the admin port? We need to be able to change the
port!
This is via "ConsolePort=9443" on the tomcat.properties
webapp\WEB-INF\classes\conf\wrapper.conf
RMI-JMX-Port of wrapper
I do not think you need to edit anything on the wrapper.conf.. did you
have to?
Ports are only one example. The user needs to know a bunch of
configuration files and options. Can we somehow change this, that at
least the most common options can be configured in a single file?
Configuring the same options in different files rundundantly, like the
http/https listener ports, has to be avoided. What if the values don't
match? This can happen quite easily.
A solution to this maybe something like a GUI driven installer..? Which
asks a few questions, and configures the instance accordingly.. will
this work?
asankha
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
