Most of the IBM BPM projects solely depends on human services or coaches which leads to many of server performance issues and PMRs. And IBM took a smart move by introducing client side human service which takes out more than 50% the server load and pushing everything to client machine and browser. Server pushes all coaches in a single call to client browser and its browser’s responsibility to load the coaches in order, coach navigation and respond back to server after completion. Coach performance and rendering will vary based on end client machine configuration(Web browser version,CPU and RAM size).
This is a wonderful solution if you have high end browsers IE 9 or higher version and latest version of Chrome or Firefox. If you have IE 8 or lower version, client side human service is NOT for you.
Server side human service or Heritage Coaches,
Client and server interaction of heritage coach.
Client side human service,
System pushes all the coaches to client browser, once all coaches are completed and then browser pushed data back to server. It reduces no of server calls and let the high end browser’s to do the job for you.
There are few limitations, if you close the browser before reaching the end point then you may lose all the data. And we have an option to save the execution context upon each coach completion, but it will increase no of calls to server.
Combination of Client side and heritage coaches,
Combination with save execution context scenario,
This is a wonderful solution if you have high end browsers IE 9 or higher version and latest version of Chrome or Firefox. If you have IE 8 or lower version, client side human service is NOT for you.
Server side human service or Heritage Coaches,
Client and server interaction of heritage coach.
Client side human service,
System pushes all the coaches to client browser, once all coaches are completed and then browser pushed data back to server. It reduces no of server calls and let the high end browser’s to do the job for you.
There are few limitations, if you close the browser before reaching the end point then you may lose all the data. And we have an option to save the execution context upon each coach completion, but it will increase no of calls to server.
Combination of Client side and heritage coaches,
Combination with save execution context scenario,
