Database Reference
In-Depth Information
The Enterprise Business Services framework
Business services with high throughput demands, participating in quick running composi-
tions are naturally interconnected in the Enterprise Business Services ( EBS ) framework.
Let's not get confused by the naming. The GF05: ESB framework in itself provides tools
and methods to address the required functionalities, which are listed as follows in terms of
implementation techniques and required functionalities:
• Implementation technique:
◦ Service Broker as composition controller
◦ Mediators
◦ Asynchronous message queues
• Required functionality:
◦ Atomic Transaction Coordinator implementation.
◦ WS-RM support (versions, implementations, and extensions).
◦ WS-Addressing support (versions, implementations, and extensions).
◦ Native WS-Coordination support (versions, implementations, and exten-
sions).
◦ Supported transport protocols.
◦ Supported messaging protocols.
◦ Supported protocol's sync-async bridging.
◦ Supported MEPS (for WSDL1.1 - 4; for WSDL 2.0-8).
◦ Concurrent Contract support (contact versioning, by proxy or by other
means, such as agents/facades).
◦ Supported adapters (including JCA).
◦ Process pipes orchestration: looping, branching, termination, and service
chaining.
◦ Basic security support: encryption, digital signature, and authorization/
authentication.
◦ Types of data model transformation (XQuery, XSLT).
◦ Types of message objects transformation ( XSD<->JSON , and so on.).
◦ Content based routing, dynamic rule-based routing.
◦ Types of message validation (complete, partial, nodes, security screening
by regular expression/pattern, and so on).
◦ Federated heterogeneous ESB support (native links to other vendors us-
ing the WS-* standard), such as coexistence with Mule or GlassfishESB
(ESB grids, snowflakes).
◦ WS-Policy, WS-SecurityPolicy, WS-PolicyAttachment support.
Search WWH ::




Custom Search