Extensible provider connection systems, methods and architecture

• US 10,015,273 B2
• Filed: 07/29/2015
• Issued: 07/03/2018
• Est. Priority Date: 07/29/2014
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open Text Sa Ulc (Open Text Corporation)
• Inventors: Jaskiewicz, Michael Gerard, Johnson, III, Claiborne Holt
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Tseng, Leon Y
• Application Number:
  US14/812,473
• Publication Number:
  US 20160036935A1
• Time in Patent Office: 1,070 Days
• Field of Search: 709217
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H01M 10/02 Details of electrodes H01M4/00; of non-active parts H01M50/00
• CPC Class Codes: H01M 10/052 Li-accumulators
• CPC Class Codes: H01M 10/0525 Rocking-chair batteries, i.e. batteries with lithium insertion or intercalation in both electrodes; Lithium-ion batteries
• CPC Class Codes: H01M 10/056 characterised by the materials used as electrolytes, e.g. mixed inorganic/organic electrolytes
• CPC Class Codes: H01M 10/0565 Polymeric materials, e.g. gel-type or solid-type
• CPC Class Codes: H01M 10/0566 Liquid materials
• CPC Class Codes: H01M 10/0568 characterised by the solutes
• CPC Class Codes: H01M 10/4257 Smart batteries, e.g. electronic circuits inside the housing of the cells or batteries
• CPC Class Codes: H01M 2220/30 Batteries in portable systems, e.g. mobile phone, laptop
• CPC Class Codes: H01M 2300/0025 Organic electrolyte
• CPC Class Codes: H01M 2300/0082 Organic polymers
• CPC Class Codes: H01M 4/131 Electrodes based on mixed oxides or hydroxides, or on mixtures of oxides or hydroxides, e.g. LiCoOx
• CPC Class Codes: H01M 4/136 Electrodes based on inorganic compounds other than oxides or hydroxides, e.g. sulfides, selenides, tellurides, halogenides or LiCoFy
• CPC Class Codes: H01M 4/505 of mixed oxides or hydroxides containing manganese for inserting or intercalating light metals, e.g. LiMn2O4 or LiMn2OxFy
• CPC Class Codes: H01M 4/525 of mixed oxides or hydroxides containing iron, cobalt or nickel for inserting or intercalating light metals, e.g. LiNiO2, LiCoO2 or LiCoOxFy
• CPC Class Codes: H01M 4/5825 Oxygenated metallic salts or polyanionic structures, e.g. borates, phosphates, silicates, olivines
• CPC Class Codes: H01M 50/569 Constructional details of current conducting connections for detecting conditions inside cells or batteries, e.g. details of voltage sensing terminals battery terminal connectors with integrated measuring arrangements G01R31/364
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: Y02E 60/10 : Energy storage using batteries
• CPC Class Codes: Y02T 10/70 : Energy storage systems for electromobility, e.g. batteries

Abstract

A system is disclosed for delivering dynamically-rendered web experiences via implementing a provider interface in a provider framework where the interface defines supported behaviors for interfacing with external content in an external content repository, and where the interface defines at least one external object and specifies at least one method for implementing the supported behaviors for the object. The provider framework discovers supported behaviors upon instantiation of a provider implementation class embodied in implementation of the provider interface. A connection is engaged to the external repository with the supported behaviors using the interface to connect to and expose the external content. During web content delivery, the system accesses the provider connection and dynamically integrates external content with system-managed content in a delivered web page.

Claims

1. A web experience management (WEM) system for delivering dynamically-rendered web experiences, the WEM system comprising:

a computing device having a memory, a processor, and a non-transitory computer-readable medium storing a set of computer-executable instructions, which when executed by the processor performs the steps of;

configuring an implementation of a provider interface into a provider framework of the WEM system, wherein;

the provider interface defines supported provider implementation behaviors for interfacing with a content repository external to the WEM system;

the external content repository is associated with a provider system and contains external content external to the WEM system; and

the implementation of the provider interface comprises defining at least one external content object of the provider system and specifying at least one method for implementing the supported provider implementation behaviors of the at least one external content object of the provider system;

the provider framework of the WEM system discovering the supported provider implementation behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface;

based at least in part on the supported provider implementation behaviors supported by the implementation of the provider interface configured into the provider framework of the WEM system, creating a provider connection to the external content repository such that the external content of the provider system is accessible by the WEM system through the provider connection; and

at a web content delivery stage, the WEM system accessing the external content through the provider connection to the external content repository and dynamically integrating the external content of the provider system with content managed by the WEM system in a web page.

2. The WEM system of claim 1, wherein the external content comprises native content objects of the provider system, and wherein accessing the external content through the provider connection further comprises accessing the native content objects of the provider system in their native representation.

3. The WEM system of claim 1, wherein creating the provider connection includes generating an external content interface to define behaviors for the external content, and wherein the behaviors comprise methods to display the external content.

4. The WEM system of claim 3, wherein generating the external content interface includes generating a search interface to enable searching of the external content residing in the external content repository, wherein searching of the external content controls at least one of interaction with the external content or display of the external content in the web page.

5. The WEM system of claim 2, wherein the external content repository comprises a plurality of repositories, and wherein external content of at least one of the repositories and external content of at least one other of the repositories is characterized by at least one of different native representations or different native formats.

6. The WEM system of claim 2, wherein the computer-executable instructions further comprise at least one of:

enriching the external content using managed content or components defined in the WEM system and enabling the display of the enriched external content;

or

integrating the external content with a web site display framework defined in the WEM system, wherein the web site display framework includes a template for displaying external content, and the template includes web site display regions for organizing the display of external content and components for defining the display of external content.

7. A method for delivering dynamically-rendered web experiences, the method comprising:

configuring an implementation of a provider interface into a provider framework of a web experience management (WEM) system running on one or more server machines, wherein;

the provider interface defines supported provider implementation behaviors for interfacing with a provider system external to the WEM system;

the provider system contains provider data; and

the implementation of the provider interface comprises defining at least one external data object and specifying at least one method for implementing the supported provider implementation behaviors for the at least one external data object;

the provider framework of the WEM system discovering the supported provider implementation behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface;

based at least in part on the supported provider implementation behaviors supported by the implementation of the provider interface configured into the provider framework of the WEM system, creating a provider connection to the provider data such that the provider data is accessible by the WEM system through the provider connection; and

at a web content delivery stage, the WEM system accessing the provider data through the provider connection and dynamically integrating the provider data with content managed by the WEM system in a web page.

8. The method of claim 7, wherein accessing the provider data through the provider connection further comprises connecting to and exposing metadata associated with the provider data, and wherein the metadata associated with the provider data is integrated with the content managed by the WEM system in the web page.

9. The method of claim 8, wherein at least one of the content managed by the WEM system, the provider data, or the metadata associated with the provider data comprises template data for formatting display of the web page.

10. The method of claim 7, wherein the provider data comprises a native representation of the provider data.

11. The method of claim 10, wherein the web page contains at least a fragment of the native representation of the provider data and wherein the fragment of the native representation is cached at a data storage location that is local to the WEM system.

12. The method of claim 10, wherein the native representation comprises at least one of:

a JavaBean encapsulating a plurality of objects into a single object, wherein the plurality of objects is presented in a display view via presentation services of the WEM system;

or

a JavaScript Object Notation (JSON) string comprising attribute-value pairs, wherein the attribute-value pairs are presented in the display view via presentation services running on a provider connection computer of the provider system.

13. The method according to claim 7, wherein creating the provider connection further comprises generating an instance of a provider connection type and assigning the provider connection type instance to a node in the provider system, and wherein the provider connection type instance defines a navigation mount point relative to a hierarchy residing on the provider system.

14. The method according to claim 13, further comprising at least one of:

placing the provider connection type instance with the content managed by the WEM system in a site tree comprising a web page;

or

configuring a page template for the provider data in the web page based on the provider connection type instance.

15. A computer program product for delivering dynamically-rendered web experiences, the computer program product comprising at least one non-transitory computer-readable storage medium storing instructions translatable by a computing device, which when translated by the computing device performs the processing steps of:

configuring an implementation of a provider interface into a provider framework of a web experience management (WEM) system, wherein;

the provider interface defines supported provider implementation behaviors for interfacing with a content repository external to the WEM system;

the external content repository is associated with a provider system and contains external content external to the WEM system; and

the implementation of the provider interface comprises defining at least one external content object of the provider system and specifying at least one method for implementing the supported provider implementation behaviors of the at least one external content object of the provider system;

the provider framework of the WEM system discovering the supported provider implementation behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface;

based at least in part on the supported provider implementation behaviors supported by the implementation of the provider interface configured into the provider framework of the WEM system, creating a provider connection to the external content repository such that the external content of the provider system is accessible by the WEM system through the provider connection; and

at a web content delivery stage, accessing the external content through the provider connection to the external content repository and dynamically integrating the external content of the provider system with content managed by the WEM system in a web page.

16. The computer program product of claim 15, wherein the external content comprises native content objects of the provider system, and wherein accessing the external content through the provider connection further comprises accessing the native content objects of the provider system in their native representation.

17. The computer program product of claim 16, wherein creating the provider connection includes generating an external content interface to define behaviors for the external content, and wherein the behaviors comprise methods to display the external content.

18. The computer program product of claim 17, wherein generating the external content interface includes generating a search interface to enable searching of the external content residing in the external content repository, wherein searching of the external content controls at least one of interaction with the external content or display of the external content in the web page.

19. The computer program product of claim 16, wherein the external content repository comprises a plurality of repositories, and wherein external content of at least one of the repositories and external content of at least one other of the repositories is characterized by at least one of different native representations or different native formats.

20. The computer program product of claim 16, wherein the computer-executable instructions further comprise at least one of:

enriching the external content using managed contents or components defined in the WEM system and enabling the display of the enriched external content;

or

integrating the external content with a web site display framework that includes a template for displaying external content, wherein the template includes web site display regions for organizing the display of external content and components for defining the display of external content.