Importing whole applications vs. importing pages and components
This article describes the import of APEX pages and shared components. This operation is relevant when deploying modifications from the development environment to the production environment.
One of the most used and simple ways of transferring modifications to the APEX application into another environment is a complete recreation of the workspace and application. The steps are not subject of this document, but the major drawbacks from this method are:
– The workspace in the destination environment is deleted, along with all associated applications, and recreated
– The applications from the workspace need to be imported again, even if we only want to deploy only one of the applications from the previously deleted workspace
– All these operations take time and make the applications unavailable during the import
So, a simpler way is to apply modifications to an application stored in a different workspace, component by component and page by page, if the total number of new/modified pages or components is not close to the total number of components and pages in the application (in this case, a full application import will be more suitable).
The main concern and the scope of this document is importing pages or shared components from a development environment to a production environment. Usually, in the production mode we have all applications installed in runtime mode and the APEX installation itself does not have an Admin section, so all operations must be done using PLSQL and SQL scripts.