• Post Reply Bookmark Topic Watch Topic
  • New Topic

Persistent Configuration Data - in J2EE  RSS feed

Tony McClay
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I would like a means to persist configuration data, outside of the EAR file, so that it survives application deployments. Actually, I would love to use a facility like JMX to allow my System administrators to Administer these values per environments, not my developers having access other environments.

Survivable of a clustered Application server = J2EE EAR's Steamed to managed server.

Basically, a persistent configuration store, that is manageable, hopefully through the same Admin console as JDBC Configuration information.

I have come up with a
1. Database Solution ( Have to manage it being up )
2. External property files ( Doesn't travel with a Cluster)
3. Possible LDAP Servers configs (May be different from DEV to QA to Production

So I do not have a good idea.

Can anyone point me in a better path?

Thank you.

Tony McClay
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!