Claims
- 1. An extended environment data structure that is part of a digital asset, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptors that provide a unique identification of the digit asset on the networks; one or more base environment descriptors that identify a required base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 2. A data structure, as in claim 1, where the common descriptors include any one or more of the following: a digital asset name of the digital asset, a unique fully qualified name of the digital asset, an address of the digital asset, a size of the digital asset, a volatility descriptor of the digital asset, a common runnable descriptor of the digital asset, a user type descriptor of the digital asset, a security descriptor of the digital asset, a price descriptor of the digital asset, the independent deployment of the digital asset, and priority of the digital asset.
- 3. A data structure, as in claim 1, where the base environment include any one or more of the following: one or more DBMS, one or more application servers, one or more Web servers, one or more JMS implementations, one or more J2EE application servers, one or more browsers, one or more Java Virtual Machine (JVM) instantiations, one or more operating systems, systems, sub-systems, applications, sub-applications, components, modules, and functions.
- 4. A data structure, as in claim 1, where the whole is defined by any one or more of the following: a graph, a containment graph, a tube graph, a call graph, a pure representation expressible as a graph.
- 5. An extended environment data structure that is part of a digital asset, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptors that provide a unique identification of the digit asset on the networks; one or more asset dependency descriptors that identify one or more associated digital assets, the associated digital assets being associated with the digital asset by means of a joint membership as parts of a whole; and one or more base environment descriptors that identify a base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 6. A data structure, as in claim 5, where the asset dependency descriptors include any one or more of the following: one or more names of other digital assets on which the digital asset is dependent, an asset identifier, and one or more unique fully qualified names of other digital assets on which the digital asset is dependent.
- 7. An extended environment data structure that is part of a digital asset, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptors that provide a unique identification of the digit asset on the networks; one or more asset dependency descriptors that identify one or more associated digital assets, the associated digital assets being associated with the digital asset by means of a joint membership as parts of a whole; one or more base environment descriptors that identify a base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer; and one or more EIS server dependencies descriptors that identify an EIS execution environment on the respective EIS on which the asset resides.
- 8. A data structure, as in claim 1, 5, and 7, where one or more of the EIS server dependencies descriptors identify an EIS execution environment on the respective EIS from which the asset is transformed into a neutral environment form.
- 9. A data structure, as in claim 1, 5, and 7, where one or more of the EIS server dependencies descriptors identify an EIS execution environment on the respective EIS from which the asset is prepared for transformation into a neutral environment.
- 10. A data structure, as in claim 1, 5, and 7, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 11. A data structure, as in claim 1, 5, and 7, where one or more EIS server dependencies identified by one or more of the EIS server dependencies descriptors include one or more of the following: EIS operating systems, EIS database management systems (DBMS), EIS servers, EIS application servers, EIS web application servers, one or more general business applications, one or more accounting applications, customer relationship management systems (CRM), business to business (B2B) systems, supply chain management systems, business to customer (B2C) system, order fulfillment systems, electronic shopping systems, one or more Enterprise Application Integration systems, one or more legacy interfaces, one or more Java Connector Framework (JCF) connectors, one or more JCF connectors for legacy interfaces, and message oriented middleware applications.
- 12. A data structure, as in claim 11, where the EIS server dependencies include one or more of the following: one or more DBMS products, one or more Oracle DBMS, one or more Sybase DBMS, and one or more DB2 DBMS.
- 13. A data structure, as in claim 1, 5, and 7, where zero or more of the base environment descriptors and zero or more of the EIS server dependencies descriptors are capable of being compared independently to a neutral form in order to determine whether a transform of the digital asset is required for the asset to be deployed on the respective target computer.
- 14. A data structure, as in claim 1, 5, and 7, where one or more of the base environment descriptors and one or more of the EIS server dependencies descriptors are capable of being compared to determine whether a transform of the digital asset is required for the asset to be deployed on the respective target computer.
- 15. A data structure, as in claim 13 and 14, where the transform of the digital asset includes a transformation of data in a logic/data section of the digital asset.
- 16. A data structure, as in claim 1, 5, and 7, further comprising one or more reference descriptors.
- 17. A data structure, as in claim 16, where the reference descriptors include any one or more of the following: a reference link descriptor, a reference file descriptor, and a reference directory descriptor.
- 18. A data structure, as in claim 16, where the reference link descriptor provides a world-wide-web (WWW) address that has contents used for processing of the digital asset.
- 19. A data structure, as in claim 16, where the reference link descriptor provides a world-wide-web (WWW) address that has contents used during execution of the digital asset.
- 20. A data structure, as in claim 16, where the reference file descriptor is a unique fully qualified name of a file required for reference by the digital asset.
- 21. A data structure, as in claim 16, where the reference directory descriptor provides an additional address information that is used to locate one or more of the associated digital assets.
- 22. A data structure, as in claim 1, 5, and 7, further comprising one or more transform descriptors that enables a transform of the digital asset from the EIS execution environment to the base execution environment.
- 23. A data structure, as in claim 22, where the transform descriptor includes a properties descriptor that provides information required for use of the digital asset on an operating system of the base execution environment.
- 24. A data structure, as in claim 22, where the transform descriptor includes a format descriptor that provides information required for use of the digital asset on an operating system of the base execution environment.
- 25. A data structure, as in claim 22, where the transform descriptor includes a registry descriptor that provide information required for use of the digital asset on a Window's operating system on the base execution environment.
- 26. A data structure, as in claim 1, 5, and 7, further comprising one or more asset type descriptors.
- 27. A data structure, as in claim 26 where the asset type descriptors include any one or more of the following asset types: static content (SC), dynamic content (DC), enterprise Java beans (EJB), reference data (RD), session bean (SB), entity bean (EB), entity data (ED), Java class (JC), Java beans (JB), Java Connector Framework (JCF), and Java applet (JA).
- 28. A data structure, as in claim 1, 5, and 7, further comprising one or more asset category descriptors.
- 29. A data structure, as in claim 28, where the asset category descriptors include any one or more of the following: a presentational descriptor, a transactional descriptor, an integration connector descriptor, and a relational data descriptor.
- 30. A data structure, as in claim 28, where the asset category descriptors include any one or more of the following: a content descriptor, a presentational component descriptor, a transactional component descriptor, an integration connector component descriptor, an object data descriptor, and a relational data descriptor.
- 31. A data structure, as in claim 1, 5, and 7, further comprising one or more asset class descriptors.
- 32. A data structure, as in claim 31, where the asset class descriptors include any one or more of the following: base, Java, non-Java, language, and non-language.
- 33. A data structure, as in claim 1, 5, and 7, further comprising one or more package relationship descriptors that represents a part-whole relationship between the digital asset and one or more packages containing the digital asset.
- 34. A data structure, as in claim 33, where the package relationship descriptors represents at least the following three relationships in the part-whole relationship: a mandatory part-whole relationship, a shared part-whole relationship, and a root part-whole relationship.
- 35. A data structure, as in claim 1, 5, and 7, further comprising one or more security descriptors.
- 36. A data structure, as in claim 35, where the security descriptors include any one or more of the following functions: encryption, authentication, authorization, and access control.
- 37. A data structure, as in claim 1, 5, and 7, further comprising one or more runnable descriptors.
- 38. A data structure, as in claim 37, further comprising one or more of the runnable descriptors that include a neutral format that would enable the deferment of the assignment to a target execution environment for the digital asset.
- 39. A data structure, as in claim 37, further comprising one or more of the runnable descriptors that include a target execution environment for the digital asset.
- 40. A data structure, as in claim 37, further comprising one or more of the runnable descriptors that include an EIS execution environment and a target execution environment for the digital asset.
- 41. A data structure, as in claim 1, 5, and 7, further comprising one or more non-runnable descriptors.
- 42. A data structure, as in claim 41, further comprising one or more non-runnable descriptors that include description of the base execution environment for the digital asset.
- 43. A data structure, as in claim 41, further comprising one or more of the non-runnable descriptors that include a neutral format that would enable the deferment of the assignment to a target execution environment for the digital asset.
- 44. A data structure, as in claim 41, further comprising one or more non-runnable descriptors that include description of the EIS execution environment and the base execution environment for the digital asset.
- 45. A data structure, as in claim 1, 5, and 7, further comprising one or more personalization descriptors that enable the digital asset to be customized upon delivery to one or more of the base execution environments.
- 46. A data structure, as in claim 45, where the personalization descriptors include one or more data keys, being derived from a directory service, that establishes a linkage among data elements in the EIS execution environment.
- 47. A data structure, as in claim 46, where the directory service is one or more of the following in combination or a federated hierarchy: an LDAP server, Single-Sign-On service, and/or JNDI service.
- 48. A data structure, as in claim 46, where the linkage of the data elements resolve to a DBMS query in which one or more EIS databases are partitioned specifically for the needs of one or more target environments.
- 49. A data structure, as in claim 46, where the linkage of the data elements resolve to one or more content related assets that are partitioned specifically for the needs of one or more target environments.
- 50. A data structure, as in claim 46, where the linkage of the data elements resolve to one or more application related assets that are partitioned specifically for the needs of one or more target environments.
- 51. A data structure, as in claim 50, where the application related assets are one or more of the following: presentational components and/or transactional components.
- 52. A data structure, as in claim 50, where the application related assets are one or more of the following: JSP, Java Servlet, and/or Java EJB.
- 53. A data structure, as in claim 45, where the personalization descriptors include one or more data keys that establish a linkage among data elements in the EIS execution environment.
- 54. A data structure, as in claim 45, where the personalization descriptors include one or more data keys that establish a linkage among logic elements in the EIS execution environment.
- 55. A data structure, as in claim 1, 5, and 7, further comprising one or more pricing descriptors.
- 56. A data structure, as in claim 55, where the pricing descriptors describe information about any one or more of the following: a price, a price scheme (subscription, pay to own, pay to use, one time payment), a payment detail, payment method, a check description, a credit card description, and a credit card number.
- 57. A data structure, as in claim 1, 5, and 7, further comprising one or more target information descriptors.
- 58. A data structure, as in claim 57, where the target information descriptors describe any one or more of the following: well known user, an anonymous user, one or more user groups, an entire user group, a target machine, an identifiable segment of target machines a collection of target machines, an internet protocol address mask, and a group of target computers in a node collection structure.
- 59. A data structure, as in claim 1, 5, and 7, further comprising one or more schema descriptors.
- 60. A data structure, as in claim 59, where the schema descriptors provide information that describe any one or more of the following:
database table names and definitions, database column names and definitions, database key identifiers and value ranges, database view names and definitions, and other well known database schema elements.
- 61. A data structure, as in claim 1, 5, and 7, further comprising one or more metadata descriptors.
- 62. A data structure, as in claim 61, where the metadata descriptors provide information that describe any or more of the following:
repository object definitions, scope object definitions, module object definitions, operation object definitions, exception object definitions, constant object definitions, properties object definitions, attribute object definitions, relationship object definitions, type object definitions, and other well known metadata object definitions.
- 63. A data structure, as in claim 1, 5, and 7, further comprising one or more distribution logic descriptors, each having one or more transactions rules and one or more concurrency rules.
- 64. A data structure, as in claim 63, where the transactions rules specify any of a number and a frequency of times that the digital asset can be distributed to one or more target computers.
- 65. A data structure, as in claim 64, where the concurrency rules specify whether or not there are any restrictions on distribution of the digital asset with respect to the distribution of one or more other digital asset.
- 66. A data structure, as in claims 1, 5, and 7, where the data structure is received from one or more network connections.
- 67. A data structure, as in claims 1, 5, and 7, where the data structure is sent over one or more network connections.
- 68. A data structure, as in claims 1, 5, and 7, where the data structure is stored on one or more memories.
- 69. A data structure, as in claims 1, 5, and 7, where information in the data structure is modified at one or more locations on one or more networks as the digital asset is distributed over the networks.
- 70. An extended environment data structure that is part of a digital asset, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptor means for providing a unique identification of the digit asset on the networks; one or more asset dependency descriptor means for identifying one or more associated digital assets, the associated digital assets being associated with the digital asset by means of a joint membership as parts of a whole; and one or more base environment descriptor means for identifying a base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 71. A computer program product that contains an extended environment data structure that is part of a digital asset, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptors that provide a unique identification of the digit asset on the networks; one or more base environment descriptors that identify a base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 72. A computer program product, as in claim 71, further comprising:
one or more asset dependency descriptors that identify one or more associated digital assets, the associated digital assets being associated with the digital asset by means of a joint membership as parts of a whole.
- 73. A memory structure having an extended environment data structure that is part of a digital asset stored on the memory structure, the digital asset capable of being transmitted over one or more multi-tiered networks, the data structure comprising:
one or more common descriptors that provide a unique identification of the digit asset on the networks; one or more base environment descriptors that identify a base execution environment on one or more target computers, the base execution environment being required to execute the digital asset on the respective target computer, where the base execution environment comprises zero or more other digital assets deployed to the respective target computer from one or more or the Enterprise Information Systems (EIS).
- 74. A memory structure, as in claim 73, further comprising:
one or more asset dependency descriptors that identify one or more associated digital assets, the associated digital assets being associated with the digital asset by means of a joint membership as parts of a whole.
PRIORITY DOCUMENTS
[0001] This application claims priority to the provisional U.S. patent application No. 60/229,685, entitled “Distributed Internet Services Provisional Filing”, filed on Sep. 1, 2000 to Chen et al. This provisional application is herein incorporated by reference in its entirety.
[0002] The following references are related to this patent application and are herein incorporated by reference in their entirety:
[0003] provisional U.S. patent application No. 60/236,864 entitled “Distributed Internet Server” to Pace et al., filed Sep. 29, 2000;
[0004] provisional U.S. patent application No. 60/237,179 entitled “Business Plan and Business Plan Executive Summary” to Chen et al., filed Oct. 2, 2000;
[0005] provisional U.S. patent application No. 60/254,377 entitled “Distributed Internet Services provisional filing II” to Pace et al., filed Dec. 8, 2000;
[0006] provisional U.S. patent application No. 60/262,288 entitled “Data Structure, Architecture, Apparatus, and Program Product Capable of Being Distributed to and Executed on Different Network Tiers and on Various Computer Platforms and Environment” to Pace et al., filed Jan. 17, 2001;
[0007] U.S. patent application Ser. No. ______, entitled “Extended Environment Data Structure for Distributed Digital Assets Over Multi-Tiered Networks”, to Pace et al., filed ______;
[0008] U.S. patent application Ser. No. ______, entitled “Server System and Method for Discovering Digital Assets in Enterprise Information Systems”, to Bobick et al., filed ______;
[0009] U.S. patent application Ser. No. ______, entitled “Server System and Method for Exporting Digital Assets in Enterprise Information Systems”, to Pace et al. filed ______;
[0010] U.S. patent application Ser. No. ______, entitled “System and Method for Transactional Deployment J2EE Web Components, Enterprise Java Bean Components, and Application Data over Multi-tiered Computer Networks”, to Pace et al., filed on ______;
[0011] U.S. patent application Ser. No. ______, entitled “Server System and Method for Distributing and Scheduling Modules to be Executed on Different Tiers of a Network”, to Pace et al. filed on ______;
[0012] U.S. patent application Ser. No. ______, entitled “Data Structure, Architecture, Apparatus, and Program Product Capable of Being Distributed to and Executed on Different Network Devices and on Various Computer Platforms and Environments”, to Pace et al. filed on ______;
[0013] U.S. patent application Ser. No. ______, entitled “System and Method for Distributing Assets to Multi-Tiered Network Nodes, to Pizzorni et al. filed on ______;
[0014] U.S. patent application Ser. No. ______, entitled “Method and System for Deploying An Asset Over a Multi-Tiered Network”, to Pace et al. filed on ______;
[0015] U.S. patent application Ser. No. ______, entitled “System and Method for Translating an Asset for Distribution Over Multi-Tiered Networks (Processing)” to Pace et al. filed on ______;
[0016] U.S. patent application Ser. No. ______, entitled “System and Method for Synchronizing Assets on Multi-Tiered Networks, to Pace et al. filed on ______;
[0017] U.S. patent application Ser. No. ______, entitled “Method and System for Deploying an Asset Over a Multi-Tiered Network”’ to Pace et al. filed on ______;
[0018] U.S. patent application Ser. No. ______, entitled “System and Method for Adjusting the Distribution of an Asset Over a Multi-Tiered Network”, to Pace et al. filed on ______;
[0019] U.S. patent application Ser. No. ______, entitled “System and Method for Bridging Assets to Network Nodes on Multi-Tiered Networks”, to Pace et al. filed on ______;
[0020] U.S. patent application Ser. No. ______, entitled streaming, to Pace et al. filed on ______;
[0021] U.S. patent application Ser. No. ______, entitled “System, Method, and Data Structure for Packaging Assets for Processing and Distribution on Multi-Tiered Networks”, to Bobick et al. filed on ______;
[0022] U.S. patent application Ser. No. ______, entitled System and Method for Transactional and Fault-Tolerant Distribution of Digital Assets Over Multi-Tiered Computer Networks, to Bobick et al. filed on ______;
[0023] U.S. patent application Ser. No. ______, entitled “System and Method for Collaboration Using Web Browsers”, to Chen et al. filed on ______; and
[0024] PCT Patent application number ______, entitled “System, Method, Uses, Products, Program Products, and Business Methods for Distributed Internet and Distributed Network Services”, to Pace et al. filed on ______.
[0025] Priority is also claimed to these documents for any matter not disclosed in the filing serial No. 60/229,685, incorporated above.
Provisional Applications (5)
|
Number |
Date |
Country |
|
60229685 |
Sep 2000 |
US |
|
60236864 |
Sep 2000 |
US |
|
60237179 |
Oct 2000 |
US |
|
60254377 |
Dec 2000 |
US |
|
60262288 |
Jan 2001 |
US |