This week's book giveaway is in the Other Languages forum.
We're giving away four copies of Rust Web Development and have Bastian Gruber on-line!
See this thread for details.
Win a copy of Rust Web Development this week in the Other Languages forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Persistent Configuration Data - in J2EE

Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic