JR43362: PROCESSES STARTED BY THE REST API WITHOUT SPECIFYING SNAPSHOTID ARE NOT SHOWN IN PROCESS INSPECTOR

Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• BPD Instances are not shown in Process Inspector when the
  following method it used to start the BPD.
  
  The BPD is started via the POST (start) method of the
  /rest/bpm/wle/v1/process REST API and the optional snapshotId
  parameter is not set. If only the processAppId is set then the
  BPD is started for the default snapshot.
  
  The BPD instance is created with the TIP column of the
  LSW_BPD_INSTANCE table set to 'T' instead of 'F'. This causes
  the BPD to not be visible in the Process Inspector of the
  Process Designer. It could also lead to other issues since the
  BPD instance is incorrectly associated with the TIP.
  
  Here is an example of the REST API used to start the process:
  http://myServer:9080/rest/bpm/wle/v1/process/action=start
  &parts=header|data
  &bpdId=25.1fbaa86d-ea86-4517-bdb3-457ab075a4c2
  &processAppId=2066.796ee9c4-80ed-4181-93cd-ea3707091c14
  

Local fix

• Use snapshotID instead of processAppID when starting the BPD via
  the REST API
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, Standard and          *
  *                  Advanced.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Problem Description:                    *
  *                      A REST API may be used to start a       *
  *                      process using either the                *
  *                      processAppId, snapshotId, or both. ‚  
  *                      If the snapshotId is not specified,     *
  *                      and the process is being started in a   *
  *                      Process Server runtime instance (as     *
  *                      opposed to Process Center), then the    *
  *                      resulting process will not be           *
  *                      displayed from Process Inspector. ‚  
  *                      Here is an example of the REST API      *
  *                      used to start the process:              *
  *                      http://myServer:9080/rest/bpm/wle/v1/pr *
  *                      ocess/action=start&parts=header|data&bp *
  *                      dId=25.1fbaa86d-ea86-4517-bdb3-         *
  *                      457ab075                                *
  *                      a4c2&processAppId=2066.796ee9c4-80ed-   *
  *                      41                                      *
  *                      81-93cd-ea3707091c14&params={ ¢â‚¬ ¦}
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Problem Description:
  A REST API may be used to start a process using either the
  processAppId, snapshotId, or both. ‚   If the snapshotId is not
  specified, and the process is being started in a Process
  Server runtime instance (as opposed to Process Center), then
  the resulting process will not be displayed from Process
  Inspector. ‚   Here is an example of the REST API used to start
  the process:
  http://myServer:9080/rest/bpm/wle/v1/process/action=start&parts=
  header|data&bpdId=25.1fbaa86d-ea86-4517-bdb3-
  457ab075a4c2&proces
  sAppId=2066.796ee9c4-80ed-4181-93cd-ea3707091c14&params={ ¢â‚¬ ¦
  The problem occurs due to an error in the BPM runtime which
  caused the process to appear to be running in Process Center,
  instead of the Process Server runtime instance. ‚   As a result,
  the Inspector did not display the process when filtering on
  the server name and snapshotId number. ‚   The problem can be
  seen by examining the database table ‚   LSW_BPD_INSTANCE for th
  snapshotId. ‚   The processes that do not display in Inspector
  will have the value 'T' in the TIP column.
  Possible workaround: the problem can be avoided by specifying
  snapshotId instead of processAppId when starting the process
  with REST.
  

Problem conclusion

• The problem was fixed in APAR JR43362, available in fix central.
  It is also fixed in future fix packs and 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 seperate download.
  

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 ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP

• R800 PSY

     UP