Posts Tagged ‘IBM Message Broker’

I’m a BIG believer in two things: a) work smarter, not harder; 2) keep things simple — avoid complexity. Complex leads to complicated, complicated leads to misunderstanding, misunderstanding leads to chaos. Nonetheless, my guidelines seem easy enough, right? Well, good news then, they are simple and easy to apply in just about anything we face day […]

Just for curiosity’s sake and this blog, I looked up the definition of ‘cache’ [as used in computer science]. Most sources define it as “…a component that transparently stores data so that future requests for that data can be served faster “.  The part about served faster reminded me of an old adage. It goes like this. […]

Peers, it is time to embrace IBM’s Integration Bus v9 aka IIBv9. Many of us are comfortable developing solutions using WebSphere Message Broker [WMB] version 6, 7 and 8. To date, all the projects I’ve worked on at Perficient, clients still used WMB 6/7. However, IBM recently re-branded WMB as Integration Bus. Much of the […]

Introduction This article addresses the DFDL message modelling feature in IBM® WebSphere® Message Broker (also known as IBM® Integration Bus). It contains step by step instructions for creating a DFDL schema for a flat file using WMB tool-kit. Data Format Description Language, commonly known as DFDL is an open standard based modelling language which is using […]

I recently had a unique integration requirement where an external service provider was expecting XML within the SOAP request. One automatically thinks CDATA but in this case the endpoint required the XML to be escaped within a SOAP request. <SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns1=”http://exacttarget.com/wsdl/partnerAPI”> <SOAP-ENV:Body> <ns1:CreateRequest> <ns1:Name>XML_Data</ns1:Name> <ns1:Value>&lt;order&gt; &lt;ns1:Attributes&gt; &lt;ns1:Name&gt;Transaction_ID&lt;/ns1:Name&gt;&lt;ns1:Value&gt;Transaction_ID goes here&lt;/ns1:Value&gt; &lt;/ns1:Attributes&gt; &lt;/order&gt; </ns1:Value> </SOAP-ENV:Body> </SOAP-ENV:Envelope> […]