Upgrading from standalone to embedded Jetty
Migration from 8.5.200.09 includes a transition to embedded Jetty. This transition includes a new set of configuration files. If you are migrating from 8.5.200.18 or later, this procedure is not required.
Complete the following steps for each Web Services and Applications node:
Start
- Stop the Jetty web server on the node.
- If you installed Jetty as service, use the chkconfig jetty9 disable command to disable the service to prevent autostart and potential port conflicts.
- Deploy the new version of Web Services and Applications.
- Copy settings from your existing configuration files to the application.yaml configuration file. See Configuring Web Services and Applications for more information about this file. The following table maps the previous configuration files to the new files:
Old file New file server-settings.yaml '"serverSettings"' section in the application.yaml file cassandra-cluster.yaml '"cassandraCluster"' section in the application.yaml file onpremise-settings.yaml '"onPremiseSettings"' section in the application.yaml file - Copy settings from your existing Jetty configuration files to the jetty section of the application.yaml configuration file. The following table maps the previous configuration files to the new files:
jetty-requestlog.xml '"jetty"' section in the application.yaml file jetty-https.xml '"jetty"' section in the application.yaml file /etc/default/jetty /etc/default/gws - Adjust the logging section of the application.yaml configuration file.
- Copy the JMV options from your exiting Jetty initialization script to the JAVA_OPTIONS variable in the /etc/default/gws file.
- Use the service gws start command to start the new version of Web Services and Applications on the node.
End
Comments or questions about this documentation? Contact us for support!