How the System Builds an Update Server and Client Package

This is an overview of how the JD Edwards EnterpriseOne system builds an update server and client package. The beginning of each step states whether the process occurs on the client from where the build is performed or on the enterprise server.

1. Client: The Server Package UBE (R9621S) initiates the server package build.

2. Client: The system creates the package build directories.

3. Client: The system initiates the connection with the enterprise server.

4. Enterprise server: The system creates the directories on the enterprise server.

5. Enterprise server: The system builds the list of objects in the update package from the F96225 table on the enterprise server. The list of business functions, NER, and Table ER that are needed from the deployment server is built into a file called bsfnfile.txt. The list of bitmaps is found in bitmapfile.txt. Both files are moved back to the <package name>\work directory on the deployment server.

6. Client: The system opens the bsfnfile.txt for the list of .c and .h files to copy from the deployment server check-in location to the enterprise server directories: source_checkin (.c files) and include_checkin (.h files). This is done to preserve a snapshot of the .c and .h files at the time of the build.

7. Client: The system opens the bitmapfile.txt for the list of bitmaps to copy from the res directory check in location on the deployment server to the enterprise server res_checkin directory.

8. Enterprise server: The system generates named event rules (NERs) from the list in the update package. The generated files are created in the source_checkin and include_checkin directories.

9. Enterprise server: The system moves server-only .c and .h files to the source and include folders respectively. If there is more than one server, then it moves the .c and .h files from the primary server to the other enterprise servers under the source and include folders.

10. Enterprise server: The system copies the parent dlls from the parent package to the update package. It then uses this dll to compile the business functions for the update package. If there are multiple servers, the system sends a message to the other servers to start the build of business functions.

11. Enterprise server: The system builds specs from Central Objects, placing the results in the package's spec tables, <table name>_<package name> (for example, F98710_DV910UPD) in the database.

12. Enterprise server: If the client package was also selected, the system copies back the files from the source_checkin and include_checkin to the deployment server package directory's include and source directories.

13. Enterprise server: If client package was selected, the system copies back res bitmaps from the res_checkin to the deployment server in the <package name>\res directory.

14. The system waits for specs to finish and for dlls to finish building.

15. Enterprise server: When the dll and specs are finished, if compression was selected for the server, then the system compresses the .dll, .so, .sl, and .SRVPGM files on the enterprise servers.

16. Enterprise server: The system moves the compressed files and the compress.inf file back to the deployment server under the <packagename>/<machine type> directory.

17. Enterprise server: The system moves the server log (svrpkgbuild.log) from each server to the deployment server under <packagename>\serverLogs directory.

18. Enterprise server: The system moves the files located under the text directory on each enterprise server to the deployment server under <packagename>\serverlogs\<server name>\text.

19. Enterprise server: The system moves the files located under the CompileLogs directory on each enterprise server to the deployment server under <packagename>\serverlogs\<servername>\CompileLogs.

20. Enterprise server: The system moves the generation of NER logs on the primary enterprise server to the deployment server under <packagename>\serverlogs\GenerateNER.logs.

21. If this is a server only package, the process is complete. However, if you have selected to build a client, the system also performs the next steps.

22. Client: R9622C initiates the client package build.

23. Client: The system creates the package inf file.

24. Client: The system compiles the .c and .h files using Busbuild. Busbuild copies the dll from the parent package to build the update business functions into the parent package dll.

25. Client: The system copies the specs from the Central Object package's spec tables <table name>_<package name> (for example, F98710_DV910UPD) into TAM files located under the spec directory.

26. Client: The system waits for the business functions to compile and the spec build to complete.

27. Client: The system copies the generated NER .c and .h files back to the check in location.

28. Client: The system copies the bin32 and lib32 directories back to the check-in location if the business function build did not have any errors.

29. Client (optional): The system compresses the directories on the deployment server. This is only necessary if building an ESU. The client install process does not use the compressed update package files.