Browse Prior Art Database

Method for page rendering in a multi tenant Portal

IP.com Disclosure Number: IPCOM000243854D
Publication Date: 2015-Oct-22
Document File: 3 page(s) / 58K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a novel mechanism for rendering a portal page in a multi tenant portal, where the page or elements of the page are shared between multiple tenants, and portlets are either private or shared in another scope.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method for page rendering in a multi tenant Portal

In a multi tenant Portal, content elements like e.g. a Portal page, a portlet etc can be shared between multiple tenants. Some resources may be shared, while other resources may not be shared, but may be associated exclusively with one tenant . The weak point in prior art is the connection between the shared and the private elements , like e.g. between a shared page and the tenants private portlets . In the nature of things, a shared resource cannot contain links to non -shared resources. What is required is a mechanism for coupling shared resources and private resources , or for coupling resources which are shared in different scopes . In particular such a mechanism is required for rendering a portal page in a multi tenant portal , where the page (or elements of the page) are shared between multiple tenants, and portlets are either private or shared in another scope.

We disclose a novel method for enhanced page rendering in a multi tenant Portal . A Portal page contains one or multiple content spots , which are used during rendering to insert portlet markup or other content. There is no direct association between a content spot and a specific portlet or another content element . Instead, the content spot defines a set of requirements, which are later used to identify the portlet that is to be inserted at the content spot. In the preferred embodiment, the requirements contain attribute constraints. A portlet specifies the attributes either in static metadata like the portlet description, or dynamically in the render headers phase , where the render headers phase precedes the "normal" rendering.

In Diagram 1, there are three content spots, each defining constraints over the attributes Attr1 and Attr2. Note that the page does not contain a direct association with specific (either shared or private) portlets and thus can be shared between multiple tenants.

While rendering the page for a specific tenant , Portal processes the content spots and - for each content spot - uses a new...