Why Multifoundation?

As a best practice, you should always set up multiple tools release foundations, including a test environment for applying fixes to JD Edwards EnterpriseOne tools releases. This helps ensure that a stable environment exists before you promote fixes to your production environment. You can also use this same principle and procedure to set up multiple foundations of major tools releases, such as Tools Release 9.1 and Tools Release 9.2.



  • A Multiple Foundation configuration allows for longer and more thorough testing of a new service pack/Tools Release before it is introduced to the Production environment.
  • New changes and/or enhancements in a new TR/SP should be tested with your customizations. It allows for "tweaking" of your modified objects to make sure they will work with the new TR/SP.
  • Changes or enhancements introduced with a new service pack/TR may bring unexpected issues to your E1/OW configuration.  Changes may include:  kernel changes, new parameters, new features, etc. that should be thoroughly tested in an environment that is not the Production environment.  MF can avoid unnecessary down time that may result from a TR/SP change introduced to your stable E1/OW configuration.
  • Test results and extended timeline can be used to develop detailed business cases on choosing whether or not to upgrade Tools Release/SP levels.
  • Multiple Foundation accounts directly for less risk.
  • Less risk equals saved money.


Multi Foundation Implementation Process - Overview:



Introduction: Introduction to Multiple Foundation for EnterpriseOne (Doc ID 626212.1)
Unix/Linux: Multi-Foundation with Tools Release 8.97 and Above on a UNIX Enterprise Server (Doc ID 972436.1)

Windows: Multifoundation with Tools Release 8.97 and Above on Windows Enterprise Server (Doc ID 865621.1)

ISeries: Multi-Foundation with Tools Release 8.97 and Above on an iSeries Enterprise Server (Doc ID 972847.1)
Working With Multifoundation under: Deployment Server Reference Guide