Sorry if this ends up be a common thread. We have finally migrated from our legacy 6i environment (thanks Michael for all your guidance on this) and now we are trying to develop the best deployment strategy moving forward.
In the old 6i days we simply would copy the FMX, PLX, MMX, REP files to a the required folders. To avoid FMX, MMX issues we would using the FORMS60_MMAP=0 setting to allow the overwriting of these files on the windows platform. For PLX files we using the FORMS_PATH env variable and injected a prefix directly before the default directly since the client is running the actually binaries (2 tier). When a use started a 6i session our launch script would pre-copy the PLX files from main deployment to this prefix directly allowing PLX file to remain current.
Now in 12c (still on windows for compatibility issues and prining via reports) we still can replace the FMX,MMX by using the MMAP env var, but PLX files we do not have the same folder redirection option. One thought we had was to have multiple copies of the “APPS” folder “APPS1”, “APPS2” and then change the FORMS_PATH env var using the EM console. Space is not an issue so that would, however it would be nice to be able to change default.env and other config files outside the EM console itself and have them activated the same way (this may be possible just have not discovered that).
So the 64,000 question is, how does this community handle this? I know there is FADS, however many times we just deploy 1 forms for a bug fix, and FADS seems overkill in that context. Please correct me if I an out to @$#%#%.
Thanks.