Browse Prior Art Database

Dynamic Administration of Personalized Portal Applications

IP.com Disclosure Number: IPCOM000020413D
Original Publication Date: 2003-Nov-20
Included in the Prior Art Database: 2003-Nov-20
Document File: 3 page(s) / 21K

Publishing Venue

IBM

Abstract

The current architecture for using personalization within WebSphere Portal is for a developer to create a content spot that gets embeded within the JSP. This spot is then mapped to a rule using the personalization administration console. This approach is somewhat rigid because it requries a new spot (custom code) for each new portlet or rule that you want to process. Business users shouldn't have to go to a developer for new code just because they want to deploy some new content out to the portal. The following approach outlines a new scenario where rules can be mapped dynamically to new copies of a content spot as necessary. This allows complete control of deploying new content to the business user and removes the developer from the workflow.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 3

Dynamic Administration of Personalized Portal Applications

WebSphere Personalization can be combined with WebSphere Portal to help target content at appropriate users. Personalization is a powerful tool but requires some experience and training to use it effectively. WCP users will find Content Management and Personalization combined within a single interface for simple administration. Using the standard architecture provided by the applications as shown below is a simple yet effective approach to targeting content in a personalized manner.

Standard Architecture for Personalization

PortletController Servlet

Rules Engine

2. ContentSpot triggers rules engine for targted content

   3. Rules engine generates content and returns results

Content Spot looks up rule that is triggered based on mapping (Campaigns) in the Pzn engine.

This approach however is somewhat restrictive in that it requries a new content spot to be developed each time a different type of content needs to be deployed. This requries some dependency on the developer to assist with new content as necessary. There is an alternate approach as shown below that can be used to reduce this dependency and allow administrators to dynamically target new content as necessary.

  View JSP ContentSpot_

<body>

</body>

  View JSP ContentSpot_

<body>

</body>

  View JSP ContentSpot_

<body>

</body>

3

1

2

 1. Servlet Includes JSP

4. Formatted HTML is displayed

1

[This page contains 1 picture or other non-text object]

Page 2 of 3

Modified Architecture for Dynamic Admin of Personalized Content

PortletController Servlet

Rules Engine

2. ContentSpot looks up it's rule and triggers rules engine for targted content

<body>

</body>

  View JSP ContentSpot_ n

<body>

</body>

  View JSP ContentSpot_ n

<body>

</body>

  View JSP ContentSpot_ n

1. Servlet sets correct rule in session and includes JSP

  3. Rules engine generates content a...