WebSphere ESB / Integration Developer / Process Server 7.0 Announced

For those already working with WebSphere Integration Developer, WebSphere ESB, or WebSphere Process Server, or those considering using them, you might be interested to know that version 7.0 has just been announced and is scheduled to be available around the end of Q4 2009.

Please look at the official announcement for more information, but some of the new things I think are particularly interesting are:

  • Service Federation Management between WebSphere Services Registry and Repository and WebSphere ESB.
  • More pattern-based development.
  • Exploitation of WebSphere Application Server V7.
  • Improved Service Gateway scenario support.
  • Event sequencing support in WebSphere ESB.

Viewing Data using WebSphere Integration Developer

WebSphere ESB uses an embedded database for the Message Logger mediation. WebSphere Process Server uses even more – for example, as the backing store for long-running processes. The test environment versions of these products that are embedded inside WebSphere Integration Developer use the Derby Embedded database to run these – it is supplied with WebSphere. But how can you view the data inside it? In older versions, the cview tool was used for this. In 6.1, you can use WebSphere Integration Developer instead. Here’s how:

  • Start WID (if it’s not already started).
  • Stop the server you are using so that the databases aren’t locked.
  • Switch to the Data perspective.
  • In the Database Explorer view, right-click and select ‘New connection…’.
  • Select Derby 10.1 as the database manager.
  • Select the database you are interested in. For example, I selected <WID_INSTALL_PATH>\pf\esb\databases\MEDB, which is the messaging engine database for my WESB test server.
  • Select <WID_INSTALL_PATH>\runtimes\bi_v61\derby\lib\derby.jar as the Class location.
  • Untick Create the database if required.
  • Set the user ID and password to the appropriate values – if you are using an out-of-the-box WID test server, they will be admin and admin.
  • Select Test Connection. If it fails, double-check the values you entered.
  • Now select Finish.
  • Now there should be a connection in your Database Explorer view. You can expand that to navigate through your database. In particular, you are probably interested in the Schemas section.