Skip to content

Commit 76a3882

Browse files
committed
moved payara upgrade into the main upgrade instruction #10646
1 parent 476cb13 commit 76a3882

File tree

1 file changed

+58
-88
lines changed

1 file changed

+58
-88
lines changed

doc/release-notes/6.3-release-notes.md

+58-88
Original file line numberDiff line numberDiff line change
@@ -276,6 +276,8 @@ These instructions assume that you've already upgraded through all the 5.x relea
276276

277277
0\. These instructions assume that you are upgrading from the immediate previous version. If you are running an earlier version, the only safe way to upgrade is to progress through the upgrades to all the releases in between before attempting the upgrade to this version.
278278

279+
Upgrading requires a maintenance window and downtime. Please plan ahead, create backups of your database, etc.
280+
279281
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.
280282

281283
In the following commands, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adjust as needed.
@@ -288,14 +290,65 @@ In the following commands, we assume that Payara 6 is installed in `/usr/local/p
288290

289291
- `$PAYARA/bin/asadmin undeploy dataverse-6.2`
290292

291-
2\. Stop Payara and remove the generated directory
293+
2\. Stop Payara and remove the following directories:
292294

293-
- `service payara stop`
294-
- `rm -rf $PAYARA/glassfish/domains/domain1/generated`
295+
```shell
296+
service payara stop
297+
rm -rf $PAYARA/glassfish/domains/domain1/generated
298+
rm -rf $PAYARA/glassfish/domains/domain1/osgi-cache
299+
rm -rf $PAYARA/glassfish/domains/domain1/lib/databases
300+
```
295301

296-
3\. Start Payara
302+
3\. Upgrade Payara to v6.2024.6
297303

298-
- `service payara start`
304+
With this version of Dataverse, we encourage you to upgrade to version 6.2024.6.
305+
This will address security issues accumulated since the release of 6.2023.8.
306+
307+
Note that if you are using GDCC containers, this upgrade is included when pulling new release images.
308+
No manual intervention is necessary.
309+
310+
The steps below are a simple matter of reusing your existing domain directory with the new distribution.
311+
But we recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting:
312+
[Payara Release Notes](https://docs.payara.fish/community/docs/Release%20Notes/Release%20Notes%206.2024.6.html)
313+
We also recommend you ensure you followed all update instructions from the past releases regarding Payara.
314+
(Latest Payara update was for [v6.0](https://github.com/IQSS/dataverse/releases/tag/v6.0))
315+
316+
Move the current Payara directory out of the way:
317+
318+
```shell
319+
mv $PAYARA $PAYARA.6.2023.6
320+
```
321+
322+
Download the new Payara version 6.2024.6 (from https://www.payara.fish/downloads/payara-platform-community-edition/), and unzip it in its place:
323+
324+
```shell
325+
cd /usr/local
326+
unzip payara-6.2024.6.zip
327+
```
328+
329+
Replace the brand new payara/glassfish/domains/domain1 with your old, preserved domain1:
330+
331+
```shell
332+
mv payara6/glassfish/domains/domain1 payara6/glassfish/domains/domain1_DIST
333+
mv payara6-2023.6/glassfish/domains/domain1 payara6/glassfish/domains/
334+
```
335+
336+
Make sure that you have the following `--add-opens` options in your `domain1/config/domain.xml`. If not present, add them:
337+
338+
```
339+
<jvm-options>--add-opens=java.management/javax.management=ALL-UNNAMED</jvm-options>
340+
<jvm-options>--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED</jvm-options>
341+
<jvm-options>[17|]--add-opens=java.base/java.io=ALL-UNNAMED</jvm-options>
342+
<jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options>
343+
```
344+
345+
(Note that you likely already have the `java.base/java.io` option there, but without the `[17|]` prefix. Make sure to replace it with the version above)
346+
347+
Start Payara:
348+
349+
```shell
350+
sudo service payara start
351+
```
299352

300353
4\. Deploy this version.
301354

@@ -379,87 +432,4 @@ AND dfv.value ILIKE 'http%';
379432

380433
A ['Reindex in Place'](https://guides.dataverse.org/en/latest/admin/solr-search-index.html#reindex-in-place) will be required and ReExportAll will need to be run to update the metadata exports of the dataset. Follow the directions in the [Admin Guide](http://guides.dataverse.org/en/latest/admin/metadataexport.html#batch-exports-through-the-api).
381434

382-
## Upgrade Payara to v6.2024.6
383-
384-
With this version of Dataverse, we encourage you to upgrade to version 6.2024.6.
385-
This will address security issues accumulated since the release of 6.2023.8, which was required since Dataverse release 6.0.
386-
387-
### Instructions for Upgrading
388-
389-
If you are using GDCC containers, this upgrade is included when pulling new release images.
390-
No manual intervention is necessary.
391-
392-
We recommend you ensure you followed all update instructions from the past releases regarding Payara.
393-
(Latest Payara update was for [v6.0](https://github.com/IQSS/dataverse/releases/tag/v6.0))
394-
395-
Upgrading requires a maintenance window and downtime. Please plan ahead, create backups of your database, etc.
396-
397-
The steps below are a simple matter of reusing your existing domain directory with the new distribution.
398-
But we also recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting:
399-
[Payara Release Notes](https://docs.payara.fish/community/docs/Release%20Notes/Release%20Notes%206.2024.6.html)
400-
We assume you are already on a Dataverse 6.x installation, using a Payara 6.x release.
401-
402-
```shell
403-
export PAYARA=/usr/local/payara6
404-
```
405-
406-
(or `setenv PAYARA /usr/local/payara6` if you are using a `csh`-like shell)
407-
408-
1\. Undeploy the previous version
409-
410-
```shell
411-
$PAYARA/bin/asadmin list-applications
412-
$PAYARA/bin/asadmin undeploy dataverse<-version>
413-
```
414-
415-
2\. Stop Payara
416-
417-
```shell
418-
service payara stop
419-
rm -rf $PAYARA/glassfish/domains/domain1/generated
420-
rm -rf $PAYARA/glassfish/domains/domain1/osgi-cache
421-
rm -rf $PAYARA/glassfish/domains/domain1/lib/databases
422-
```
423-
424-
3\. Move the current Payara directory out of the way
425-
426-
```shell
427-
mv $PAYARA $PAYARA.MOVED
428-
```
429-
430-
4\. Download the new Payara version (6.2024.6), and unzip it in its place
431-
432-
5\. Replace the brand new payara/glassfish/domains/domain1 with your old, preserved domain1
433-
434-
6\. Make sure that you have the following `--add-opens` options in your domain.xml. If not present, add them:
435-
436-
```
437-
<jvm-options>--add-opens=java.management/javax.management=ALL-UNNAMED</jvm-options>
438-
<jvm-options>--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED</jvm-options>
439-
<jvm-options>[17|]--add-opens=java.base/java.io=ALL-UNNAMED</jvm-options>
440-
<jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options>
441-
```
442-
443-
(Note that you likely already have the `java.base/java.io` option there, but without the `[17|]` prefix. Make sure to replace it with the version above)
444-
445-
446-
7\. Start Payara
447-
448-
```shell
449-
service payara start
450-
```
451-
452-
8\. Deploy this version.
453-
454-
```shell
455-
$PAYARA/bin/asadmin deploy dataverse-6.3.war
456-
```
457-
458-
9\. Restart payara
459-
460-
```shell
461-
service payara stop
462-
service payara start
463-
```
464-
465435
[↑ Table of Contents](#table-of-contents)

0 commit comments

Comments
 (0)