IBM Support

JR49304: BUSINESS OBJECT DOES NOT CREATE DATA OBJECT FOR WSDL MESSAGE TYPE IN CUSTOM CODE IF SHARED LIBRARY IS ADDED TO SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you use shared libraries and share your assets
    by-reference between Service Component Architecture (SCA)
    modules and add the shared libraries to the applications, the
    shared libraries are included in the application class loader
    scope. You can successfully create a data object in an
    application according to the message type that is defined in
    the shared library,  as described in the  ᄁ¬ツᆲ モBy-reference sha
    of Java binaries, XML schemas, and interface definitions in
    WebSphere Process Server (using Shared Libraries) ᄁ¬ツᆲ   technot
    http://www.ibm.com/support/docview.wss?uid=swg21322617).
    
    However, if you add the shared libraries to the server, these
    libraries are not included in the application scope class
    loader; they are included in the server scope class loader
    instead. As a result, you cannot create a data object in an
    application according to the message type that is defined in
    the shared library. You receive  ᄁ¬ツᆲ モnull ᄁ¬ツᆲ   from the BOFa
    

Local fix

  • -
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
    *                  Advanced                                    *
    *                  IBM BPM Express                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: When you use shared libraries and       *
    *                      share your assets by-reference          *
    *                      between Service Component               *
    *                      Architecture (SCA) modules and add      *
    *                      the shared libraries to the             *
    *                      applications, the shared libraries      *
    *                      are included in the application class   *
    *                      loader scope. You can successfully      *
    *                      create a data object in an              *
    *                      application according to the message    *
    *                      type that is defined in the shared      *
    *                      library,  as described in the           *
    *                       ¢â‚¬ “By-reference sharing of Java
    *                      binaries, XML schemas, and interface    *
    *                      definitions in WebSphere Process        *
    *                      Server (using Shared Libraries) ¢â‚¬  ½
    *                      technote (                              *
    *                      http://www.ibm.com/support/docview.wss? *
    *                      uid=swg21322617).                       *
    *                      However, if you add the shared          *
    *                      libraries to the server, these          *
    *                      libraries are not included in the       *
    *                      application scope class loader; they    *
    *                      are included in the server scope        *
    *                      class loader instead. As a result,      *
    *                      you cannot create a data object in an   *
    *                      application according to the message    *
    *                      type that is defined in the shared      *
    *                      library. You receive  ¢â‚¬ “null ¢â‚¬  ½
    *                      the                                     *
    *                      BOFactory API.                          *
    ****************************************************************
    * RECOMMENDATION:  Add the shared libraries to the             *
    *                  applications instead of to the server.      *
    ****************************************************************
    When you use shared libraries and share your assets
    by-reference between Service Component Architecture (SCA)
    modules and add the shared libraries to the server, you cannot
    create a data object the custom code of your application
    according to the message type that is defined in the shared
    library. You receive  ¢â‚¬ “null ¢â‚¬  ½ from the BOFactory API.
    

Problem conclusion

  • A fix is available for IBM BPM V7.5.1.1 that finds the WSDL
    message type definition in the server scope class loader and
    creates the data object successfully.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR49304:
    1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
    2. Select APAR or SPR, enter JR49304, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Add the shared libraries to the applications instead of to the
    server.
    

Comments

APAR Information

  • APAR number

    JR49304

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-10

  • Closed date

    2014-04-29

  • Last modified date

    2014-04-29

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021