Monday, April 20, 2015

Why Message Flow Node Name MUST (SHOULD) be unique within flow in IBM Integration Bus v9.0 (WMB) ?

In IIB 9.0 Toolkit, it gives the error “Node name: Node name must be unique within flow” in properties view when we try to assign same name to any other node within the flow and in problem view, the error message is“Node name ‘<NodeName>’ is not unique within the flow”

IBM Knowledge Center Goes Mobile!!!

In this year, IBM has successfully completed the redirection of all 950 of IBM product information centers to IBM Knowledge Center.

Now IBM Introduced IBM Knowledge Center mobile beta and it currently supports iOS and Android Mobiles



Features available in Mobile Beta:
  • search all of IBM Knowledge Center
  • filter your searches by product
  • preview search results
  • read topics and get context with mobile-friendly breadcrumbs
  • log in and add topics you want to read later to “My Collections” of the desktop application. When you sign into the desktop after doing this in mobile, the topics you added are shown in a special entry called “Added from IBM Knowledge Center Mobile”
  • it also lets you switch back to the full desktop site from the options page

How to extract content of the message flows from Broker runtime?

Below are the two commands that can be used to retrive the message flow contents from the Broker.

mqsibrowse
mqsireportproperties

These commands will be very useful to check what code is currently deployed to broker and also for reengineering if we missed the source code and bar files.

Usage:
mqsibrowse <BrokerName> -t brokerresources > brokerresources.txt
mqsireportproperties <BrokerName> -e <ExGrpName> -o AllMessageFlows -r > mqsireportproperties.txt