How the System Builds a Full Client-Only Package

This is an overview of how the JD Edwards EnterpriseOne system builds a full client-only package.

1. R9621S runs first and determines that this is a client-only package so R9622C runs and initiates the client package build.

2. The system creates the package build directories.

3. The system creates the INF file.

4. These directories and files are copied from the check-in location to the package name directory:

   • res

   • source (.c files)

   • include (.h files)

   • work

   • bin32

   • lib32

   • obj

   Note: If you select to build business functions with the package build, the system does not copy bin32, lib32, and object (.obj) files because Oracle's JD Edwards EnterpriseOne BusBuild program creates them.

5. Creates a local OEE database with all the central objects tables.

6. Copies the 17 central objects tables into the created local OEE database.

7. Runs the JD Edwards EnterpriseOne BusBuild program to generate the NER, and compile and link the business functions, which create the DLLs in the bin32 directory, the objects in the obj directory, and the libraries in the lib32 directory.

8. The business services are built.

9. Any features that were included in the package are built.

10. The system copies any changed/new files from the include, source, bin32, lib32, and obj folders of the package to the path code check-in location.

11. The system compresses the directories.