Method and system for deploying an asset over a multi-tiered network

• US 7,150,015 B2
• Filed: 09/04/2001
• Issued: 12/12/2006
• Est. Priority Date: 09/01/2000
• Status: Active Grant

• Current Assignee: Op40 Holdings, Inc.
• Original Assignee: OP40 Incorporated
• Inventors: Pace, Charles P., Chen, Shuang, Pizzorni, Paolo R., Deforest, Darin S.
• Primary Examiner(s): BULLOCK JR, LEWIS ALEXANDER
• Application Number:
  US09/946,438
• Publication Number:
  US 20030051066A1
• Time in Patent Office: 1,925 Days
• Field of Search: 717100-178, 709200-253
• US Class Current: 717/176
• 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 method and system for deploying assets to multi-tiered network nodes. An asset may represent network and/or application components (e.g., data, objects, applications, program modules, etc.) that may be distributed among the various resources of the network. In one embodiment, a target node'"'"'s environment may be adjusted before an asset is deployed to that target node. In an alternative embodiment, a target deployment adapter, associated with the asset, may be selected and deployed with the asset in order to allow the asset to operate in the target node environment. An implementation class, associated with the asset, may be inserted into the target node environment. An altered target deployment descriptor may also be inserted into the target node environment.

Claims

1. A method for deploying an asset into a base environment of a target node, the target node being connected to a multi-tiered network through a network connection, comprising the steps of:

organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determining if at least one asset type is at least one of a session bean type and an entity bean type;

translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distributing the package over the multi-tiered network to the target node; and

inserting at least one enterprise Java bean implementation class associated with the translated asset(s) into a target archive in the base environment of the target node.

2. The method according to claim 1, wherein the target archive further includes at least one other enterprise Java bean implementation class.

3. The method according to claim 1, further including storing at least one stub and skeleton associated with the enterprise Java bean implementation class in the target archive.

4. The method according to claim 1, further including storing at least one client deployment descriptor located in the extended environment of the asset in the target archive.

5. The method according to claim 1, further comprising the step of:

determining whether a target table exists in at least one memory of the target node, the target table being associated with the asset type.

6. The method according to claim 5, wherein the target table does exist and further comprising the step of:

storing an asset table data, in the target table.

7. The method according to claim 5, wherein the asset is an enterprise bean having at least one asset table specified in the logic/data portion of the asset, the asset table having asset table data.

8. The method according to claim 7, wherein the target table does not exist and further comprising the steps of:

creating the target table; and

storing an asset table data, located in the asset, in the target table.

9. The method according to claim 8, wherein said creating the target table includes:

using a target table specification, located in the extended environment portion of the asset, to create the target table.

10. The method according to claim 1, further comprising the steps of:

determining if the asset type of the asset is not a session bean type or an entity bean type;

determining if the asset type of the asset is at least one of a reference data type and an entity data type; and

determining whether a target table exists in at least one memory of the target node, the target table being associated with the asset type.

11. The method according to claim 10, wherein at least one data structure of the asset is stored in the target table.

12. The method according to claim 10, wherein the target table does not exist and further comprising the steps of:

creating the target table; and

storing at least one data structure of the asset in the target table.

13. The method according to claim 10, further comprising the steps of:

writing an entry in a target database table, the entry indicating that at least one data structure in the asset was stored on at least one memory of the target node.

14. The method according to claim 1, further comprising the step of:

determining if said deploying should occur based on a scheduled deployment time, the scheduled deployment time being at, or before, a current time.

15. A method for deploying an asset into a base environment of a target node, the target node being connected to a multi-tiered network through a network connection, comprising the steps of:

organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determining if at least one asset type is at least one of a static content type, a Java server page type, and a Java bean type;

translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distributing the package over the multi-tiered network to the target node; and

copying at least one file specified in a data structure of the translated asset(s) into a memory location on the target node corresponding to the asset type.

16. The method according to claim 15, further comprising the steps of:

determining if the asset type of the asset is not a static content type, a Java server page type, or a Java bean type; and

determining if the asset type of the asset is at least one of a plurality of secondary asset types.

17. The method according to claim 16, wherein the memory location is associated with the asset type of the asset.

18. A node environment, the node environment being connected to a multi-tiered network through a network connection, comprising:

means for organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

means for determining if an asset type of an asset is at least one of a session bean type and an entity bean type; and

means for translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

means for distributing the package over the multi-tiered network to a target node; and

means for inserting at least one enterprise Java bean implementation class associated with the translated asset(s) into a target archive in the base environment of a target node.

19. The node environment according to claim 18, further comprising:

means for storing, on at least one memory of a target node system, at least one of an EJB implementation class, stubs and skeletons associated with an EJB implementation class, and a target deployment descriptor located on the extended environment of the asset.

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

organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determining if at least one asset type is at least one of a session bean type and an entity bean type;

translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distributing the package over the multi-tiered network to the target node; and

inserting at least one enterprise Java bean implementation class associated with the translated asset(s) into a target archive in the base environment of the target node.

21. A method for deploying an asset to a multi-tiered network node, comprising:

organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determining at least one asset type associated with the asset(s);

selecting a target deployment asset adapter associated with the asset(s);

translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distributing the package over the multi-tiered network to the node;

inserting at least one implementation class associated with the translated asset(s) into a base environment associated with the node; and

inserting an altered target deployment descriptor of the translated asset(s) into the base environment.

22. The method according to claim 21, wherein the asset is at least one of a session bean asset and an entity bean asset.

23. The method according to claim 21, wherein the asset is at least one of an entity bean asset, a reference data asset, and an entity data asset.

24. The method according to claim 23, wherein the asset includes an associated data structure having a table specification.

25. The method according to claim 24, further comprising:

determining whether a database table associated with the table specification exists in the base environment; and

creating the database table if the database table does not exist.

26. The method according to claim 25, further comprising importing data from the data structure into the database table.

27. The method according to claim 26, further comprising exporting the data from the data structure into a system database table.

28. The method according to claim 21, wherein the implementation class is an enterprise Java bean implementation class.

29. The method according to claim 28, further comprising:

inserting at least one of an enterprise Java bean stub and an enterprise Java bean skeleton into the base environment.

30. The method according to claim 29, wherein the at least one implementation class, enterprise Java bean stub, and enterprise Java bean skeleton is inserted into an archive in the environment.

31. A computer-readable medium that stores instructions for deploying an asset to a multi-tiered network node, the instructions adapted to be executed by a processor to perform the steps of:

organizing a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determining an at least one asset type associated with the asset(s);

selecting a target deployment asset adapter associated with the asset;

translating the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distributing the package over the multi-tiered network to the node;

inserting at least one implementation class associated with the translated asset(s) into a base environment associated with the node; and

inserting an altered target deployment descriptor of the translated asset(s) into the base environment.

32. The computer-readable medium according to claim 31, wherein the asset is at least one of a session bean asset and an entity bean asset.

33. The computer-readable medium according to claim 32, wherein the implementation class is an enterprise Java bean implementation class.

34. The computer-readable medium according to claim 33, further comprising inserting at least one of an enterprise Java bean stub and an enterprise Java bean skeleton into the base environment.

35. The computer-readable medium according to claim 34, wherein the at least implementation class, enterprise Java bean stub, and enterprise Java bean skeleton is inserted into an archive in the base environment.

36. The computer-readable medium according to claim 31, wherein the asset is at least one of an entity bean asset, a reference data asset, and an entity data asset.

37. The computer-readable medium according to claim 36, wherein the asset includes an associated data structure having a table specification.

38. The computer-readable medium according to claim 37, further comprising instructions adapted to be executed by the processor to perform the steps of:

determining whether a database table associated with the table specification exists in the base environment; and

creating the database table if the table does not exist.

39. The computer-readable medium according to claim 38, further comprising instructions adapted to be executed by the processor to perform the step of:

importing data from the data structure into the database table.

40. The computer-readable medium according to claim 39, further comprising instructions adapted to be executed by the processor to perform the step of:

exporting the data from the data structure into a system database table.

41. A system for synchronizing an asset on a multi-tiered network, comprising:

a processor;

a port coupled to the processor; and

a memory, coupled to the processor, storing instructions adapted to be executed by the processor to;

organize a package according to a package boundary, the package including;

at least two assets, each asset being a component of an application and having an asset type defined by an asset boundary and at least two asset layers including a logic/data layer and an extended environment layer; and

a base environment associated with said at least two assets;

wherein the package boundary may be determined by the asset boundary of at least one asset in the package;

determine at least one asset type associated with the asset(s);

select a client deployment adapter associated with the asset(s);

translate the asset(s) to deploy on a target node with a different base environment than the base environment associated with the asset(s);

distribute the package over the multi-tiered network to the node;

insert at least one implementation class associated with the translated asset(s) into a base environment associated with the node; and

insert an altered target deployment descriptor of the translated asset(s) into the base environment.

42. The system according to claim 41, wherein the asset is at least one of a session bean asset and an entity bean asset.

43. The system according to claim 42, wherein the implementation class is an enterprise Java bean implementation class.

44. The system according to claim 43, further comprising inserting at least one of an enterprise Java bean stub and an enterprise Java bean skeleton into the base environment.

45. The system according to claim 44, wherein the at least implementation class, enterprise Java bean stub, and enterprise Java bean skeleton is inserted into an archive in the base environment.

46. The system according to claim 41, wherein the asset is at least one of an entity bean asset, a reference data asset, and an entity data asset.

47. The system according to claim 46, wherein the asset includes an associated data structure having a table specification.

48. The system according to claim 47, further storing instructions adapted to be executed by the processor to perform the steps of:

determining whether a database table associated with the table specification exists in the base environment; and

creating the database table if the table does not exist.

49. The system according to claim 48, further storing instructions adapted to be executed by the processor to perform the step of:

importing data from the data structure into the database table.

50. The system according to claim 49, further storing instructions adapted to be executed by the processor to perform to perform the step of:

exporting the data from the data structure into a system database table.