System and method for transactional deployment of J2EE web components, enterprise java bean components, and application data over multi-tiered computer networks

• US 20030050932A1
• Filed: 09/04/2001
• Published: 03/13/2003
• Est. Priority Date: 09/01/2000
• Status: Abandoned Application

• Current Assignee: OP40 Incorporated
• Original Assignee: OP40 Incorporated
• Inventors: Pace, Charles P., Chen, Shuang, Pizzorni, Paolo R., Bobick, Mark
• Application Number:
  US09/947,096
• Publication Number:
  US 20030050932A1
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 2209/549 Remote execution
• CPC Class Codes: G06F 2216/15 Synchronised browsing
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5651 : Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface

Abstract

A computer system and a method for transactional deployment of one or more components over a multi-tier network is provided, which computer system has one or more J2EE application server programs which are stored on one or more memories of the system and which are executed by one or more central processing units (CPUs). One or more J2EE applications can be executed by the J2EE application servers, and one or more J2EE application containers are contained within each J2EE application server. In turn, each J2EE application container contains one or more J2EE application container components, and one or more Java EJB containers or Java web containers are contained within each J2EE application container. One or more J2EE components are delivered to the J2EE application server over one or more tiers of the network. There are one or more logical connections to one or more databases located on the network. The at least one J2EE application server program, the at least one J2EE application, the at least one J2EE application container, the at least one J2EE application container component, the at least one delivered J2EE component and the logical connection define a sphere of control managing a transactional deployment of the at least one delivered J2EE component and an update of the database to keep the data consistent with the J2EE application.

Claims

1. A computer system in a network environment for transactional deployment of at least one component, the computer system having access to at least one storage device containing a database, the computer system comprising:

a processor;

at least one memory device containing at least one J2EE application server program adapted to be executed by the processor, the at least one J2EE application server program containing at least one J2EE application, the at least one J2EE application having at least one J2EE application container, the at least one J2EE application container having at least one J2EE application container component, the at least one J2EE application server program adapted to receive at least one J2EE component delivered from the network environment over at least one tier of the network; and

a means for providing a logical connection to the database;

wherein the at least one J2EE application server program, the at least one J2EE application, the at least one J2EE application container, the at least one J2EE application container component, the at least one delivered J2EE component and the logical connection define a sphere of control managing a transactional deployment of the at least one delivered J2EE component and an update of the database to keep data consistent with the J2EE application.

2. The computer system in accordance with claim 1, wherein the at least one J2EE application container component is a web container.

3. The computer system in accordance with claim 2, wherein the web container contains at least one of a static content, a Java Servlet, a Java Server Page (JSP), an HTML page, and an XML page.

4. The computer system in accordance with claim 1, wherein the J2EE application container component is an Enterprise Java Bean (EJB) container.

5. The computer system in accordance with claim 4, wherein the EJB container contains at least one enterprise Java bean.

6. The computer system in accordance with claim 2, wherein a plurality of J2EE application container components are provided, and the J2EE application container components further include at least one Enterprise Java Bean (EJB) container.

7. The computer system in accordance with claim 6, wherein the at least one EJB container contains at least one enterprise Java bean.

8. The computer system in accordance with claim 1, wherein the sphere of control achieves the steps of:

accessing the database;

initiating a deployment of a latest version of a data object to the database;

determining whether the deployment of the data object is successful;

deploying at least one file containing a latest version of the delivered J2EE component into the at least one J2EE application container;

determining whether the latest version of the delivered J2EE component is successfully deployed into the at least one J2EE application container;

storing one of a previous version and the latest version of the delivered J2EE component for rollback in case of subsequent deployment failures involving one of the data object and the delivered J2EE component; and

discarding the previous version of delivered J2EE component and a previous version of the data object only if both the deployment of the latest version of the data object and the deployment of the latest version of the delivered J2EE component into the J2EE application container are successful.

9. A method for managing a transactional deployment of components using a computer system in a network, the method comprising the steps of:

accessing a database;

initiating a deployment of a latest version of a data object to the database;

determining whether the deployment of the data object is successful;

deploying at least one file containing a latest version of delivered J2EE component into at least one J2EE application container;

determining whether the latest version of the delivered J2EE component is successfully deployed into the at least one J2EE application container;

storing one of a previous version and the latest version of the delivered J2EE component for rollback in case of subsequent deployment failures involving one of the data object and the delivered J2EE component; and

discarding the previous version of delivered J2EE component and a previous version of the data object only if both the deployment of the latest version of the data object and the deployment of the latest version of the delivered J2EE component into the J2EE application container are successful.

10. The method in accordance with claim 9, wherein if the deployment of the latest version of the data object is successful and the deployment of the latest version of the delivered J2EE component is unsuccessful, the successful deployment of the database is rolled back.

11. The method in accordance with claim 9, wherein if the deployment of the latest version of the data object is unsuccessful and the deployment of the latest version of the delivered J2EE component is successful, then the previous version of the delivered J2EE component is retained.

12. The method in accordance with claim 9, wherein if at least one of deployment of the latest version of the data object and deployment of the latest version of the delivered J2EE component is unsuccessful, then no action is taken.

13. The method in accordance with claim 9, wherein if at least one of deployment of the latest version of the data object and deployment of the latest version of the delivered J2EE component is unsuccessful, then a set of failure rules are applied.

14. The method in accordance with claim 13, wherein the failure rules comprise at least one of the following:

a retry of the data object deployment, a retry of the delivered J2EE component deployment, accessing an alternative source for the data object involved in the failed data-object deployment, and accessing an alternative source for the J2EE component involved in the failed J2EE-component deployment.

15. A computer system for transactional deployment of at least one component, said computer system being in a network and having access to an external database stored in a storage medium, the computer system comprising:

means for accessing the external database;

means for initiating a deployment of a latest version of a data object to the database;

means for determining whether the deployment of the data object is successful;

means for opening at least one file containing a latest version of J2EE component delivered to the computer system;

means for storing at least one J2EE application container;

means for determining whether the latest version of the delivered J2EE component is successfully deployed into the at least one J2EE application container;

means for discarding a previous version of delivered J2EE component and a previous version of the data object only if both the deployment of the latest version of the data object and the deployment of the latest version of the delivered J2EE component into the J2EE application container are successful; and

means for storing a latest state of the database and a latest state of the J2EE application container, wherein said latest states are available as a log for rollback in case of subsequent deployment failures involving the data object and the delivered J2EE component.

16. A medium for storing instructions adapted to be executed by a processor to perform the steps of:

accessing a database;

initiating a deployment of a latest version of a data object to the database;

determining whether the deployment of the data object is successful;

deploying at least one file containing a latest version of delivered J2EE component into at least one J2EE application container;

determining whether the latest version of the delivered J2EE component is successfully deployed into the at least one J2EE application container;

storing one of a previous version and the latest version of the delivered J2EE component for rollback in case of subsequent deployment failures involving one of the data object and the delivered J2EE component; and

discarding the previous version of delivered J2EE component and a previous version of the data object only if both the deployment of the latest version of the data object and the deployment of the latest version of the delivered J2EE component into the J2EE application container are successful.