By Topic

WebSphere connector architecture evolution

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $33
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
S. M. Fontes ; IBM Software Group, 3039 Cornwallis Road, Research Triangle Park, NC 27709, USA ; C. J. Nordstrom ; K. W. Sutter

The ability of applications to communicate with resources that are outside of the application server process and to use those resources efficiently has always been an important requirement for application developers. Equally important is the ability for vendors to plug in their own solutions for connecting to and using their resources. These capabilities have evolved over time in the IBM WebSphere Application Server, from the JDBC™ application programming interface to the Common Connector Framework and later to the J2EE™ Connector Architecture, the latter providing functions such as application server inbound communications, life cycle management, and work management. In this paper, the evolution of the WebSphere Application Server implementation of these architectures, their benefits, and their trade-offs are discussed. A preview of an important new architecture, the WebSphere Channel Framework Architecture (a logical extension to the J2EE Connector Architecture) is also presented.

Note: The Institute of Electrical and Electronics Engineers, Incorporated is distributing this Article with permission of the International Business Machines Corporation (IBM) who is the exclusive owner. The recipient of this Article may not assign, sublicense, lease, rent or otherwise transfer, reproduce, prepare derivative works, publicly display or perform, or distribute the Article.  

Published in:

IBM Systems Journal  (Volume:43 ,  Issue: 2 )