This chapter contains the following topics:
This section discusses the software master creation process.
Use this checklist to ensure that you complete all of the processes that are necessary for creating a software master:
Verify that at least 1 GB of space is available for the TEMP directory of the workstation from which you use JD Edwards EnterpriseOne Product Packaging Tools.
This memory requirement is the most memory that you might need for a software master. The actual size of the master depends on the size of the package that you create.
Complete the tasks in this section.
Define a software master using Oracle's JD Edwards EnterpriseOne CD Configuration Director.
Provide information about the type of master that you want to create, such as its name, release number, and so on.
Select the package that you want built into the master.
Configure change tables using Oracle's JD Edwards EnterpriseOne Change Table Director.
Provide the target release number for the change tables.
Provide source environment information about the change tables.
Select the change tables and their versions.
Validate the software master definition.
Create the final software master, which automatically validates the master.
Use the software master to update JD Edwards EnterpriseOne.
This section discusses how to:
Set up the system TEMP directory.
Set up the UBEs.
Create pristine control tables.
Create a data dictionary in the pristine data source.
Create change tables.
Verify the creation of change tables.
This task creates a temporary directory that will be used to store the Oracle-supported local database for mastering the JD Edwards EnterpriseOne Product Packaging CD.
To set up the System TEMP directory:
From the Windows desktop, select Start, Settings, Control Panel.
On Windows Control Panel, double-click the System button.
On System Properties, click the Advanced tab.
Double-click Environment Variables.
Set the TEMP and TMP variables for both the User and System settings so that they all access the same directory (for example, c:\TEMP).
Note:
Ensure that the windows temporary directory on the workstation has at least 1 GB free disk space available (the more space the better). If the temp directory has less than 1 GB of free space, you can create a temp directory on another disk drive with adequate space and set the system environment variables TEMP and TMP to point to the new temp folder. Reboot the system for the change to take effect.This directory will store the software master that you create in the following tasks.
In the temporary directory that you specified in the previous step, create an empty subdirectory called \master.
Note:
The name of this subdirectory is case-sensitive and should be all lowercase.JD Edwards EnterpriseOne is initially configured to accommodate internal Oracle naming conventions that are not relevant to customer installations. Therefore, customers must change the configuration of data source names and paths in the UBEs so that they correspond to the naming conventions that are described in this document.
Note:
Unless you check out the versions before making the following changes, these changes will be available only on this workstation until another package is installed.To set up the UBEs:
On the Mastering Workstation, enter BV in the FastPath field to open up Batch Version.
Search for the R9640E UBE, select the XJDE0002 version, and change the Component File Specifications parameter to *.*.
For each of the UBEs listed, search for the UBE, select the specified version, and change the following processing option for the "Data Source Name" to OneWorld - Product Packaging.
| UBE | Version |
|---|---|
| R9670 | XJDE0001 |
| R9670 | XJDE0002 |
| R9670 | XJDE0003 |
| R96700 | XJDE0001 |
| R9600400C | XJDE0001 |
Create a JD Edwards EnterpriseOne Object Configuration Manager (OCM) mapping to run R9640B locally.
For control table changes to be included on an update CD, the JD Edwards EnterpriseOne Product Packaging Tool requires a pristine copy of the control tables. If the installation includes the PS900 pristine environment, these tables already exist in the JD Edwards EnterpriseOne instance and you can bypass the following task. If the installation does not include the pristine environment, you can create a set of pristine control tables by copying the Control Table tables from Control Tables Local to a new data source: Control Tables - PS900. You perform this process only once.
To create pristine control tables:
On the Deployment Server, sign in to JD Edwards EnterpriseOne in the DEP900 environment.
From menu GH9011, select Batch Versions.
Type R98403 in the Batch Application field and click Find.
On Work With Batch Versions - Available Versions, select version XJDE0501 (Control Tables For Pristine Database), and select Processing Options from the Row menu.
Select the Environment tab and change these processing options:
Target Environment (option 1)
Leave this field blank.
Target data source (option 2)
Enter Control Tables - PS900.
Data Load (option 3)
Enter 2 to copy data to the table.
Source data source (option 4)
Enter Control Tables Local.
Run the version locally.
The report copies the F9000, F9001, F9002, F0004, F0004D, F0005, F0005D, F9005, F9005D, F9006, F9006D, F91100, F91100D, F91400, F91410, F91420, F91430, F91500, F91510, and F951000 tables from the Control Tables Local data source to Control Tables - PS900.
Verify the results of the report and the creation of the tables.
Quit the Batch Versions application.
From menu GH9011, select Object Configuration Manager.
On Machine Search and Select, select the machine with the System - 900 data source.
For the PS900 environment, add Object Configuration Manager mappings for tables F9000, F9001, F9002, F0004, F0004D, F0005, F0005D, F9005, F9005D, F9006, F9006D, F91100, F91100D, F91400, F91410, F91420, F91430, F91500, F91510, and F951000, and assign these new tables to the Control Tables - PS900 data source.
Activate the new mappings.
Quit Object Configuration Manager.
You must create a data dictionary in the pristine data source.
To create a data dictionary in the pristine data source:
From the deployment server, sign in to the JDEPLAN environment.
Use JDE as the user name and JDE as the password.
From the System Administration Tools menu (GH9011), select Batch Versions.
On Work With Batch Versions - Available Versions, type R98403 into the Batch Application field and click Find.
Select version XJDE0509 and click Copy.
On Version Copy, enter a new version name and a new version title, and then click OK.
On Work With Batch Versions - Available Versions, select the version that you just created and select Processing Options from the Row menu.
Complete these processing options as indicated:
Target data source (option 2)
DATA DICTIONARY - PS900
Source environment (option 5)
Data Dictionary Local
Use these processing options to set up the batch process to copy the data dictionary tables from the JDEPLAN environment to the new pristine data dictionary.
Set the version that you just created to run in the proof mode first.
Run this report locally, not on the enterprise server.
Verify the results of this report.
When satisfied with the proof mode results, run the version that you just created in final mode.
Run OCM from the Fast Path field and select the enterprise server.
For the PS900 environment, add OCM mappings for F9200, F9202, F9203, F9207, F9210, F9211, and F9212 that point these tables to Data Dictionary - PS900.
Activate the new OCM mappings.
JD Edwards EnterpriseOne Product Packaging requires that a set of tables, called change tables, exist and be mapped to the Control Tables - <environment> data source. A change table is a table that contains the items that have changed between releases or updates. Normally, these tables are generated during the installation process, when you run the environment workbench. If, however, the environment is populated with demo data, these tables will not be generated even though the environment workbench reports that they were created successfully.
Complete this task and the next if you need to create change tables in the mastering environment.
To create change tables:
On the deployment server, sign in to the JDEPLAN environment.
From menu GH9011, select Batch Versions.
Type R98403 in the Batch Application field and click Find.
Select version XJDE0507 (Change Table) and click Copy.
On Version Copy, complete these fields as directed:
New Version
Version Title
Type a name for the new version.
CREATECT
Click OK.
On Batch Version Design, click the Processing Options button on the General tab.
Edit these processing options for CREATECT as directed:
Target Environment (option 1)
Type the name of the mastering environment.
Target Data Source (option 2)
Leave this field blank.
Data Load (option 3)
1: Load Production to create the table without data.
Source data source (option 4)
Control Tables Local
Click OK.
On Batch Version Design, click Run.
On Version Prompting, select Data Selection and click Submit.
On Data Selection, verify that these tables are listed in the right operand for BC OBNM, and add those that are missing:
F960004
F960005
F967611
F969000
F969001
F969002
F969005
F969006
F9691100
F9691400
F9691410
F9691420
F9691430
F9691500
F9691510
F9695100
F9698710
F9698712
F9755
F9757
F9759
F9760
F98800DN
F98800N
F98800TN
F98810DN
F98810N
F98811N
F98830N
F98840N
F98845N
Run the version.
The program creates the change tables in Control Tables - CRP or whichever environment Control Table data source you specified.
For each of the change tables, verify that an OCM mapping exists and points to the appropriate data source for the mastering environment.
To verify the creation of change tables:
From menu GH9011, select Object Configuration Manager.
On Machine Search and Select, select the machine with the System - 900 data source.
For the mastering environment, verify that each of these change tables is mapped to the correct data source and that each mapping is activated:
| Change Table | Data Source |
|---|---|
| F960004, F960005, F969000, F969001, F969002, F969005, F969006, F9695100, F98800DN, F98800N, F98800TN, F98810DN, F98811N, F98810N, F98830N, F98840N, F98845N | Control Tables - <environment> |
| F9698710, F9698712 | Central Objects - <environment> |
| F967611, F9691100, F9691400, F9691410, F9691420, F9691430, F9691500, F9691510, | System - 900 |
| F9755, F9757, F9759, F9760 | Data Dictionary - 900 |
Quit OCM.
Run Oracle's JD Edwards EnterpriseOne Universal Table Browser (UTB) to verify that the tables were created in the correct location.
This section provides an overview of software master definitions, lists a prerequisite, and discusses how to:
Define a software master.
Configure change tables.
Set the package build application to the mastering mode.
Validate a software master definition.
Create a final software master.
Confirm the software master.
Move the software master to a CD ROM.
Update JD Edwards EnterpriseOne with the software master.
A software master definition provides the structure for the finished software master. It establishes what template and packages to use, what build steps to follow, and the directory structure of the final master. The software master definition is only the structure or outline of the master. After you set up the software master definition, you validate it and then create the actual software master.
The JD Edwards EnterpriseOne Product Packaging application enables you to include custom data on the software master. Read the following tips for including custom tables and custom media objects on the software image.
If the customer creates a new, customized table that is to be delivered with pristine data, the mastering process should automatically handle this procedure if these conditions are met:
The table is included in the update package.
The table is in the environment of the update package.
The table is not included in the target environment.
The table and index change table exist.
To include custom media objects in the product package, add these build steps to the ASU template:
Add a build step to copy table records from the F00165 to the XML database.
Add a build step to copy the media object files from the deployment server to the image path directory.
This example illustrates why change table configurations are needed:
Create change table configurations to indicate to the JD Edwards EnterpriseOne Product Packaging Tools the change tables that you want included with the software master. When you install the finished software master, the installation process will update the control tables of the enterprise with the change tables that you indicate.
Assume that the home office in Denver, USA, makes software changes and wants to update an enterprise that is not networked to the Denver enterprise. The other enterprise, which has its own set of JD Edwards EnterpriseOne software and control tables, is in Paris, France. The Denver enterprise creates a software master that includes the package containing the software changes, as well as the change tables that contain data dictionary and user-defined codes changes, which, for this example, are the only control table changes since the Paris enterprise was last updated. The Denver enterprise writes the software master to a CD and ships it to Paris. When the Paris enterprise installs the software master, the change tables update the Paris control tables, making the tables concurrent with the Denver control tables.
This task explains how to create the final software master image from a definition that you previously created. You can master a single definition or master all definitions of a specific JD Edwards EnterpriseOne release.
The report that accomplishes this task is Oracle's JD Edwards EnterpriseOne Master CD (R9640B) report. This report controls the execution of all of the build steps and the UBEs that are associated with the build steps. This report also changes the status of each build step from 30 - Validated to a new status of 60 - Built or 50 - Failed.
With an average workstation, network, and ERP environment, the mastering process should take about one hour. However, the software includes many variables that can affect the time that is necessary to build a product package CD. These variables are:
Status and level of debugging.
Number of objects in the update package.
Size of the objects in the update package.
Overall size of the parent package.
Number of change tables to define.
Network speed.
Type of database.
Build machine speed.
Build machine memory.
Number of other processes running on the enterprise server, deployment server, and build machine.
Ensure that at least 1 GB of space is available for the TEMP directory of the workstation from which you use the JD Edwards EnterpriseOne Product Packaging Tools. This memory requirement is the most memory that you might need for a software master. The actual size of the master depends upon the size of the package that you create.
See Also:
To define a software master:
Sign in to a JD Edwards EnterpriseOne workstation using the development environment where the modifications exist, such as DV900.
From Product Packaging (GH962), select Product Packages (P9640).
On CD Configuration Director, click Next.
On CD Information, complete these fields:
Name
Enter a unique name for the software master definition that you are adding, such as E900UPDATE. This name must exactly match the name of the package to be included, and it must be in all uppercase letters.
Release
Enter the release for the software master definition, such as E900. This is the release that is currently installed on the client workstation that you are using.
Type
Specify the type of CD that you want to master. In this case, it is an ASU CD (option 09) which is the default. If you select an option other than 09, the software displays an error message when you press Next. This field indicates which software template to use when you further define the master. Templates include the build steps and directory structure that is necessary to create a software master.
Build Phase
Enter the development phase that the software master definition represents, such as alpha, beta, or general availability.
Description
(Optional) Enter a description of the software master definition.
Image Path
Enter the directory path where you want the software master definition to reside on the JD Edwards EnterpriseOne Product Packaging build machine (for example, d:\E900\PP). The directory that you indicate will be the root directory for the software master that you create. It will contain the contents of the master. After you create the image, the CD can be burned through the CD burner software.
Click Next.
If you chose a template that appears on the list of values when you click the Search button for the Type field, but the template is not on the enterprise, the CD Template Does Not Exist form appears. You have probably entered the incorrect release number. Click OK to continue adding the software master definition, or click Cancel to stop adding the definition.
If the template that you chose using the Type field was set up to include packages, the CD Packages form appears.
Select the update package that includes the objects for the update disk.
You can either select an existing update package or create a new one. To ensure that the update package is defined correctly, note that:
You can use only update packages for this process.
The package name must be the same name as the product package that was previously defined, and it must be in all uppercase letters.
The package should be created from its very beginning.
The update package must always include specifications, build specifications, build business functions, and compression.
If the package is not compressed, then product packaging will not work correctly because JD Edwards EnterpriseOne Product Packaging looks only for cab files to copy to the image.
If the package is undefined, the Select Package Build form automatically appears; otherwise, click Select Package.
You can also add packages by clicking New Package Build or Package Assembly.
On Select Package Build, if you need to assemble or define a package or both, select one of these from the Form menu:
Pkg Assembly
Pkg Build
Note:
Make sure that you compress any packages that you build.See Setting the Package Build Application to the Mastering Mode.
On the Select Package Build form, find and select a package, and then click Select.
On CD Packages, select the package marker that appears.
For an ASU CD, only one package is required. For other types of software masters, more than one package might be required.
Click Next.
If the template that you chose was set up to include change table configurations, after you click Next, the JD Edwards EnterpriseOne Change Table Director form appears.
Continue to the next task, which explains how to configure the change tables.
On the JD Edwards EnterpriseOne Change Table Director, which appears automatically during the mastering process if required by the template, click Next.
Alternatively, from Product Packaging (GH962), select Change Table Configurations (P9642) and then click Add.
On the JD Edwards EnterpriseOne Change Table Director, click Next.
On the Target Release Selection form, complete the Target Release field.
Change the target release to a custom user-defined code (UDC) name that you are mastering. This name needs to be unique, such as E900TAX for the 1099 tax update. Select the release name using the visual assist button.
Note:
The software will not function correctly if these tables have the same value for the source and target release. To add the custom UDC, press the visual assist and then click Revisions. This action displays the Work with User Defined Codes form. Work with User Defined Codes, click Add. Scroll to the bottom of the grid and add the new value in the last line of the grid. After you have created the UDC, select the new UDC on the Work with User Defined Codes form, and click Select. This action will populate the Target Release field with the new value.Click Next.
On Source Environment Selection, complete these fields:
Source Environment
Enter the name of the environment that includes the control tables that are used as the baseline for the changes. The source is typically the pristine environment (PS900). The software builds the change table records by comparing the target environment to this baseline.
Source Release
Verify that the source release matches the release and the cumulative update level, such as E900, of the source environment that you want. The software automatically populates this field based upon the source environment.
Click Next.
The Batch Application Selection form appears. This form lists the available change tables along with the batch application and version that will create the change table.
To select the default change tables that you want with the software master, double-click the gray button to the left of the change table row.
A check mark appears on the button.
Select any or all of these change tables where you made additions, deletions, or changes. The batch process compares the source and target tables in each selected category and creates a change table that contains all changes.
Data Dictionary
User Defined Codes
This batch application should always be chosen because changes always occur to the UDC that defines the release.
Workflow.
Favorites.
Templates and Smart Fields.
Tips of the Day.
Table and Index Changes.
Solution Explorer.
Service Constants. (8.97 only)
You can double-click a check mark to remove it.
To select a different version or to select multiple versions, select a change table row, and then select Version Selection from the Row menu.
On Version Selection, select one or more versions and click Select or double-click the gray button to the left of a version.
A check mark appears to the left of the versions that you chose.
After choosing the versions that you want, click Close.
The Batch Application Selection form reappears.
A check mark appears to the left of the change table row that you chose. The change tables that you want to be built for the software master must have check marks next to them or the software will ignore them. If you chose more than one version, the word <MULTIPLE> appears under the Version column for that change table.
Either select another change table row and select Version Selection from the Row menu, or click Next.
If you click Next, the Additional Change Table Definitions form appears.
On Additional Change Table Definitions, perform one of these actions:
To define additional change table configurations for a new source and target release combination, select Continue and click OK.
The program displays the Target Release Selection form. Return to the beginning of this task and repeat the steps for a different source and target combination.
Select Quit and click OK.
This action stops the change table configuration director and displays the final revisions screen for mastering the defined CD.
If you select Quit, the CD Revisions form appears. Use this form to revise the software master definition.
On CD Revisions, click OK.
the software master definition is saved, and the CD Revisions form closes.
Continue to the next task, which explains how to validate the definition that you just created.
To compress an update package, you must set the package build application to the mastering mode.
To set Oracle's JD Edwards EnterpriseOne Package Build Application to the mastering mode:
On the Deployment server, log on to the DEP900 environment.
From the Package and Deployment Tools menu (GH9083), right-click Package Build, and select Prompt For Values.
On Processing Options, type 1 in option 2 to set up the mastering mode.
Click OK.
Quit the package build application.
This task explains how to run Oracle's JD Edwards EnterpriseOne Pre-Mastering CD Validation report (R9640A) to validate the software master definition that you set up and what to review in the report to help with the validation. The report runs in final mode. The report lists whether the build step is validated. The report will change the status of build steps that do not have errors.
To validate a software master definition:
From the Product Packaging menu (GH962), select Product Packages (P9640).
On Work With Software Mastering, click Find.
The existing software master definitions appear.
Select the master that you want to validate, and then select Validate from the Row menu.
On Report Output Destination, select to view the report on screen and click OK.
The report runs. All steps without errors whose statuses were In Definition (10) or Defined (20) are promoted to the status of Validated (30); they will work properly during the software mastering process. Otherwise, the build step will have either a warning or an error message. Error messages will stop the creation of a software master. You must fix any build steps that contain error messages. The message specifies the error.
Warning messages will not stop the creation of a software master. If a build step has a warning message, you should verify that the build step is as you want it before proceeding.
Note:
The report will always include a warning stating that the build step is different from the template. This warning is always true because the process uses a custom package build.Continue to the next task, which explains how to create the final software master.
To create a final software master:
From Product Packaging (GH962), select Product Packages (P9640).
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.
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.
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.
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.
After you create the software master image, you should visually check the directory structure and XML database to verify that the image is complete.
To confirm the software master:
In Windows Explorer, open the image path directory.
Verify that the package directory includes these objects:
Install manager files.
Planner directory.
A data cab in the planner directory.
A directory that is named the same as the package.
Cab files in the package directory.
Verify that the $TEMP\final directory includes these two files:
packagename.cab
packagename.exe
Open the XML database in the $TEMP\master directory, and verify that this database is populated with tables.
Note:
If the package includes new custom tables, verify that they are in the XML database and that they and their associated index change tables have records.After the software master process has been completed and confirmed, the image can be burned onto a CD.
To move the software master to a CD ROM:
Using a CD burner and CD burner software, copy the packagename.cab or packagename.exe file from the $TEMP/final directory on to the CD ROM.
This task explains how to update JD Edwards EnterpriseOne using the software master that you created. To perform this update, access the Work with Updates (P96470) application from the System Installation Tools (GH961) menu. This process includes setting merge flags, running the self-extracting executable (package_name.exe), running software updates, and executing the installation workbench.
To update JD Edwards EnterpriseOne using a software master:
Run the package_name.exe executable file from the CD.
This process installs the package into the Planner\Package directory on the deployment server, and extracts the package_name.mdf and package_name.ldf files into the Planner\Data directory. The process also creates the software master image in the PLANNER directory.
Note:
You can also use the CAB file to create the software master image on the deployment server, but you need to use a third-party application to uncompress the file.If InstallManager.exe exists on the CD, start the installation by double-clicking it.
If this file is not on the CD, double-click the package_name.exe file to self-extract and uncompress the CAB file. After it is uncompressed, Install Manager will automatically launch.
On Installation Setup Screen, click Next.
On Installation Setup Type, verify that the machine has the necessary disk space and that the install path is correct, and then click Finish.
When the installation is complete, the Install Manager displays the "Installation Complete" window.
Click OK.
On the Deployment Server, sign in to the Planner environment (JDEPLAN).
Type GH9612 in the Fast Path field.
Select Application Software Updates (P96470).
On Work with Software Updates, click Find.
Select the product package to install, and click Next.
On Software Update Environment Selection, select the path code on which to install the package, and click Next.
If you select unattended mode, the Installation Workbench will automatically perform all the workbench tasks to complete the installation. If you do not select unattended mode, the Installation Workbench tasks must be done manually.
If you select backup, the process will create a PAR file (PRJ_packagename_pathcode_60_99.par)) in the Planner\Package\Package_Name\PathCode.bak directory. All objects that are affected by the update will be backed up in the PAR file.
The Installation Workbench should stop after the Table Conversion workbench process is complete.
Review the PDFs and the log files that were created by the table conversions, and then continue with Installation Workbench.
When Installation Workbench is complete, the system returns to the Work with Software Updates screen, and the selected software update should have the Completed Normally install status.
Click Close to quit Work with Software Updates.
Review all PDFs that were generated on the deployment server by the software update process, and verify that each of report is free of errors.
If a report has errors or does not appear to have run, review the jde.log file to determine the source of the problem. This table provides descriptions of the Software Update reports.
| Report | Version | Description |
|---|---|---|
| R98405 - Application | XJDE0001 | Table Conversion/Merge Driver for Application Tables: Master UBE for creating and regenerating application tables. This report should have only one record—Table and Index Creation (F984072). The status of the record should be, "Completed Normally." |
| R98407 | XJDE0001 | Table and Index Creation: Launched by R98405 UBE, which creates or regenerates all tables that are specified in the table change table. Page one of the report includes source, target, and environment information. Page two includes the overall status of the table creation in green or red text. Subsequent pages list the status of each table and index to be created or regenerated. |
| R98405 - Control | XJDE0001 | Table Conversion/Merge Driver for Control Tables: The master UBE that specifies the control table merge UBEs to launch. It should list the Data Dictionary UBE (R989200P), and the User Defined Codes UBE (R9600042). The status on all should be, "Completed Normally." |
| R989200P | XJDE0001 | Data Dictionary Merge: Launched by R98405. This UBE merges all data dictionary changes that are specified in the data dictionary change tables into the existing data dictionary. Page one of the report has source, target, and environment information. Subsequent pages list the status of each data dictionary addition or change. At the end of the individual listings, the overall status of the data dictionary merge is listed in green or red text. The final page has detailed summary information. |
| R9600042 | XJDE0001 | User Defined Code Merge: Launched by R98405. This UBE merges all user-defined code changes that are specified in the UDC change tables into the existing UDC tables. Page one of the report lists source, target, and environment information. Subsequent pages list the status of each UDC addition or change. The final page has detailed summary information. |
| R9690002 | XJDE0001 | JD Edwards EnterpriseOne Solution Explorer Merge: Launched by R98405. This UBE merges all JD Edwards EnterpriseOne Solution Explorer changes that are specified in the SE change tables into the existing SE tables. Page one of the report lists source, target, and environment information. Subsequent pages list each addition, change, or deletion in the change tables. The final page has detailed summary information. |
| R96911002 | XJDE0001 | Favorites Merge: Launched by R98405. This UBE merges all Favorites changes that are specified in the Favorites change tables into the existing Favorites tables. Page one of the report lists the source, target, and environment information. Subsequent pages list the status of each Favorites addition or change. The final page has detailed summary information. |
| R96914002 | XJDE0001 | Report Director Templates Merge: Launched by R98405. This UBE merges all changes that are specified in the Report Director Templates change tables into the existing Report Director Templates tables. Page one of the report lists the source, target, and environment information. Subsequent pages list the status of each addition or change. The final page has detailed summary information. |
| R96915002 | XJDE0001 | Tips Merge: Launched by R98405. This UBE merges all Tips changes that are specified in the Tips change tables into the existing Tips tables. Page one of the report lists the source, target, and environment information. Subsequent pages list the status of each addition or change. The final page has detailed summary information. |
| R96951002 | XJDE0001 | Service Constant Merge: Launched by R98405. This UBE merges all service constant data that is specified in the change table into the existing Service Constant table. Page one of the report lists source, target, and environment information. Subsequent pages list the status of each service constant addition. This merge is only used for release 8.97. |
| R98405 - Spec | XJDE0001 | Table Conversion/Merge Driver for specification tables: Master UBE for specification table merge. This report should have only one record—Specification Merge (F98710). The status of this record should be, "Completed Normally." |
| R98700 | ZJDE0002 | Specification Merge: Launched by R98405. This UBE adds, replaces, and merges all specified object specifications into the selected Central Objects path code. This report is the standard specification merge report. Page one of the report lists the source, target, and environment information. Page two summarizes information about the merge status. The remaining pages include the individual object action and status. |
On the Deployment Server, sign in to the DEP900 environment.
Find the package in Oracle's JD Edwards EnterpriseOne Package Assembly (P9601), and build and deploy the update package to a client workstation.
This section lists the form that is used to delete software masters. All records that are associated with the definition, such as the change table configurations and repair director records, will be deleted when you delete the software master.
This section provides overviews of software master revisions and software master validation and discusses how to:
Revise a software master definition.
Load a subdirectory from an enterprise network directory.
Copy a software master definition.
Proof a software master definition.
After you have completed the definition of a software master, you can revise any of the information, including the build steps and directory structure. You also can copy the definition information to a new software master definition, delete the definition, and proof and validate it.
You can revise a software master definition that you have created. This revision enables you to modify the information that you entered into the JD Edwards EnterpriseOne CD Configuration Director, as well as the build steps and directory structure that is included with the template that you chose.
The system uses icons to indicate the status of a software master. The icons have these meanings:
| Icon | Meaning |
|---|---|
| Gray Partial Cog | The status code is 10: In Definition. |
| Gray Full Cog | The status code is 20: Defined. |
| Gray Cog with Green Check Mark | The status code is 30: Validated. |
| Yellow-to-Gray Cyclic Arrows | The status code is 40: Processing. |
| Red Octagon | The status code is 50: Failed. |
| Gold Cog | The status code is 60: Built. |
You run a report to validate the software master definition that you created. The report runs in final mode, and it changes the status of the build steps that do not have errors. All steps without errors whose status was In Definition or Defined are promoted to the status of Validated. The report lists each build step that will run when you create the master. The report lists whether the build step is validated. If it is validated, the build step will work properly when you are creating the software master. Otherwise, the build step will have either a warning or error message.
Warning messages will not stop the creation of a software master. The message specifies what the warning is. If a build step has a warning message, you should verify that the build step is as you want it before proceeding.
Error messages will stop the creation of a software master. You must fix any build steps that contain error messages. The message specifies the error.
Access the Work With Software Mastering form.
Select the CD Information tab.
Displays the status of a build step or directory structure within the mastering process. For example, the build step or directory structure could be at a status of defined, validated, or built. Use the visual-assist button to view a complete list of values for this field.
Displays short informational comments that are provided by the system about each step of the mastering process. You can enter comments into this field, but the system will overwrite any text that is currently in the field during the next mastering process.
Overfills the directory path where you want the software master to reside on the enterprise. The directory that you indicate will be the root directory for the creation of the final software master.
Select the Build Steps tab.
Displays the order in which the system processes build steps, usually in increments of 10 (for example, 10, 20, 30, and so on).
Verify the order in which you want the step performed during the creation of the software master definition. You can use the same sequence number for multiple build steps.
Displays the type of CD being mastered. Verify which component type you want the build step to perform. For example, you can define steps to create file structures, build a package, or create INF files.
Verifies the current status of the build step, which can indicate whether to run the particular step during the mastering process. For example, if you need to perform a manual step during the mastering process, you can manually complete the step, change the step's status to 60 (Built) by choosing the step, and then, from the View menu, select Execute Step.
Displays the name of the target folder, such as planner or updatepkg. The system populates this field based upon the template that was used to define the software master. Change the name of the target folder only if you added the folder yourself.
Displays the software that might populate this field based upon the build step's definition in the software master template. To change this field, click the Executable button and use the Select a Windows Executable form to select an executable for this build step.
Verifies the value or parameter. To change this information, click the Value/Parameter button, and then enter a value or parameter that is appropriate to the step you chose. This field is dynamic. The button name is either Value or Parameter, based upon the step that you select. The form that appears when you click the button also depends upon which step you select. For example, the Package Build step calls the Select Package Build form, from which you can select a package; and the Build Change Tables step calls the Work With Change Table Definitions form, from which you can modify the change table configuration.
Select the Directory Structure tab.
Displays the directory on the enterprise that you want to use to populate the highlighted target folder. You can use an absolute (full) directory path name, or you can use a relative path name with a token. The system copies the data that is contained in the source path, depending upon how you filter those files (see the File Filter field description for this information), into the highlighted target folder of the software master.
Verifies the directory path of the source that will populate the component. This is the source path name of the data that you want to retrieve for the master and that you placed into the target folder. You can specify this path using either a relative or absolute path. See Appendix A, "Troubleshooting Product Packaging" for information about relative and absolute paths.
Displays the filter, which you can designate, for the files that are contained in the source path. For example, you can use *.* to retrieve all files in the source path, or *.exe to retrieve only executable programs.
Verify the file filter. The default is *.*. The file filter enables you to filter any data files that you retrieve from the source directory. For example, you can use *.* to retrieve all files in the source directory.
Displays the names and functions. This field is dynamic and its name and function depend upon the build step that is highlighted. The possible names and functions are:
Value: The value that is needed to complete the highlighted build step. For example, if the build step is a batch process, the value field contains the name of the batch process and its version, such as R95012\XJDE0001.
Parameter: The parameters that are needed for the highlighted build steps that process an executable program.
The full (absolute) target path name of the highlighted directory, such as Root/planner/updatepkg.
This table provides information for building the task list:
| Task | Action |
|---|---|
| To run one or more steps: | Select the build step that you want to run, and from the View menu, either select Execute Step to run just that step or select Run From Step to run that step plus any steps that follow it.
This option runs the step and updates its status to 60 (Built). You might use this option for manual build steps. Manual steps are those that you need to perform yourself, such as an additional mastering step that is not part of the JD Edwards EnterpriseOne Product Packaging Tools. After you complete the manual step, use the Execute Step option to update the step to a status of 60 so that you can proceed to the next step in the process. |
| To renumber the build steps: | From the Form menu, select Renumber.
The software renumbers the build steps, updating the Sequence field. The renumbering begins with 10 and increments each step by 10. The software keeps the build steps in the same sequence that you or the software master template established. |
| To add a subdirectory: | Click a directory for which you want to add a subdirectory and click Add. You can select any directory, including the Root directory.
The software creates a new directory that is labeled Undefined and places it at the bottom of the structure. |
Access the CD Revisions form.
Select the Directory Structure tab.
Select the directory that will be the root of the subdirectory that you want to load, which must already exist on the enterprise, and click Load.
This feature copies any enterprise directory structure into the software master definition.
On the Load Folders From Directory form, click Windows Folder.
On the Select Directory form, find and select a directory that you want to load into the software master, and then click OK.
On the Load Folders From Directory form, select one of these options:
Re-create subfolders
This option deletes the existing subdirectories and replaces them with the subdirectories that you want to load into the software master.
Append to existing
This option appends to the existing subdirectories the subdirectories that you want to load into the software master.
If necessary, select the Setup Source Directories check box.
During software master creation, by having this option enabled, the system automatically creates the structure of the source directories and copies all files within the source directories to the software master.
If you do not select Setup Source Directories, the software will create the source directory structure within the software master and the directories will be empty.
Click OK.
Access the Copy CD Configuration form.
You can copy a software master definition that you already created, which enables you to copy the information that you entered into the CD Configuration Director, the build steps, and the directory structure.
The type of CD that is being mastered. Verify which component type you want the build step to perform. For example, you can define steps to create file structures, build a package, or create INF files.
In most cases, you will not need to change the default value. If you need to, however, you can change the type of the software master when making a copy. For example, you can change the type from a Setup CD to an ASU CD. This change does not change build steps or the directory structure. When you validate the software master, you will receive warning messages that the master does not match the default settings of the ASU CD template. This is because the master is actually based on the Setup CD template. You will not be prevented from creating the software master.
Access the Work With Software Mastering form.
You can proof software master definitions. To do so, you create a report, which details each build step in the definition and lists the sequence of steps and processes that each step will run when creating the actual master.
Proofing a software master definition does not change any part of the status of a software master.
To proof a software master definition, perform one of these actions:
To proof one software master definition, select the definition that you want to create, and then select Proof CD from the View menu.
To proof all software master definitions for a specific release, select Proof Release from the View menu.
On the form that appears, enter the release number of the definitions that you want to proof.
This section provides overviews of software master templates, the all build step processes, the ASU CD template, and the custom CD, and lists the forms used to work with software master templates.
The JD Edwards EnterpriseOne Product Packaging Tool uses software master templates. These templates provide default information when you are creating a new software master. For example, to distribute objects to a disconnected enterprise, you would build a master based on the ASU (Application Software Update) CD template. Oracle's JD Edwards EnterpriseOne Mastering Director would use the ASU CD template to determine which director steps, build steps, and directory structure to use when creating the software master. You can configure the default information that is provided by the templates.
You use build steps to build a template. Build steps are the processes that are used to create a software master. You also can add, revise, copy, and delete software master templates. After you add a template, you can use the JD Edwards EnterpriseOne Mastering Director to create a software master definition using that template.
The processes for revising, copying, proofing, and deleting software master templates are identical to those for the software masters themselves.
A template can offer all of the following software mastering build step processes. Not all of these processes appear on every template.
Type = 00
Performed Automatically = Not applicable
This build step is the default process when you are adding a new build step to a software master or template. After you add this build step, you need to define it for the master or template.
Type = 01
Performed Automatically = Yes
This build step creates the physical directory structure at the image-path location that you specified when creating the software master definition.
Type = 02
Performed Automatically = Yes
This build step builds the assigned package based upon the package assembly and build definitions.
Type = 03
Performed Automatically = No (See the specific template definition for complete information about the performance of this build step.)
This build step enables the administrator to instruct the user how to perform a process that has not yet been automated. You should verify the mastering steps and options of this step before beginning the master.
Note:
The software mastering batch process stops when it encounters this build step. After you complete this build step, change its status to Succeeded (status code 60), and restart the software mastering batch process.Type = 08
Performed Automatically = Yes
For Oracle internal use only.
Type = 09
Performed Automatically = Yes
For Oracle internal use only.
Type = 10
Performed Automatically = Partial (See the specific template definition for complete information about the performance of this build step.)
This build step creates the pristine data tables in the final pristine database that corresponds to the given set of modules.
Type = 11
Performed Automatically = Yes
For Oracle internal use only.
Type = 12
Performed Automatically = Yes
For Oracle internal use only.
Type = 13
Performed Automatically = Yes
This build step builds the change tables based on the change table configuration that was set up as part of the software master definition.
Type = 14
Performed Automatically = No
For Oracle internal use only.
Type = 15
Performed Automatically = Partial (See the specific template definition for complete information about the performance of this build step.)
This build step compresses the final pristine JDE Masters database into the data.cab file in the final image path.
Type = 16
Performed Automatically = Yes
Do not modify this file manually. This build step updates the deployment.inf file that the installation applications use during the update installation.
Type = 17
Performed Automatically = Yes
This build step copies the built package to the target image path. This step also copies any additional files that are defined in the software master directory structure to the target image path.
Note:
If you have already built the package and do not want the mastering process to build the package again, set the status of the Package Build step to 60. When you create the software master, the process bypasses the package build and, when it runs this Copy CD Directory Files step, copies the package.Type = 19
Performed Automatically = Partial (See the specific template definition for complete information about the performance of this build step.)
This build step enables you to specify a Microsoft Windows executable or batch file as part of the mastering process.
Type = 21
Performed Automatically = Yes
For Oracle internal use only.
The ASU CD is the main template that is used with the JD Edwards EnterpriseOne Product Packaging Tools. This template is the basis for delivering objects to distributed enterprises. The Product Packaging ASU Template data is delivered in the ASUTMPL900 configuration package on the Update Center. Use Change Assistant to download and deploy this package. This table shows the build steps and their sequence for an ASU CD:
| Sequence Number | Build Step (Type) |
|---|---|
| 10 | Check Mastering Items (03 - Manual Build Step) |
| 20 | Cleanup Temporary Files (22 - Batch Process) |
| 30 | Create CD File Structure (01 - Create the CD File Structure) |
| 40 | Build (02 - Package Build) |
| 60 | Build Change Tables (13 - Build Change Tables) |
| 70 | Create/Load ASU Change Tables (22 - Batch Process) |
| 80 | Create/Load ASU Control Tables (22 - Batch Process) |
| 90 | Create/Load ASU Misc Tables (22 - Batch Process) |
| 100 | Create/Load New and Regen Tables (22 - Batch Process) |
| 110 | Create/Load ASU OL & VL Tables (22 - Batch Process) |
| 120 | ASU v/s Package Validation (22 - Batch Process) |
| 130 | Compress/Copy Database (15 - Compress) |
| 140 | Copy Package and Feature INFs (22 - Batch Process) |
| 180 | Copy CD Directory Files |
| 190 | Create INF |
| 200 | Create self-extracting executable |
| 210 | Validate the mastered CD |
This table provides additional information pertaining to a particular build step within the ASU CD template:
| Sequence Number | Build Step (Type) with Additional Information |
|---|---|
| 10 | Check Mastering Items (03 - Manual Build Step)
Verify the mastering steps and options of the step before beginning the master. This build step must be executed manually before the Master CD. |
| 20 | Cleanup Temporary Files (22 - Batch Process)
Launches the R967002 batch process using version XJDE0001. This process deletes the files and folders from the directory that you specify (for example, $TEMP\data). |
| 30 | Create CD File Structure (01 - Create CD Structure)
Creates the CD file structure on the Image path. |
| 40 | Build (02 - Package Build)
Builds the defined update package. This build step can be set to Built status if the package has run through the Package Build application. |
| 60 | Build Change Tables (13 - Build Change Tables)
Builds the change tables based on the configuration that was set up during the director phase. |
| 70 | Create/Load ASU Change Tables (22 - Batch Process)
Launches the R9670 batch process using version XJDE0003. This process creates change tables in the XML database, populating the tables from the Change Table data source. |
| 80 | Create/Load ASU Control Tables (22 - Batch Process)
Launches the R9670 batch process using version XJDE0001. This process creates control tables in the XML database, and populates the tables from the Control Table data source. |
| 90 | Create/Load ASU Misc Tables (22 - Batch Process)
Launches the R9670 batch process using version XJDE0002. This process creates miscellaneous tables in the XML database, and populates the tables based on the selections that you made for the objects in the ASU package, the change tables, and the software master definition. |
| 100 | Create/Load New & Regen Tables (22 - Batch Process)
Launches the R96700 batch process using version XJDE0001. This process creates tables in the XML database that are marked as new or regenerate in the table change table or the table conversion scheduler. |
| 110 | Create/Load ASU OL & VL tables (22 - Batch Process)
Launches the R9600400C batch process using version XJDE0001. This process copies to the XML database the Object Librarian, Versions List, and package assembly information for the master. Verify that the data source, which you can set in the processing options for this version, is set correctly. |
| 120 | ASU v/s Package Validation (22 - Batch Process)
Launches the R9671 batch process using version XJDE0001. This process cross- validates information, ensuring that objects, tables, and specifications in the ASU package definition match with the object change table, table change table, index change table, and table conversion scheduler in the software master. |
| 130 | Compress/Copy Database (22 - Batch Process)
Launches R9640E using version XJDE0003. This process compresses the ASU database XML files and copies them from the $TEMP/data directory to the final software master image path as Data.cab. |
| 140 | Copy Package and Feature INFs (22 - Batch Process)
Launches the R9600400E batch process using version XJDE0001. This process copies deployment features INFs, the package INFs, and the feature INFs from the deployment server to the $TEMP directories. |
| 180 | Copy CD Directory Files (17 - Copy CD Directory Files)
Copies additional specified items into the image path. For example, all install programs are copied to the root of the image path. |
| 190 | Create INF (16 - Create INF)
Creates the deployment INF file into the image path directory. |
| 200 | Create self-extracting exe (22 - Batch Process)
Launches the R9640J batch process using version XJDE0001. This process takes the entire software master image and creates a CAB file and a self-extracting executable file in the $TEMP/final directory. You can use either of these files to deliver the software master. Uncompress the CAB file or run the executable file on the deployment server, and then refer to the Application Software Update Guide to update JD Edwards EnterpriseOne with the software master. |
| 210 | Validate the Mastered CD (22 - Batch Process)
Launches R9640D version XJDE0001, which performs post-mastering validation on the master that has been created. Refer to the report output for details. |
The Custom CD is for general use; this CD type has no template. A JD Edwards EnterpriseOne administrator uses this CD type primarily to create backups of source code, documents, and so forth, while still using the JD Edwards EnterpriseOne Product Packaging Tools. This CD type enables you to enter a directory structure that contains all of the files that you want loaded on to a custom CD image. After the process is completed, the administrator can move that image to a CD burner to create the actual CD.