Extensible Provider Connection Systems, Methods and Architecture
First Claim
1. A web experience management (WEM) system for delivering dynamically-rendered web experiences, the 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 system, wherein;
the provider interface defines supported behaviors for interfacing with a content repository external to the system;
the external content repository contains external content; and
the implementation of the provider interface comprises defining at least one external content object and specifying at least one method for implementing the supported behaviors of the external content object;
the provider framework discovering the supported behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface;
engaging a provider connection to the external content repository with the supported behaviors using the provider interface to connect to and expose the external content; and
at a web content delivery stage, the system accessing the provider connection and dynamically integrating external content with system-managed content in a delivered web page.
4 Assignments
0 Petitions
Accused Products
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.
13 Citations
20 Claims
-
1. A web experience management (WEM) system for delivering dynamically-rendered web experiences, the 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 system, wherein; the provider interface defines supported behaviors for interfacing with a content repository external to the system; the external content repository contains external content; and the implementation of the provider interface comprises defining at least one external content object and specifying at least one method for implementing the supported behaviors of the external content object; the provider framework discovering the supported behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface; engaging a provider connection to the external content repository with the supported behaviors using the provider interface to connect to and expose the external content; and at a web content delivery stage, the system accessing the provider connection and dynamically integrating external content with system-managed content in a delivered web page. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
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 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 behaviors for the external data object; the provider framework discovering the supported behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface; engaging a provider connection to the provider data with the supported behaviors using the provider interface to connect to and expose provider data; and at a web content delivery stage, the WEM system accessing the provider connection and dynamically integrating provider data with WEM-managed data in a delivered web page. - View Dependent Claims (8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer program product for delivering dynamically-rendered web experiences, the computer program product comprising at least one computer-readable 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, wherein; the provider interface defines supported behaviors for interfacing with a content repository external to the system; the external content repository contains external content; and the implementation of the provider interface comprises defining at least one external content object and specifying at least one method for implementing the supported behaviors of the external content object; the provider framework discovering the supported behaviors upon instantiation of at least one provider implementation class contained in the implementation of the provider interface; engaging a provider connection to the external content repository with the supported behaviors using the provider interface to connect to and expose the external content; and at a web content delivery stage, accessing the provider connection and dynamically integrating external content with managed content in a delivered web page. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification