Lifecycle Management - Expert Oracle Application Express - page 379

select workspace id into l workspace id
from apex workspaces
where workspace = 'FM';
-- set the context for the target workspace
apex application install.set workspace id( l workspace id );
-- override the original application id 100 with a different value
apex application install.set application id( 200 );
-- generate a new offset to ensure that the metadata for the Application
-- Express application definition does not collide with other metadata on
-- the instance
apex application install.generate offset;
-- override the original parsing schema FM with a different value
apex application install.set schema( 'FM TEST' );
-- set a different application alias, it should be unique within an APEX instance
apex application install.set application alias( 'FM TEST' );
end;
/
-- install the original application export, now the values for the workspace id,
-- application id, parsing schema and application alias will be overridden
@f100 facility management v2.0.0.0.sql
■ Caution Whenever you change the application id, the privately stored interactive reports are lost!
One issue you might not be aware of can really annoy end users. The problem in a nutshell is that
the users will lose their privately stored interactive reports once the application id is changed. This is due
to the way these user preferences are stored within the APEX metadata. (A detailed discussion of this
issue can be found on the Internet at http://dpeake.blogspot.com/2009/01/preserving-user-saved-
interactive.html and http://joelkallman.blogspot.com/2010/07/where-did-my-saved-interactive-
reports.html . )
Although you could work around this issue using the new package APEX APPLICATION INSTALL , it is
preferable to establish procedures that let you forget about it and require no fix.
This issue has largely determined our deployment strategy. In an effort to make our end users happy
we make sure they don't lose their privately stored reports. The real restriction is on identical application
IDs in the development and production environments.
Hotfixes
While working on the next release of the application (e.g., 2.0.0), you might detect a problem in the
current production release (e.g., 1.3.0.5). This problem has to be corrected, resulting in another patch
release, 1.3.1.