 |  |  |  |  |
| | | | |
 |  |
The FUSE Services Framework binding component provides connectivity to external endpoints using either SOAP/HTTP or SOAP/JMS. The endpoints are defined using WSDl files that contain FUSE Services Framework specific extensions for defining the transport. In addition, you can add FUSE Services Framework-based Spring configuration to use the advanced features.
It allows for the creation of two types of endpoint:
A consumer endpoint listens for messages on a specified address. When it receives a message it sends it to the NMR for delivery to the appropriate endpoint. If the message is part of a two-way exchange, then the consumer endpoint is also responsible for returning the response to the external endpoint.
For information about configuring consumer endpoints see Consumer Endpoints.
A provider endpoint receives messages from the NMR. It then packages the message as a SOAP message and sends it to the specified external address. If the message is part of a two-way message exchange, the provider endpoint waits for the response from the external endpoint. The provider endpoint will then direct the response back to the NMR.
For information about configuring provider endpoints see Provider Endpoints.
The FUSE Services Framework binding component has the following features:
HTTP support
JMS 1.1 support
SOAP 1.1 support
SOAP 1.2 support
MTOM support
Support for all MEPs as consumers or providers
SSL support
WS-Security support
WS-Policy support
WS-RM support
WS-Addressing support
Using the FUSE Services Framework binding component to expose SOAP endpoints usually involves the following steps:
Defining the contract for your endpoint in WSDL.
Configuring the endpoint and packaging it into a service unit.
Bundling the service unit into a service assembly for deployment into the FUSE ESB container.
For more information about using FUSE Services Framework to create SOAP endpoints see the FUSE Services Framework library..
| | | |
 |
