Hello, Working for a previous employer and on a previous version of WAS (4)i was used of putting configuration files (log4j, database properties etc) in property files wich were made availabe to an application (ear) by adding a classpath to the application (application not appserver!). This was a kind of a handy because you could make the configuration files available per enviroment, without changing your actual ear. Now I switched employer and WAS version (5) and whole of a sudden this doesnt seem possible anymore because I cant find any entry in the wasadmin console that looks like a classpath entry per application. In wsad this entry is still available on the path-tab of my server configuration. Few questions: 1) is putting configuration files on a classpath a best practice? If not wat is the most common alternative? (in particualar for log4j configuration but I'm also interested in other configuration issues). 2) where can I find the classpath entries per application on the webbased wasadmin console. 3) I understood that IBM uses its own log4j implementation called JRASS. Is this the WAS way of logging, or can I use special WAS appenders in log4j. the JRAS implementation doesnt seem so intuitive as log4j. many thanx for your response, regards, j.
I think you can set this through the ADMIN console in 5.0. Check out "Application Serevers > [your server] > Java Virtual Machine (at the bottom). I think this is where you find the classpath. This is a per server classpath. For an application only class or jar (thats not included with WebSphere) I would include this in the EAR.