This is my usual weekly roundup of what’s new and interesting on developerWorks. This week we start with something for the WebSphere Application Server developer. When abstracting configuration properties out of code they often end up in a simple properties file. This is fine if the values are static but, if they need updating, you either need to redeploy the application containing the file or else put the file somewhere separate from the application. (If taking the latter approach then the config directory is a good place for the file as then you call leave the application server to replicate it across the nodes.) Perhaps a better approach is to configure a resource environment provider as described in this article, enabling properties to be defined administratively.
The second article I’d like to highlight is relevant to those using WebSphere Process Server and WebSphere ESB. When faced with a GUI environment like WebSphere Integration Developer the question is often asked, how do I make this part of my automated build environment? Some customers don’t even try, checking built artefacts in to their version control system. This article describes how to use Ant to retrieve SCA modules from ClearCase and build them using WebSphere Integration Developer in headless mode.
Finally, whilst not earth shattering, if you are new to JMS and WebSphere MQ then this article describes how to get started in a non-J2EE environment.