How the System Builds a Full Server and Client Package

This is an overview of how the JD Edwards EnterpriseOne system builds a full server and client package. The beginning of each step states whether the process occurs on the client machine or on the enterprise server.

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

2. Client: The system creates the package build directories on the deployment machine.

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

4. Enterprise server: The system creates the directories on the Enterprise server and builds the list of objects from the F96225 table.

5. Client: The system copies the business function .c and .h 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.

6. Client: The system compresses the res directory from the checkin location of the deployment server. Sends the res.cab to the enterprise server under the res_checkin folder.

7. Enterprise server: The system generates named event rules (NERs) on the enterprise server. The generated files get created in the source_checkin and include_checkin directories on the enterprise server.

8. Enterprise server: The system moves server-only .c and .h files to the source and include folders respectively on the enterprise server. 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.

9. Enterprise server: The system compiles business functions on the Primary enterprise server to generate .dll, .so, .sl, or .SRVPGM files. If there are multiple servers, the Primary enterprise server sends a message to the other servers to start the build of business functions.

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

11. 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.

12. Enterprise server: If client package was also selected, the system copies back res.cab from the res_checkin to the package directory. The client then uncompresses it into the <package name>\res directory.

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

14. Enterprise server: When the dll and specs are finished, if the compress feature for server is enabled, then it compresses the .dll, .so, .sl, and .SRVPGM files on the enterprise servers. The Primary enterprise server also sends a message to all other servers to compress.

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

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

17. 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.

18. 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.

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

20. 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.

21. Client: The Client Package UBE (R9622C) runs to initiate the client package build.

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

23. Client: The .c and .h files are compiled using Busbuild.

24. Client: The specs are copied from the Central Objects package spec tables <table name>_<package name> (for example, F98710_DV910FA) into a local Oracle database, Oracle Enterprise Edition (OEE).

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

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

27. 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.

28. Client: The system compresses the directories on the deployment server if compression was selected.