Coming from Otto v3?
This document is for people who are familiar with Otto v3 and want to know what's changed in OttoFMS and OttoDeploy. If you have never used Otto v3 before you can safely skip this section of the documentation.
Please read everything on this page before you rush to upgrade from Otto v3. OttoFMS is a major upgrade and includes many backward-incompatible changes. If you are using Otto v3 in production you should continue to use it until OttoFMS has all the features you need.
OttoFMS and OttoDeploy will be free forever as long as you abide by the terms of the license agreement. This is a change from Otto v3 which was a paid product. We are making this change because we want to make it as easy as possible for people to use OttoFMS and OttoDeploy.
Otto v3 included email based tech support. Since OttoFMS is a free product, free support will be provided via the community forum (opens in a new tab) so that our answers to all questions can be public to help others. Paid support is available; learn more on the support page.
OttoFMS requires FileMaker 19.6 or later. It runs on any OS supported by FileMaker Server 19.6 or greater.
OttoFMS and and OttoDeploy take the place of Otto and Migrator.fmp12 respectively. We changed the names because we felt that the new names were a better description of what each product does and where it is installed and runs.
OttoFMS and OttoDeploy are complete, from the ground up, rewrites of Otto v3 and Migrator.fmp12. They are not compatible with Otto v3 or Migrator.fmp12.
OttoFMS, like Otto v3 and earlier, runs on your FileMaker Server, hence the "FMS" in the name. It provides the DevOps and runtime features which supercharge your development practices and your FileMaker based applications.
OttoDeploy.fmp12 takes the place of Migrator.fmp12. "Data Migration" describes only one part of what Migrator was doing. Really what it was doing was deploying FileMaker files from one server to another. Deploying files is a much more accurate description of the workflows that are possible, and so we changed the name accordingly.
OttoDeploy is now the place where you configure your "Deployments" and send them off to OttoFMS to do its thing.
OttoFMS and OttoDeploy have roughly the same feature set as the applications they replace but they have been much improved and expanded. Here is a list of some of the most important changes:
- No more port 3030. OttoFMS now runs on port 80/443 along with your FileMaker Server. This means that you no longer need to open up an additional port on your firewall, and you don't have to do anything special to get it to work with SSL.
- Redesigned Web Interface. The web interface has been completely redesigned to modern standards and is much easier to use. All features of OttoFMS are now available via the web interface.
- Migrations are now Deployments. Data Migration is now just one option in a Deployment. You can also install, replace, or simply close files during a deployment.
- Deployments are now atomic. If any file in a deployment fails the entire deployment is rolled back.
- Deployment can have sub-deployments which are run in order. This allows for more advanced use cases then was possible before. Sub-deployments are atomic, but by default they do not cause other sub-deployments to revert.
- Deployments scheduling improved. Schedules are now part of the deployment and don't require Migrator.fmp12 or OttoDeploy.fmp12 to be running on the server that performs the deployment.
- Post Migration Scripts are now Post Deployment Scripts. In addition to changing the name, these scripts are now part of the Deployment.
- Webhooks are easier. Webhooks are much easier to setup and use. They no longer need to run over port 3030.
- OttoDeploy can auto-upgrade. OttoDeploy can be auto-installed and auto-upgraded on any server running OttoFMS.
- OttoDeploy UI is simpler. The ui is up to modern standards both in look and feel, and usability. You won't believe it is a FileMaker file.
Some features are being retired as they are no longer useful or viable. Others are planned for future releases.
- Google Groups Authentication. We have a replacement for this called Ottomatic SSO.
- Calendar Integration. This feature was hardly ever used in Otto v3.
- OttoFMS Application Logging