All editions of Business Integration Connect provide the ability to connect to back-end integration systems. Business Integration Connect - Express provides file-based integration, while Business Integration Connect Enterprise and Advanced Editions provide both file-based integration and integration over HTTP, HTTPS, and JMS transports.
Business Integration Connect is the entry point for messages and documents coming into the enterprise. Depending on the type of message, Business Integration Connect processes the message and passes it on to another product.
Where there is a need for a direct XML transformation of the content, WebSphere InterChange Server or WebSphere Business Integration Message Broker can be used to meet that need.
Where there is a need for a specific type of optimized transformation (EDI transformation), WebSphere Data Interchange can be used.
The following illustration shows how Business Integration Connect can be integrated with WebSphere InterChange Server.
Figure 5. Document flow through Business Integration Connect to InterChange Server
A document intended for the WebSphere InterChange Server can be sent from a community participant in an XML, EDI, RosettaNet, or binary format, and can be sent (after transformation, if necessary) through the HTTP or JMS transport protocol.
The following illustration shows how Business Integration Connect can be integrated with WebSphere Data Interchange.
Figure 6. Document flow through Business Integration Connect to WebSphere Data Interchange
An EDI document intended for WebSphere Data Interchange is sent through the JMS transport protocol. As shown in the illustration, WebSphere Data Interchange can interact with WebSphere InterChange Server or directly with an application. In a typical WebSphere Data Interchange installation, an EDI document can also be delivered directly from a Value Added Network (VAN) to WebSphere Data Interchange.
Integration with back-end systems is described in more detail in the Enterprise Integration Guide.