IBM Support

JR51955: IF A BPD IS STARTED FROM A SERVICE IN A TOOLKIT, IT RETRIEVES INCORRECT VALUES FOR ENVIRONMENT VARIABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you develop a toolkit that defines an environment variable
    with a default value, the business process definition (BPD),
    which is also defined in that toolkit, uses the environment
    variable.
    For example, the same toolkit contains a service that starts
    this BPD by using the tw.system.startProcessByName() JavaScript
    API. The BPD that is started by the service is the same BPD that
    is defined in the toolkit.
    In addition, you define a process application that uses this
    toolkit. You activate or install this process application and
    override the value of the environment variable in the Process
    Admin Console.
    If you start the BPD from the toolkit directly, for example by
    using IBM Process Portal, the BPD retrieves the value of the
    environment variable that was specified in the Process Admin
    Console on process application level, as expected.
    If you start the service from the toolkit that in turn starts
    the BPD, the BPD retrieves the default value of the environment
    variable that was specified when the toolkit was modeled, which
    is incorrect behavior.
    

Local fix

Problem summary

  • When IBM BPM retrieves environment variables, it uses a
    versioning context to retrieve the correct version of the
    environment variable. The implementation of the
    tw.system.startProcessByName() API uses the current versioning
    context to start the BPD. In the error scenario, the current
    versioning context is the versioning context of the toolkit.
    Therefore, the BPD is started in the context of the toolkit and
    retrieves the environment variable value specified in the
    toolkit.
    

Problem conclusion

  • A fix is/will be available that uses the root versioning
    context, the versioning context of the process application, to
    start the BPD. This new approach allows the BPD to run in the
    context of the process application and to retrieve the values
    of the environment variables that were specified for the
    process application.
    
    Incorrect environment variable values might be retrieved in
    other scenarios. To avoid these problems, also install interim
    fixes JR47116, JR47937, JR49126, and JR50141.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR51955:
    
    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 JR51955, 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

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR51955

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-04

  • Closed date

    2015-01-15

  • Last modified date

    2015-01-15

  • 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

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"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:
15 January 2015