IBM Support

IT29890: THE PROPERTYUI.WAR CONTAINS THE OLD OJDBC7.JAR DRIVER AFTER YOU UPGRADE FROM V5.2.6.3 TO V6.0.1

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

  • During the upgrade of IBM Sterling B2B Integrator v5.2.6.3 to
    v6.0.1, update JDK version to v1.8 and also update Oracle JDBC
    Driver from ojdbc7.jar to ojdbc8.jar.
    
    The JDBC Driver update works for:
    
    dynamicclasspathAC.cfg, dynamicclasspathAC.cfg.in,
    dynamicclasspath.cfg, dynamicclasspath.cfg.in files, but
    displays a "system error" when trying to access the
    "propertyUI" interface by clicking on the "customization" link
    in the IBM Sterling B2B Integrator 6.0.1 UI.
    The propertyUI.war file is created with the ojdbc7.jar file.
    
    If you enable SSL on the JDBC driver connection,
    you get an SSL Error as the old driver tries to use SSL v3.0
    while Oracle only allows TLS 1.2.
    To fix this, follow the steps below:
    1). Stop IBM Sterling B2B Integrator.
    2). Remove the ojdbc7.jar file from:
    /install/liberty/wlp/usr/servers/SIServer/apps/propertyUI.war
    and under:
    /install/liberty/wlp/usr/servers/SIServer/apps/APIjarsLib/
    3).Manually update the propertyUI.war with the new
    ojdbc8.jar file.
    4). Run setupfiles.sh and deployer.sh
    After this the Customization / Property UI works fine.
    Comments:
    If you do not enable the SSL on the JDBC driver
    connection, after the upgrade you could be using the old
    ojdbc7.jar driver potentially causing
    some problems with the customization UI or REST API's.
    When we upgrade the JDBC Driver, the one located under
    /install/liberty/wlp/usr/servers/SIServer/apps/APIjarsLib/ is
    not updated and stays in the file system.
    

Local fix

  • RTC #: 583637
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    Database driver jars are being bundled in the propertyUI.war,
    which causes issues if the the database driver jar is updated.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    
    A code fix is provided.
    A change was made to prevent the database driver jars from being
    bundled with the propertyUI.war file.
    
    Delivered In:
    6000003
    6000101
    6000201
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29890

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-01

  • Closed date

    2019-09-12

  • Last modified date

    2019-11-22

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"600","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
22 November 2019