Application Management
Managing Environment-Specific Properties
WebSphere applications often rely on property files to contain environment-specific values. These files usually contain any settings that change between environments, and the files can be in a variety of formats Java properties (key/value pairs), XML, or a custom format.
Reader Feedback : Page 1 of 1
#4 |
Michael Frank commented on the 23 Apr 2008
The article asserts that most will want to use a classpath for locating their "external" properties files, but I've found that the easiest way to manage external properties is to use the local file system, but include the root directory for all files as a Java System Property. The technique is platform portable and intuitive. |
#3 |
Peter Sramka commented on the 14 Nov 2005
Ok... so I finally found the related links for the tables and figures... but shouldn't they be part of the "printer friendly" version? Now I have to hit print 7 times to read the article on paper. That is NOT "printer friendly". Also, after reading the rest of the article, I found MANY more mistakes. It is amazing to me to see that your web site is so elaborate with all of the fancy ads, but the actual "meat" of your site -- the article -- is treated with such disregard... typical marketing BS... |
#2 |
Peter Sramka commented on the 14 Nov 2005
Hmmm... where to begin... I've only read the first part of this article and already I have found numerous mistakes: 1) References to tables and figures that do not exist. 2) A "Sentence" that is not really a sentence. You guys are supposed to be writers? Why can't you write? Also, your web site has these really annoying pop up windows.... |
#1 |
Interesting overview of the different techniques. I've been using env-entry elements in web.xml to pass assorted configuration data to my Web application. This works great at build/deploy time, but (it seems) not so great afterward. I'm more used to Tomcat, which will let me alter these values after an application has been deployed so that I can change an application's configuration through an admin or manager console without redeploying. I'm now using WebSphere Express 5.1, which as far as I can tell will only let me *view* the descriptor, but not alter it. What are my options for having my Web app read environment values that I can alter through the admin console after deployment? (I know I can edit web.xml on the server, but this is something of a hack; why have an admin console if I cannot admin my Web application?) Thanks for any pointers. |