Client Applications

Client applications can communicate with AgilePoint BPMS Engine in different ways via HTTP/WebDav (Web Services), Remoting, WCF, Messaging (JMS/MSMQ) which provides flexibility in fine tuning performance needs. AgilePoint also supports client applications to run in their native environments and communicate with the BPMS Engine. This offers users great flexibility in scenarios such as front end Java Web Applications running on their enterprise hardware and software finely tuned to handle heavy volume retaining their efficiency while interacting with the BPMS Engine.

We recommend the following guidelines for client applications interacting with AgilePoint Server.

• Web Service - We recommend this as the default option for client applications communicating with AgilePoint as it is the de facto standard of the SOA paradigm.

• MSMQ/JMS - We recommend this approach in scenarios where client applications want to interact in loosely coupled mode via messages. Also they want messages to be delivered in persistence mode.

• .NET Remoting - We recommend this approach in scenarios where integrated applications want to have high performance data transferring between AgilePoint Server and Client Applications.