Method and system for deploying web components between portals in a portal framework
View Patent ↗Disclosed are embodiments of a method, system and computer program product for deploying components of a site between systems in a portal framework. In one embodiment, file assets as well as non-file assets of at least one component of a site designated for export are stored as an export file. Non-file assets may be constructed as an extensible markup language fragment, such as an XML fragment, having a predetermined structure. In one embodiment, the site comprises a collection of software objects that can be manipulated by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects. The export file is transferred to a remote system such as a web portal. The assets, which are configured to operate on the remote system, are extracted from the export file to a plurality of locations on the remote system.
1. A computer-implemented method of deploying components of a site between systems, the method comprising the steps of:
storing assets of at least one component of a site designated for export as an individual export file, wherein the site comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
transferring the individual export file to a system at a remote location, wherein the system is a web portal capable of executing program instructions; and
extracting the assets from the individual export file to a plurality of locations on the system at the remote location, wherein the assets include file assets and non-file assets configured to operate on the web portal at the remote location.
2. The method according to claim 1 , further comprising querying a local system to identify one or more components associated with the site.
3. The method according to claim 1 , wherein each non-file asset is an extensible markup language fragment with a predetermined structure.
4. The method according to claim 3 , further comprising parsing the extensible markup language fragment.
5. The method according to claim 4 , further comprising instantiating each at least one non-file asset.
6. The method according to claim 1 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
7. The method according to claim 1 , further comprising collecting at least one file-asset of the component in the individual export file, wherein each file-asset is configured to operate on the system at the remote location.
8. The method according to claim 7 , further comprising querying a subsystem to identify one or more components associated with the site.
9. The method according to claim 8 , wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
10. The method according to claim 9 , wherein the subsystem collects each object and each file-asset.
11. A computer-implemented method of importing components of a site to a system at a remote location in a, portal framework, the method comprising the steps of:
extracting at least one object of a component from an individual export file of an exported site, wherein the exported site comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
wherein the at least one object includes at least one non-file asset configured to operate on the system at the remote location; and
storing each object of the component to a location on the system at the remote location.
12. The method according to claim 11 , further comprising transferring the individual export file to the system at the remote location.
13. The method according to claim 11 , further comprising parsing each non-file asset wherein each non-file asset is constructed as an extensible markup language fragment with a predetermined structure.
14. The method according to claim 11 , further comprising instantiating each non-file assets.
15. The method according to claim 11 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
16. The method according to claim 11 , further comprising extracting at least one file-asset of the component from the individual export file; and
storing each file-asset to a location on the system at the remote location.
17. The method according to claim 16 , wherein storing each object and file-asset is accomplished by a subsystem at the remote location, wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
18. A computer program product embodied in a computer readable medium for deploying a component of a site between systems in a portal framework, the computer readable medium carrying computer program instructions, executable by a processor, for performing the steps of:
designating a component of the site intended for export, wherein the site comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
collecting at least one object of the component in an individual export file;
wherein the at least one object includes at least one non-file asset configured to operate on the system at the remote location;
transferring the individual export file to a system at a remote location; and
extracting each object from the individual export file to a location on the system at the remote location.
19. The computer program product according to claim 18 , further comprising computer program instructions for performing the step of collecting the assets of the component.
20. The computer program product according to claim 19 , wherein designating the component for export further comprises querying a local system.
21. The computer program product according to claim 19 , wherein each non-file asset is constructed as an extensible markup language fragment with a predetermined structure.
22. The computer program product according to claim 21 , further comprising computer program instructions for performing the step of parsing each extensible markup language fragment.
23. The computer program product according to claim 22 , further comprising computer program instructions for performing the step of instantiating each non-file assets.
24. The computer program product according to claim 18 , wherein each non-file assets include at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
25. The computer program product according to claim 18 , further comprising computer program instructions for collecting at least one file-asset of the component in the individual export file, wherein each file-asset is configured to operate on the system at the remote location.
26. The computer program product according to claim 25 , wherein designating the component comprises querying a subsystem.
27. The computer program product according to claim 26 , wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
28. The computer program product according to claim 27 , wherein the subsystem collects each object and each file-asset.
29. A computer program product embodied in a computer readable medium for importing components of a site to a system at a remote location in a portal framework, the computer readable medium carrying computer program instructions, executable by a processor, for performing the steps of:
extracting at least one object of a component from the individual export file of an exported site wherein the at least one object includes at least one non-file asset configured to operate on the system at the remote location, wherein the exported site comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects; and
storing each object of the component to a location on the system at the remote location.
30. The computer program product according to claim 29 , further comprising transferring the individual export file to the system at the remote location.
31. The computer program product according to claim 29 , further comprising instantiating each non-file asset.
32. The computer program product according to claim 29 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
33. The computer program product according to claim 29 , further comprising
extracting at least one file-asset of the component from the individual export file;
and storing each file-asset to a location on the system at the remote location.
34. The computer program product according to claim 33 , wherein storing each object and file-asset is accomplished by a subsystem at the remote location, wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
35. A system for deploying a component of a site between systems in a portal framework, comprising:
a local system configured with a first deployment manager and operable to collect at least one object of a component of a site for deployment as an individual export file, wherein each object includes at least one non-file asset configured to operate on a system at a remote location;
a means for transferring the individual export file from the local system to a the system at the remote location; and
the system at the remote location configured with a second deployment manager and operable to extract each object from the individual export file to a location on the system at the remote location.
36. The system according to claim 35 , wherein the object is collected by a first component module.
37. The system according to claim 36 , wherein the first component module is further operable to query the local system to identify the component designated for export.
38. The system according to claim 36 , wherein the first component module is further operable to construct each non-file asset as an extensible markup language fragment with a predetermined structure.
39. The system according to claim 38 , wherein the second deployment manager further includes a second component module operable to parse each extensible markup language fragment.
40. The system according to claim 38 , wherein the second component module is further operable to instantiate each non-file assets.
41. The system according to claim 35 , wherein the second component module is further operable to extract each object of the component from the export file to a location on the system at the remote location.
42. The system according to claim 35 , wherein the non-file assets include at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
43. The system according to claim 35 , wherein the first deployment manager is further operable to collect at least one file-asset of the component in the individual export file, wherein each file-asset is configured to operate on the system at the remote location.
44. The system according to claim 43 , wherein the first deployment manager is further operable to query a subsystem.
45. The system according to claim 44 , wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
46. The system according to claim 45 , wherein the subsystem collects each object and each file-asset.
47. The system according to claim 41 , wherein the second deployment manager is further operable to:
extract at least one file-asset of the component from the individual export file; and store each file-asset to a location on the system at the remote location.
48. The system according to claim 47 , wherein the second deployment manager further includes a subsystem, wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
49. A system for importing a component of a site in a portal framework comprising:
a local system configured with a component module operable to:
extract at least one object of the component of the site from an individual export file, wherein each object includes at least one non-file asset configured to operate on the local system, wherein the site comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects, and wherein at least one non-file asset is constructed as an extensible markup language fragment having a predetermined structure;
parse the extensible markup language fragment;
instantiate, each non-file asset; and
store each object of the component to the local system.
50. The system according to claim 49 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
51. The system according to claim 49 , wherein the component module is further operable to:
extract at least one file-asset of the component from the individual export file; and store each file-asset to a location on the system at the remote location.
52. The system according to claim 51 , wherein the component further includes a subsystem, wherein the subsystem is configured to manage a type of component, wherein the type includes at least one of a site, module, template and style.
53. A computer-implemented method of deploying a component of a functioning application between systems, the method comprising the steps of:
designating a component of the functioning application intended for exports, wherein the functioning application comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
collecting a set of objects of the component of the functioning application designated for export in an individual export file;
transferring the individual export file to a system at a remote location; and
extracting each object from the individual export file to a location, wherein each object is configured to operate on the system at the remote location.
54. The method of claim 53 , wherein the component is a software component used by the application, a configuration of a software component or data used with a software component.
55. The method according of claim 54 , further comprising instantiating each object that is a non-file asset.
56. The method according to claim 54 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object and a user group object.
57. A computer program product embodied in a computer readable medium for deploying a component of a functioning application between systems in a portal framework, the computer readable medium carrying computer program instructions, executable by a processor, for performing the steps of:
designating a component of the functioning application intended for exports, wherein the functioning application comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
collecting at least one object of the component designated for export as in an individual export file, wherein the at least one object includes at least one non-file asset configured to operate on the system at the remote location;
transferring the individual export file to a system at a remote location; and
extracting the assets of the component from the individual export file to a plurality of locations on the system at the remote location.
58. The computer program product of claim 57 , wherein the component is a software component used by the application, a configuration of a software component or data used with a software component.
59. The computer program product according of claim 58 , wherein the computer program instructions are further executable for performing the step of: instantiating each object that is a non-file asset.
60. The computer program product according to claim 58 , wherein each non-file asset includes at least one of: a permissions object, a user preference object, a settings object, a menu object, an instantiated programming language object. and a user group object.
61. A computer-implemented method of deploying a functioning application between systems, comprising:
collecting a set of software components used by a first application on a first system in a set of individual export files, wherein the first application comprises a collection of software objects manipulatable by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects;
collecting a set of configurations for use with the set of software components in the set of individual export files;
collecting the data utilized by the software components in the set of individual export files;
collecting the set of individual export files into a group export file;
transferring the group export file to a second system at a remote location;
extracting the set of individual export files from the group export file;
extracting the set of software components, the set of configurations, and the data from the set of individual export files to create a second application on the second system, wherein the second application has the same state as the first application.
62. The method of claim 61 , wherein the first application is executing.