Skip to content

Commit

Permalink
rearranged the payara upgrade notes a bit (IQSS#8012)
Browse files Browse the repository at this point in the history
  • Loading branch information
landreev committed Jul 27, 2021
1 parent 8496b7c commit a8263c3
Showing 1 changed file with 11 additions and 5 deletions.
16 changes: 11 additions & 5 deletions doc/release-notes/5.6-release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ A new DB Constraint has been added in this release. Full instructions on how to

### Payara 5.2021.4 (or Higher) Required

Some changes in this release require an upgrade to Payara 5.2021.4 or higher.
Some changes in this release require an upgrade to Payara 5.2021.4 or higher. (See the upgrade section).

Instructions on how to update can be found in the [Payara documentation](https://docs.payara.fish/community/docs/5.2021.4/documentation/user-guides/upgrade-payara.html) We've included the necessary steps below, but we recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting.

Expand Down Expand Up @@ -72,6 +72,9 @@ If this is a new installation, please see our [Installation Guide](https://guide

0\. These instructions assume that you've already successfully upgraded from Dataverse Software 4.x to Dataverse Software 5 following the instructions in the [Dataverse Software 5 Release Notes](https://github.com/IQSS/dataverse/releases/tag/v5.0). After upgrading from the 4.x series to 5.0, you should progress through the other 5.x releases before attempting the upgrade to 5.6.

The steps below include a required upgrade to Payara 5.2021.4 or higher. (It is a simple matter of reusing your existing domain directory with the new distribution). But we also recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting: [Payara documentation](https://docs.payara.fish/community/docs/5.2021.4/documentation/user-guides/upgrade-payara.html)


If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. Use `sudo` to change to that user first. For example, `sudo -i -u dataverse` if `dataverse` is your dedicated application user.

In the following commands we assume that Payara 5 is installed in `/usr/local/payara5`. If not, adjust as needed.
Expand All @@ -80,19 +83,22 @@ In the following commands we assume that Payara 5 is installed in `/usr/local/pa

(or `setenv PAYARA /usr/local/payara5` if you are using a `csh`-like shell)

1\. Undeploy the previous version.
1\. Undeploy the previous version

- `$PAYARA/bin/asadmin list-applications`
- `$PAYARA/bin/asadmin undeploy dataverse<-version>`

2\. Stop Payara and remove the generated directory

2\. Stop Payara

- `service payara stop`
- `rm -rf $PAYARA/glassfish/domains/domain1/generated`

3\. Move the current Payara directory out of the way

4\. Unzip the new Payara version in its place
- `mv $PAYARA $PAYARA.MOVED`

4\. Download the new Payara version (5.2021.4+), and unzip it in its place

5\. Replace the brand new payara/glassfish/domains/domain1 with your old, preserved `domain1`

Expand All @@ -102,7 +108,7 @@ In the following commands we assume that Payara 5 is installed in `/usr/local/pa

7\. Deploy this version.

- `$PAYARA/bin/asadmin deploy dataverse-5.6.war`5.6-release-notes.md
- `$PAYARA/bin/asadmin deploy dataverse-5.6.war`

8\. Restart payara

Expand Down

0 comments on commit a8263c3

Please sign in to comment.