Installing and Executing the DB Upgrade Client

The DB Upgrade Client is a standalone client used for upgrading your Liferay DXP database. This article documents how to install and execute the DB Upgrade Client.

Resolution

Installation

To install and execute the DB Upgrade Client, there are two methods you can follow.

  1. The client is included in all bundles available from the Customer Portal. Even if you are deploying Liferay DXP as a .WAR on an application server, it is still a good idea to download a bundle for additional files. 
    1. Deploy Liferay DXP to an application server. 
    2. Shut down the application server.
    3. Unzip the client into your Liferay Digital Enterprise instance (e.g., ${liferayHome}/tools/portal-tools-db-upgrade-client)
    4. Run java -jar com.liferay.portal.tools.db.upgrade.client.jar
  2. Using JPM
    1. Install jpm
    2. Run jpm install com.liferay.portal.tools.db.upgrade.client
    3. Run liferay-upgrade-db

Both methods have separate ways of executing the tool. The command line options listed in the next section, however, can be appended the same way for both methods (e.g., liferay-upgrade-db --noShell).

Usage

The first time you run the tool, it will automatically configure properties for your installation of Liferay DXP. You can also do this manually by configuring app-server.properties, portal-upgrade-database.properties, and portal-upgrade-ext.properties. Make sure to place these .properties files in the same directory from which you execute the tool.

The DB Upgrade Client also connects to the Gogo shell automatically after the upgrade. This lets you check the status of any module upgrades.

Note: You can configure the portal to only upgrade the core, and not external modules by adding a file called com.liferay.portal.upgrade.internal.configuration.ReleaseManagerConfiguration.cfg in the osgi/configs/ folder with the following content: autoUpgrade=false.

You can reference options for command line execution, Gogo shell commands, and configuration below.

Command Line Options

  • --jvm-opts or -j - sets any JVM options for the upgrade process
  • --log-file or -l - uses a custom name for your log file
  • --shell or -s - connect to the Gogo shell during upgrades

Gogo Shell Command Options

  • exit or quit - exits the Gogo shell
  • upgrade:help - displays upgrade commands
  • upgrade:check - list upgrades that failed or hasn't been started
  • upgrade:execute {module_name} - executes upgrade for that module
  • upgrade:list - lists all registered upgrades
  • upgrade:list {module_name} - lists the upgrade steps required for that module
  • upgrade:list | grep Registered - lists registered upgrades and their versions
  • upgrade:list | grep Registered | grep steps - lists registered upgrades in progress
  • verify:execute {module_name} - executes a verifier
  • verify:list - lists all registered verifiers

Configuration Options

app-server.properties

  • dir - the application server directory (required)
  • extra.lib.dirs - a comma delimited list of extra directories you want to add to the classpath (required)
  • global.lib.dir - the global lib directory of your application server (required)
  • portal.dir - the portal directory (required)

portal-upgrade-database.properties

  • jdbc.default.driverClassName (required)
  • jdbc.default.url (required)
  • jdbc.default.username (required)
  • jdbc.default.password (required)

portal-upgrade-ext.properties

  • liferay.home - the Liferay DXP home directory (required)
  • hibernate.jdbc.batch_size - the JDBC batch size used to improve performance; set to 250 by default (optional)
Was this article helpful?
1 out of 1 found this helpful