IBM Support

IT17104: BIP4310 EXCEPTION WHEN USING A DECISIONSERVICE NODE WITH A BLANK/NULL SIMPLE XS:STRING PARAMETER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a DecisionService node uses a decision service the
    parameter table has to be populated with XPaths that supply the
    data for each parameter.
    If a parameter has a simple type of an xs:string and the XPath
    identifies a message tree field that has a blank or NULL value
    then a BIP4310 exception is thrown.
    
    Specifically the BIP4310 will show an exception stack that has
    a java NullPointerException with the following at the top of
    the stack:
    
    com.ibm.rules.sdk.res.internal.xml.XMLConversionService.stringTo
    Object(XMLConversionService.java:74)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v9.0 and v10.0 using a
    DecisionService node to invoke a decision service that contains
    a parameter of simple type xs:string.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A DecisionService node is used to invoke IBM Operational
    Decision Manager (ODM) business rules that have been authored in
    IBM Integration Bus (IIB) or ODM. A decision service contains a
    set of rules along with the parameters that are passed into the
    rules evaluation. Each parameter has a schema type which can
    either be complex or one of the basic schema types such as
    xs:string or xs:int etc.
    
    When a DecisionService node uses a decision service the
    parameter table has to be populated with XPaths that supply the
    data for each parameter. If a parameter has a simple type of an
    xs:string and the XPath identifies a message tree field that has
    a blank or NULL value then a BIP4310 exception is thrown with an
    an exception stack  like:
    java.lang.NullPointerException at
    com.ibm.rules.sdk.res.internal.xml.XMLConversionService.stringTo
    Object(XMLConversionService.java:74)
      at
    com.ibm.rules.sdk.res.internal.xml.XMLParametersProvider.getInpu
    tParameters(XMLParametersProvider.java:125)
      at
    ilog.rules.res.session.internal.IlrRuleServiceBase.executeRulese
    t(IlrRuleServiceBase.java:125)
      at
    com.ibm.rules.sdk.res.XMLRuleService.executeRuleset(XMLRuleServi
    ce.java:63)
      at
    com.ibm.broker.businessrules.wodm.RuleEngineImpl.executeRule(Rul
    eEngineImpl.java:494)
      at
    com.ibm.broker.businessrules.DecisionServiceNode.evaluate(Decisi
    onServiceNode.java:345)
      at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1451):
    
    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 product has been modified so that a blank or NULL value is
    accepted as a parameter value for an xs:string parameter in a
    decision service.
    
    Note, this only applies to parameters with a simple type of
    xs:string; other XSD simple data types do not have a concept of
    a blank or NULL value, as such cannot accept them and will
    correctly result in a BIP4310 exception.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.7
    v9.0       9.0.0.7
    
    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 number

    IT17104

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-19

  • Closed date

    2016-11-23

  • Last modified date

    2016-11-23

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020