Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Distributed Layout Management was designed by Sungard SCT in the 2.1 uPortal release timeframe but was only available in the version of uPortal included in Sungard SCT's Luminis product. DLM was contributed back to the uPortal code base in uPortal version 2.5. It is an extension of SLM and uses SLM's User Preferences channel for modifying a user's layout and editing fragment contents. DLM provides the ability to define fragments that get pushed to end users but allows the maintainer of the fragment to determine just how much of the pushed fragment can be edited by the end user. If such restrictions are later changed then changes made to a fragment by the users will be replaced with the original content of the fragment. See Distributed Layout Management for more information.

Converting Between SLM, ALM, and DLM

uPortal version 2.5 comes configured to use ALM by default. To convert between the different layout management approaches follow these simple steps.

Step 1

Stop the web server if not stopped already.

Step 2

Open portal.properties and search for any of these three accronyms. There are two properties that the portal uses to startup the appropriate code to perform that layout management functionality. Preceding each of these properties is a comment block outlining what value that property should have for each of the respective layout management approaches. The properties that need to be changed are:

portal.properties to be Changed

org.jasig.portal.UserLayoutStoreFactory.implementation

org.jasig.portal.layout.UserLayoutManagerFactory.coreImplementation

After changing this value redeploy using, "ant deploy", so that the modified portal.properties file is pushed to <webApplicationRoot>/WEB-INF/classes/properties unless you changed the version in that location.

Step 3

Next, you need to modify user accounts in the database. Specifically, the UP_USER_PROFILE table contains a lookup of the structure and theme stylesheets that should be used by users. The following SQL can be used to modify the values for the respective layout management approaches. See the following table for the specific stylesheet values that come in the default uPortal database.

No Format

UPDATE up_user_profile
SET structure_ss_id=<struct Id From Below>,
theme_ss_id=<theme Id From Below>
WHERE theme_ss_is=<current Theme Id In up_user_profile>;

Approach

Structure Stylesheet Id

Theme Stylesheet Id

SLM

1

1

ALM

3

11

DLM

4

3

Step 4

Resart the web server.