The Service Palette
A service implements one or more interfaces and exposes one or more endpoints per interface. In web service terminology, the interface would be a PortType in a WSDL 1.1 file. The endpoint would be referred to as a port. However, the term endpoint does not imply a physical network address where the service is listening. Services provide an abstraction of web services so that you can implement a more generic service-oriented architecture (SOA) that is not dependent upon a specific transport or implementation. The Service palette contains resources that allow you to define services.
Services decouple the underlying transport from the implementation. You can define an interface you wish to offer, describe the endpoints through which clients can access the service, and specify the implementation for each operation in the service.
In this release of ActiveMatrix BusinessWorks, each service can implement any number of interfaces. The endpoints available are SOAP over HTTP, SOAP over JMS and Local.
For example, you may wish to offer a bidding service that implements a Buyer interface. The interface is exposed on the SOAP over HTTP endpoint. The operations contained in the Buyer interface are Bid, Retract, and Raise.
See
for a detailed description of the resources in the Service palette.The following figure illustrates the service model.
Service model
A service joins an abstract WSDL interface to concrete implementations and exposes them on one or more endpoints. A web service client invokes one of the abstract interface operations using configuration settings provided by the service in the form of concrete WSDL bindings.