Upgrading to Liferay Portal 6.0 EE SP1

When upgrading to the latest 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 are listed in order of what should be completed first.

  1. Backup - Ensure every component that is mentioned in the following instructions is backed up before proceeding.
  2. Permissions Algorithm - Follow the instructions in the Portal 6.1 Upgrading Liferay documentation to upgrade permissions algorithm before the upgrade.
  3. 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.
  4. 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.
  5. Supported Upgrade Paths - See this Liferay Portal Upgrade Chart to see what upgrade.processes to use in portal-ext.properties.
  6. 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).
  7. 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.
  8. 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)
  9. Activation Key - A new activation key is necessary to upgrade to version 6.0EE. Please refer to Requesting a Liferay Portal Activation Key for details.
  10. Customizations - Download and use the latest released Plugins SDK. C 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. Note: 6.0EE+ does not support the old EXT environment.

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.1.2 CE to 6.0 EE SP2

  1. Shutdown application server for 5.1.2
  2. In the 6.0 EE SP2 portal-ext.properties, place the database setting that points to the database used for 5.1.2 and add the following property:

    permissions.user.check.algorithm=5
    #If your 5.1.2 is using another permission algorithm (1-4), then use that instead.

  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. Refer to the Detailed Upgrade Instructions for more information.
  4. Start up the application server and you'll see the upgrade logs.
  5. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

5.1 EE SP5 to 6.0 EE SP1

  1. Shut down the application server for 5.1.8.
  2. In portal-ext.properties for 5.2.8, place the database settings that point to the database used for 5.1.8 and add the following property:
    upgrade.processes=\
    com.liferay.portal.upgrade.UpgradeProcess_5_1_8_to_5_2_8
  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. Refer to the Detailed Upgrade Instructions for more information.
  4. Start the application server and you'll see upgrade logs.
  5. Shut down the application server for 5.2.8
  6. In portal-ext.properties in 6.0.11, place the database settings that point to the database used for 5.2.8 and add the following property:
    upgrade.processes=\
    com.liferay.portal.upgrade.UpgradeProcess_5_2_8_to_6_0_5,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_6,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_11,\

    permissions.user.check.algorithm=5
    #If your 5.2.8 is using another permission algorithm (1-4), then use that instead.

  7. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version. Refer to the Detailed Upgrade Instructions for more information.
  8. Start application server for 6.0.11 and you'll see the upgrade logs.
  9. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

5.2.3 CE to 6.0 EE SP1

  1. Shutdown the application server for 5.2.3.
  2. In /webapps/sevencogs-hook/WEB-INF/classes/portal.properties delete this line:
    upgrade.processes=\
    com.liferay.sevencogs.hook.upgrade.UpgradeProcess_1_0_0

    Skip this step if you have deleted the sample data that comes with the portal.

  3. Start the 5.2.3 application server.
  4. Shutdown the 5.2.3 application server.
  5. In portal-ext.properties in 6.0.11, place the database settings that point to the database used for 5.2.3 and add the following property:

    permissions.user.check.algorithm=5
    #If your 5.2.3 is using another permission algorithm (1-4), then use that instead.

  6. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version. Refer to the Detailed Upgrade Instructions for more information.
  7. Start application server and you'll see the upgrade logs.
  8. When the portal starts up, you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

5.2 SP3 to 6.0 EE SP1

  1. Shut down the application server for 5.2.7.
  2. In portal-ext.properties in 6.0.11, place the database settings that point to the database used for 5.2.7 and add the following lines:
    upgrade.processes=\
    com.liferay.portal.upgrade.UpgradeProcess_5_2_7_to_6_0_0,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_1,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_2,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_3,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_5,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_6,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_11

    permissions.user.check.algorithm=5
    #If your 5.2.7 is using another permission algorithm (1-4), then use that instead.

  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. Refer to the Detailed Upgrade Instructions for more information.
  4. Start application server for 6.0.11 and you'll see the upgrade logs.
  5. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

5.2 SP4 to 6.0 EE SP1

  1. Shut down the application server for 5.2.8.
  2. In portal-ext.properties in 6.0.11, place the database settings that point to the database used for 5.2.8 and add the following lines:
    upgrade.processes=\
    com.liferay.portal.upgrade.UpgradeProcess_5_2_8_to_6_0_5,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_6,\
    com.liferay.portal.upgrade.UpgradeProcess_6_0_11

    permissions.user.check.algorithm=5
    #If your 5.2.8 is using another permission algorithm (1-4), then use that instead.

  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. Refer to the Detailed Upgrade Instructions for more information.
  4. Start application server for 6.0.11 and you'll see the upgrade logs.
  5. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

5.2 SP5 to 6.0 EE SP1

  1. Shut down the application server for 5.2.9.
  2. In portal-ext.properties in 6.0.11, 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

    permissions.user.check.algorithm=5
    #If your 5.2.9 is using another permission algorithm (1-4), then use that instead.

  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. Refer to the Detailed Upgrade Instructions for more information.
  4. Start application server for 6.0.11 and you'll see the upgrade logs.
  5. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

6.0.5 CE to 6.0 EE SP1

  1. When upgrading from an older 6.0, always update to 6.0.5 CE before moving on to 6.0.11.
  2. Shut down the application server for the older 6.0 CE.
  3. In portal-ext.properties in 6.0.5, place the database settings that point to the database used for the older 6.0 CE.
  4. Start the application server and you'll see the upgrade logs.
  5. Shut down the application server for 6.0.5.
  6. In portal-ext.properties in 6.0.11, place the database settings that point to the database used for 6.0.5.
  7. Place any other settings from the old portal-ext.properties (Ex. document library location) into the portal-ext.properties for your new Liferay version. Refer to the Detailed Upgrade Instructions for more information.
  8. When the portal starts up you will be notified that you need a product key. Different than 5.2, you will get a license .xml file that you drop into your hot deploy folder. After deploying the .xml file, the portal page will automatically redirect you to the license agreement page.

Previous 6.0 EE Versions to 6.0 EE SP1

  1. Shutdown Liferay 6.0.10.
  2. In the portal-ext.properties for 6.0.11, place the database settings that point to the database used for 6.0.10.
  3. Place any other settings from the previous 6.0.10 portal-ext.properties (Ex. document library location) in the 6.0.12 portal-ext.properties. Refer to the Detailed Upgrade Instructions for more information.
  4. Start the application server for 6.0.11 and you'll see the upgrade logs.
  5. When the portal starts up you will be notified that "This server is not registered". Different from 5.2, 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 Welcome page.
这篇文章有帮助吗?
0 人中有 0 人觉得有帮助