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

Chapter 1. Introduction to this book 5

also benefit from these chapters because they present an overview of the

architectural challenges, concepts, vision, and objectives that influenced the

architecture for our EIS integration scenarios.

Part 2, “Development example” on page 93 implements an EIS integration

solution, using J2EE, Web services, J2C connectors, JMS, and BPEL processes

into a real-world EIS running IMS™ and CICS and Cobol transactions. This part

of the book is for designers and developers who want to see how the architecture

was implemented using technologies and development tool sets, such as

WebSphere Studio Application Developer Integration Edition.

1.2 What we do in this book

In this redbook, we modelled our EIS integration architecture and design from the

use cases of a fictitious stock trading firm that is called ITSO Trading Firm. The

ITSO Trading Firm must integrate with various back-end EIS systems to

successfully processes its business processes. We focussed on architecture for

the ITSO Trading Firm’s EIS integration requirements, using standard

technologies such as J2EE, JMS, Web services, and J2C. (See 2.3, “Key

technologies” on page 58 for descriptions of some of the key technologies that

we used in our EIS integration architecture.)

Proof points for our EIS integration solution were:

򐂰 EIS integration using J2C connectors

– CICS connector

– IMS connector

򐂰 EIS integration to a remote EIS

– Creating an EIS integration adapter using JMS that uses the J2C

connector for EIS integration.

– Using Web services to access an external EIS

򐂰 Using BPEL processes

– Creating processes using WebSphere Studio Application Developer

Integration Edition

– Running BPEL processes in Business Process Choreographer

򐂰 Transaction management

– Managing a unit of work across activities in a BPEL process

– Performing compensation on a BPEL activity