Rapid Application Development
Migrating HTMLDB Applications from Test to Production
When migrating an HTMLDB application from one server to another
you need to migrate each component separately.
The main stages in the migration are
- Request that your schema and workspace be migrated from test to production.
- Once that has happened, you can import your application into the production workspace.
- Finally, all supporting files that are shared between applications in a
workspace must be moved over separately. This includes but is not limited to PL/SQL scripts, images and cascading stylesheets.
This checklist should
help you get everything ported successfully.
- Request database table and workspace migration from test to production. Issue a Help SU request several days in advance.
- export the application from test and import into production in the new workspace. Re-use existing schema and auto-assign a new application ID.
- install and run
auth-prod.sql, making sure to supply the shared secret. If you wish to use a different shared secret in production for additional security, notify
and someone will contact you to establish the new secret.
- install and run other PL/SQL scripts as necessary
- upload all images from your test workspace. If you are using a custom stylesheet you will need to migrate that as well.
- go through the app and alter all redirect buttons (e.g. invocations of export functions) from htmldb to webdb (the export file will show all instances)
- grant execute on all functions like export_tsv, e.g.
grant execute on export_csv to public;
-
The Oracle-by-example demo application and its associated tables may have been created during the move; if this application and its associated tables
bothers you feel free to remove it. Here is a script to
remove all demo tables.
