JR44597: BPD INSTANCES STARTED VIA A SERVICE INITIATED BY THE REST SERVICES APIS CANNOT BE SEEN IN PROCESS INSPECTOR

7.5.1.2-WS-BPM-IFJR44597

APAR status

• Closed as program error.

Error description

• BPD instances cannot be viewed in Process Inspector after being
  started in a manner similar to the following.
  
  A BPD is started via a service which uses the startBpdWithName
  JavaScript API to start the BPD. The service is started via the
  REST APIs using the POST (start) method of
  /rest/bpm/wle/v1/service/.
  
  When the BPD is started one of the TIP columns from the
  LSW_BPD_INSTANCE table is incorrectly set to 'T' instead of 'F'.
  This prevents the BPDs from being viewed in the Process
  Inspector section of Process Designer, unless the related
  snapshot is the tip of the process.
  
  This issue is also similar to that in APAR JR43362.
  

Local fix

• In the LSW_BPD_INSTANCE table, set the TIP column to 'F' for
  BPD instances which are not related to the process tip.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
  *                  Advanced.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: BPD instances cannot be viewed in       *
  *                      Process Inspector after being started   *
  *                      in a manner similar to the following.   *
  *                      A BPD is started via a service which    *
  *                      uses the startBpdWithName JavaScript    *
  *                      API to start the BPD. The service is    *
  *                      started via the REST APIs using the     *
  *                      POST (start) method of                  *
  *                      /rest/bpm/wle/v1/service/.              *
  *                      When the BPD is started one of the      *
  *                      TIP columns from the LSW_BPD_INSTANCE   *
  *                      table is incorrectly set to 'T'         *
  *                      instead of 'F'. This prevents the BPDs  *
  *                      from being viewed in the Process        *
  *                      Inspector section of Process            *
  *                      Designer, unless the related snapshot   *
  *                      is the tip of the process.              *
  *                      This issue is also similar to that in   *
  *                      APAR JR43362.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Launching a BPD by specifying its name results in the BPD at
  the tip of the branch for the default snapshot being started,
  regardless of whether Process Center or Process Server is
  being used. ‚   Since "tip" is not a concept supported by
  Process Server, a Process Designer user would not see the
  launched BPD in the Process Inspector.
  

Problem conclusion

• A check for the type of environment (Process Center or
  Process Server) was added to the code.  For Process Center,
  the BPD at the tip of the branch of the default snapshot will
  be started, while for Process Server, the BPD of the default
  snapshot will be started.
  
  An interim fix for Business Process Manager Version 8.0.0.0 has
  been published to Fix Central.  Please refer to the separate
  file that is automatically downloaded with the interim fix
  for prerequisite information and installation/uninstallation
  instructions.
  

Temporary fix

Comments

APAR Information

• 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

• R800 PSY

     UP