IC99987: PROVIDE MAPPING FUNCTIONS TO ACCESS IBM INTEGRATION BUS PROPERTIES WITHIN A GRAPHICAL DATA MAP

IBM Integration Bus V9.0 - Fix Pack 9.0.0.2

APAR status

• Closed as program error.

Error description

• Provide mapping functions to access IBM Integration Bus
  properties within a Graphical Data Map
  

Local fix

• Prior to the provision of the mb:get...() mapping functions it
  was necessary to use a Custom ESQL transform calling a user
  written ESQL function that returned the required Broker
  property. However calling out to ESQL causes additional
  processing overheads. Also ESQL is not available in all
  licensing modes.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus who use the Mapping node to
  transform messages with reference to IIB property values.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  A Mapping node executing a Graphical Data Map that transforms a
  message with reference to IIB property values has to do so by
  invoking a Custom ESQL Transform to a user written function that
  returns the required property value, causing additional
  processing overhead. In some operation modes the product does
  not allow the use of ESQL.
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0. For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The Mapping node now provides the following mapping functions,
  which can be invoked in a custom XPath transform in a Graphical
  Data Map to retrieve the value of an IIB property.
  
  mb:getBrokerName()
  Name of the Integration Server the Mapping node executing the
  map is running in
  
  mb:getQueueManagerName()
  Name of the default queue manager of the Integration Server the
  Mapping node executing the map is running in
  
  mb:getNodeName()
  Name set as the label, in the flow editor, of the Mapping node
  executing the map
  
  mb:getMessageFlowName()
  Name of the message flow the Mapping node executing the map is
  in
  
  mb:getApplicationName()
  Name of the Application the message flow the Mapping node
  executing the map is in
  
  mb:getLibraryName()
  Name of the Library the message flow the Mapping node executing
  the map is in
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.2
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0530

Applicable component levels

• R900 PSY

     UP