Example: JD Edwards EnterpriseOne Deployment Server Directory Structure

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

This is an example of the directory structure for PD910 (path code name)\Package\<package name> on the deployment server:

bin32

include

java

lib32

obj

pkgspec

res

serverlogs

source

spec

work

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

When you build a client-only package, the directories under the package name are populated. Files for the source and include directories are copied from the path code check in location on the deployment server to the corresponding package folder. For server/client packages, the include and source are copied from the primary build server include_checkin and source_checkin folders. Information for all other directories comes from central objects. The bin32, lib32, and obj directories are populated with the output of the business function build process.