4 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
1.1 Who should read this book
Integrating to an EIS is not a trivial exercise. You probably have come to
appreciate the complexity of this process if you have gone through similar
exercises in your organization. Most organizations have enterprise architectures,
including principles, frameworks, and components for their EIS integrations.
Whether these architectures are actually used across the enterprise by the
different development channels or development teams is another debate.
However, the real challenge is whether your organization or channel EIS
integration methodologies are working for or against you.
For example, ask yourself these questions about your EIS integration
architecture:
???? Is it easy to maintain?
???? Is it developer friendly?
???? Is it a disciplined development environment?
???? Does it perform fast?
???? Does it abstract your EIS integration from your business processes?
???? Can you add new connectors?
???? Can you change from a CICS® or COBOL transaction to a JDBC-stored
procedure without affecting the business process?
???? Can your business processes invoke an EIS transaction and be totally
agnostic as to where the EIS is located?
???? Can your business processes invoke an EIS transaction and be agnostic to
any connector that is used for the integration?
???? How are your business processes or applications affected when you change
a back-end transaction? Does it require extensive re-factoring to your
processes and/or applications?
???? Do you have questions on which technologies you can or should use for your
EIS integration (for example, J2C connectors, JDBC, JMS, Web services,
BPEL processes, and so on). Importantly, what is the right fit for your
organization?
If any of these questions relate to your situation and the challenges that you face
in your environment then the information in this book will be helpful to you.
Architects, designers, and developers of all skills will benefit by reading some of
the chapters in this book. Part 1, “Scenario introduction” on page 1 covers the
architecture, business scenario, design, and environment. Architects and
designers should read all of the chapters in this part of the book. Developers can
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.