The----of the SOA standard and the idea of JBI architecture

the----of the SOA standard and the idea of JBI architectureSOA has two sets of standards in the Java World: one is Sun's JBI (not recognized by BEA and IBM) and the other is the SCA and SDO standards introduced by companies such as IBM and BEA. JBI's focus on Java components only handles the integration of Java components. SCA implements the separation of business components and transport protocols, and can handle the integration of various platform components. SDO can freely read data from a variety of different data sources.   In addition, BPEL is essentially a language that integrates WebService services and can also be counted as part of an SOA. Here is a detailed introduction to JBI's architectural ideas. I. Knowledge of JBIThe JBI (Java Business integration) Chinese translation is a standard for the integration of Java components by Sun. The nature of JBI is a service bus idea. The goal of JBI is to create a running environment for the integration of various Java Component Services. ii. knowledge of JBI containersJBI is the idea that the implementation of JBI is the JBI container.   JBI containers are designed to compensate for deficiencies in existing Java EE containers.   The container type of the existing application server: Servlet container, EJB container, JMS container. There are not enough containers for existing application servers: a), each container has its own special transport protocol and cannot communicate with each other directly. For example: The servlet container can only accept the HTTP/SOAP transport protocol, the EJB container can only handle the RMI transport protocol, JMS can only handle the JMS transport protocol. b), is a pure service provider, not a service integrator. In other words, the service cannot be inherited between containers.   c), the invocation of the inter-container service requires writing client code. The JBI container integrates different types of services in a pluggable way, rather than implementing the integration of services by writing client code. third, the composition and structure of JBI container1. Architecture Diagram of JBI container
2. The three major parts of the JBI container: a), binding component (Bc:binding components): specifically used to receive a variety of different transport protocol requests, the principle is JBI implementation of a variety of different protocols binding components, binding components can be subdivided into receiving BC and send BC. The receiving BC is primarily responsible for sending requests and receiving responses, and sending BC is primarily used to invoke external services. b), service engine (Se:service Engines): This type of component only handles messages inside the JBI container. A JBI container typically receives a message, requires some "processing" of the requested message, and then invokes the provider of the external service. Depending on the functionality, the SE components are divided into the following three types: Transform SE: specialized in handling various transport protocols and format changes. BPEL SE: is specifically responsible for the process orchestration of Web service. Rules SE: is specifically responsible for integrating various services through a rule. c), JBI's normalized message router (normalized message Router): Is the core of the JBI internal messaging system, where no messages can be exchanged between all the components, but only through NMR. Inside the JBI container, there is only one standard normalized message (normalized messages). Before the task service component enters the JBI environment, the BC is converted to the specification message nm. In a JBI environment, none of the services can be called to each other, either for a request or for a response, to be forwarded to the NMR before being distributed by the NMR. The components (SE, BC) and NMR in the JBI runtime environment are exchanged for information via NM. iv. Conceptual diagram of JBI container work
As shown above:
The external requestor sends an HTTP request to the JBI container, the container's HTTP BC receives the request and formats the requested message as NM to the message receiving transformation engine, and then sends NM to the NMR, which is then sent by the NMR to the SOAP Bc,soap BC converts NM to a SOAP message sent to the external WS component. After execution, the message is returned in the original way.
   ----------------------personal point of view: Jbi is the Sun's standard, and Sun's improvements to the Java EE container, Sun does not want to be compatible with components in other languages. With Sun's takeover, several giants outside Sun Du Li The SCA Standard, and Sun's JBI standard will be in its own, hard to reuse. Understanding the workings of the container provides a clearer understanding of the principles and processes of JBI integration Services. If only for learning development, container standards to understand the next, you should study more about the JBI standard API interface and specifications.