J2EE Cluster: Is there a common way to handle a central configuration?

Question

We are developing an application that is typically deployed on a single web server. Now we check how it works in a cluster environment, as some clients use clusters.

The problem is that the application creates a local configuration (in the registry / file) that does not make any sense in the cluster. The configuration is changed by the application. Is there a general way (for example, an interface) for creating a central configuration, so config (-file) itself is not duplicated on each node when deploying the application in the cluster? Any other recommended options? (do it manually using the configuration on the network share / in the database / some MBean?)

why common? It should work on different application servers (for example, tomcat, jboss, Webspere, weblogic ...), so we can not use certain specifics for the server.

Thank.

Answer 1

The easiest way for a central configuration is to put it in a file system. Thus, you can connect the file system to your OS and make it available for your application server no matter which brand or version.

. / , ( ). JVM parms, JNDI ( ), .

.

, , . , , ( ?). , ? node? , , , . , , .

, , , , .

Answer 2

, Commons Configuration , , ​​ JDBC JNDI.

Answer 3

JDBC JDNI, , , , , ​​ subversion/ git/mercurial, .. , .

, , , , ( )

, , - databasse, ( ), , , .