Scheduler Migration
The use of the Scheduler microservice was deprecated in Zoomdata 4.3. All the scheduling functionality provided by the Scheduler microservice is provided by Composer's primary microservice. Because of this change, the following migration steps must be performed when you first upgrade to Zoomdata 4.3 (or later) or to Composer 5.7 (or later).
Back up the
zoomdata-scheduler
metadata store. Save the backup in case a problem occurs during the migration.Add the following properties to the
zoomdata.properties
file for your current Composer installation and save the file:Property Description migration.job-scheduler.url=jdbc:postgresql://localhost:5432/<existing-zoomdata-scheduler-db-name>
Specify the URL to the existing zoomdata-scheduler database. migration.job-scheduler.username=<username>
Specify a valid user name for the existing zoomdata-scheduler database. migration.job-scheduler.password=<password>
Specify the password associated with the user name for the existing zoomdata-scheduler database. Upgrade your Zoomdata installation to Zoomdata 4.3 (or later) or to Composer 5.7 or later. See Upgrade Composer.
After the upgrade has completed, start Zoomdata or Composer. When you start the product the first time after the upgrade, the Scheduler metadata from your original
zoomdata-scheduler
database is migrated to thezoomdata
metadata store.Verify that your data source data refreshes correctly, as defined in your data source configurations.
If data store data refreshes are working correctly, remove the migration properties you defined in Step 2 from the
zoomdata.properties
file and save the file. If you do not do this, the software will attempt to perform the Scheduler metadata migration every time you start it.Delete the
zoomdata-scheduler
database.
Comments
0 comments
Please sign in to leave a comment.