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

• US 8,473,468 B2
• Filed: 10/25/2010
• Issued: 06/25/2013
• Est. Priority Date: 09/01/2000
• Status: Expired due to Fees

• Current Assignee: OP40 Holding Incorporated
• Original Assignee: OP40 Holding Incorporated
• Inventors: Pace, Charles P., Bobick, Mark, DeForest, Darin S., Chen, Shuang
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Black, Linh
• Application Number:
  US12/925,572
• Publication Number:
  US 20120005166A1
• Time in Patent Office: 974 Days
• Field of Search: 707/638, 707/695, 707/806, 717/717, 717/718, 717/148, 715/749, 715/234, 715/239, 715/760, 715/276
• US Class Current: 707/695
• 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 data processing systems or methods, specially adapted for e-commerce G06Q30/00
• 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

Provided is a computer system and method for transactional deployment of component(s) over a multi-tier network with J2EE application server program(s) stored on a memory(ies) of the system and which are executed by a central processing unit(s) (CPUs). A J2EE application(s) can be executed by the J2EE application servers, and a J2EE application container(s) are contained within each J2EE application server. Each J2EE application container contains a J2EE application container component(s) and a Java EJB container(s) or Java web containers are contained within each J2EE application container. A J2EE component(s) 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. This defines a sphere of control managing transactional deployment of the delivered J2EE component(s) 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;

a component distribution server/asset distribution server system connected to the network environment through a network interface and comprising;

a package specification process that receives at least one package, the package being subparts of at least one J2EE application server program from at least one Enterprise Information System (EIS), the package having at least one J2EE application container component/asset comprising the J2EE application server program, each of which having an asset type and at least two asset layers, a first asset layer being a logic/data layer and a second asset layer being an extended environment layer, the logic/data layer having information that includes a function of the J2EE application container component/asset and the extended environment layer being a subset of the Enterprise Information System and having portions of the Enterprise Information System system necessary to support the respective logic/data layer;

a process adapter process that translates at least one of the asset layers comprising at least one J2EE application container component/asset in the package so that the component/asset performs the asset function on at least one base environment of at least one J2EE application container on a J2EE application server upon deployment of the J2EE application component/asset thereon; and

a target process that changes at least one of the layers of the J2EE component/asset to provide specific information for the target computer, whereby a transformed J2EE application container component/asset is an J2EE application component/asset that is translated by the process adapter process and changed by the target process;

at least one memory device containing the 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 the at least one J2EE application container component, the at least one J2EE application server program adapted to receive at least one J2EE application container component delivered from the network environment over at least one tier of the network through the component distribution server/asset distribution server system; and

a logical connection to the database through the component distribution server/asset distribution server system;

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 through the component distribution server/asset distribution server system 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. A method for managing a transactional deployment of components using a computer system in a network, the method comprising the steps of:

accessing the database through the CDS/ADS comprising the computer system of claim 1;

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.

9. The method in accordance with claim 8, 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.

10. The method in accordance with claim 8, 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.

11. The method in accordance with claim 8, 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.

12. The method in accordance with claim 8, 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.

13. The method in accordance with claim 12, 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.

14. A non-transitory computer memory storage device for storing a computer program with instructions for managing a transactional deployment of components using a computer system in a network, the instructions adapted to be executed by a processor to perform the steps of the method of claim 8.