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.

7 Responses to Viewing Data using WebSphere Integration Developer

  1. anton_evane says:

    Version 6.1 working faster with large table amount.

  2. Sadh says:

    Hi –

    Can you tell me how I can access the BPEDB through the data explorer in a WID 6.2 desktop Windows installation ?

  3. Sadh, well the method is essentially the same – just the database path will end in BPEDB.

    Having said that, whilst it’s obviously OK to poke around out of curiousity, it’s strongly recommend not to manipulate the BPEDB manually.

  4. Sadh says:

    Hey Andrew-

    Thanks for the response . But , when I try the connection it throws me the following exception –

    SQL Exception: Failed to start database ‘C:\WID6.2\pf\wps\databases\BPEDB’, see the next exception for details.
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

  5. Pingback: Confluence: NovaERM

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: