IT11598: UNABLE TO CONNECT TO ODM VIA JDBC WITH ADDITIONAL CONNECTION URL PROPERTIES

APAR status

• Closed as program error.

Error description

• When using a DecisionService node to access IBM Operational
  Decision Management using JDBC with additional DB2 connection
  URL properties, such as 'securityMechanism', it fails with a
  tokenization exception.
  
  An example connection URL is:
  jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];
  password=[password];securityMechanism=13;
  
  This connection URL works successfully with a DatabaseRetrieve
  node but fails for the DecisionService node with the following
  exception:
  
  BIP4325E: A DecisionService node detected an exception when it
  used the DecisionServiceRepository configurable service. The
  exception is ''. The exception stack trace is
  'java.util.StringTokenizer.nextToken(StringTokenizer.java:360)
  java.util.StringTokenizer.nextToken(StringTokenizer.java:388)
  com.ibm.db2.jcc.DB2Driver.tokenizeURLProperties(Unknown Source)'
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V9.0 and V10.0 connecting to an
  external IBM Operational Decision Manager repository.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using a DecisionService node to access an external IBM
  Operational Decision Management repository using JDBC with
  additional DB2 connection URL properties, such as
  'securityMechanism', it fails with a tokenization exception.
  
  An example connection URL is:
  jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];
  password=[password];securityMechanism=13;
  
  This connection URL works successfully with a DatabaseRetrieve
  node but fails for the DecisionService node with the following
  exception:
  
  BIP4325E: A DecisionService node detected an exception when it
  used the DecisionServiceRepository configurable service. The
  exception is ''. The exception stack trace is
  'java.util.StringTokenizer.nextToken(StringTokenizer.java:360)
  java.util.StringTokenizer.nextToken(StringTokenizer.java:388)
  com.ibm.db2.jcc.DB2Driver.tokenizeURLProperties(Unknown Source)'
  
  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 DecisionService Node now correctly handles additional JDBC
  connection URL properties.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.6
  v10.0      10.0.0.5
  
  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