Databases Reference
In-Depth Information
Unfortunately, the development environment is currently blocked because the team is already
working on release 2.0.0 in the regular development environment. You cannot develop the patch release
(also known as a hotfix) there, but need another development environment for your production issues.
Since you typically want to separate the development environment from the test and production
environments, you will need another database instance running the hotfix test environment, as shown
in Figure 9-4.
Figure 9-4.
Adding a hotfix environment to the setup
This way you can make sure that the hotfix development environment can also have the same
application id as the production system, e.g., 100. This will preserve the privately-stored interactive
reports once you install the hotfix in the production environment.
Consolidating Environments
Using five different environments to cleanly support the development process is not always a feasible
option, especially for smaller development projects.
What is the minimum number of environments required to support this approach effectively? You
could get by with only three different APEX installations if you followed the suggested structure shown in
Figure 9-5
