Re: One more APEX question - Developing Schemas vs. Live Production Application Schemas?

The way we do this is we typically create an application schema. The application schema contains views and synonyms that point back to the schema that contains the data. Within APEX the application schema is considered the "parsing" schema. Workspaces and application APEX code are stored within the APEX schema (e.g. APEX_040100) installed with the install of APEX. Workspaces are not database schema objects but rather just "metadata" within Apex.

When promoting code from tier to tier, we migrated database objects (e.g. database views, tables, packages, ...) separately from APEX using existing database deployment tools. Apex supports changing the application schema (e.g. parsing schema) and even the application name during deployments.

On Tue, Jul 26, 2016 at 12:47 PM, Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:

> Let's say I create a WORKSPACE in my Development APEX environment and Joe
> Developer creates an application there in his workspace.
>
> All the objects for his application are owned by his database ID - JDEVMAN
> and are stored in their own tablespace.
>
> Now, Joe is ready to migrate his app to Production AND he kindly exports
> it for me, the Administrator.
>
> Now, do I import it into a generic APP Schema that I create in
> Production? Cause I don't think Joe is going to have his own Workspace in
> Production, right?
>
> I'm just unclear (and looking for clarifications) on what Joe's
> Application looks like in DEV versus what it's going to look like in Prod.
>
> I'm imagining his Application would have it's own schema & workspace in
> Production but maybe I'm wrong?
>
> Chris
>
>
>
>
>
>

-- 
Rumpi Gravenstein

--
http://www.freelists.org/webpage/oracle-l