IBM Support

JR55475: WRONG NAMESPACE IN SAP IMPORT FILE GENERATED DURING INSTALL OF EAR FILE EXPORTED BY SERVICEDEPLOY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Ø
    If you are exporting an EAR file using ServiceDeploy, you might
    face an issue in namespace definitions on a SAP import file.
    This is changed during the installation steps on the EAR file.
    

Local fix

  • You can use the IID exported EAR file to deploy/install your
    application. As this EAR file contains already a lot of
    required files, it is not using the same code path as the
    ServiceDeploy EAR file.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM Business Process Manager       *
    *                  (BPM) Advanced V8.0.1.3                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When you run SCA module with some       *
    *                      enterprise information system (EIS)     *
    *                      import, such as SAP, you might          *
    *                      receive an exception similar to the     *
    *                      following exception:                    *
    *                      [12/18/15 12:45:04:799 CET] 0000016b    *
    *                      BOCore        1   EClassifier           *
    *                      "http://com/ibm/j2ca/fault/afcfault#Sap *
    *                      ZLgCheckBomPmf" not found in            *
    *                      ClassLoaderScope:                       *
    *                      <<ClassLoader things>>                  *
    *                      This issue occurs only when the EAR     *
    *                      file containing the EIS import was      *
    *                      generated by ServiceDeploy.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The definitions of some adapters, such as SAP, contain complex
    schema for generating EIS binding code. This schema could
    import other schema from different utility jars. The imported
    schema location might be calculated incorrectly when
    ServiceDeploy generates the EIS binding code.
    

Problem conclusion

  • A fix is available for IBM BPM V8.0.1.3 that corrects the
    wrong algorithm to calculate the schema location in the EIS
    binding.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR55475:
    
    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 JR55475, 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

Comments

APAR Information

  • APAR number

    JR55475

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-07

  • Closed date

    2016-05-04

  • Last modified date

    2016-05-04

  • 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

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
04 May 2016