IBM Support

IT36917: GETJDBCTYPE4CONNECTION CALL THROWS BIP6278E IF THE SECURITYIDENTITY IS NOT DEFINED.

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

  • If the JDBC connection does not require a userName and password
    then the JDBC Policy can be configured with 'jdbc::none' or
    'default_User@default_Server' as the securityIdentity value.
    Still the getJDBCType4Connection call fails with a BIP6278E
    error message.
    
    BIP6278E: ( BKR11.default ) Node ''Java Compute'' is unable to
    create a connection with the datasource represented by
    JDBCProviders policy name ''{JDBCPolicy}:MYJDBC'', because of
    incomplete configuration settings. The JDBCProviders policy has
    been configured with securityIdentity property value
    ''jdbc::none'', which has not been defined by using the
    mqsisetdbparms or mqsicredentials command.
    

Local fix

  • Define the referenced securityIdentity using mqsisetdbparms
    command.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 and V12.0 using
    the getJDBCType4Connection API.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the JDBC connection does not require a userName and password
    then the JDBC Policy can be configured with 'jdbc::none' or
    'default_User@default_Server' as the securityIdentity value. But
    the getJDBCType4Connection call fails with a BIP6278E error
    message.
    
    BIP6278E: ( BKR.default ) Node ''Java Compute'' is unable to
    create a connection with the datasource represented by
    JDBCProviders policy name ''{JDBCPolicy}:MYJDBC'', because of
    incomplete configuration settings. The JDBCProviders policy has
    been configured with securityIdentity property value
    ''jdbc::none'', which has not been defined by using the
    mqsisetdbparms or mqsicredentials command.
    

Problem conclusion

  • The product no longer throws BIP6278E error if values of
    'jdbc::none' or 'default_User@default_Server' are set as the
    securityIdentity value in the JDBC Policy.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.14
    v12.0      12.0.2.0
    
    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

    IT36917

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-16

  • Closed date

    2021-08-19

  • Last modified date

    2021-10-06

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
13 October 2021