Unfortunately the configuration migration feature has been introduced in version 3.5
, so you will have to do this manually. Now, before you start the migration, note that your CloverETL Server is of milestone (M3 suffix) version and thus potential issues may occur during the migration process – this is because milestone releases are not intended to be used in production environments. In order to stay on the safe side I would recommend you making a dump of your Clover Server database and doing the migration afterwards. The migration itself may be as simple as new deployment of CloverETL Server web application – in case of Apache Tomcat app server you can do this with the following steps:
- Shutdown Tomcat
- Remove clover web application from webapp directory
- Replace clover.war (if exists) with the new version.
- Start Tomcat
CloverETL Server should apply appropriate DB patches that will alter your Clover DB structure the way it is required by the latest version.
Hope this helps.