soatipsntricks – Twitter Latest WebSphere related RedbooksEarlier in the year I helped to author an IBM Redbook, Connecting Enterprise Applications to WebSphere Enterprise Service Bus. I’m pleased to announce that it’s now available in public draft. In particular, the book focuses on CICS, MQ, JDBC, and HTTP integration. Kudos to Peter, the project leader, for all his hard work in getting it to this stage.
Your comments, praise, or complaints would of course be greatly appreciated.
If you have a WSDL or XSD schema that has already been published to the web that you need to use in WebSphere Integration Developer you can import it straight from the web by choosing the File>Import>HTTP option and specify the URL rather than download the file and import it from the filesystem.
If you have a secured instance of WebSphere Service Registry and Repository and you want to use the Endpoint Lookup mediation primitive to use this instance to determine which endpoints you have available, then you may want to check out this technote which describes the configuration steps necessary and an iFix you will require if you are on the 6.0.2.0 level of the WebSphere ESB or WebSphere Process Server.
If you’re creating a Message Filter primitive in a mediation flow using WebSphere Integration Developer, it may not be immediately obvious how to define a criterion that will fire when an element of the message is null. The following XPath expression should be sufficient:
count(/body/myOperation/myElement) = 0
Obviously, the expression inside the brackets should be replaced with the part of the message you wish to test. You can find this easily by using the regular XPath editor. Then click ‘Override’ and alter the expression so that it is of the form shown above.
Thanks to Ian for help with this tip.
In WebSphere Integration Developer, you may sometimes find yourself importing a Project Interchange File, only to see errors about a missing dependency on websphere_default_messaging_provider.
This is an automatically generated project that is created whenever you use a JMS binding. Ideally, you should export it whenever you are creating a Project Interchange file containing modules with JMS imports or exports, and this will happen if you include the modules’ dependencies. However, if you forget to do this (or someone else doesn’t include it and you are given the interchange file), there is an easy fix – simply create a new export in a module, add any interface, and then a JMS binding. Save the project, and you should find the warning disappears. You can now delete the export.
