System and method for transactional and fault-tolerant distribution of digital assets over multi-tiered computer networks

• US 8,650,226 B2
• Filed: 01/14/2011
• Issued: 02/11/2014
• Est. Priority Date: 09/01/2000
• Status: Expired due to Fees

• Current Assignee: Op40 Holdings, Inc.
• Original Assignee: Op40 Holdings, Inc.
• Inventors: Pace, Charles P., Bobick, Mark
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Black, Linh
• Application Number:
  US12/930,752
• Publication Number:
  US 20110137953A1
• Time in Patent Office: 1,124 Days
• Field of Search: 707/799, 707/954, 707/807, 707/812, 707/945, 707/960, 707/638, 707/695, 707/694, 707/674, 707/679, 707/687, 707805-806, 719313-316, 719328-329, 710/54
• US Class Current: 707/807
• 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 herein is a system and computer program product for distributing at least one infrastructure description record (IDR) over at least one tier of a network. The system includes at least one network interface that receives the infrastructure description records (IDRs) and the IDRs being enqueued on at least one incoming, transactional, persistent queue (ITPQ), at least one transactional, persistent store, and at least one transactional process that dequeues the IDR from the ITPQ and accesses the IDR to create an accessed IDR, the accessed IDR being stored in the transactional, persistent store in the system.

Claims

1. A computer system having at least one memory and one network connection for distributing at least one infrastructure description record and at least one digital asset over at least one tier of a network, comprising:

a component distribution server system connected to at least one network through at least one network interface that receives therefrom the infrastructure description records and at least one digital asset 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 asset and the extended environment layer being a subset of the EIS and having portions of the EIS necessary to support the respective logic/data layer;

both of the infrastructure description records and the digital assets being enqueued on at least one incoming, transactional, persistent queue; and

at least one transactional, persistent store;

said component distribution server system comprising at least one transactional process that;

dequeues the infrastructure description record and the digital asset from the incoming, transactional, persistent queue and accesses the infrastructure description record and the digital asset to create an accessed infrastructure description record and an accessed digital asset, both being stored in the transactional, persistent store in the computer system; and

distributes the accessed infrastructure description record and the accessed digital asset via;

a package specification process that receives at least one package which is a subpart of at least one application program from an enterprise information system (EIS), the packages having the accessed infrastructure description record and the accessed digital assets;

a process adapter process that translates the asset layers so that the asset performs the asset function on a target base environment of a target computer; and

a target process that changes at least one of the layers of the asset in order to provide specific information for the target computer.

2. The computer system according to claim 1, wherein the infrastructure description record includes control information that causes the transactional process to change state and the process insuring that the incoming, transactional, persistent queue and the transactional, persistent store achieve a consistent state with the process.

3. The computer system according to claim 2, wherein the consistent state is atomic, consistent, isolated, or durable.

4. The computer system according to claim 2, wherein the transactional process insures that the incoming, transactional, persistent queue and the transactional, persistent store achieve a consistent state with the process in accordance with a compensating transaction based recovery.

5. The computer system according to claim 1, wherein the infrastructure description record includes at least one of a node identifier, a node address, a client address, a client identifier, a client platform identifier, a client environment descriptor, a client application name, a package specification record, a node registration specification, and a delivery schedule process message.

6. The computer system according to claim 1, wherein the transactional process further sends the accessed infrastructure description record and the accessed digital asset from the transactional, persistent store through the network interface over the network via the transactional processes comprising the component distribution server system.

7. The computer system according to claim 1, wherein digital assets are enqueued on at least one first input asset transactional, persistent queue and the infrastructure description records are enqueued on at least one second input asset transactional, persistent queue or wherein digital assets are stored on at least one first transactional, persistent store and the infrastructure description records are stored on at least one second transactional, persistent store.

8. The computer system according to claim 1, wherein the transactional process includes one or more of:

a) an export process,

b) a packaging process,

c) a versioning process,

d) a package specification process,

e) a deployment process,

f) a deployment adapter method,

g) a process adapter method,

h) a target adapter method,

i) a synchronization asset adapter process, and

j) an adjustment asset adapter process, and

the infrastructure description record includes one or more of a corresponding;

a) at least one of an Enterprise Java Bean archive, a web application archive, a J2EE application archive, a Java Server Page file, a database query parameter file, a “

where clause”

, an asset definition structure, an intermediate representation, at least one context rule, and a preliminary package specification,

b) at least one of a packaging specification record, a client deployment record, a deployable asset record, a pending asset record, and a client identification,

c) an asset version request,

d) at least one of a package specification record and a delivery schedule record,

e) at least one of a client deployment record and an asset descriptor manifest,

f) at least one of an asset descriptor record, a static content digital asset, a Java Server Page, and an Enterprise Java Bean,

g) at least one of;

a deployment descriptor, a digital asset extended environment, and at least one digital asset extended environment descriptor,

h) at least one of a database query parameter file and a “

where clause”

,

i) at least one synchronization argument data object, and

j) at least one of;

at least one adjustment context record, at least one adjustment metrics record, at least one adjustment topics record, and at least one adjustment constraints record.

9. The computer system according to claim 1, wherein the digital assets include at least one of:

static content, dynamic content, enterprise java beans, reference data, session bean, entity bean, entity data, java class, and java beans.

10. The computer system according to claim 9, wherein the static content includes at least one of the:

a JPEG file, a GIF file, a Java Applet, a SVG (Scalable Vector Graphics) file, a PDF (Portable Document Format) file, a TIFF (Tag Image File Format) file, an EPS (Encapsulated Postscript) file, a PNG (Portable Network Graphics) file, an XML file, a WML (Wireless Meta Language) file, a BMP (Bit Map) file, an XHTML (extended HTML) file, a DHTML (Dynamic HTML) file, an MPEG (Motion Picture Expert Group) file, an AVI file, and at least one static content object transferable via an HTTP protocol.

11. The computer system according to claim 9, wherein the dynamic content includes at least one of:

a Java Server Page and a Java Servlet, C++, Small Talk, Visual Basic, and Perl.

12. The computer system according to claim 1, wherein the transactional, persistent queue includes an enterprise information messaging system queue.

13. The computer system according to claim 12, wherein the enterprise information messaging system queue includes at least one of:

an in-memory Java Message Service “

temporary”

queue, a Tibco Rendevous messaging queue, a Talarian SmartSockets messaging queue, an IBM MQSeries messaging queue, and a Microsoft MQMS messaging queue.

14. The computer system according to claim 12, wherein the enterprise information messaging system queue includes a Java Message Service Server provided persistently backed Java Message Service persistent queue.

15. The computer system according to claim 12, wherein the enterprise information messaging system queue includes a Java Message Service Server provided persistently backed Java Message Service persistent queue with data transferred to a relational store by the transactional process.

16. The computer system according to claim 15, wherein the Java Message Service Server provider includes at least one:

a BEA Weblogic Application Server, an iPlanet Application Server, an IBM MQSeries used with an IBM Websphere Application Server, a Borland VisiMessage used with a Borland Application Server.

17. The computer system according to claim 1, wherein the transactional process includes a discovery process and the infrastructure description record includes at least one of:

an asset name, an application name, an enterprise information service application name, a Java Server Page used as a list of digital assets, an HTML document used as a list of digital assets, an asset candidate list, a descriptor, a descriptor for Enterprise Java Beans, an intermediate representation, and an asset definition data structure.

18. The computer system according to claim 1, wherein the transactional process includes a node registration process and the infrastructure description record includes at least one of:

a client specification record, a node/client registration record, and a client package registration record.

19. The computer system according to claim 1, wherein the transactional, persistent store includes at least one of:

at least one Oracle Database Management System, at least one Sybase Database Management System, at least one DB2 Database Management System, at least one Microsoft SQLServer Database Management System, at least one Postgres Database Management System, at least one Informix Database Management System, at least one Informix Cloudscape Database Management System, and at least one HypersonicSQL Database Management System.

20. The computer system of claim 1, wherein the computer memory tangibly stores a transactional unit of work chain of at least two transactional units of work for transactional and fault-tolerant distribution of at least one infrastructure description record over at least one tier of a network, comprising:

a first transactional unit of work including;

at least one first incoming, transactional, persistent queue;

at least one first transactional, persistent stores;

at least one first network interface that consumes the infrastructure description records by receiving the infrastructure description record and enqueuing the infrastructure description record on the first incoming, transactional, persistent queue; and

at least one first transactional process that dequeues the infrastructure description record from the first incoming, transactional, persistent queue, accesses the infrastructure description record to create an accessed infrastructure description record, stores the accessed infrastructure description record in the first transactional, persistent store in the system, and produces the accessed infrastructure description record by sending the accessed infrastructure description record from the first transactional, persistent store through the first network interface over the network; and

a second transactional unit of work including;

at least one second incoming, transactional, persistent queue;

at least one second transactional, persistent store;

at least one second network interface that consumes the accessed infrastructure description record by receiving the accessed infrastructure description record from the first transactional unit of work and enqueuing the accessed infrastructure description record on the second incoming, transactional, persistent queues; and

at least one second transactional process that dequeues the infrastructure description record from the second incoming, transactional, persistent queue, accesses the infrastructure description record to create a second accessed infrastructure description record, stores the second accessed infrastructure description record in the second transactional, persistent store in the system, and produces the second accessed infrastructure description record by sending the second accessed infrastructure description record from the second transactional, persistent store through the second network interface over the network.

21. The computer system of claim 20, wherein the transactional unit of work chain further comprises a third transactional unit of work and a fourth transactional unit of work, wherein said third and fourth transactional units of work with the first and second transactional units of work comprise a transactional unit of work matrix.

22. A method for distributing at least one infrastructure description record over at least one tier of a network, the method comprising the steps of:

receiving at least one of the infrastructure description records in the network interface linked to the component distribution server system comprising the computer system of claim 1;

enqueuing the infrastructure description records on at least one incoming, transactional, persistent queue;

dequeuing the infrastructure description record from the incoming, transactional, persistent queue;

accessing the infrastructure description record to create an accessed infrastructure description record; and

storing the accessed infrastructure description record in a transactional, persistent store.

23. A computer program product having a memory, said memory tangibly storing therein the method for distributing at least one infrastructure description record over at least one tier of a network comprising the steps of claim 22.