IBM Support

IT47061: UNEXPECTED RESULTS WHEN USING THE XSLT TRANSFORM NODE AFTER 12.0.12.0

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

  • There are 3 different XSLT engines available by default in App
    Connect Enterprise version 12 when running with the default Java
    8.0 JRE. These are:
    Xylem - IBM's high performance xslt engine
    Xalan  (Compiled) - Open source XSLT engine
    Xalan (Interpreted) - Open Source XSLT Interpreter
    
    By default the Xylem engine should be used however after
    12.0.12.0 the Xalan engine was used.
    
    
    There may be some changes in behaviour between the 2 engines,
    particularly with respect to anonymous namespaces.
    
    Additionally there was an existing environment variable
    MQSI_XSLT_USE_XALAN_PROCESSOR which allowed the user to select
    the Xalan processor in preference to the Xylem one. This did not
    work correctly on all fixpack levels.
    
    This APAR will correct the default behaviour such that Xylem is
    the default processor when using Java 8.0 and Xalan (Compiled)
    is the default processor when using Java 11 on ACE version 12 or
    Java 17 on ACE version 13.
    
    It will also correct the behaviour of the
    MQSI_XSLT_USE_XALAN_PROCESSOR environment variable.
    
    Additionally this APAR will add the new environment variable
    MQSI_XSLT_OVERRIDE_ENGINE this env var allows the user to set a
    specific engine name from the following selection:
    
    
    Xylem
    
    Xalan
    Interpreter
    
    Note that the Xylem engine is not compatible with Java version
    11 or higher so this engine is not available when the ACE
    runtime is not running in Java 8.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise version 12 or higher
    using the XSLTransform Node
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    There are 3 different XSLT engines available by default in App
    Connect Enterprise version 12 when running with the Java
    8.0 JRE. These are:
    
    Xylem - IBM's high performance xslt engine
    Xalan  (Compiled) - Open source XSLT engine
    Xalan (Interpreted) - Open Source XSLT Interpreter
    
    By default the Xylem engine should be used however after
    12.0.12.0 the Xalan engine was used.
    
    There may be some changes in behaviour between the 2 engines,
    particularly with respect to anonymous namespaces.
    
    Additionally there was an existing environment variable
    MQSI_XSLT_USE_XALAN_PROCESSOR which allowed the user to select
     the Xalan processor in preference to the Xylem one. This did
    not work correctly on all fixpack levels.
    

Problem conclusion

  • This APAR will correct the default behaviour such that Xylem is
    the default processor when using Java 8.0 and Xalan (Compiled)
    is the default processor when using Java 11 on ACE version 12 or
    Java 17 on ACE version 13.
    
    It will also correct the behaviour of the
    MQSI_XSLT_USE_XALAN_PROCESSOR environment variable.
    
    Additionally this APAR will add the new environment variable
    MQSI_XSLT_OVERRIDE_ENGINE this env var allows the user to set a
    specific engine name from the following selection:
    
    
    Xylem
    
    Xalan
    Interpreter
    
    Note that the Xylem engine is not compatible with Java version
     11 or higher so this engine is not available when the ACE
    runtime is not running in Java 8.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v12.0      12.0.12.8
    v13.0      13.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

    IT47061

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0560

  • Reported release

    C00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-10-11

  • Closed date

    2024-10-25

  • Last modified date

    2024-10-25

  • 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

    5724J0560

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C00","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
25 October 2024