[Lifted from an old email I sent to my previous project mates.]

This is an email to remind about wantonly tweaking configuration settings in the Oracle Fusion Middleware stack to make the code work. Wantonly in this case means it did not go through the official change management process as the members in question wanted to quickly solve an issue that was first encountered in the UAT environment.

E2 is supposed to mirror the E3 environment to catch any problem that could happen in E3, or replicate an ongoing issue.

Our goal is not to make our deliverables pass UAT, but to provide deliverables that will not malfunction in production.

Any setting that needs to be changed needs to be evaluated properly to ensure it doesn’t affect the other applications in the environment. Each setting change is always a compromise between two conflicting scenarios (e.g. performance vs scalability, traceability vs resource management, etc.). We need to understand what we are exchanging for each setting update. The E2 settings change needs to be propagated to E3 afterwards.

For the nomenclature:

  • E2 is the User Acceptance environment, and
  • E3 is the Production environment.