IBM Support

JR47937: A REST API CALL TO START A SERVICE BEHAVES DIFFERENTLY IN PROCESS CENTER AND PROCESS SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A REST API call to start a service behaves differently in
    Process center and Process server
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the "start service"                *
    *                  (/rest/bpm/wle/v1/service?action=start)     *
    *                  REST API.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the "start service" REST API is    *
    *                      used within the Process Server          *
    *                      environment to start a service          *
    *                      contained within a toolkit, an          *
    *                      "Internal Server Error 500" could       *
    *                      occur if the snapshot name is not       *
    *                      specified as part of the service name.  *
    *                      When calling the "start service" REST   *
    *                      API, the service name can be            *
    *                      specified as                            *
    *                      "<project-shortname>@<service-name>"    *
    *                      or                                      *
    *                      "<project-shortname>@<service-          *
    *                      name>@<sn                               *
    *                      apshot-name>".   If the snapshot name   *
    *                      is omitted, then the REST API           *
    *                      implementation will use the default     *
    *                      snapshot associated with the project    *
    *                      (process app or toolkit).  But,         *
    *                      within the Process Server               *
    *                      environment, there is no concept of     *
    *                      "default snapshot" for a toolkit.       *
    *                      This concept is only applicable for a   *
    *                      Process Application.    So, when a      *
    *                      name like "MYTK@MyService" is used in   *
    *                      Process Server, the REST API            *
    *                      implementation is unable to determine   *
    *                      the correct snapshot and that results   *
    *                      in the Internal Server Error.           *
    ****************************************************************
    * RECOMMENDATION:  Yes. To avoid the problem, simply include   *
    *                  the snapshot name as part of the service    *
    *                  name (e.g. MyTK@MyService@Snap1).           *
    ****************************************************************
    "START SERVICE" REST API FAILS IN PROCESS SERVER WHEN USING A
    TOOLKIT.
    

Problem conclusion

  • This iFix includes a code change that will allow the REST API
    implementation to find the most recent snapshot in the event
    that the default snapshot cannot be found.
    
    Note that if a specific named snapshot is desired, you can
    simply include the snapshot name when specifying the
    service-name to the "start service" REST API.  For example,
    you could use something like "MYTK@MyService@Snap1" to ensure
    that MyService within snapshot Snap1 is used.
    
    An iFix on BPM v8.5 is available to download in Fix Central.
    Please reference to the README file of this iFix for
    installation instruction.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47937

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-27

  • Closed date

    2013-10-17

  • Last modified date

    2013-10-17

  • 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

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2013