Upgrading to Liferay Portal 6.1 EE GA1

When upgrading to the latest version of Liferay Portal, there are many things to take into account. This guide is designed to assist in the upgrading process. Please read and ensure your environment is ready prior to performing the upgrade.

Resolution

These instructions should be used if you have customized the portal in any way. Each component needs to be updated to complete the upgrade process.

These are listed in order of what should be completed first.

  1. Activation Key - For versions 6.0.x and below, a new key is necessary to upgrade to version 6.1 EE. Please refer to Requesting a Liferay Portal Activation Key for details.
  2. Backup - Ensure every component that is mentioned in the following instructions is backed up before proceeding.
  3. Permissions Algorithm - Follow the instructions in the user guide to upgrade permissions algorithm before the upgrade
  4. Liferay Portal - Download the latest released EE Portal WAR, EE Portal Dependencies, and EE Plugins. Remove the old EE Portal WAR, EE Portal Dependencies, and EE Plugins. Deploy the latest released EE Portal WAR, EE Portal Dependencies, and EE Plugins.
  5. Fix-Packs - Install all the Fix Packs on the latest released EE Portal using the Patching Tool to eliminate known issues.
  6. Portal-ext.properties - Copy the old portal-ext.properties settings to the new version. If performing a major upgrade, also review the settings from legacy.x.x.properties. Copy only the legacy.x.x.properties settings that are desirable for backward compatibility.
  7. Supported Upgrade Paths - See the upgrade chart to see what upgrade.processes to use in portal-ext.properties.
  8. Document Library / Image Gallery - Make sure the portal is using the same hook and pointing to the old location that files are being stored (image.hook.impl, image.hook.file.system.root.dir, dl.hook.impl, dl.hook.file.system.root.dir).
  9. Database - The application server should be pointing to the same data source. The Liferay database schema will automatically be updated to sync with the new version once you restart the server.
  10. Checkpoint - Stop here and make sure the above components have been upgraded successfully. (If the database has been upgraded successfully, remove this upgrade.processes= from portal-ext.properties!)
  11. Customizations - Download and use the latest released Plugins SDK. Copy code (Customizations, portlets, hooks, themes, layout templates, etc) to Plugins SDK environments and compile. Deploy customizations when all errors and API changes have been reconciled. (6.0EE+ does not support the old EXT environment. See this Extension Environment Migration Tips for how to migrate to the new ext-plugin)
  12. Portal Behavior Changes - Major portal upgrades may include some changes in the way it is used. Please verify if anyone of the points below affect your portal:
  13. Access to control panel - In 6.1 a new mechanism for viewing control panel was introduced. This is achieved through a new permission. It could not be added automatically during the upgrade process as it may break some of your previous access policies. The easiest way to allow users to access control panel is to add to whatever role is suitable for you (in new 6.1 deployments it is assigned to User role) the VIEW_CONTROL_PANEL permission. you can do that by editing the role from teh control panel and selecting the Portal > General > Go to Control Panel permission.

Best Practices

  • Don't attempt upgrades when there are already obvious issues with your current environment. The current issues will snowball into larger problems if you attempt to ugrade. Fix all problems first.
  • If you fail an upgrade attempt, do not continue to attempt upgrades on the same database. Fix the upgrade problems, then attempt a fresh upgrade with a database that you have never attempted an upgrade with yet.
  • Test the upgrade in a Test environment first.
  • Don't deploy directly to your live production server. Instead you should build a copy of the live site on a test environment. When the upgrade is successful, you could copy the entire environment to production. This technique will minimize downtime and reduce risk to the actual production environment.

Use Cases

5.2.3 CE to 6.1 EE

  1. If your permissions algorithm is lower than 5, upgrade to permissions algorithm 5.
  2. Shutdown application server for 5.2.3 CE
  3. In a Liferay 6.0 SP2 bundle portal-ext.properties, place the database settings that point to the database used for 5.2.3.
  4. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for 6.0 SP2.
  5. Start application server for 6.0 SP2 and you'll see the upgrade logs.
  6. Deploy license file for 6.0 SP2. You will need a license .xml file that you will drop into your hot deploy folder. In a default bundle of Liferay, this hot deploy folder is located in $LIFERAY_HOME/deploy. After deploying the .xml file, refresh the browser.
  7. Upgrade permissions algorithm to permissions algorithm 6.
  8. In portal-ext.properties in 6.1.10, place the database settings that point to the database used for 5.2.3/ 6.0 SP2.
  9. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for 6.1.10.
  10. Start application server for 6.1.10 and you'll see the upgrade logs.
  11. Deploy license for 6.1.10

5.2 EE SP5 to 6.1 EE

  1. If your permissions algorithm is lower than 6, upgrade to permissions algorithm 6.
  2. Shut down the application server for 5.2.9.
  3. In portal-ext.properties in a 6.1.10 bundle, place the database settings that point to the database used for 5.2.9 and add the following lines:
    upgrade.processes=\
    com.liferay.portal.upgrade.UpgradeProcess_5_2_9_to_6_0_11,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_12,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0,\
    com.liferay.portal.upgrade.UpgradeProcess_6_1_1
  4. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  5. Start application server for 6.1.10 and you'll see the upgrade logs.
  6. When the portal starts up you will be notified that "This server is not registered". You will need a license .xml file that you will drop into your hot deploy folder. In a default bundle of Liferay, this hot deploy folder is located in $LIFERAY_HOME/deploy. After deploying the .xml file, refresh the browser and you will be taken to the 6.1 EE Basic Configuration page.

6.0.6 CE to 6.1 EE

  1. Shutdown the application server for 6.0.6.
  2. In portal-ext.properties in 6.1.10, place the database settings that point to the database used for 6.0.6.
  3. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  4. Start application server for 6.1.10 and you'll see the upgrade logs.
  5. When the portal starts up you will be taken to the 6.1 EE Basic Configuration page.

6.0 to 6.1 EE

  1. Shutdown the application server for 6.0.10.
  2. In portal-ext.properties in 6.1.10, place the database settings that point to the database used for 6.0.10 and add the following property:
upgrade.processes=\
com.liferay.portal.upgrade.UpgradeProcess_6_0_12,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0,\
com.liferay.portal.upgrade.UpgradeProcess_6_1_1
  1. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  2. Start application server for 6.1.10 and you'll see the upgrade logs.
  3. When the portal starts up you will be taken to the 6.1 EE Basic Configuration page.

6.0 SP1 to 6.1 EE

  1. Shutdown the application server for 6.0.11.
  2. In portal-ext.properties in 6.1.10, place the database settings that point to the database used for 6.0.11 and add the following property:
upgrade.processes=\
com.liferay.portal.upgrade.UpgradeProcess_6_0_12,\
com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0,\
com.liferay.portal.upgrade.UpgradeProcess_6_1_1
  1. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  2. Start application server for 6.1.10 and you'll see the upgrade logs.
  3. When the portal starts up you will be taken to the 6.1 EE Basic Configuration page.

6.0 EE SP2 to 6.1 EE

  1. Shut down the application server for 6.0.12.
  2. In portal-ext.properties in 6.1.10, place the database settings that point to the database used for 6.0.12 and add the following property:
upgrade.processes=\
com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0,\
com.liferay.portal.upgrade.UpgradeProcess_6_1_1
  1. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  2. Start application server for 6.1.10 and you'll see the upgrade logs.
  3. When the portal starts up you will be taken to the 6.1 EE Basic Configuration page.

Previous 6.1 Versions to 6.1 EE

  1. Shutdown Liferay 6.1.0.
  2. In the portal-ext.properties for 6.1.10, place the database settings that point to the database used for 6.1.0.
  3. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version.
  4. Start the application server for 6.1.10 and you'll see the upgrade logs.
  5. When the portal starts up you will be taken to the 6.1 EE Basic Configuration page.
这篇文章有帮助吗?
0 人中有 0 人觉得有帮助