Managing Information Access to an Enterprise Information System Using J2EE and Services Oriented Architecture

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.

84 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture

Figure 3-15 shows the overall system.

Figure 3-15 System Overview

The system that encompasses the total scenario involves two internal systems

and one external system for the Buy Shares scenario.

The internal systems incorporate both the Internet Trading System and the

business process for ITSO Trading Firm. These processes involve two J2EE

applications that run on WebSphere Business Integration Server Foundation,

one functioning as the main business process for the Internet Trading System

and the other for the Stock Broker. The Stock Broker is in a remote location on

the WAN.

The internal business process also communicates with a CICS system that has

some trader information that the system uses to process incoming requests. This

CICS system is hosted on a z/OS® operating environment.

Internet Trading System

Cluster

WebSphere Business Integration

Server Foundation

Client

Web Application

Order

WebSephere Business Integration

Server Foundation

Stock Broker

M

Q

M

Q

IMS

JCA

JMS

JMS

CICS

Trading Process

Trader CICS

Process

CICS

JCA

z/OS System

CTG

Analysis

Stock Analysis

Repository

EIS

EIS System

Adapter

WBI

Adapter

M

Q

WebSephere Business Integration

Server Foundation

Chapter 3. Scenario overview and design 85

The external system is exposed via a Web service that retrieves stock analysis

and quote information from a repository stored in a relational database. The

information is retrieved from the database using the WebSphere Business

Integration Adapter for JDBC. The service link between the adapter and the

business process is done through JMS calls to the adapter framework. The

external adapter service and stock quote service is running in an instance of the

WebSphere Business Integration Server Foundation application server.

For more information about the configuration, deployment, and domain structure

see Chapter 4, “Environment” on page 87 and the chapters in Part 2,

“Development example” on page 93

86 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture