Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 112: J2EETM Connector Architecture 1.5

Stage Access Start Finish
Final Release Download page 24 Nov, 2003  
Final Approval Ballot View results 28 Oct, 2003 11 Nov, 2003
Proposed Final Draft 2 Download page 06 Nov, 2002  
Proposed Final Draft Download page 15 Jul, 2002  
Public Review Download page 17 May, 2002 16 Jun, 2002
Community Draft Ballot View results 30 Apr, 2002 06 May, 2002
Community Review Login page 04 Apr, 2002 06 May, 2002
Expert Group Formation   03 Apr, 2001 08 Nov, 2001
JSR Review Ballot View results 20 Mar, 2001 02 Apr, 2001
Status: Final
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0


Description:
The J2EE(TM) Connector Architecture 1/5 extends the existing 1.0 specification with new features including asynchronous integration with enterprise information systems, Java Message Service (JMS) provider pluggability.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Binod PG Sun Microsystems, Inc.
Expert Group
  Bahwan Cybertek Private Limited Barreto, Charlton BEA Systems
  Bull S.A. Ericsson Infotech AB Fujitsu Limited
  Hewlett-Packard IBM Micro Focus Ltd.
  NEON Systems, Inc. Novell, Inc. Oracle
  Progress Software SAP AG Siemens AG
  Sonic Software Sun Microsystems, Inc. Sybase
  TIBCO Software Inc. Unisys WebMethods Corporation

Updates to the Original Java Specification Request (JSR)

The following section have been updated from the original JSR. 2006.02.15:

Specification Lead: Binod P G

E-Mail Address: binod.pg@sun.com

Telephone Number: +91 80569 27784

Fax Number:

2002.05.12:
The original request was modified, as the scope of the JSR has been reduced to a subset of the items it was originally planned to address.

2.1 Please describe the proposed Specification:

The J2EE Connector Architecture 1.0 defines a standard architecture for connecting to heterogeneous enterprise information systems (EIS), such as enterprise resource planning (ERP), mainframe transaction processing and database systems from the J2EE platform. The architecture defines a set of scalable, secure, and transactional mechanisms that describe the integration of enterprise information systems to an application server and enterprise applications. This architecture enables an enterprise information system (EIS) vendor to provide a resource adapter for its EIS that can be plugged into any application server that supports the J2EE Connector Architecture.

The purpose of the J2EE Connector Architecture 1.5 specification is to address areas in J2EE Connector Architecture 1.0 where further support has been requested by the Connector expert group and the public. The areas this specification intends to address include the following:

  • Asynchronous integration with EISs

  • Connector Architecture 1.0 supports a synchronous request/reply model from a J2EE server to an EIS. This specification will add support for bi-directional, asynchronous interactions between a J2EE server and resource adapters. This feature may require enhancement of the existing Connector system contracts and addition of new system contracts.
    ?
  • JMS Provider Pluggability

  • This specification will define a standard architecture to integrate a JMS provider into a J2EE server. This feature will enable one or more JMS providers to be plugged into any J2EE server that supports the J2EE Connector Architecture 1.5. This feature may require enhancement of the existing Connector system contracts and addition of new system contracts.

Original Java Specification Request (JSR)

Note that this JSR has been updated from the original.

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Sun Microsystems Inc.

Name of Submitter: Tony Ng

E-Mail Address: tony.ng@sun.com

Telephone Number: +1 408 343 1648

Fax Number: +1 408 863 3195


Specification Lead: Ram Jeyaraman

E-Mail Address: ram.jeyaraman@sun.com

Telephone Number: +1 408 517 5352

Fax Number:

NOTE that this information has been updated from this original request.

Initial Expert Group Membership:

  • BEA
  • Borland
  • Fujitsu
  • IBM
  • Netscape / iPlanet
  • Oracle
  • Sybase
  • Unisys
  • WebGain


  • Section 2: Request

    2.1 Please describe the proposed Specification:

    The J2EE Connector Architecture 1.0 defines a standard architecture for connecting to heterogeneous enterprise information systems (EIS), such as enterprise resource planning (ERP), mainframe transaction processing and database systems from the J2EE platform. The architecture defines a set of scalable, secure, and transactional mechanisms that describe the integration of enterprise information systems to an application server and enterprise applications. This architecture enables an enterprise information system (EIS) vendor to provide a resource adapter for its EIS that can be plugged into any application server that supports the J2EE Connector Architecture.

    The purpose of the J2EE Connector Architecture 1.5 specification is to address areas in J2EE Connector Architecture 1.0 where further support has been requested by the Connector expert group and the public. The areas this specification intends to address include the following:

    • Asynchronous integration with EISs

    • Connector Architecture 1.0 supports a synchronous request/reply model from a J2EE server to an EIS. This specification will add support for bi-directional, asynchronous interactions between a J2EE server and resource adapters. This feature may require enhancement of the existing Connector system contracts and addition of new system contracts.
      ?
    • JMS Provider Pluggability

    • This specification will define a standard architecture to integrate a JMS provider into a J2EE server. This feature will enable one or more JMS providers to be plugged into any J2EE server that supports the J2EE Connector Architecture 1.5. This feature may require enhancement of the existing Connector system contracts and addition of new system contracts.
      ?
    • CCI Metadata

    • The Common Client Interface (CCI) defines a standard mechanism for invoking remote functions in EISs. In Connector Architecture 1.0, there is no standard way for enterprise development tools or applications to obtain information about the EIS remote functions. This specification will enhance CCI to provide metadata about function names, input and output record types.
      ?
    • XML Support in CCI

    • This specification will define support for handling XML data using CCI. This may involve integration with existing XML APIs and enhancement of CCI.

    Please note that this section has been updated from the original.

    2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

    JavaTM 2, Enterprise Edition

    2.3 What need of the Java community will be addressed by the proposed specification?

    This specification will enhance the capabilities of J2EE platform and resource adapters, enabling developers to perform more complex and sophisticated integration between J2EE platform and heterogeneous enterprise information systems.

    2.4 Why isn't this need met by existing specifications?

    The existing J2EE Connector Architecture specification does not address the areas described in section 2.1. Vendors and developers are forced to use implementation-specific architectures or contracts, resulting in non-portable solutions.

    2.5 Please give a short description of the underlying technology or technologies:

    The J2EE Connector Architecture is based on the technologies that are defined and standardized as part of the JavaTM 2 platform, Enterprise Edition. Specifically, the J2EE Connector Architecture leverages concepts and mechanisms defined by J2EE, Java Transaction API (JTA), JDBC and JMS specifications.

    2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

    javax.resource.spi
    javax.resource.cci

    2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

    No

    2.8 Are there any security issues that cannot be addressed by the current security model?

    No

    2.9 Are there any internationalization or localization issues?

    No

    2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

    The proposed specification will supersede J2EE Connector Architecture 1.0 specification.

    2.11 Please describe the anticipated schedule for the development of this specification.

    The final schedule will need to be determined by the expert group, and will also be dependent on the progress of Java 2 Platform, Enterprise Edition. A community draft should be available by Q4 2001.





    Section 3: Contributions

    3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

    J2EE Connector Architecture Specification, Version 1.0
    http://java.sun.com/j2ee/connector

    Java 2 Platform, Enterprise Edition Specification, Version 1.3
    http://java.sun.com/j2ee/docs.html

    Java Transaction API, Version 1.0.1
    http://java.sun.com/products/jta

    JDBC Specification, Version 3.0
    http://java.sun.com/products/jdbc

    Java Message Service, Version 1.0.2
    http://java.sun.com/products/jms
    ?

    3.2 Explanation of how these items might be used as a starting point for the work.

    This specification extends J2EE Connector Architecture 1.0 specification.. This specification leverages concepts and mechanisms defined in J2EE, JTA, JDBC and JMS specifications.