How the System Builds Client Only Update Package (Prior to Tools Release 9.2.5.0)

The following section describes how the JD Edwards EnterpriseOne system builds a client only update package.

Note: Any references to 64-bit apply to Tools Release 9.2.3 and higher.

1. Server Package UBE (R9621S) runs first and initiates the server package build. The process determines this is a Client Only package and will continue to the R9622C UBE.

2. Client Package UBE (R9622C) runs and initiates the client package build.

3. Creates the package build directories.

4. Creates the INF file.

5. For each object in the Package Build History table (F96225), retrieves theinformation from the Central Objects and adds it to the TAM specification files and builds the individual .par file for the object under the <package name>\spec\packagename> directory.

6. If F00942T-> emdbsrcflg= 0 or blank, 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.

7. If F00942T->emdbsrcflg=1, then it retrieves each par file from the F98780R and puts the files in the package's directory on the Deployment Server.

8. Runs the JD Edwards EnterpriseOne BusBuild program. Generates the NER from the list of objects. It copies from the parent package, the bin32/bin64 and lib32/lib64 files to the update package bin32/bin64 and lib32/lib64 directory. It compiles the business functions objects in the package. The updates are now in the bin32/bin64 and lib32/lib64 files of the update package.

9. Updates the Parent Package: If the build machine is not the deployment server, it will copy the parent package local database from the spec directory to the build machine. The attach and detach of the parent local database can only occur on a local machine and not across the network. The specs from the update package are than merged into this parent package local database. The parent package local database is then copied back to the deployment server parent package directory. If the build machine is the deployment server, than the merge of the update objects happens to the parent package specs located under the parent package spec directory.

10. Copies from the update package bin32/bin64, lib32/lib64, obj, source/source64 and include/include64 files to the parent package directory on the Deployment Server.

11. Builds any features included in the package.

12. If compression was selected, then compresses the directories.