This section discusses different approaches to the deployment process.
Topics:
To move an application from one Oracle Application Express instance to another, you must move both the metadata and supporting objects used by the application as follows:
Move the application definition and all associated files.
Move the supporting objects. Review the Database Object Dependencies report to determine what objects to move.
When you develop an application in App Builder, you create the application within a specific workspace. Each workspace has a unique ID and name. A common scenario is to create the application in a development instance and then deploy it to a production instance.
Deployment options to consider include:
Use the same workspace and same schema. Export and then import the application and install it using a different application ID. This approach works well when there are few changes to the underlying objects, but frequent changes to the application functionality.
Use a different workspace and same schema. Export and then import the application into a different workspace. This is an effective way to prevent a production application from being modified by developers.
Use a different workspace and different schema. Export and then import the application into a different workspace and install it so that it uses a different schema. This new schema needs to have the database objects required by your application.
Use a different database with all its variations. Export and then import the application into a different Oracle Application Express instance and install it using a different workspace, schema, and database.
See Also:
Deciding whether to copy an existing workspace is a matter of preference. Keep in mind that the production version must have access to all the appropriate objects. For example, you might want to copy a workspace in the following situations:
When you want to keep the same application identifiers between development and other environments.
When the application relies on Oracle Application Express authentication. Copying the workspace automatically migrates all the required user data.
When deciding whether to copy the database, remember that the schema against which the application runs must have access to the same objects as the development instance. The actual name of the schema is unimportant. You can change it during the import process.
It is not necessary to have matching application IDs for a development version and production version of an application. In fact, as a best practice never hard code the application ID into your application. Instead, use the application alias (defined on the Edit Application page), or use a built-in substitution string (such as APP_ID and APP_ALIAS). Using a substitution string is the better approach because it enables you to change the application ID without affecting any application functionality.
See Also:
"Name" for information about defining an application alias
"Using Built-in Substitution Strings" for information about using APP_ID and APP_ALIAS