Convert a customized, published app to an Oracle or SQL Server database (Platform Edition institutions only)

Platform Edition institutions with a customized, published app can convert their configuration to an Oracle or SQL Server database.

About this task

Because the URL of your customized, published app is hard-coded with the ID of your existing configuration, you should NOT delete your existing configuration. If you delete your existing configuration, your app will not be able to download configuration data.
Warning: Your app will be briefly unavailable to users while you update your config.groovy file to connect to the new database. After that, the app will be available but will display either cached or incomplete information while you add your configuration information back into the Cloud Configuration tool.

Procedure

  1. Create an instance of the SQL Server or Oracle database that you want to use, and set up permissions as described in Step 2 of the Migrate an existing configuration to a new SQL Server or Oracle database process.
  2. Export your existing configuration for later reference.
  3. Stop Tomcat.
  4. Update your config.groovy file with the appropriate information for your database, as described in Step 5 of the Migrate an existing configuration to a new SQL Server or Oracle database process.
  5. Restart Tomcat.
  6. In the Cloud Configuration tool, re-validate your configuration as described in Create a configuration.
  7. Using the configuration export file, re-enter the configuration information.
    Consider adding the information in priority order, because as you add information, it becomes available immediately to users.
  8. Ensure that the updated data is appearing in your published app.