forked from IQSS/dataverse
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request IQSS#7514 from OdumInstitute/4259_java_11
IQSS#4259 support Java 11
- Loading branch information
Showing
15 changed files
with
154 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
#!/bin/sh | ||
psql -U postgres -c "CREATE ROLE dvnapp UNENCRYPTED PASSWORD 'secret' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN" template1 | ||
psql -U postgres -c "CREATE ROLE dvnapp PASSWORD 'secret' SUPERUSER CREATEDB CREATEROLE INHERIT LOGIN" template1 | ||
psql -U dvnapp -c 'CREATE DATABASE "dvndb" WITH OWNER = "dvnapp"' template1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,91 @@ | ||
## Release Highlights | ||
|
||
### Java 11 | ||
|
||
The Dataverse software now runs and requires Java 11. This will provide performance and security enhancements, allows developers to take advantage of new and updated Java features, and moves the project to a platform with better longer term support. This upgrade requires a few extra steps in the release process, outlined below. | ||
|
||
## Notes to Admins | ||
|
||
### Java 11 | ||
|
||
There are some things to note and keep in mind regarding the move to Java 11: | ||
|
||
- You should install the JDK/JRE following your usual methods, depending on your operating system. | ||
- We targeted and tested Java 11, but 11+ will likely work. Java 11 was targeted because of its long term support. | ||
- If you're moving from a Dataverse installation that was previously running Dataverse 4.x, wou will need to adjust some JVM options in domain.xml as part of the upgrade process. We've provided these optional steps below. These steps are not required if you first installed Dataverse version was in the 5.x series. | ||
|
||
### New JVM and DB Options | ||
|
||
#### New JVM Options | ||
|
||
For installations that were previously running on Dataverse 4.x, the following JVM Options have been added in support of Java 11: | ||
|
||
<jvm-options>[9|]--add-opens=java.base/jdk.internal.loader=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-exports=java.base/jdk.internal.ref=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.lang=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.net=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.nio=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.util=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.nio.ch=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.management/sun.management=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.net.www.protocol.jrt=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.net.www.protocol.jar=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.naming/javax.naming.spi=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.logging/java.util.logging=ALL-UNNAMED</jvm-options> | ||
|
||
## Upgrade Instructions | ||
|
||
1\. Undeploy the previous version. | ||
|
||
- `<payara install path>/bin/asadmin list-applications` | ||
- `<payara install path>/bin/asadmin undeploy dataverse<-version>` | ||
|
||
(where `<payara install path>` is where Payara 5 is installed, for example: `/usr/local/payara5`) | ||
|
||
2\. Stop Payara and remove the generated directory | ||
|
||
- `service payara stop` | ||
- remove the generated directory: | ||
`rm -rf <payara install path>/payara/domains/domain1/generated` | ||
|
||
3\. (only required for installations previously running on Dataverse 4.x) | ||
|
||
In domain.xml: | ||
|
||
Remove the following JVM options from the domain><configs><config name-"server-config"><java-config> element:: | ||
|
||
<jvm-options>-Djava.endorsed.dirs=/usr/local/payara5/glassfish/modules/endorsed:/usr/local/payara5/glassfish/lib/endorsed</jvm-options> | ||
459a448 | ||
<jvm-options>-Djava.ext.dirs=${com.sun.aas.javaRoot}/lib/ext${path.separator}${com.sun.aas.javaRoot}/jre/lib/ext${path.separator}${com.sun.aas.instanceRoot}/lib/ext</jvm-options> | ||
|
||
Add the following JVM options to the domain><configs><config name-"server-config"><java-config> element: | ||
|
||
<jvm-options>[9|]--add-opens=java.base/jdk.internal.loader=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-exports=java.base/jdk.internal.ref=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.lang=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.net=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.nio=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/java.util=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.nio.ch=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.management/sun.management=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.net.www.protocol.jrt=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.base/sun.net.www.protocol.jar=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.naming/javax.naming.spi=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[9|]--add-opens=java.logging/java.util.logging=ALL-UNNAMED</jvm-options> | ||
|
||
4\. Start Payara | ||
|
||
- `service payara start` | ||
|
||
5\. Deploy this version. | ||
|
||
- `<payara install path>/bin/asadmin deploy dataverse-5.4.war` | ||
|
||
6\. Restart payara | ||
|
||
- `service payara stop` | ||
- `service payara start` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters