Best Practices Introduction

OTM Cloud is a SaaS application that was first released as a software product in the year 2000, with GTM following in 2009. Both products were built on the premise of allowing great flexibility and configurability with the use and flow of the application. This flexibility allows great power and is a large reason that OTM has been the leader in the Gartner Magic Quadrant for so many years. However, if not designed or implemented correctly, bad configurations can cause instability and/or performance problems. In recent years, Oracle's engineering team has built many guardrails in the application that prevent the most egregious errors, but there are still configuration mistakes that are outside our control to contain. This section contains recommendations from OTM experts on the best practices for configuring those key parts of the application. Oracle will continue to expand this section as we discover more common configuration mistakes, so please stay tuned. We hope that you use this guide to both drive new configuration work and review existing configurations. Most of the content in this best practices section is intended for the OTM superuser, not for the average user. As always, we encourage feedback on this documentation.