|
Oracle® HTML DB
Release 2.0 |
|
 Previous |
 Next |
Whether you want to move an application to another workspace or just make a copy of it, the deployment process involves the following steps:
Move the supporting database objects (if appropriate). Review the Database Dependencies report to determine what objects to move. See "About the Database Object Dependencies Report".
Export the application definition and all related files. See "Exporting an Application and Related Files".
Import the exported files into the target Oracle HTML DB instance. See "Importing Export Files".
Note that if the target instance is a different schema, you also need to export and import any required database objects.
Install the exported files from Export Repository. See "Installing Export Files".
You can import an application into your workspace regardless of the workspace in which it was developed.
Before you export an application and the appropriate related files, you need to determine if you also need to migrate the database objects referenced by the application. If you are unsure of which database objects to move, review the Database Object Dependencies report.
If the target Oracle HTML DB schema is different from the schema used in the development environment, you will need to migrate the database objects referenced by the application. In many cases this process can be as simple as using Oracle database export and import utilities to copy the application schema from the development environment to target Oracle HTML DB instance. The following are two common scenarios where this approach will not work:
When the object development schema refers to tablespaces to which the target instance schema does not have access
When the development instance schema has sample data that you do not to want migrate to the target instance schema
If a database administrator or an Oracle HTML DB administrator is the person responsible for exporting Oracle HTML DB applications, be sure to clearly communicate if he or she:
Should include all data when exporting your application
Should not include data from specific tables you identify