Modeled processes can function both as a server and a client in a web services interaction. Services and references are defined at the process level while the bindings are created at the component level.
The supported service classes are:
- REST (Representational State Transfer)-compliant services, where the primary purpose of the service is to manipulate XML representations of web resources using a uniform set of stateless operations. When using a stateless operation, the state is managed by the job itself instead of by the engine.
- SOAP services, which are used for exchanging information in the implementation of web services relying on XML message format sent over HTTP and JMS.
Web services are typically associated with the following characteristics:
- Interfaces that describe the operations available within a service. An interface is analogous to a port type in a WSDL file. Each interface can contain multiple operations.
- Operations define an action that can be performed by the service and the way the message is encoded.
- Transport used for communication such as HTTP or JMS.
- Schema used for message exchanges such as XSD.