Creating a Final Software Master

To create a final software master:

1. From Product Packaging (GH962), select Product Packages (P9640).

2. On Work With Software Mastering, perform one of these actions:

   • To create a software master from one specific definition, click Find, select the definition that you want to create, and then select Master CD from the Row menu.

   • To create software masters for all definitions of a specific release, select Master Release from the Row menu.

     A form appears in which you enter the release number of the definitions that you want to master.

     Either choice runs a batch process (R9640B) that creates the software master based upon the definition that you chose. Run the report locally and select the option to display the results on screen. Depending on the build steps that are necessary to complete, the report launches several other reports, each corresponding to a particular build step.

     The software mastering process stops when it encounters a manual build step.

3. To complete the manual build step, select that build step, and select Execute Step from the View menu.

   The status of that step is advanced to 60 (Built). Click Master CD or Master Release to continue the software master process. The progress of the build can be monitored from the CD Revisions screen.

4. From the View menu, select Refresh.

   As each step is processed and completed, the icons change color and style. The last build step automatically validates the software master and generates a final report (R9840B) This report includes a comprehensive status of the product package build.

5. Review this report for errors.

   If the validation report does not indicate any errors, you have successfully created a software master. This report validates that the number of directories match between the software master definition and the final software master. It also provides details about the file counts and the total size of the master in megabytes.

   This process automatically creates a self-extracting executable file and a CAB file and places them in the $TEMP/final directory using the name of the software master followed by the .exe and .cab extensions. Use the executable (.exe) file to update JD Edwards EnterpriseOne. Both files include the full software master with all of its directories. If you have a size restriction, such as when downloading from the internet, you can use the CAB file (which is always smaller than the executable file), but you will need to use a third-party application to uncompress the CAB file.