Chapter 3. Scenario overview and design 83
The Web Services Gateway provides the resiliency and interchangeability that is
required by the business and technology requirements mentioned in sections
“Business requirements” on page 69 and “Technology requirements” on page 70.
You can find details of the features that the Web Services Gateway provides at:
http://www-106.ibm.com/developerworks/webservices/library/ws-routing/
Also, refer to the IBM Redbook Patterns: Implementing an SOA Using An
Enterprise Service Bus, SG24-6346.
Now that you understand the major components of the system, we architect the
scenarios so that they can be established as components, allowing for reuse and
flexibility. The most important components are the logical components are the
EIS connectivity services. The J2C EIS component service connects to the CICS
and IMS systems, and the WebSphere Business Integration Adapter component
service allows for the quick plugable reuse of various adapters.
This architecture keeps the EIS features separate from the business process
functionality. In our scenario, and in the future, this architecture can be used to
adapt to a changing environment and business needs.
The technology used in the proof points, JMS to JCA to SOAP, are used to
achieve certain business requirements and to provide the functionality required
for a service-oriented solution.
3.4 System description
This section gives an overview of the systems that are involved in our scenario
and their components, including where the components can be located and the
role that they play in the system.
3.4.1 System overview
This section discusses briefly the overview of the system, its components, the
environment topology, and how they interact.