88 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
4.1 Development environment
To develop our proof of concept, we used the following products:
򐂰 WebSphere Studio Application Developer Integration Edition Version 5.1.1. It
supports the development of BPEL processes and JCA services.
򐂰 WebSphere Business Integration System Manager Version 4.2.2. It supports
the development of WebSphere Business Integration Adapter services.
򐂰 WebSphere Business Integration Modeler Version 5.1. It is the business
analyst tool to model the high-level process.
򐂰 Rational® XDE™ 2003 to support the requirement analysis and the design
phases.
4.2 CICS system and connectors
The Internet Trading system is composed of two nodes, the business integration
node and the back-end node, as shown in Figure 4-1. The EIS is a CICS
Transaction Server for z/OS Version 2.2.
The CICS Transaction Gateway is a set of client and server software
components that incorporate the facilities of the CICS Universal Client, which
allow a Java application to invoke services in a CICS region.
Figure 4-1 Software components of the Internet Trading system
The back-end node is a z/OS system where the following products are installed:
򐂰 CICS Version 2.2
򐂰 CICS Transaction Gateway Version 5.1

Get Managing Information Access to an Enterprise Information System Using J2EE and Services Oriented Architecture now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.