developerWorks roundup

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.

5 Responses to “developerWorks roundup”

  1. Harish says:


    I am using wid6.1.2, i want to write a auto build and auto deploy script for SOA modules.

    It would be gr8 helpful, if you could suggest me some articles on this.

    Thanks in Advance

    • Dave says:

      Hi Harish,

      I see the original article I linked to has now moved on. Here is more recent one covering the same subject.


  2. Harish says:

    Thanks Dave for your reply.

    I verified the same article previously, but it talks about the previous version WID6.0.2.

    I didnt have the WID directory structure as its mentioned in the article.

    Bu still i copied to one of the plugin folder but i couldn’t get the option “Generate project ref file” in WID.

    Any idea how to get the “Generate project ref file option” option in WID.

    Below is my WID directory structure
    IBM\Installation Manager\eclipse

    • Dave says:

      I haven’t followed the article through but I would suggest putting the plugin in the same directory as all of the plugins. Be sure to run WID with the -clean command option afterwards so that it picks up the new plugin. If you still can’t get it to work then I’d suggest contacting Grant Taylor would developed the plugin. You can find his contact details here.

  3. Harish says:

    Thank you Dave, I am able to build and deploy the scripts