See information about the latest product version
Services
A Service in WebSphere® Message Broker is a specialized application with a well-defined interface and structure, and implementation flows for each service operation.
An application is a container for all the resources that are required to create a solution. A Service is a container for a Web Services solution, and has a defined interface with specified operations that you implement as separate message subflows.
You can create the service interface from scratch or based on existing WSDL by using the New Service wizard. You then implement the operations as subflows by using the Service editor.
When you implement the service, you can deploy it to an execution group. You can start and stop the deployed service as you would an application. A web service consumer can interrogate the deployed service to return its interface.
Although the schemas in a library can be shared across services, you cannot put a schema that defines the service interface in a library and use it across services.
The New Service wizard and Service editor support SOAP services with an HTTP binding.
To start working with Services, see Developing a service.
Interfaces
An interface consists of one or more operations and a binding style.
An operation is a description of an action that is implemented by the service. An operation may be a request-response type, meaning that a request is sent and a response returned to the interface, or a one-way type, meaning that only a request is sent and no response is needed. Each operation in the interface defines the data that can be passed in the form of inputs to and outputs from the component when the operation is invoked. A one-way operation has only an input. Each operation may have one or more faults to handle error conditions.
The binding style specifies the protocol and data format of the operation.