System and method for bridging assets to network nodes on multi-tiered networks

• US 20110016348A1
• Filed: 07/02/2010
• Published: 01/20/2011
• Est. Priority Date: 09/01/2000
• Status: Active Grant

• Current Assignee: Charles P. Pace, Paolo R. Pizzorni, Shuang Chen
• Original Assignee: Charles P. Pace, Paolo R. Pizzorni, Shuang Chen
• Inventors: Pace, Charles P., Chen, Shuang, Pizzorni, Paolo R.
• Granted Patent: US 8,386,525 B2
• Time in Patent Office: Days
• US Class Current: 714/2
• 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

An exemplary method and/or exemplary embodiment of the present invention provides a system and method for bridging an asset over a multi-tiered network. Generally, communications can be maintained between executable assets residing on different network nodes by bridging the execution context of the two nodes. In an embodiment, a mapping layer can be generated for assets that have run-time dependencies; the mapping layer uses a distribution system to bridge the execution context of a first environment with that of a second environment. The asset executing in the first environment can access another resource located in the second environment, even though the asset does not have local access to the resource in the second environment. A fault is detected when at least one asset deployed on a local node attempts to access at least one resource on a remote node through an application programming interface. The fault is then handled appropriately.

Claims

1. A method for maintaining communication between at least two executable system parts executing on at least two nodes of a multi-tiered network, comprising the steps of:

detecting a fault when at least one asset deployed on a local node attempts to access at least one resource on a remote node, the resource being accessed through an application programming interface;

determining whether the resource causing the fault is defined in a directory service that should be accessed on the remote node, and if so, providing a reference to the remote node;

if the resource is not defined in the directory service, determining whether the fault is a database interface fault; and

if the fault is not a database interface fault, determining whether the fault is at least one of a server fault and an object fault.

2. The method according to claim 1, wherein the reference includes a remote proxy object.

3. The method according to claim 1, wherein the reference includes at least one of a redirection, a server proxy, an object proxy, and an API proxy.

4. The method according to claim 1, wherein the reference includes a lookup mechanism, the lookup mechanism determining a source node associated with the asset.

5. The method according to claim 4, wherein the lookup mechanism includes a flat file, the flat file being edited when the asset is deployed to the local node to indicate that the asset requires a reference to a remote object.

6. The method according to claim 4, wherein the lookup mechanism is stored in a persistent database in the source node.

7. The method according to claim 1, wherein the fault is a database interface fault, and further including at least one of:

distributing at least one of an entity bean asset, an entity data asset, and a reference data asset; and

synchronizing at least one of an entity bean asset, an entity data asset, and a reference data asset.

8. The method according to claim 1, wherein the fault is a server fault, the server fault being associated with an attempt to reference an object on a server and the server is registered as requiring a proxy connection.

9. The method according to claim 8, further including connecting a proxy to a component distribution/asset distribution server that can proxy the request for the server.

10. The method according to claim 8, wherein the server resides on one of a component distribution/asset distribution server and a source node.

11. The method according to claim 1, wherein the application programming interface includes a J2EE API, the directory service includes a JDNI, and the database interface includes a JDBC.

12. The method according to claim 1, wherein the fault is an object fault, the object fault being associated with a request for an object that is a stub/proxy of an actual object.

13. The method according to claim 12, wherein the actual object resides in at least one of a source node and an intermediate target node.

14. The method according to claim 12, further including performing a proxy by at least one of a redirection and a proxy request.

15. The method according to claim 1, wherein the local node is at least one of a personal computer, a workstation, a pervasive device, a local server, a local area network server, a proxy server, an edge server, a general network servers, and an enterprise information system.

16. A method for bridging assets residing on multi-tiered network nodes, comprising:

receiving, from a first asset in a target environment, a request to access a second asset;

failing to access the second asset;

generating a fault;

creating a bridged computational environment associated with the second asset and an alternative environment; and

accessing the second asset in the alternative environment.

17. The method of claim 16, wherein the alternative environment is a source environment, a distribution tier environment, or an alternative target environment.

18. The method of claim 16, wherein the fault is a J2EE API fault.

19. The method of claim 18, wherein the second asset is a remote object defined in a JNDI.

20. The method of claim 19, wherein said creating includes providing a reference associated with the remote object to the first asset.

21. The method of claim 20, wherein said providing a reference is by redirection, server proxy, object proxy, or API proxy.

22. The method of claim 20, wherein said providing a reference is by lookup into a flat file having associations between assets and remote objects.

23. The method of claim 20, wherein said providing a reference is by lookup into a persistent database table having associations between assets and remote objects.

24. The method of claim 16, wherein the fault is a JDBC fault.

25. The method of claim 24, wherein the second asset is an enterprise bean, an entity data, or a reference data type.

26. The method of claim 25, wherein said creating includes distribution of the second asset.

27. The method of claim 25, wherein said creating includes synchronization of the second asset.

28. The method of claim 16, wherein the fault is a server fault associated with a server.

29. The method of claim 28, wherein the second asset is a server object.

30. The method of claim 29, wherein said creating includes connecting a proxy to the server.

31. The method of claim 29, wherein the proxy is a component distribution server.

32. The method of claim 29, wherein the proxy is in the source environment or the distribution environment.

33. The method of claim 30, wherein the bridged computational environment includes HTTP tunneling of IIOP traffic through a firewall associated with the server.

34. The method of claim 16, wherein the fault is an object fault.

35. The method of claim 34, wherein the second asset is a stub object associated with an actual object in the alternative environment.

36. The method of claim 35, wherein said creating includes connecting the stub object and the actual object.

37. The method of claim 16, wherein said accessing is transparent to the first asset.

38. A system for bridging assets residing on multi-tiered network nodes, comprising:

a first asset;

a second asset;

a target environment, including the first asset, an asset access adapter, and a fault handler;

an alternative environment, including the second asset; and

a bridged computational environment associated with the second asset and the alternative environment.

39. The system of claim 38, wherein the alternative environment is a source environment, a distribution tier environment, or an alternative target environment.

40. The system of claim 38, further comprising a server proxy, an object proxy, or an API proxy.