Databases Reference
In-Depth Information
3.
The end users run the application from the same instance in which you
developed it.
If these applications frequently change (but with relatively little changes to the database objects), adopt
the following deployment approach:
1.
Export the application.
2. Import the application into the same workspace/schema using a new
application ID.
For larger organizations, a development server (for development and testing or your applications) that is
separate from the production server should be adopted. In this case, the following deployment approach
may be more suitable:
1.
Export the application.
2.
Import the application into a different workspace (and/or schema).
If you need to deploy to an entirely separate server (for example, deploying at your customer's office),
adopt the following deployment approach:
1.
Export the application.
2.
Import the application into the target Oracle APEX instance (install it using a
different schema/database).
How It Works
Many large organizations develop on a development server, move their applications over to a staging or
User Acceptance Testing (UAT) server, and after the system has been approved by the users, to the
production server. This type of deployment is quite common, and there are numerous ways to segregate
or share your APEX instances, workspaces, and schema. A common setup is shown in Figure 9-1.
