Systems and methods for modular component deployment

• US 7,165,249 B2
• Filed: 03/27/2003
• Issued: 01/16/2007
• Est. Priority Date: 05/02/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch, Golding, Christa, Potter, Timothy, DeGrande, Rick
• Primary Examiner(s): Zhen; Wei
• Assistant Examiner(s): DENG, ANNA CHEN
• Application Number:
  US10/400,821
• Publication Number:
  US 20040015859A1
• Time in Patent Office: 1,391 Days
• Field of Search: 717100-104, 717106-108, 709/219, 719/318, 719/328
• US Class Current: 717/174
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Abstract

An integration component such as an application integration engine can be bundled as a single, self-contained J2EE Enterprise archive (EAR) file. The bundling of the component into an EAR file enables the component to be deployed to any valid system domain that is running and available. A recycling of the server then may be necessary only if a Java archive file is added to the classpath for non-system domains.

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 method for the modular deployment of a integration component, comprising:

bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;

deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;

adding a Java archive file that packages the common class to class paths for any non-system domains; and

re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.

2. A method according to claim 1, further comprising:

recycling a server for the valid system domain.

3. A method according to claim 1 wherein the resource adapter carries out request interaction with the enterprise information system.

4. A method according to claim 3 wherein the application view bean maps service requests to interactions with the resource adapter.

5. A method according to claim 1, wherein:

bundling the integration component allows the integration component to be backward compatible with existing integration systems.

6. A method according to claim 1, wherein:

deploying the integration component allows the integration component to utilize JMS resources available to the valid system domain.

7. A method according to claim 1, further comprising:

configuring parameters for the integration component using a management console.

8. A computer-readable medium, comprising:

means for bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;

means for deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;

means for adding a Java archive file that packages the common class to class paths for any non-system domains; and

means for re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.

9. A computer program product stored in a computer readable medium for execution by a server computer for deploying an adapter, comprising:

computer code for bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;

computer code for deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;

computer code for adding a Java archive file that packages the common class to class paths for any non-system domains; and

computer code for re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.

10. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

bundle an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;

deploy the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;

add a Java archive file that packages the common class to class paths for any non-system domains; and

re-cycle a server on which the integration component is deployed if a Java archive file is added to the class oath for a non-system domain.

11. A computer system stored in a computer-readable medium for modular deployment of a integration component, comprising:

an integration component including an application view and a resource adapter for connecting to an enterprise information system wherein the integration component is bundled as an enterprise archive file; and

a valid system domain including a class path wherein the integration component is deployed by using the enterprise archive file;

wherein the re-cycling of a server is necessary only if a Java archive file is added to the class path for non-system domains.

12. A computer readable medium having instructions thereon which when executed by one or more processors cause a system to:

bundle an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for allowing a user to connect to an enterprise information system;

deploy the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;

add a Java archive file that packages the common class to class paths for any non-system domains; and

re-cycle a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.