
Oracle SOA Suite 11g Performance Tuning Cookbook

There are a number of options available when choosing how your client code makes calls to the human workflow service. This recipe discusses some of the trade-offs between them.
The following guidelines are used when selecting a strategy for creating a client that interacts with the workflow service:
If an application is not implemented in Java, or connects over a WAN or a LAN, then using the SOAP client will be your only option.
If you are connecting using Java, either from within the same or from a remote JVM, then using the Remote EJB client will be the best option.
The workflow service can be accessed using one of three clients: the SOAP client, the remote EJB client, and the local EJB client. The SOAP client uses SOAP over HTTP as its access protocol, so it is perfect for situations where you are talking to a non-Java client, or where you need a protocol that will work through a firewall. The local EJB client can...