Deployment Server and Enterprise Server Multi-Foundation Architecture

Understanding Multi-Foundation Architecture

Multi-foundation is a JD Edwards EnterpriseOne architecture that allows for contrasting tools release foundations to reside on different path codes. For implementation details, refer to the appendix “Working With Multiple Tools Release Foundations” in one of these platform dependency documents as applicable:

• Deployment Server Reference Guide for UNIX
• Deployment Server Reference Guide for Microsoft Windows
• Deployment Server Reference Guide for IBMi

Before you upgrade to a new tools release foundation, it is a good practice to test and validate the functionality prior to upgrading the production (PD) path code. You can keep the production path code running on the existing tools release foundation and apply the new tools release foundation to all other path codes. This architecture enables you to perform tests on the new tools release foundation without impacting the PD path code. When you complete the validation, you upgrade the PD path code to the new tools release foundation.

The following are the common server configurations:

• Deployment Server with multiple physical Enterprise Servers
• Deployment Server with one physical server with multiple ports
• Deployment Server with one physical server with one port

For additional information, refer to this MOS Document, which provides a listing of all documents for understanding and implementing multi-foundation with JD Edwards EnterpriseOne:

E1: TR: Primary Note of Documents Explaining the Concepts and Implementation of Tools Release Multi-Foundation (Doc ID 1307646.1)

Deployment Server with Multiple Physical Enterprise Servers

In the above graphic, the PD path code resides on Enterprise Server 1 with a Tools Release 9.2.1 foundation. The prototype (PY) and development (DV) path codes share Enterprise Server 2 with a Tools Release 9.2.1 foundation. This is a multi-foundation architecture where different path codes on different Enterprise Servers have separate tools release foundations.

Deployment Server with One Physical Enterprise Server with Multiple Ports

In the above graphic, the PD path code uses Port 6017 with the  Tools Release 9.2.1 foundation. The PY and DV path codes use Port 6117 with the Tools Release 9.2.1 foundation. This architecture illustrates multi-foundation. This is a multi-foundation architecture where the path codes are on the same Enterprise Server but on different ports. Each port can have a different tools release foundation.

Deployment Server with One Physical Enterprise Server with One Port

In the above graphic, the PD, PY, and DV path codes use Port 6017 and the Tools Release 9.2.1 foundation. This architecture is not multi-foundation because the path codes use the same tools release foundation on the same server and port.

Tools Release Upgrade Example

Initial State

In the above architecture, the Deployment Server and both the Enterprise Servers use the Tools Release 9.2.1 foundation.

Upgrade State

To upgrade a tools release foundation:

1. Manually back up the current tools release foundation on the Deployment Server.
2. Apply the new tools release foundation to the Deployment Server as the default system.
3. Apply the new tools release foundation to Enterprise Server 2.
4. Run validations on Enterprise Server 2.
5. After the system validations are performed, apply the new foundation to Enterprise Server 1.
   

Final State

The Deployment Server and both the Enterprise Servers are now running on the Tools Release 9.2.2 foundation.