How the System Builds an Update Client-Only Package

This is an overview of how the JD Edwards EnterpriseOne system builds an update 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. For each object in the Package Build History table (F96225), the system retrieves the information from the Central Objects and adds it to the TAM specification files.

5. The system copies the associated .c, .h, and .hxx files for the selected objects from the check-in location on the deployment server to the package's directory on the deployment server.

6. The JD Edwards EnterpriseOne BusBuild program runs. NER is generated from the list of objects. The bin32 and lib32 dll is then copied from the parent package to the update package's bin32 and lib32 directories. The system compiles the business function objects in the package. The updates are then in the bin32 and lib32 directories of the update package.

7. If the build machine is not the deployment server, the system copies the parent package's local database from the spec directory to the build machine. The attach and detach of the parent package's local database can only occur on a local machine and not across the network. The specs from the update package are then merged into this parent package's local database and the database is copied back to the deployment server parent package directory. If the build machine is the deployment server, then the merge of the update objects happens to the parent package specs.

8. The system copies the bin32, lib32, obj, source, and include files from the update package to the parent package directory on the deployment server.

9. The system builds any features included in the package.

10. If compression was selected, the system compresses the directories.