IBM Support

JR43463: DISCOVER WSDL ERROR IF USING ENVIRONMENT VARIABLE AS URI

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an environment variable was used by embedding JavaScript
    in the WSDL URI field, in some instances the variable would
    not resolve to its value, leaving the original environment
    variable in the field.  If the environment variable used was
    not a property of the "tw.env" object, the JavaScript being
    evaluated would not compile leading to an exception that was
    silently handled.
    

Local fix

  • remove PS Toolit from Process App
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, Standard and          *
    *                  Advanced.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an environment variable was used   *
    *                      by embedding JavaScript in the WSDL     *
    *                      URI field, in some instances the        *
    *                      variable would not resolve to its       *
    *                      value, leaving the original             *
    *                      environment variable in the field.      *
    *                      If the environment variable used was    *
    *                      not a property of the "tw.env"          *
    *                      object, the JavaScript being            *
    *                      evaluated would not compile leading     *
    *                      to an exception that was silently       *
    *                      handled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an environment variable was used by embedding JavaScript
    in the WSDL URI field, in some instances the variable would
    not resolve to its value, leaving the original environment
    variable in the field.  If the environment variable used was
    not a property of the "tw.env" object, the JavaScript being
    evaluated would not compile leading to an exception that was
    silently handled.
    

Problem conclusion

  • The solution for this issue results in the
    JavaScript successfully compiling, and the environment
    variable resolving to its value.
    
    Problem is fixed in interim fix and future fixpack/releases.
    Install/Dependency information is available in the readme.txt
    on FixCentral. When the user goes to the download files page
    in FixCentral, the readme will be available with the fix
    package as a separate download.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR43463

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-17

  • Closed date

    2012-10-02

  • Last modified date

    2012-10-02

  • 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 STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R750 PSY

       UP

  • R800 PSY

       UP

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

Document Information

Modified date:
12 October 2021