System, method and program product for a content viewer portlet

• US 7,818,676 B2
• Filed: 09/22/2005
• Issued: 10/19/2010
• Est. Priority Date: 09/22/2005
• Status: Expired due to Fees

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Baker, Gregory L., Bell, Donald S., Gong, Yixing
• Primary Examiner(s): Pitaro; Ryan F
• Application Number:
  US11/232,472
• Publication Number:
  US 20070067712A1
• Time in Patent Office: 1,853 Days
• Field of Search: 715/742
• US Class Current: 715/744
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A system, method and program product for creating a customized content viewer portlet from a content viewer portlet template. The system comprises a content viewer portlet template that is imported into a workbench. The content viewer portlet template includes a persistent interface component, a model component, a view component and a controller component. The persistent interface component is configured to connect to and retrieve data from a content management system, with the retrieved data being stored in the model component. The view component is configured to retrieve the data from the model component and to display the data as content items. The controller component is configured to invoke methods to be executed by the persistent interface component and the view component in response to a user request, such that the content viewer portlet template is transformed into the customized content viewer portlet that can be installed into a desired portal.

Claims

1. A system for creating a customized content viewer portlet from a content viewer portlet template, said system comprising:

a central processing unit (CPU), a computer readable memory, and a computer readable storage media;

first program instructions to instantiate a workbench;

second program instructions to instantiate a content viewer portlet template imported into said workbench;

third program instructions to instantiate a persistent interface component of said content viewer portlet template being configured to connect to and retrieve requested data from a back-end content management system;

fourth program instructions to instantiate a model component of said content viewer portlet template being coupled to said persistent interface component, said model component having an internal computational representation that correlates to an external taxonomy in a plurality of content management areas, wherein said model component incorporates said requested data retrieved from said back-end content management system into a current set of data beans;

fifth program instructions to instantiate a view component of said content viewer portlet template coupled to said model component, said view component being configured to retrieve said requested data incorporated into said model component and to display said requested data retrieved as one or more content items; and

sixth program instructions to instantiate a controller component of said content viewer portlet template coupled to each of said persistent interface component and said view component, said controller component being configured to invoke a plurality of methods to be executed by each of said persistent interface component and said view component in response to a user request, such that said content viewer portlet template is transformed into said customized content viewer portlet that can be installed into a desired portal, wherein said controller component determines whether said model component has said requested data pertaining to said user request, and if said model component has said requested data, said controller component invokes one of said plurality of methods to be executed by said view component to retrieve said requested data from said model component and to display said requested data retrieved as one or more content items, and if said model component does not have said requested data pertaining to said user request, said controller component invokes another one of said plurality of methods to be executed by said persistent interface component to retrieve said requested data from said back-end content management system and to store said requested data in said model component, and

wherein said first, second, third, fourth, fifth and sixth program instructions are stored on said computer readable storage media for execution by said CPU via said computer readable memory, and wherein said first, second, third, fourth, fifth, and sixth program instructions are executed on a portal server.

2. The system according to claim 1, wherein said view component of said content viewer portlet template further comprises a configuration page containing a plurality of parameters that are modifiable for customizing said content viewer portlet template for installation into said desired portal.

3. The system according to claim 1, wherein said controller component of said content viewer portlet template further comprises an exception class for handling exceptions and displaying error messages in multiple languages and a logging interface for displaying debugging messages in one or more log files.

4. The system according to claim 1, wherein said requested data retrieved from said back-end content management system comprises of concepts or sub-concepts and files;

and wherein said persistent interface component converts said requested data retrieved from said back-end content management system into a new set of data beans and stores said new set of data beans in said model component.

5. The system according to claim 1, wherein said model component incorporates said new set of data beans into said current set of data beans in order to store said requested data retrieved from said back-end content management system;

and wherein each of said current and new set of data beans comprises of category data beans and document data beans.

6. The system according to claim 1, wherein said view component executes a plurality of JavaServer Page (JSP) files for displaying said requested data retrieved as one or more content items, and wherein any of said plurality of JSP files of said view component of said content viewer portlet template can be modified to display said one or more content items in a specific format in said desired portal.

7. The system according to claim 1, wherein one or more codes of said controller component of said content viewer application template is modified if a particular mode of operation is desired for developing said content viewer application template into said customized content viewer application.

8. The system according to claim 6, wherein said back-end content management system comprises a relational database and a file system, wherein the persistent interface component is configured to retrieve data from either the relational database or the file system while using a same structure of a taxonomy tree used by the model component.

9. A method for deriving a customized content viewer portlet from a content viewer portlet template that is ready for installation into a desired portal, said method comprising:

importing a content viewer portlet template into a workbench;

implementing a persistent interface component of said content viewer portlet template for connecting to and retrieving data from a different back-end content management system;

modifying a current set of data beans stored in a model component of said content viewer portlet template based on said data retrieved from said different back-end content management system;

modifying a view component of said content viewer with data retrieved from said model component; and

modifying a controller component of said content viewer portlet template if a particular mode of operation is desired for said customized content viewer portlet template, such that said customized content viewer portlet is ready for installation into said desired portal, wherein said controller component is capable of subsequently directing said view component to be returned to a web client as said desired portal, wherein said model component populates said view component with said data that is locally stored in said model component, wherein said controller component directs said persistent interface component to retrieve said data in response to said data being lacking. in said model component, and wherein said controller component, said view component, said model component and said persistent interface component are each distinct subcomponents of a single content viewer portlet on a portal server.

10. The method according to claim 9, wherein said importing step includes the step of:

providing a content viewer portlet template that includes a configuration page for modifying a plurality of parameters for displaying said content items, a logging interface for displaying debug messages in one or more log files, and an exception class for handling exceptions and displaying error messages in multiple languages.

11. The method according to claim 9, wherein said implementing step includes the steps of:

retrieving said data stored in said different back-end content management system;

converting said data retrieved into a new set of data beans; and

storing said new set of data beans in said model component.

12. The method according to claim 11, wherein said modifying a current set of data beans in said model component step includes the step of:

incorporating said new set of data beans into said current set of data beans and storing said new set of data beans in said model component.

13. The method according to claim 11, wherein said different content management system comprises one of:

a relational database and a file system.

14. A computer program product for creating a customized content viewer portlet from a content viewer portlet template for installation into a desired portal, said computer program product comprising:

a tangible computer readable storage medium;

first program instructions to implement a persistent interface component of said content viewer portlet template for retrieving data from a back-end content management system;

second program instructions to modify a current set of data beans stored in a model component of said content viewer portlet template to incorporate said data retrieved from said back-end content management system;

third program instructions to modify a view component of said content viewer portlet template with data from a modified said current set of data beans from said model component, wherein said view component, said model component and said persistent interface component are each distinct subcomponents of a single content viewer portlet; and

wherein said first, second and third program instructions are stored on said tangible computer readable storage medium.

15. The computer program product according to claim 14, further comprising:

fourth program instructions to modify a controller component of said content viewer portlet template if a particular mode of operation is desired when said customized content viewer portlet is installed into said desired portal.

16. The computer program product according to claim 14, wherein said first program instructions include instructions to import said content viewer portlet template into a workbench for creating said customized content viewer portlet.

17. The computer program product according to claim 14, wherein said first program instructions include instructions to convert said data into a new set of data beans and to store said new set of data beans in said model component.

18. The computer program product according to claim 17, wherein said second program instructions include instructions to incorporate said new set of data beans into said current set of data beans for storage in said model component.

19. The computer program product according to claim 17, wherein said back-end content management system comprises one of:

a relational database and a file system.