How Coaches of 8.0 are different from Coaches of previous versions ?

Coach in IBM BPM 8.0 is a improvement of Coach in previous versions which is now called as heritage coach. A concept of Coach view is introduced in 8.0, which makes it possible to reuse parts of coaches in different Human Services. A coach can consits of one or more Coach Views. Another Big difference in Coach of 8.0 is introduciton of client-side model to coaches to apply Web2.0 appearance and behaviour. The Coach has data on the client, which is available to all of the Coach Views. That is, fields in different Coach Views that are bound to the same data object update without requiring a full-page refresh.

Instead of the one-button mechanism of Heritage Coaches, Coach Views use named boundary events. Programmers use boundary events for actions such as data updates with the server and transitions to other Coaches or services. For example, a Coach can have multiple buttons. In the human service diagram, you can wire each button to a different event. Any Coach View can declare and fire a boundary event. You are not limited to using only buttons to do so although, of the stock controls, only the button stock control can fire a boundary event. Furthermore, the programming for Coach Views consists entirely of client-side JavaScript. There is no need for server-side JavaScript.

Coaches support collaboration while Heritage Coaches do not. More than one person can work on the

Invoking IBM BPM Service using REST API from an external system (java system)

In this post, I would like demonstrate how to invoke a Lombardi service using via rest API, and how to pass the inputs and get back outputs. Let’s just pass two numbers (‘a’ and ‘b’) as input parametersand get back sum of these two numbers as the output parameter ‘sum’.

First of all let us know the restrictions on the services which can be invoked using REST API, you can very well find this on IBM BPM rest API documentation. Just for reference, only a human service or AJX service can be invoked using REST API URL.

In order to overcome the restriction on length of the URL which can become large because of the query parameters, the rest URL which will be used for invoking a Lombardi service is provided with POST method call.

Below shown is the format of the URL: