On 03/10/18 17:18, Amit Pande wrote: > Thank you so much, Mark! > > In our case, the server.xml contains some information which is generated run > time (pre-config before Tomcat is started) like the paths to key store and > trust store, cipher suites, etc. > > Also, we have an active-passive cluster setup in which only the currently > active node has the access to a shared disk which has all our product > configuration data including the key store, trust store files needed in > server.xml. > > We have a requirement to share the configuration across both the nodes of the > cluster to avoid keeping duplicate copies of configuration (server.xml). And > since some of the server.xml configuration is generated runtime, it isn’t > trivial in our case to keep these copies in sync. > > This is the prime reason to have a shared Tomcat configuration. We may also > want, in future, to spawn and additional instance of Tomcat with re-usable > configuration (except adjusting the port numbers ). > > The not-so-elegant choice we might have is to move the entire Tomcat > installation to this cluster aware shared storage but defeats the purpose of > having a shared disk for configuration data and not the binaries. > > What alternates should we explore?
You could look at using separate CATALINA_HOME and CATALINA_BASE. See https://tomcat.apache.org/tomcat-9.0-doc/introduction.html#CATALINA_HOME_and_CATALINA_BASE Whether have the web applications on the node or the shared storage is arguable either way. If you want it on the node, just use an absolute path that points to someone on the node for appBase. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
