Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Upgrading uPortal 2.1 to uPortal 2.3/2.4

Database migration

  1. Modify properties/db/tables.xml by commenting out UP_ENTITY_CACHE_INVALIDATION "not null" constraint on the ENTITY_CACHE_ID column. You need to comment out the not null constraint because it's not supported by all databases in alter table commands. Later you should add this constraint back.
  2. Run ant -f upgrade21.xml.  This will upgrade the database to the 2.3/2.4 schema version, make any necessary data changes, perform internationalization modifications, and publish the site map.

Switching from Simple Layouts to Aggregated Layouts (optional)

  1. Configure portal.properties to use aggregated versions of the layout manager and layout store: 
    org.jasig.portal.UserLayoutStoreFactory.implementation=org.jasig.portal.layout.AggregatedUserLayoutStore
org.jasig.portal.layout.UserLayoutManagerFactory.coreImplementation=org.jasig.portal.layout.AggregatedLayoutManager
  2. Turn off the locale manager awareness in portal.properties: 
    org.jasig.portal.i18n.LocaleManager.locale_aware=false
  3. Configure pushfragments.xml (uPortal 2.3) or fragments.xml (uPortal 2.4) with the fragments you want in your portal.
  4. Run ant -f upgrade21.xml convert-to-al
  5. Turn locale manager awareness back on (reverse Step 2) if necessary.
  • No labels