Example: JD Edwards EnterpriseOne Deployment Server Directory Structure

The E920 (release name) directory structure looks similar to this example.

This is an example of the directory structure for PD920 (path code name)\Package\<package name> on the Deployment Server:

bin64

include

java

lib32

obj

pkgspec (Prior to Tools Release 9.2.5.0)

res

serverlogs

source

spec

work

<operating system name of enterprise server (for example, INTEL5.2)

This is an example of a directory structure that has a 64-bit enabled path code:

lib32 OR bin64

include

include64

java

lib32 OR lib64

obj OR obj64

pkgspec (Prior to Tools Release 9.2.5.0)

res

serverlogs

source

source64

spec

work

When you build a client-only package, the directories under the package name are populated. Files for the source/source64 and include/include64 directories are retrieved from the repository, F98780R table. For server/client packages, the include and source are copied from the primary build server checkin/include for 32-bit, checkin/include64 for 64-bit and checkin/source for 32-bit, checkin/ source 64 for 64-bit folders. Information for all other directories comes from central objects. The bin32/bin64, lib32/lib64, and obj/obj64 directories are populated with the output of the business function build process.