J2EE component extension architecture

• US 7,930,704 B2
• Filed: 02/04/2003
• Issued: 04/19/2011
• Est. Priority Date: 02/06/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: June, Deborah C., Mukherjee, Prasenjit, Mousseau, Richard
• Primary Examiner(s): Cao; Diem K
• Assistant Examiner(s): Hoang; Phuong N
• Application Number:
  US10/357,810
• Publication Number:
  US 20030225944A1
• Time in Patent Office: 2,996 Days
• Field of Search: 719/328, 719/331, 719/332, 719/315, 719/316, 719/311, 719/313, 709/225, 709/203, 718/101
• US Class Current: 719/328
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/4492 Inheritance
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

The J2EE connector architecture can be extended to reduce coding redundancy and resource consumption. A base J2EE connector can be used to allow an application to communicate with a first system or location. An extended connector can be used to communicate with a second system or location. The extended connector can use communication information located in the base connector, such that the extended connector only needs to store configuration information to allow the application to communicate with the second system or location.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A computer memory containing instructions, when read and executed by a computer, cause the computer to perform steps comprising:

using a base connector that allows an application server to communicate with a first port of an enterprise information system, wherein the base connector use a transaction contract to support a transaction access to the enterprise information system, wherein the transaction contract allows the application server to use a transaction manager to manage one or more transactions across multiple resource managers in the enterprise information system;

using a plurality of extended connectors that allow the application server to communicate with a plurality of ports of the enterprise information system in addition to the first port of the enterprise information system, wherein each extended connector of the plurality of extended connectors contains different configuration information for a particular port of the plurality of ports of the enterprise information system and uses information in the base connector to communicate with the particular port of the enterprise information system, wherein said each extended connector inherits attributes from the base connector as specified in a deployment descriptor and shares the transaction contract with the base connector to support a different transaction access to the enterprise information system through the particular port of the enterprise information system; and

providing a connector container for providing underlying services for said base connector and said plurality of extended connectors; and

managing said base connector and said plurality of extended connectors using the connector container.

2. A computer memory according to claim 1, wherein:

said connector container allows monitoring of said base connector and said plurality of extended connectors.

3. A computer memory according to claim 1, wherein:

class files and resource files that can be used by said base connector to communicate with said first port of the enterprise information system.

4. A computer memory according to claim 3, wherein:

said class files and resource files can further be used by one of said plurality of extended connectors to communicate with said plurality of ports of the enterprise information system.

5. The computer-readable storage medium of claim 4, wherein a common class loader is shared for the plurality of class and resource files.

6. A computer memory according to claim 1, wherein said extended connector further comprises information for modifying attributes of said base connector.

7. The computer-readable storage medium of claim 1, wherein each of the plurality of extended connectors includes configuration changes to a machine or port on which the extended connector is running.

8. The computer-readable storage medium of claim 1, wherein each of the plurality of extended connectors modifies or extends attributes of the base connector.

9. A computer memory according to claim 1, further containing instructions, when read and executed by a computer, cause the computer to perform a step of allowing one or more application components in the application server to connect with the enterprise information system using the base connector and at least one of the plurality of extended connectors, wherein one or more application components form a scalable application environment that can support a large number of clients requiring access to the enterprise information system.

10. A computer-based method for extending connector architecture components, comprising:

using a base connector that allows an application server to communicate with a first port of an enterprise information system, wherein the base connector use a transaction contract to support a transaction access to the enterprise information system, wherein the transaction contract allows the application server to use a transaction manager to manage one or more transactions across multiple resource managers in the enterprise information system;

using a plurality of extended connectors that allow the application server to communicate with a plurality of ports of the enterprise information system in addition to the first port of the enterprise information system, wherein each extended connector of the plurality of extended connectors contains different configuration information for a particular port of the plurality of ports of the enterprise information system and uses information in the base connector to communicate with the particular port of the enterprise information system, wherein said each extended connector inherits attributes from the base connector as specified in a deployment descriptor and shares the transaction contract with the base connector to support a different transaction access to the enterprise information system through the particular port of the enterprise information system; and

providing a connector container for providing underlying services for said base connector and said plurality of extended connectors; and

managing said base connector and said plurality of extended connectors using the connector container.

11. A computer-based method according to claim 10, further comprising:

creating class files and resource files that can be used by the base connector to communicate with said enterprise information system.

12. A computer-based method according to claim 11, further comprising:

sharing said class files and resource files that can be used by the base connector with the plurality of extended connectors.

13. The computer-based method of claim 12, wherein a common class loader is shared for the plurality of class and resource files.

14. A computer-based method according to claim 10, further comprising:

creating additional extended connectors that contain configuration information for additional enterprise information systems and utilize information in said base connector, the additional extended connectors allowing the application server to communicate with the additional enterprise information systems.

15. The computer-based method of claim 10, wherein each of the plurality of extended connectors includes configuration changes to a machine or port on which the extended connector is running.

16. The computer-based method of claim 10, wherein each of the plurality of extended connectors modifies or extends attributes of the base connector.

17. A computer-implemented system for extending connector components, comprising:

one or more processors;

a base connector that allows an application to communicate with a first port of an enterprise information system, wherein the base connector use a transaction contract to support a transaction access to the enterprise information system, wherein the transaction contract allows the application server to use a transaction manager to manage one or more transactions across multiple resource managers in the enterprise information system;

a plurality of extended connectors that allow the application to communicate with a plurality of ports of a plurality of enterprise information systems, each extended connector containing different configuration information for a particular port for a system from the plurality of enterprise information systems and adapted to use information in the base connector to communicate with the particular port, wherein said each of the plurality of extended connectors shares the transaction contract with the base connector to support a transaction access to the enterprise information system through the particular port of the enterprise information system and includes only configuration changes;

a connector container for providing underlying services for the base connector and the extended connector, wherein the connector container allows managing and monitoring of the base connector and the plurality of extended connectors;

a plurality of class and resource files that can be used by the base connector to communicate with the first system and by each connector of the plurality of extended connectors to communicate to each system of the plurality of systems.

18. The computer-implemented system of claim 17, wherein each of the plurality of extended connectors includes configuration changes to a machine or port on which the extended connector is running.

19. The computer-implemented system of claim 18, wherein each of the plurality of extended connectors modifies or extends attributes of the base connector.

20. The computer-implemented system of claim 17, wherein a common class loader is shared for the plurality of class and resource files.

21. The computer-implemented system of claim 17, wherein the plurality of extended connectors share the plurality of class and resource files that are used by the base connector to communicate with the first system.

22. The computer-implemented system of claim 17, wherein the base connector supports communication between an application component and the enterprise information system using a separate contract, and wherein the application component runs on the application server.

23. The computer-implemented system of claim 17, wherein each of the extended connector implements a different enterprise information system specific interface to communicate with a different enterprise information system.