Upgrade Steps for Composer
To begin the upgrade process, you must receive an email containing upgrade instructions from Technical Support. This email provides the upgrade script that you need to run on the server where the Composer environment resides.
If you have not received upgrade instructions, open a ticket with Composer Support.
Make sure you have read and performed the recommendations in Prerequisites to Upgrading Composer. Be sure to back up your metadata store before you upgrade (see Back Up the Metadata Store).
When you receive the email, enter the upgrade command on your target server to start the automated upgrade process. The following Composer components are downloaded on your target server:
- The Composer server
- Connector microservices
- Query Engine
- Data Writer microservice
After the upgrade script has completed, it will take a few minutes for Composer to complete its update of the metadata store. We recommend that you wait a few minutes before accessing Composer from your web browser.
If you receive a message indicating that Composer is not yet accessible, it may not have completed its setup yet. Wait a few more minutes before trying again or opening a Support ticket. If you continue to have issues accessing Composer from your browser, open a ticket with Composer Technical Support. For information about accessing Composer, see Access Composer.
If you notice some unusual behavior in the Composer UI after upgrading the Composer software (for example, if a drop-down menu doesn't open or the application doesn't react when you select a button), clear the browser cache and try again. If the problem persists, contact Support.
The upgrade script provided by Technical Support assumes that your Postgres metadata store is running locally on the same machine as the Composer code and automatically adds the new databases required by Zoomdata 4.9 (or later) and Composer 5.7 (or later) to your local installation. If you have upgraded and your metadata store is installed on a different machine (not locally), you will need to manually create the following databases in your Postgres metadata store after the upgrade.
zoomdata
zoomdata-keyset
zoomdata-qe
zoomdata-upload
The firewall setup you used with earlier versions of Composer should have been retained and your Composer IP address should remain unchanged, but see the following for more information:
SQL connectors require a JDBC driver to be configured before you can connect to your data source. You can download the driver from the vendor’s site. Be aware that you need to download and configure JDBC drivers for the following Composer connectors:
If you are using one of these connectors, you need to download and configure a JDBC driver as soon as your Composer server has finished upgrading. For steps, see Add a JDBC Driver.
Reimport any CA certificates to the Java 11.0.5 or later you installed prior to the Composer upgrade. (In Prerequisites to Upgrading Composer, we recommended that you store them or back them up before the Composer upgrade.
Comments
0 comments
Please sign in to leave a comment.