6 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
???? Security
– Securing the EIS integration
???? Using J2EE
???? Using the WebSphere Business Integration adapter framework in WebSphere
Business Integration Server Foundation to connect and to run transactions
against a database
With the focus on EIS integration using J2EE, SOA, and Web services, we
created an architecture for our EIS integration. Using this architecture, we then
designed and implemented our EIS integration services, processes, and
components.
1.3 How to use this book
This redbook consists of two parts.
Part 1, “Scenario introduction” on page 1 covers the following:
???? The architecture of our EIS integration in Chapter 2, “Architecture” on page 9
???? The business scenarios and design of the EIS integration architecture in
Chapter 3, “Scenario overview and design” on page 65
???? The environment setup in Chapter 4, “Environment” on page 87
Part 2, “Development example” on page 93 provides details about our
implementation of the EIS integration design. (See 2.3, “Key technologies” on
page 58 for descriptions about some of the key technologies that we used in the
EIS integration architecture.) We implemented Web services, BPEL processes,
and components.
If you have an immediate technology or implementation question, you can begin
with Part 2, “Development example” on page 93. Here, you can find the
implementations of the services, processes, and components, and you can read
about how we used the J2C connectors to connect to the back-end EIS system.
However, to get the greatest benefit from this redbook, you should first read
Part 1, “Scenario introduction” on page 1. Reading though this first part of the
book will give you a clear view of what we set out to build and how we built it. The
Note: This redbook does not discuss EAI using WebSphere Business
Integration for integration of data, applications, or processes. Instead, it
focusses on integrating to a back-end EIS, using J2EE, J2C, JMS, and Web
services.