Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add release note instructions for migrating servers from Glassfish 4 to Payara 5 #6961

Closed
scolapasta opened this issue Jun 4, 2020 · 4 comments · Fixed by #7125
Closed

Add release note instructions for migrating servers from Glassfish 4 to Payara 5 #6961

scolapasta opened this issue Jun 4, 2020 · 4 comments · Fixed by #7125
Milestone
Dataverse 5

Comments

@scolapasta
Copy link
Contributor

For Dataverse 5, we are dropping support of Glassfish 4 for Payara 5. We have a new installer and documentation for new installations, but we need to add to the release notes what existing installations should do to migrate their servers.
@scolapasta
Copy link
Contributor Author

There are two possible paths:
• take existing domain and move into a fresh Payara installation (with some tweaks)
• use the installer to set everything up then re add needed jvm options and connection to exisitng DB

We discussed at tech hours and are leaning towards the first one - @landreev will add what he currently has for instructions in this issue and we can review to make sure that it works.

@djbrooke djbrooke added this to the Dataverse 5 milestone Jun 4, 2020
@djbrooke
Copy link
Contributor

  • @landreev and @donsizemore have been doing some experiments here
  • Domain move is the option we want to go with here
  • We have instructions here, there is a potential issue if there are things included in Payara 5.x (Hazelcast) that aren't handled in Glassfish.
  • Plan is to get it in PR and move it along there

@donsizemore
Copy link
Contributor

@landreev I just retested the pseudo-RST I wrote and successfully moved domain1 from Glassfish 4 to Payara 5.

You were correct - on launch Payara copied domain.xml to domain.xml.bak, modified some settings, and added others, among them:

>       <phone-home-runtime-configuration phone-home-id="2e9ae397-0e21-4104-8bc8-94ac430f50ee"></phone-home-runtime-configuration>
>       <notification-service-configuration>
>         <log-notifier-configuration></log-notifier-configuration>
>       </notification-service-configuration>
>       <hazelcast-config-specific-configuration></hazelcast-config-specific-configuration>
>       <hazelcast-config-specific-configuration></hazelcast-config-specific-configuration>
>       <payara-executor-service-configuration></payara-executor-service-configuration>
>       <zendesk-support-configuration></zendesk-support-configuration>
>       <stuck-threads-checker></stuck-threads-checker>
>       <health-check-service-configuration>
>         <log-notifier></log-notifier>
>       </health-check-service-configuration>
>       <asadmin-recorder-configuration></asadmin-recorder-configuration>
>       <metrics-health-check-configuration></metrics-health-check-configuration>
>       <microprofile-config></microprofile-config>
>       <request-tracing-service-configuration>
>         <log-notifier></log-notifier>
>       </request-tracing-service-configuration>
>       <amx-configuration></amx-configuration>
>       <admin-audit-configuration></admin-audit-configuration>
>       <microprofile-metrics-configuration></microprofile-metrics-configuration>
>       <ejb-invoker-configuration></ejb-invoker-configuration>
>       <rest-monitoring-configuration></rest-monitoring-configuration>
>       <microprofile-openapi-configuration></microprofile-openapi-configuration>
>       <microprofile-fault-tolerance-configuration></microprofile-fault-tolerance-configuration>

With your permission I'll submit the instructions I have as a PR if you'd like.

@landreev
Copy link
Contributor

@donsizemore

With your permission I'll submit the instructions I have as a PR if you'd like.

That would be much appreciated! I was going to copy-and-paste the current instruction into a PR myself... it's going to be a PR with just one release note, correct? - Either way works, thank you for all the testing!

donsizemore added a commit to uncch-rdmc/dataverse that referenced this issue Jul 16, 2020
@donsizemore
IQSS#6961 add upgrade instructions to release notes
f638af2
donsizemore added a commit to uncch-rdmc/dataverse that referenced this issue Jul 20, 2020
@donsizemore
IQSS#6961 correct warfile version
708df3c
@pdurbin pdurbin moved this from Up Next 🛎 to IQSS Team - In Progress 💻 in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34) Jul 21, 2020
donsizemore added a commit to uncch-rdmc/dataverse that referenced this issue Jul 23, 2020
@donsizemore
IQSS#6961 add Glassfish4-to-Payara5 upgrade instructions
01463d5
@donsizemore donsizemore mentioned this issue Jul 23, 2020
Merged
@donsizemore donsizemore removed their assignment Jul 23, 2020
landreev added a commit to uncch-rdmc/dataverse that referenced this issue Jul 30, 2020
@landreev
couple of small additions to the instruction IQSS#6961
be7251e
donsizemore added a commit to uncch-rdmc/dataverse that referenced this issue Jul 31, 2020
@donsizemore
IQSS#6961 use dataverse as service account instead of payara
13fd3c8
donsizemore added a commit to uncch-rdmc/dataverse that referenced this issue Jul 31, 2020
@donsizemore
IQSS#6961 The Installation Guide recommends a service account of data…
7a4a63d 
…verse.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Dataverse 5
Development

Successfully merging a pull request may close this issue.

add Glassfish4-to-Payara5 upgrade instructions to Dataverse 5 release notes uncch-rdmc/dataverse
4 participants
@landreev @scolapasta @djbrooke @donsizemore