Understanding Multitier Deployment of Server Packages

Server multitier deployment lets you automatically deploy a server package from one deployment server to another. The target deployment server to which you are deploying the package can be either in the same location as the source deployment server that sends the package or in one or more remote locations.

You typically build packages on the primary deployment server at the base location, but using a different server for installations from the base location might have advantages. In some situations, you might prefer to deploy a server package to a server at a remote location rather than require remote users to access the server package over a WAN.

Server package multitier deployment enables users to select which package builds they want to deploy. For example, if you are building a Prod package for multiple server platforms, you can select the build for the platform that has been successfully built. The benefit of having the ability to select builds is that users are no longer required to wait to install a new client package.

You use the JD Edwards EnterpriseOne Deployment Director program (P98631) for server multitier deployment. When you deploy a server package, the system copies these components:

• Foundation and data.

• Subdirectories of the package name directory:

  • bin32

  • include

  • lib32

  • obj

  • source

  • spec

• Subdirectories of the server build directories:

  • bin32

  • spec

  • obj

  • lib32

• ServerPackage.inf file in the server build directories:

  • The package.inf file.

  • The pack directory that is subordinate to the package name directory.

When server-only builds are deployed without client builds, only the pack subdirectory is copied.

This table describes where major package components are copied from and to during the deployment process; the server share path is derived from the F9651 table:

Package Component	Copied From	Copied To
Package	The path indicated in the SrcDirs section of the package.inf file.	<server share path>\<path code>\<package name> on the destination deployment server.
Foundation and data	The path indicated in the SrcDirs section of the package.inf file.	<server share path>\systemcomp on the destination deployment server if the default location is selected.
Package.inf file	The path indicated in the F00942 table if the source deployment server is the primary deployment server in the base location. Otherwise, the path to the package.inf file in the F9651 table.	<server share path>\package_inf on the destination deployment server.