J2EE? Connector Architecture and Enterprise Application Integration

by ; ;
Edition: 1st
Format: Paperback
Pub. Date: 2001-12-14
Publisher(s): Addison-Wesley Professional
  • Free Shipping Icon

    This Item Qualifies for Free Shipping!*

    *Excludes marketplace orders.

List Price: $41.99

Buy New

Arriving Soon. Will ship when available.
$39.99

Rent Textbook

Select for Price
There was a problem. Please try again later.

Used Textbook

We're Sorry
Sold Out

eTextbook

We're Sorry
Not Available

How Marketplace Works:

  • This item is offered by an independent seller and not shipped from our warehouse
  • Item details like edition and cover design may differ from our description; see seller's comments before ordering.
  • Sellers much confirm and ship within two business days; otherwise, the order will be cancelled and refunded.
  • Marketplace purchases cannot be returned to eCampus.com. Contact the seller directly for inquiries; if no response within two days, contact customer service.
  • Additional shipping costs apply to Marketplace purchases. Review shipping costs at checkout.

Summary

The Javatrade; 2 Enterprise Edition (J2EE) platform connector architecture is the key component in Java's support for enterprise application integration (EAI) and for linking enterprise information systems (EISs) with Web services. Because many services are now provided through the Web, it is essential that business enterprises have an efficient EAI solution. J2EEtrade; Connector Architecture and Enterprise Application Integration is the definitive guide to showing enterprise organizations how to incorporate existing enterprise infrastructure and applications, taking them into the Web-enabled economy of the future.Written for application component developers who are building Connector architecture applications, J2EEtrade; Connector Architecture and Enterprise Application Integration explains how to connect applications not only to one another but also to a multitude of EISs and legacy systems. This book is also of interest to independent software developers (ISVs) and others who develop resource adapters for specific EISs. Readers will learn how to link underlying infrastructure products with J2EE application server and platform technologies. 0201775808B11052001

Author Biography

Rahul Sharma is the lead architect of the J2EE Connector architecture and a Senior Staff Engineer at the Java Software division of Sun Microsystems, Inc. Presently, he is the lead architect of the JAX-RPC (Java APIs for XML based RPC) 1.0. Rahul has been with Sun for the last five years. Rahul holds a computer engineering degree from the Delhi University, India, and an MBA from the Haas School of Business, UC Berkeley.

Beth Stearns is the principal partner of ComputerEase Publishing, a computer consulting firm she founded in 1982. Among her publications are Java Native Interface in The Java Tutorial Continued (Addison-Wesley), “The EJB Programming Guide” for Inprise Corporation, and “ Understanding EDT, ” a guide to Digital Equipment Corporation's text editor.

Tony Ng is a Staff Engineer with Sun Microsystems. He is currently the project lead of the J2EE SDK and Reference Implementation. He has designed and implemented a number of Java technologies, including the J2EE Connector Architecture, the Java Transaction Service, and the J2EE Blueprints. Tony has a B.S. degree in Computer Science from the University of Illinois, Urbana-Champaign, and a S.M. degree in Electrical Engineering and Computer Science from Massachusetts Institute of Technology.



0201775808AB09232002

Table of Contents

Foreword xv
Preface xix
Acknowledgments xxvii
Enterprise Application Integration
1(24)
What is Enterprise Application Integration?
2(2)
Web-driven Application Integration
4(2)
Enterprise Information Systems
6(3)
Challenges in EIS Integration
9(2)
Enterprise Application Integration Approaches
11(9)
Two-Tier Client-Server Approach
11(2)
Using Synchronous Adapters
13(1)
Using Asynchronous Adapters
14(1)
Queue-Based Approach
15(1)
Publish-Subscribe Approach
15(3)
Application Server-Based Integration
18(2)
J2EE Connector Architecture and EAI
20(2)
Conclusion
22(3)
J2EE Connector Architecture Overview
25(20)
What is the J2EE Platform?
25(5)
Components and Containers
27(1)
J2EE Technologies
28(2)
J2EE Connector Architecture Overview
30(6)
Connector Architecture Contracts
31(1)
System-Level Contracts
31(3)
Application Contract
34(1)
Packaging and Deployment
34(1)
Why Use the Connector Architecture?
34(2)
Example Scenario
36(6)
Application Requirements
37(1)
Example Architecture
38(4)
Conclusion
42(3)
Managing Connections
45(8)
Connection Management Contract
47(1)
Connection Management Architecture
47(3)
Application Programming Model
50(2)
Conclusion
52(1)
Working with Transactions
53(16)
Introduction to Transactions
54(4)
Characteristics of Transactions
55(1)
Commit Protocols
56(1)
Key Issues with Transactions
57(1)
Developing Transactional Applications
58(5)
Using the J2EE Platform
58(1)
Using Enterprise Beans
59(1)
Using JTA Transactions
60(2)
Compensating Transactions
62(1)
Transaction Levels
63(1)
Sample Application Transaction Scenario
63(4)
Conclusion
67(2)
Managing Security
69(16)
Security Concepts
70(3)
Authentication
70(1)
Authorization
71(1)
Security Definitions
72(1)
Security Model for EIS Connections
73(2)
Container-Managed Sign-On
73(1)
Component-Managed Sign-On
74(1)
Understanding EIS Sign-On
75(2)
Setting a Resource Principal
75(1)
Authenticating a Resource Principal
76(1)
Authorizing a Resource Principal
76(1)
Establishing a Secure Communication
77(1)
Managing Security
77(2)
Role of the Application Component Provider
78(1)
Role of the Deployer
78(1)
Role of the Application Server Vendor
78(1)
Other Roles
79(1)
Security Example
79(3)
Security Environment
80(1)
Example Deployment
81(1)
Conclusion
82(3)
Asynchronous Messaging
85(26)
Synchronous Communication
85(3)
Issues to Consider
87(1)
Dependency on Specific Middleware Mechanisms
87(1)
Dependency Between EIS and Application
88(1)
Asynchronous Communication
88(1)
Connector Architecture 2.0 Message Handling
89(3)
Asynchronous Inbound Communication
90(1)
Asynchronous Outbound Communication
91(1)
Synchronous Inbound Communication
91(1)
JMS-based Communication
92(1)
Communication Trade-offs
92(2)
Enterprise Messaging Technologies
94(1)
Java Message Service
95(6)
JMS Overview
96(1)
JMS Interfaces
97(4)
JMS and EAI
101(1)
J2EE Platform and EAI
102(2)
Message-driven Bean
104(1)
Example
105(4)
Conclusion
109(2)
Common Client Interface
111(24)
Overview of the CCI
112(2)
CCI Programming Example
114(4)
Connection Interfaces
118(4)
ConnectionFactory Interface
118(1)
ConnectionSpec Interface
119(1)
Connection Interface
120(1)
Local Transaction Interface
121(1)
Interaction Interfaces
122(3)
Interaction Interface
122(1)
InteractionSpec Interface
123(2)
Data Representation Interfaces
125(2)
Metadata Interfaces
127(2)
Exception Interfaces
129(1)
Code Examples
129(5)
Obtaining a Connection
129(1)
Using an InteractionSpec Object
130(1)
Using a Generic Record
130(1)
Using a ResultSet
131(2)
Using a Custom Record
133(1)
Conclusion
134(1)
Tools and Frameworks
135(16)
Types of Tools
136(1)
Connector Architecture Tools Support
137(1)
EIS Access Objects
138(9)
Command Bean
140(2)
Record
142(3)
Data Access Object
145(2)
Guidelines for Access Objects
147(1)
EJB 2.0 Container-Managed Persistence
148(2)
Conclusion
150(1)
XML and the Connector Architecture
151(18)
Enterprise Application Integration and XML
151(2)
Overview of XML Concepts
153(1)
Defining Document Types and Formats
154(1)
Java Technologies Supporting XML
155(6)
Java API for XML Processing (JAXP)
156(4)
Java Architecture for XML Binding (JAXB)
160(1)
Java API for XML Messaging (JAXM)
160(1)
Java API for XML-based RPC (JAX-RPC)
160(1)
Java API for XML Registries (JAXR)
161(1)
XML and Connector Architecture
161(5)
XML and Connector Scenario
162(1)
Example Application Processing
162(4)
XML Support in Connector Architecture
166(1)
Conclusion
167(2)
Building a Resource Adapter
169(20)
Implementing a Resource Adapter
169(3)
Client API
171(1)
Transaction Support Level
171(1)
Authentication Mechanism
171(1)
Reauthentication Support
172(1)
System Contract Interfaces
172(7)
Implementing Connection Management
172(3)
Connection Factory
175(1)
Managed Connection Factory
176(1)
ConnectionManager
177(1)
ManagedConnection
177(2)
Connection Handle
179(1)
Managing Transactions
179(1)
Using Local Transactions
179(1)
Handling XAResource Transactions
180(1)
Implementing Security Management
180(2)
Container-Managed Sign-on
181(1)
Application-Managed Sign-on
181(1)
Using the ConnectionRequestInfo Interface
181(1)
Handling Connection Events
182(1)
Distributing a Resource Adapter
183(3)
Packaging a Resource Adapter
183(1)
Resource Adapter Deployment Descriptor
184(2)
Using an Adapter in the Runtime Environment
186(1)
Conclusion
187(2)
Resource Adapter Packaging and Deployment
189(14)
Deployment Approaches
191(1)
Standalone Deployment
191(1)
Bundled Deployment
191(1)
Packaging a Resource Adapter
192(3)
Deployment and Configuration
195(1)
Connection Factory Creation
196(1)
Using Packaging and Deployment Tools
196(5)
Conclusion
201(2)
Connection Management Contract
203(22)
Connection Management Contract
203(1)
Contract Overview
204(1)
Scenarios
205(12)
Creating New Connections
206(4)
Matching Existing Connections
210(2)
Handling Connection Events
212(2)
Nonmanaged Environment
214(3)
Connection Management Classes and Interfaces
217(6)
ConnectionFactory and Connection Interfaces
217(1)
Connection Management Contract
218(5)
Support for Error Handling
223(1)
Conclusion
223(2)
Transaction Management Contract
225(20)
Transaction Management Contract
226(2)
Local Transaction Management
228(4)
Example Local Transaction
229(1)
Local Transaction Management Contract Interfaces
230(2)
XAResource Transaction Management
232(4)
XAResource Interface
233(1)
Java Transaction API (JTA)
234(1)
Two-Phase Commit Protocol
235(1)
Requirements for Transaction Management Contract
236(1)
Connection Sharing
237(2)
Transaction Scenarios
239(3)
Transaction Setup
239(2)
Transaction Cleanup
241(1)
Conclusion
242(3)
Security Management Contract
245(10)
Interfaces and Classes
246(4)
Subject Class
246(1)
Principal Interface
247(1)
PasswordCredential
247(1)
GenericCredential Interface
248(1)
ManagedConnectionFactory Interface
249(1)
Security Management Contract
250(3)
Resource Adapter to Application Server Contract
250(2)
Application Server to Resource Adapter Contract
252(1)
Conclusion
253(2)
Future Directions
255(6)
Connector Architecture 2.0
255(3)
Asynchronous Resource Adapter Support
256(1)
Java Message Service Provider Pluggability
257(1)
XML Support in Common Client Interface
257(1)
Common Client Interface Metadata Support
258(1)
J2EE and EAI
258(1)
Conclusion
259(2)
The SAP Connector
261(14)
Architecture of SAP Systems
262(2)
SAP's Remote Function Call
263(1)
The Java Connector (JCO)
264(1)
Architecture of the SAP Connector
264(4)
Connection Management of the SAP Connector
265(1)
Transaction Management of the SAP Connector
266(1)
Security Management of the SAP Connector
266(1)
The Common Client Interface of the SAP Connector
267(1)
Example
268(7)
Package and Class Declaration
269(1)
Member Variables
269(1)
Getting the Bank List
270(1)
Creating a New Bank
271(4)
Developing Applications with JCA-based Tools
275(22)
Enterprise Access Builder (EAB) 101
276(1)
JCA Application Development Process
277(16)
Overview of the Application
278(1)
Using the EAB Session Bean Tool
279(3)
Using the Session Bean Editor
282(1)
Testing the Application in the WebSphere Test Environment
282(3)
Moving Your Application to the WebSphere Application Server
285(1)
Deploying the RAR File
285(2)
Specifying the Connection Pooling Properties
287(2)
Assembling and Deploying the Application onto the WebSphere Application Server
289(1)
Using the Deployed Application
290(1)
Accessing Session Beans as Web Services
291(2)
Future Directions
293(1)
Conclusion
294(3)
Connectors in VisualAge for Java, Enterprise Edition, Version 4.0
294(1)
References
295(2)
Embracing the J2EE Connector Architecture: The BEA WebLogic Experience
297(18)
WebLogic Server's Implementation of the J2EE Connector Architecture Specification
298(7)
WebLogic Server Supplementary Deployment Descriptor
298(3)
Extended Connection Pool Services
301(1)
Example web logic-ra.xml Deployment Descriptor
302(2)
Deployment Descriptor Editor
304(1)
Monitoring a Resource Adapter in the WebLogic Server Environment
304(1)
WebLogic Integration 2.0
305(7)
Application Views
307(1)
Adapter Development Kit (ADK)
308(4)
BEA Partners Adopting the J2EE Connector Architecture
312(3)
Reference
313(2)
Appendix A: API Reference 315(50)
Glossary 365(8)
Index 373

Excerpts

This book provides an in-depth coverage of the Java 2, Enterprise Edition (J2EE) platform Connector architecture. The Connector architecture is an integral part of the J2EE platform, and, as a key component in the platform's support for application integration, it ensures that J2EE applications can connect to and use a multitude of EISs and legacy systems. The Connector architecture, because it defines a standard set of contracts for handling connections, transactions, and security, makes it easier for vendors to develop products that can hook into the J2EE platform. Vendors follow the guidelines of these Connector contracts to develop special software modules, called resource adapters, that enable this linkage between their underlying products and the J2EE platform.This book is written for application component developers who are building applications that run on the J2EE platform. It is also of interest to independent software vendors (ISVs) and others who develop resource adapters for specific EISs, such as legacy and database systems. Conventions Used in This BookThis book uses certain graphical conventions.The graphical conventions used here are based on the Unified Modeling Language (UML) standard. UML is a modeling language for object-oriented development. In general, object-oriented modeling decomposes systems into collaborating objects. The resulting model captures the underlying semantics of a problem. UML defines different models for representing systems, and graphical diagrams to depict these models, including a class model, a state model, a use case model, an interaction model, an implementation model, and a deployment model.We only use a subset of the UML diagrams in this book. The diagrams of most interest to readers are the class diagrams, which depict static structure, and sequence, object, and collaboration diagrams, which depict dynamic object interactions.Note that we use the terms application server, server, and J2EE application server interchangeably. Unless otherwise noted, these three terms all refer to a J2EE application server.For those interested in more information about UML, we refer you to the following sources: UML Distilled,Second Edition, Fowler, Scott, 2000, Addison-Wesley Instant UML,Muller, 1997, Wrox Press Ltd. Other Sources of InformationYou should refer to other publications related to J2EE and to the J2EE Web site, http://java.sun.com/j2ee/. The following books, both online and in print, are of particular interest to those developing J2EE Connectors and other application components. Java 2 Platform, Enterprise Edition Connector Specification,2000, Sun Microsystems, Inc. Available at http://java.sun.com/j2ee/docs.html. Java Message Service API,2000, Sun Microsystems, Inc. Available at http://java.sun.com/j2ee/docs.html. Java 2 Standard Edition Platform (J2SE),2000, Sun Microsystems, Inc. Available at http://java.sun.com/products. Java Authentication and Authorization Service (JAAS) 1.0 Specification,2000, Sun Microsystems, Inc. Available at http://java.sun.com/products/jaas. Java 2 Platform, Enterprise Edition, Platform and Component Specifications,Shannon, Hapner, Matena, Davidson, Pelegri-Llopart, Cable, Enterprise Team, 2000, Addison-Wesley. Enterprise JavaBeans 2.0 Specification,Copyright 2001, Sun Microsystems, Inc. Ava

An electronic version of this book is available through VitalSource.

This book is viewable on PC, Mac, iPhone, iPad, iPod Touch, and most smartphones.

By purchasing, you will be able to view this book online, as well as download it, for the chosen number of days.

Digital License

You are licensing a digital product for a set duration. Durations are set forth in the product description, with "Lifetime" typically meaning five (5) years of online access and permanent download to a supported device. All licenses are non-transferable.

More details can be found here.

A downloadable version of this book is available through the eCampus Reader or compatible Adobe readers.

Applications are available on iOS, Android, PC, Mac, and Windows Mobile platforms.

Please view the compatibility matrix prior to purchase.