Updating Matillion ETL
This article describes the Matillion ETL update process. Matillion ETL will notify the user when updates are required. For support purposes we would always recommend that users run the latest version of Matillion ETL.
Please read the release notes before updating, as they may contain important information regarding the update.
Release Notes for Matillion ETL are available here.
When to update
Matillion ETL will notify you when updates are required. You will see a notification in the notices section to the bottom right of the screen.
Perform a Backup
While we do our best to ensure updates go smoothly, you should take an EBS snapshot of the AMI root volume to provide a restore point in case of any problems.
- In the EC2 Management Console locate the Instance running Matillion ETL and select it.
- Find Root devices and then select the EBS ID of the volume.
- Right click on the volume and select Create Snapshot.
- Enter a Name and Description for your snapshot.
Updating with the Administration Application
The Administration Application for Matillion is available by adding /admin to the host name of your Matillion instance and logging in with an admin user.
Please see the Software Updates section of Administering Matillion ETL.
Updating manually via SSH
The AMI comes pre-configured with a software repository where updates are published. Therefore a standard 'sudo yum update' is all that is required to update the software on the AMI.
- In the EC2 Management Console locate the Instance running Redshift and select it.
- Right click and choose connect. Follow the on screen instructions.
- Once connected issue the following - sudo yum update matillion-* - Follow the on screen instructions.
- Restart Apache Tomcat using the following - sudo service tomcat8 restart
- Log out of your session with - exit
Note: Without Internet Access - If you run the AMI inside a VPC and do not allow outbound internet access, then updates will not be possible using the standard update procedure.
If you notice any problems after updating, please shut down the instance, create a new volume from the backup taken prior to update, and make this the instance's root volume. This will effectively roll-back the update. Then please contact our support team.