Re: APEX Development / APEX Production Layout Question

It can be as simple or as complicated as you want it.

I've opted for a semi-complicated process. Two different servers, running the same Oracle software - one test & development and one production.

On the development environment, I create (and modify over and over), my apps in the 200 series. Once I am ready for user testing, then I export it into the 100 series of application numbers. Once the user testing is satisfactory, I then export it again and import it into the production server in the 200's series again, re-test in the real working environment, and if successful I'll then move into the 100's.

Since there are no rules, you can basically do whatever you want, but the better organized you are, the easier it is for others to follow what you've done if you ever get hit by a bus.

Bill Ferguson

On Tue, Jul 26, 2016 at 10:07 AM, Alfredo Abate <alfredo.abate_at_gmail.com> wrote:

> Chris,
>
> We have the same APEX workspace/underlying database schema created in each
> of our environments. Environments I'll define as a database with the
> designation of Development, QA, and Production. Developers only get access
> to Development and this is where they do all their work. The DBAs would
> migrate the APEX application/database objects to QA for business sign off
> and then finally migrate it to Production.
>
> Oracle recommends (but not mandatory) to have your Production APEX
> environment created as a run-time version (https://docs.oracle.com/cd/
> E59726_01/install.50/e39144/overview.htm#HTMIG29140).
>
> Another thing to keep in mind is if you refresh your Development
> environment with Production. You have to make sure you're not wiping out
> the developers work at the workspace and/or schema level. Hopefully they
> have that saved to some version control software ahead of time. We refresh
> quite often because we are using APEX in our E-Business Suite
> environments. I have special scripts to export the APEX applications and
> schemas before the refresh then re-import them after the refresh. Once the
> environment is available, the developers don't know any different and
> continue on their merry way.
>
> Alfredo
>
>
>
>
>
> On Tue, Jul 26, 2016 at 10:25 AM, Chris Taylor <
> christopherdtaylor1994_at_gmail.com> wrote:
>
>> For you guys/gals that are Administering APEX environments, how do you
>> manage Development/Test/Production copies of APEX projects/workspaces etc?
>>
>> I'm trying to figure out how I want to architect this setup and I'm just
>> getting started so I'm looking for suggestions.
>>
>> I "think" I want a separate environment for Developers to "play in" and
>> an actual production APEX environment to prevent a muddy environment.
>>
>> I understand (I think) that I could have both in the same environment - I
>> could have developers "playing" with new projects in the same APEX
>> environment where there are live applications but that doesn't seem to make
>> sense logically. (I understand that the nature of APEX can keep them
>> separate by utilizing specific workspaces but it seems like I could end up
>> with a lot of projects that aren't doing anything with only a few "live"
>> applications.
>>
>> What are you guys doing with APEX environments in relation to
>> development/production setups?
>>
>> Thanks,
>> Chris
>>
>>
>

-- 
-- Bill Ferguson

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