Understanding the Platform Pack
The Platform Pack installs these major components:
JD Edwards EnterpriseOne Server code
JD Edwards EnterpriseOne database files
Assuming the installation programs are run on different machines, you can concurrently install these JD Edwards EnterpriseOne servers:
Deployment Server
Platform Pack on Enterprise Server and/or Database Server
HTML Server
This can decrease the overall time it takes to complete the installation.
To reinstall any Enterprise Server components, refer to Rerunning the Platform Pack Installer.
This table lists the mandatory and optional components of the Platform Pack installation:
Server |
Mandatory Component |
Optional Components |
|---|---|---|
Enterprise Server |
JD Edwards EnterpriseOne Foundation |
ES Production ES Prototype ES Development ES Pristine |
Database Server |
System Database |
Production Databases Prototype Databases Development Databases Pristine Databases |
Microsoft Windows Considerations. Microsoft clustering is supported for system failover protection.
As detailed in the Minimum Technical Requirements, install any Microsoft Windows server upgrades that are required to support Release 9.2.
Before you install Release 9.2 software on the Microsoft Windows Enterprise Server, you must create the Release 9.2 administrator user, verify disk space, and set up and verify the hosts file.
New for Tools and Application Releases for 9.2, customer must build a full package after the Platform Pack completes. Customers will not be able to build an update package out of the box.
Although the Platform Pack will no longer deliver packages, it still delivers the Package Repository and the package definition records because these are needed in order to run services. The Platform Pack will not deliver the source and include files (for example, obj and lib) for the package. The directories are delivered in the path code on the Deployment Server, just not as a package.