...
The Normalized Message Router (or NMR) receives message exchanges from JBI components and routes them to the appropriate component for processing. This decouples the service producers from consumers and enable additional processing.
Consumers and providers
| Section |
|---|
| Column |
|---|
JBI components (Service Engines and Binding Components) can act as a |
|
...
service consumer, a service provider or both. The diagram to the right outlines this using the example of a ServiceMix HTTP Consumer BC and a ServiceMix HTTP Provider BC. Notice where requests are intiated and the direction of the arrows to denote the flow from the intiator.
The provider makes a WSDL-described service available through an endpoint. This service implements a WSDL interface, which is a collection of operations.
The consumer can invoke the service by creating a message exchange that invoke a particular operation.
Consumers and providers only share the abstract service definition and are thus decoupled, as the consumer does not know the protocol and location of the invoked service.
Several services can implement the same WSDL interface so a consumer looking providers of an interface may find more than one endpoint |
| Column |
|---|
| Panel |
|---|
| borderColor | #ccc |
|---|
| bgColor | #ffffff |
|---|
| title | Consumers vs. Providers |
|---|
| borderStyle | solid |
|---|
|  Image Added
|
|
|
Normalized message
JBI uses the concept of a normalized message for interactions between consumers and providers.
A normalized message consists of three parts:
...
