IT03010: NEW MBNODE API CALLS FOR BASE64 ENCODE AND DECODE FUNCTIONS

APAR status

• Closed as program error.

Error description

• In IBM Integration Bus V9 a utility class called "Base64" was
  moved from
  the com.ibm.broker.javacompute package (javacompute.jar) to an
  internal utility package.
  
  The Base64.Class was never officially part of the Broker API,
  but some customers were using it.
  
  Two new calls are added to the MbNode API to create an
  officially supported Base64 interface. These are called:
  
   MbNode.base64Encode((byte[ ] clearText)
   Where clearText a byte array to be encoded.
   The call returns a String that represents the encoded text.
  
   MbNode.base64.Decode(String base64Text) .
   Where base64Text is a String to be decoded.
   The call returns a byte array that represents the Base64
   decoded text.
  

Local fix

• See
  DCF:http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg2167
  6037
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10 who want to use Base64
  encoding in the JavaCompute node.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  In IBM Integration Bus V9 a utility class called "Base64" was
  moved from
  the com.ibm.broker.javacompute package (javacompute.jar) to an
  internal utility package.
  
  The Base64.Class was never officially part of the Broker API,
  but some customers were using it.
  
  Two new calls are added to the MbNode API to create an
  officially supported Base64 interface. These are called:
  
   MbNode.base64Encode((byte[ ] clearText)
   Where clearText a byte array to be encoded.
   The call returns a String that represents the encoded text.
  
   MbNode.base64.Decode(String base64Text) .
   Where base64Text is a String to be decoded.
   The call returns a byte array that represents the Base64
   decoded text.
  
  
  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 Base64 Class has been reinstated in the
  com.ibm.broker.javacompute package, but its use is deprecated.
  
  Two new methods have been added to the MBNode API to perform
  Base64 encoding and decoding.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.8
  
  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