Hi all,
today I bothered my head about how to use one WSO2 ESB installation with
different configurations (ports, logging configuration etc.) on the same
machine.
We are used to install all server software like Weblogic, JBoss in one
central location (centralized data center rollout) and use several
instances with different configurations on the same host.
How could I do this with WSO2 ESB?
Relevant configuration resides in:
<ESB_INSTALLATION>/webapp/WEB-INF/classes/conf
<ESB_INSTALLATION>/tomcat/conf
The problem seems to be the conflict between standalone server and WAR
deployment? The whole WSO2 ESB infrastructure is build following an
exploded WAR-structure.
I thought whether it would be possible to make this an installation
option and only put the WSO2 ESB software in a WAR structure if it has
to be deployed to an existing web container.
Ideally I would like to pass an option specifying the configuration
location (directory) to a server start script. Of course the synapse
configuration plays a special role and any user should be able to put
this file to a location outside this configuration folder. Right now
this is already possible via using the System-Property "synapse.xml".
How can I achieve my goals with the current implementation?
Only thoughts, nothing tried yet...:
- copy content of <ESB_INSTALLATION>/webapp/WEB-INF/classes/conf
and <ESB_INSTALLATION>/tomcat/conf to n instance-specific
locations: <ESB_INSTANCE_DIR>/<CONFIG_DIR>
- patch wso2-esb-deamon.sh to only set WRAPPER_CONF and PIDDIR
if not already set
- create new central startup shell script which:
- accepts instance-directory as parameter
- set and export CONFIG_DIR as absolute path
- modify wrapper.conf in $CONFIG_DIR to your needs
- remove line
"wrapper.java.classpath.10=webapp/WEB-INF/classes/conf"
- remove line "wrapper.java.classpath.3=tomcat/conf"
- add line "wrapper.java.classpath.3=$CONFIG_DIR"
- remove line
"wrapper.java.additional.4=-Djava.io.tmpdir=work/temp/esb"
- add line
"wrapper.java.additional.4=-Djava.io.tmpdir=$INSTANCE_DIR/tmp
- set all system properties which are normally set in
<ESB_INSTALLATION>/webapp/WEB-INF/web.xml as
servlet init parameters to point to the files in
$CONFIG_DIR
- export WRAPPER_CONF as $CONFIG_DIR/wrapper.conf
- export PIDDIR as $INSTANCE_DIR/run
- call patched <ESB_INSTALLATION>/bin/wso2-esb-deamon.sh
Hmm, even if this would really work (I'm going to check this, if I find
the time), it does not look convenient, or?
What could we do to support these requirements?
Regards,
Eric
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
