System and method for bridging assets to network nodes on multi-tiered networks
First Claim
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:
- attempting to request at least one resource on a remote node by at least one asset deployed on a local node through an application programming interface over a Distributed Internet Services (DIS) system, said system including;
a component distribution server/asset distribution server system (CDS/ADS) comprising;
a package specification process that receives at least one package which is subparts of at least one application program from at least one enterprise information system (EIS), the package having at least one asset comprising the at least one resource, each 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 pending asset and the extended environment layer being a subset of the EIS and having portions of the EIS system necessary to support the respective logic data layer;
a process adapter process that translates at least one asset layer comprising at least one asset in the package so that the asset performs the asset function on a base environment of the local node requesting the resource; and
a target process that changes the at least one layers of the requested resource to provide specific information for the local node, whereby a transformed asset is an asset that is translated by the process adapter process and changed by the target process;
an EIS deployment agent (EDA) to task creation of the at least one package; and
a client deployment agent (CDA) to communicate with the CDS/ADS;
detecting a fault after requesting the resource on the remote node;
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 via the CDS/ADS;
wherein,(i) if the resource is not defined in the directory service, determining whether the fault is a database interface fault, and if so, distributing and/or synchronizing entity bean asset, an entity data asset, and a reference data asset between the nodes via the CDS/ADS;
(ii) if the fault is not a database interface fault, determining whether the fault is a server fault, and if so, connecting a proxy to the CDS/ADS to proxy the request for the resource for the server; and
(iii) if the fault is not a server fault, determining whether the fault is an object fault, and if so, performing a proxy request for the resource, said request accepted by a proxy object, said proxy object then calling the CDS/ADS to proxy the request, said CDS/ADS then calling the EIS deployment agent (EDA) on the remote node, said EDA performing the call within an environment of the remote node to access and package the requested resource as one or more assets and to return the same to the CDS/ADS; and
returning the requested resource, consecutively, to the CDA from the CDS/ADS, then to the proxy object from the CDA and then to the local node from the proxy object, thereby maintaining communication.
0 Assignments
0 Petitions
Accused Products
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.
18 Citations
37 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:
-
attempting to request at least one resource on a remote node by at least one asset deployed on a local node through an application programming interface over a Distributed Internet Services (DIS) system, said system including; a component distribution server/asset distribution server system (CDS/ADS) comprising; a package specification process that receives at least one package which is subparts of at least one application program from at least one enterprise information system (EIS), the package having at least one asset comprising the at least one resource, each 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 pending asset and the extended environment layer being a subset of the EIS and having portions of the EIS system necessary to support the respective logic data layer; a process adapter process that translates at least one asset layer comprising at least one asset in the package so that the asset performs the asset function on a base environment of the local node requesting the resource; and a target process that changes the at least one layers of the requested resource to provide specific information for the local node, whereby a transformed asset is an asset that is translated by the process adapter process and changed by the target process; an EIS deployment agent (EDA) to task creation of the at least one package; and a client deployment agent (CDA) to communicate with the CDS/ADS; detecting a fault after requesting the resource on the remote node; 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 via the CDS/ADS;
wherein,(i) if the resource is not defined in the directory service, determining whether the fault is a database interface fault, and if so, distributing and/or synchronizing entity bean asset, an entity data asset, and a reference data asset between the nodes via the CDS/ADS; (ii) if the fault is not a database interface fault, determining whether the fault is a server fault, and if so, connecting a proxy to the CDS/ADS to proxy the request for the resource for the server; and (iii) if the fault is not a server fault, determining whether the fault is an object fault, and if so, performing a proxy request for the resource, said request accepted by a proxy object, said proxy object then calling the CDS/ADS to proxy the request, said CDS/ADS then calling the EIS deployment agent (EDA) on the remote node, said EDA performing the call within an environment of the remote node to access and package the requested resource as one or more assets and to return the same to the CDS/ADS; and
returning the requested resource, consecutively, to the CDA from the CDS/ADS, then to the proxy object from the CDA and then to the local node from the proxy object, thereby maintaining communication. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A method for bridging assets residing on multi-tiered network nodes, comprising:
-
receiving, over a Distributed Internet Services (DIS) system, from a first asset in a target environment on a target node, a request to access a second asset;
said first and second assets each 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 pending asset and the extended environment layer being a subset of an EIS and having portions of the EIS system necessary to support the respective logic data layer, each of said assets comprising a package which is subparts of at least one application program from at least one enterprise information system (EIS);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 over the BCE via a component distribution server/asset distribution server system (CDS/ADS) in the DIS for delivery to the target environment, said CDS/ADS comprising; a package specification process that receives the package comprising the second asset; a process adapter process that translates at least one of the asset layers of the second asset so that the asset performs the asset function on a target base environment of the target node; and a target process that changes the at least one layer of the second asset to provide specific information for the target node, whereby a transformed asset is an asset that is translated by the process adapter process and changed by the target process, thereby bridging the first and second assets, thereby bridging the assets. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34)
-
-
35. A system for bridging assets residing on multi-tiered network nodes, comprising:
-
in a Distributed Internet Services system on the multi-tiered network, said network comprising at least one network connection to at least one computer having a memory and a processor; a first asset; a second asset;
said first and second assets each 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 pending asset and the extended environment layer being a subset of an EIS and having portions of the EIS system necessary to support the respective logic data layer, each of said assets comprising a package which is subparts of at least one application program from at least one enterprise information system (EIS);a target environment in a target node, including the first asset, an asset access adapter, and a fault handler; an alternative environment, including the second asset; a bridged computational environment (BCE) associated with the second asset and the alternative environment; and a component distribution server/asset distribution server system (CDS/ADS), comprising; a package specification process that receives the package comprising the second asset; a process adapter process that translates at least one of the asset layers of the second asset so that the asset performs the asset function on a target base environment of the target node; and a target process that changes the at least one layer of the second asset to provide specific information for the target node, whereby a transformed asset is an asset that is translated by the process adapter process and changed by the target process. - View Dependent Claims (36, 37)
-
Specification