System and method for providing SPI extensions for content management system

• US 8,316,025 B2
• Filed: 04/08/2011
• Issued: 11/20/2012
• Est. Priority Date: 09/26/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: McVeigh, Ryan Sean, Roth, Steven Leslie, Patadia, Jalpesh, Saarva, Tanya, Zhou, Xiaojiang, Posner, Brad
• Primary Examiner(s): Casanova, Jorge A
• Application Number:
  US13/083,332
• Publication Number:
  US 20110184929A1
• Time in Patent Office: 592 Days
• Field of Search: 707/736, 707/781
• US Class Current: 707/736
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

A virtual content repository (VCR) is a logical representation of one or more individual content repositories. The VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to one or more individual content repositories. The API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR. A SPI adapter can be interposed between the at least one non-compliant repository in the VCR and the SPI. The SPI adapter can map a request to the non-compliant repository and provide content received from the non-compliant repository to originators of the requests.

Claims

1. A method for providing a content management system, the method comprising:

providing a virtual content repository (VCR) that is a logical representation of a plurality of content repositories, wherein the VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to the plurality of content repositories, wherein the common API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR and isolates direct interaction with the plurality of content repositories from the common API;

allowing at least one repository of the plurality of content repositories to be not compliant with the SPI of the content management system, wherein the at least one non-compliant repository is associated with a separate API that provides direct access to content in the at least one non-compliant repository;

interposing an adapter between the separate API associated with the at least one non-compliant repository and the SPI, wherein the adapter maps one or more methods in the common API to the separate API associated with the at least one non-compliant repository, and wherein the adapter allows the VCR to model content in the plurality of content repositories and to provide uniform content services;

exposing only a subset of features and/or capabilities provided by the at least one non-compliant repository via the separate API using the adapter, and allowing at least one method provided in the separate API associated with the at least one non-compliant repository to be not exposed to the common API;

receiving a request from one or more originator, at the common API that is associated with the SPI, to access content in both at least one compliant repository of the plurality of content repositories and the at least one non-compliant repository;

mapping the request to the at least one compliant repository via the SPI, and to the at least one non-compliant repository via the SPI and the adapter; and

combining the content received from both the at least one compliant repository and the at least one non-compliant repository, and providing the combined content to the one or more originators of the request based upon the VCR.

2. The method of claim 1, further comprising:

relating structured content and unstructured content into a searchable corpus that does not comply with the SPI of the content management system.

3. The method of claim 1, further comprising:

configuring a software adapter interposed between the non-compliant repository and the SPI such that the non-compliant repository is capable of communicating with the SPI through the adapter.

4. The method of claim 1, further comprising:

translating an object of the SPI into an object of the non-compliant repository and passing the object to the non-compliant repository.

5. The method of claim 1, further comprising:

translating an API invocation to the SPI into an API of the non-compliant repository and passing the invocation to the API to the non-compliant repository.

6. The method of claim 1, further comprising:

allowing the common API to provide at least one extra method that is not provided in the separate API associated with the at least one non-compliant repository.

7. The method of claim 1, further comprising:

applying a security model for controlling access to the plurality of content repositories in the VCR.

8. The method of claim 7, further comprising:

applying a different security model for controlling access to the at least one non-compliant repository.

15. The method of claim 1, further comprising:

selecting a security policy to be applied to the request.

16. The method of claim 1, further comprising:

applying a security mechanism to only a portion of the content received from the non-compliant repository upon receiving the request.

17. The method of claim 1, further comprising:

redacting the content received from the non-compliant repository to make it permissible according to a selected security policy.

9. A machine-readable non-transitory storage medium storing one or more sequences of instructions for providing a content management system in a content management system, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

providing a virtual content repository (VCR) that is a logical representation of a plurality of content repositories, wherein the VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to the plurality of content repositories, wherein the common API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR and isolates direct interaction with the plurality of content repositories from the common API;

allowing at least one repository of the plurality of content repositories to be not compliant with the SPI of the content management system, wherein the at least one non-compliant repository is associated with a separate API that provides direct access to content in the at least one non-compliant repository;

interposing an adapter between the separate API associated with the at least one non-compliant repository and the SPI, wherein the adapter maps one or more methods in the common API to the separate API associated with the at least one non-compliant repository, and wherein the adapter allows the VCR to model content in the plurality of content repositories and to provide uniform content services;

exposing only a subset of features and/or capabilities provided by the at least one non-compliant repository via the separate API using the adapter, and allowing at least one method provided in the separate API associated with the at least one non-compliant repository to be not exposed to the common API;

receiving a request from one or more originator, at the common API that is associated with the SPI, to access content in both at least one compliant repository of the plurality of content repositories and the at least one non-compliant repository;

mapping the request to the at least one compliant repository via the SPI, and to the at least one non-compliant repository via the SPI and the adapter; and

combining the content received from both the at least one compliant repository and the at least one non-compliant repository, and providing the combined content to the one or more originators of the request based upon the VCR.

10. The machine-readable medium as recited in claim 9, further comprising instructions for carrying out the step of:

relating structured content and unstructured content into a searchable corpus that does not comply with the SPI of the content management system.

11. The machine-readable medium as recited in claim 9, further comprising instructions for carrying out the step of:

configuring a software adapter interposed between the non-compliant repository and the SPI such that the non-compliant repository is capable of communicating with the SPI through the adapter.

12. The machine-readable medium as recited in claim 9, further comprising instructions for carrying out the step of:

translating an object of the SPI into an object of the non-compliant repository and passing the object to the non-compliant repository.

13. The machine-readable medium as recited in claim 9, further comprising instructions for carrying out the step of:

translating an API invocation to the SPI into an API of the non-compliant repository and passing the invocation to the API to the non-compliant repository.

14. An apparatus for providing a content management system, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

providing a virtual content repository (VCR) that is a logical representation of a plurality of content repositories, wherein the VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to the plurality of content repositories, wherein the common API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR and isolates direct interaction with the plurality of content repositories from the common API;

allowing at least one repository of the plurality of content repositories to be not compliant with the SPI of the content management system, wherein the at least one non-compliant repository is associated with a separate API that provides direct access to content in the at least one non-compliant repository;

interposing an adapter between the separate API associated with the at least one non-compliant repository and the SPI, wherein the adapter maps one or more methods in the common API to the separate API associated with the at least one non-compliant repository, and wherein the adapter allows the VCR to model content in the plurality of content repositories and to provide uniform content services;

exposing only a subset of features and/or capabilities provided by the at least one non-compliant repository via the separate API using the adapter, and allowing at least one method provided in the separate API associated with the at least one non-compliant repository to be not exposed to the common API;

receiving a request from one or more originator, at the common API that is associated with the SPI, to access content in both at least one compliant repository of the plurality of content repositories and the at least one non-compliant repository;

mapping the request to the at least one compliant repository via the SPI, and to the at least one non-compliant repository via the SPI and the adapter; and

combining the content received from both the at least one compliant repository and the at least one non-compliant repository, and providing the combined content to the one or more originators of the request based upon the VCR.