5 Running Software Updates

This chapter contains the following topics:

5.1 Understanding Software Updates

After downloading the software update or updates, selecting the update to install, and selecting the environment to be updated, you choose to run the software update workbenches in either attended or unattended mode.

It is recommended that you use the JD Edwards EnterpriseOne and World Change Assistant to run software updates. However, if you choose not to use the JD Edwards EnterpriseOne and World Change Assistant (for example, if your company has fire walls that block your access), then use the methods discussed in this chapter to run updates.

You will use Oracle's JD Edwards EnterpriseOne Table Conversion Workbench if you are applying any Application Software Update (ASU).

Depending on the contents of the update, these workbenches may run:

  • JD Edwards EnterpriseOne Control Table Workbench runs the batch applications for the planned merges that update the data dictionary (DD), user-defined codes (UDCs), menus, and workflow tables. It then updates the F98405 table to reflect completion, and writes a conversion log record to the F984052 Table Conversion History Log.

  • JD Edwards EnterpriseOne Table Conversion Workbench runs the batch application that creates tables and indexes. It then updates the F98405 table to reflect completion, and writes a conversion log record to the F984052 Table Conversion History Log.

  • JD Edwards EnterpriseOne Specification Table Merge Workbench runs the batch applications that update the specification tables. It then updates the F98405 table to reflect completion, and writes a conversion log record. The Object Librarian and Versions List merges are now a part of the specification merge.

  • JD Edwards EnterpriseOne Package Workbench transfers the F9603 and F9631 Package Information tables from the Planner data source to the System - 900 data source. It then updates the Package Plan Detail table (F98404) to reflect completion.

5.2 Working with the Software Updates

The software update application combines a series of individual update workbenches into a single process. You will see only the workbenches that apply to your update.

You can run the workbenches manually (attended mode), or automatically (unattended mode). If you run the workbenches unattended, you will start the update as described. The status of each individual workbench will display as the workbench begins. Unattended mode is the default.

5.3 Starting and Running the Software Updates

This section provides an overview of starting and running the software updates and discusses how to:

  • Select environments and start the software.

  • Replace language data when running a language update.

  • Restore a backup.

5.3.1 Selecting Environments and Starting the Software Update

The following procedure lets you select environments and starts the software update workbenches in unattended mode or attended mode. Unattended mode is the default.

In unattended mode, if an error is encountered in any of the individual workbenches, the process stops. Fix the error and continue. The software update resumes.

This procedure also creates a JD Edwards EnterpriseOne Object Management Workbench (OMW) project, an installation plan, and an update package for this update. In addition, the procedure optionally creates a backup of specs, so that the original specs can be restored if necessary.

Do not lock the deployment server during the software update (for example, with a screen saver password) because doing so pauses some processes. In addition, do not minimize any of the workbench forms, or the software update will not continue to the next workbench form until it is again maximized.

If you use a SQL Server database, be sure that these database options are selected before you start the software update:

  • Select Into/Bulk Copy.

  • Truncate Log on Checkpoint.

This table lists the requirements for starting the update workbenches:

Task Details
Personnel Installer
Logon status On the deployment server, logged on as user JDE with the database password for user JDE, in the JDEPLAN environment.
Prerequisites Software update installed on the deployment server.
Concurrent Tasks None

To select the environment and start the update workbenches:

On the deployment server, log on to the JDEPLAN (planner) environment as user JDE with the database password for user JDE.

From the System Installation Tools menu (GH9612), select Application Software Update, Electronic Software Update, or Language Update, depending on the type of update you are installing.

  1. On Work with Software Updates, select the software update that you want to install. Click Next.

    Important!:

    If you want to install more than one update at the same time, you must use the JD Edwards EnterpriseOne and World Change Assistant. See Using Change Assistant for more information.

    The Work with Software Updates panel presents these row exits:

    • Select

      Selects the software update, and puts a check mark in the media object column for the selected row.

    • Deselect

      Deselects the software update, and puts an X in the media object column for the selected row.

    • Update Detail

      Provides more information on the software update

    • Update Status

      Shows the statuses of the processes that run during the software update.

    • Update Sched Comp

      Displays all merges (DD Merge, Spec Merge, and so forth) that are scheduled for the software update. This row exit is not applicable for language updates.

    • Update Objects

      Displays all objects, SARs and dependencies that are part of the software update. Use this exit to check for dependent and baseline updates.

      Note:

      If you don't install the correct dependent or baseline updates, the system will display an error message.
    • Update Cntrl Table

      Displays all DD, UDCs, Menus, Favorites, Tips of the Day, and Report Director Templates that are delivered with the software update. This row exit is not applicable for language updates.

    • Update Table Changes

      Displays table changes delivered with the software update.

    • Update Index Changes

      Displays index changes delivered with the software update.

    • Update History

      Shows the environment and plan history of the software update.

    • Advanced Setup

      The program performs a series of common processes when each software update is run on the first environment. If you want to run these processes on a second environment, however, you must use this option to select processes that you want to run again. Note that you must clear the check boxes for the processes you want to run again.

    The Work with Software Updates panel presents these form exits:

    • Remove Updates

      Opens the Software Update Remove form where you can choose packages to remove. You can also select to remove files only or history and files.

    • Update Hist. Rpt

      Runs a report of all of the software updates that have been applied.

  2. Double-click the environments where you want the software update installed.

  3. If you want the software update to run in unattended mode, verify that the Unattended Workbench check box is selected. Unattended Workbench is checked by default.

  4. If you want to make a backup of specs, so that the original specs can be restored, select the Backup check box. Backup is selected by default. This option is not available for language updates.

    Note:

    If you have custom modifications and will be retrofitting these to the new update, it is strongly recommended that you make a backup of your original specs. For more information about retrofitting, see Retrofitting Custom Modifications.

    The Backup option creates a backup directory with the path planner\package\software update name\PATHCODE.BAK (for example, \planner\package\JL123456\DV900.BAK). All artifacts for the delivered objects (specs, source, include files) are stored in a single file with the extension .PAR. Control tables (data dictionary, UDC, and others) are not backed up. The contents of the backup file may be viewed with the JD Edwards EnterpriseOne Universal Table Browser tool or WinZip.

  5. Select the Create OMW Project and Package Assembly check box if you want to create the OMW project and package assembly record for the software update. This option is not available for language updates.

    The Software Update Environment Selection panel also presents these row exits:

    • Select

      Selects the environment to be updated, and puts a check mark in the media object column for the selected row.

    • Deselect

      Deselects the environment to be updated, and puts an X in the media object column for the selected row.

    • Affected Objects

      Use this exit to view:

      • Objects that will be installed.

      • SARs that will be installed to a specific path code.

      • Checked out objects.

      • Modified objects.

      • Objects with tokens.

      This row exit is not applicable for language updates.

    • Restore Backup

      If backups were performed for a software update for a specific environment, this option restores all specs and business functions. Control tables are not backed up and hence will not be restored. For information about restoring a backup, see Restoring a Backup. This row exit is not applicable for language updates.

    • Delete Backup

      Deletes the backup directory created, and frees up disk space. A warning message is displayed if no backup was performed. This row exit is not applicable for language updates.

    • Advanced Setup

      When applying software updates to alternate environments, we recommend that you do not perform the spec merge. Instead, transfer objects using OMW. However, this exit enables you to override this option and run the spec merge.

5.3.2 Replacing Language Data when Running a Language Update

In order to preserve your customized language records, the update process only appends new language records in the target environment and does not update any existing records. This is the default setting for updates, but you can change this setting by changing a processing option.

If you do not have any customized language records, you may want to change the processing option value so that changes delivered in the language update will replace the current records. Follow these steps to change the processing option value:

  1. After installing language updates on the deployment server, sign onto JD Edwards EnterpriseOne JDEPLAN on the deployment server.

  2. Enter BV in the Fast Path to open the Batch Version application.

  3. Find R98403XB and select version XJDE0030.

  4. Select Processing Options from the Row Menu.

  5. On the Advanced Tab, enter 'Y' for the following processing option:

    Enter a 'Y' to replace duplicate records in the target table, or enter 'N' (or leave blank) to preserve duplicate records in the target table.

  6. Click OK to save your changes.

  7. Repeat this process and change the same processing option value to a 'Y' for versions XJDE0031, XJDE0032, and XJDE0033.

  8. Enter GH9612 in the Fast Path.

  9. Run Language Updates to apply the update to the target environment.

5.3.3 Restoring a Backup

Use this procedure to restore a backup you made while starting the software update. If you are not restoring a backup, skip this section and proceed to Completing the Update.

You can restore a backup if you selected the Backup check box on the Software Update Environment Selection panel, as described previously.

To restore a backup:

From the System Installation Tools menu (GH9612), select Application Software Update, or Electronic Software Update. The Work with Software Updates panel appears.

  1. Select the software update for which you want to restore the backup.

  2. Click Next. The Software Update Environment Selection panel appears.

  3. Select the environment for which you want to restore the backup.

  4. On the Row Exit menu, click Restore Backup. The backup is restored.

    This may take several minutes.

  5. Click Cancel to close the Software Update Environment Selection panel.

    Note:

    The restore process doesn't remove objects that were added through the software update. If you wish to remove the added objects, use the JD Edwards EnterpriseOne Object Management Workbench (OMW) project created by the software update. A list of added objects can be found in the software update spec merge report.

    If you are restoring objects for a software update that you have already transferred to other path codes, make sure you re-transfer the restored specs to the other path codes using OMW. If you wish to remove the added objects in all path codes, use the OMW project created by the software update.

5.4 Completing the Update

This section provides an overview of the completion process for the attended mode and discusses how to complete these update workbenches:

  • Add a Security Override for Running Table Conversions.

  • Run Table Conversions.

  • Configure your control tables.

  • Merge your specification tables.

  • Restart the Specification Merge.

  • Configure your packages.

  • Validate the update.

If you selected the unattended mode, the process begins and all workbenches are completed automatically. In this case, skip the following tasks and continue with "Custom Modifications and Packages."

When the workbenches are complete, an update package must be built.

When the software update begins, status messages appear in the status bar at the bottom of the screen reporting progress. If an error occurs, the process stops. In this case, click Previous to return to the Work with Software Updates screen, and then, on the Row menu, click Update Status. Status messages are displayed.

5.4.1 Adding a Security Override for Running Table Conversions

If your database is Oracle, SQL, or DB2 for Linux, UNIX, and Windows, you must add a security override so that the table conversion process can drop and recreate a table. Adding a security override must be done by a security administrator. To add a security override, you must first add a system user for the data source owner, and then add an override for the EnterpriseOne user who will run the table conversion.

To add a system user for the data source owner:

  1. In P98OWSEC, select the form exit Add System User.

  2. On Work with System Users, enter the appropriate data source owner (for example PRODDTA,TESTDTA, or CRPDTA) in the System User field and select Find.

  3. If no values are returned, add the data source owner as a system user by selecting Add and completing the fields on the System User Revisions form:

    • System User

    • Data Source

    • Password

    • Password Verify

  4. Click OK and then Cancel and Close to return to the Work with User Security form.

To add an override for an EnterpriseOne user who is going to run the table conversion:

  1. On Work with User Security, enter the user who is going to run the table conversion, and select Find.

  2. Select the Form exit, Add Data Source.

  3. On Add Data Source, complete the User ID, Data Source, and System User fields.

Note:

This override can be deleted once the table conversion has run.

Note:

For IBM i, either sign on as a user who has *ALLOBJ rights to the table to be converted or complete the steps above, setting up a security override for the EnterpriseOne user so that when they connect to the data source, they connect as a system user (IBM i user profile) who has *ALLOBJ rights to the table.

5.4.2 Running Table Conversions

Table conversions are performed after applying the software update to the path code. Review the special instructions for the software update that you are applying to see if there are any table conversions.

Note:

You must be signed on as an administrative user who has rights to change security overrides.

To run table conversions:

  1. Build and deploy an update package containing the software update changes.

  2. Install the update package on an administrative client.

  3. Sign onto the administrative client in the environment that had the changes applied.

  4. For each table conversion that is going to be run, check which data source contains the base table that the table conversion is changing. The name of the table should be in the special instructions.

  5. Add security overrides for the JD Edwards EnterpriseOne user who will run the table conversions.

    See Adding a Security Override for Running Table Conversions.

  6. Go to Batch Versions and verify, on the Properties tab for the table conversions, that the input and output environments point to the login environment.

  7. Run the table conversions.

  8. Review the table conversion logs in the print queue, and verify that the table conversions completed successfully.

5.4.3 Configuring your Control Tables

If you are running the software update in unattended mode, this process is run automatically.

Complete this task to configure your control tables.

  1. On Control Table Workbench, the system displays all control table merges in the detail area. From the Form menu, select Merge All.

  2. After each merge finishes, verify the output of the report produced.

  3. From Control Table Workbench, click Next.

5.4.4 Merging your Specification Tables

If you are running the software update in unattended mode, this process is run automatically.

To merge your specification tables:

  1. On Specification Table Merge Workbench, from the Form menu, select Merge All.

  2. After the merge finishes, verify the output of the report that is produced.

  3. After all merges complete, click Next.

    The Package Workbench form appears.

5.4.5 Restarting the Specification Merge

If you are running the software update in unattended mode, this process is run automatically.

If the Specification Merge stops before it completes successfully because the merge of an object fails, you can restart it from the point where it stopped. If all merges complete successfully, you can skip this task.

To restart the Specification Merge:

This table lists the requirements for restarting the specification merge.

Task Details
Personnel Installer
Logon status On the deployment server, logged on as user JDE with the database password for user JDE, in the JDEPLAN environment.
Prerequisites Specification merge must be stopped.
Concurrent Tasks None

Before you restart the Specification Merge you must set the status of the failed merge back to Not Processed (zero). The restarted Specification Merge will skip completed merges and process the failed merge and all subsequent merges.

Use this procedure to set the status of the failed merge back to Not Processed (zero):

From Advanced Operations menu (GH9611) select Specification Merge Status (P98700).

  1. On the SpecMerge Status panel, complete these fields:

    • Package Name

      Enter the name of the software update.

    • Source Environment

      Enter JDEPLAN (the Planner environment).

    • Target Environment

      Enter the name of the environment you are updating.

  2. Click Find. All objects that are part of the specification merge are displayed.

  3. Select the object for which the specification merge failed. The object will have a status of 4 (Error) in the Merge Status column.

  4. On the Row Exit menu, click Reset Merge Status. The Reset Merge Status panel appears.

  5. In the New Merge Status field, specify 0 (zero, or Not Processed).

  6. Click OK.

    The object's merge status is changed.

  7. Click Close.

You can now restart the specification merge.

5.4.6 Configuring your Packages

If you are running the software update in unattended mode, this process is run automatically.

Package Workbench transfers the F9603 and F9631 Package Information tables from the Planner data source to the System - 900 data source. It then updates the Package Plan Detail table (F98404) to reflect completion.

If you are running the software update in unattended mode, this process is run automatically.

Item Details
Personnel Installer
Logon status On the deployment server, logged on as user JDE with the database password for user JDE, in the deployment environment (DEP900).
Prerequisites None
Concurrent Tasks None

  1. On Package Workbench, review your packages.

  2. From the Form menu, select Configure. The Congratulations form appears.

  3. Click Finish. The Software Updates History report will appear.

    Note:

    After this screen appears, processing continues to occur in the background. Once completed the program displays a message that the update was completed successfully.

    After this report appears processing continues in the background. Once this is completed, an Update Completion message appears.

  4. Click OK.

See Also:

5.4.7 Validating the Update

After the spec merge process, JD Edwards EnterpriseOne generates the Software Update Report (R96701) that lists the updated objects and the SARs addressed by the update.

For Tools Release 9.2.1.x and after, if the path code value in the F00942T.emdbsrcflg field is set to 1, this report also updates the Object Librarian Archive Repository (F98780R) and Object Librarian Archive History (F98780H) tables in central objects.

This report is summarized in a PDF file that opens automatically once the update process is complete. If the spec merge process fails, this report is not created.

To validate the update process, view the R96701 report and note the value of the Object Install Flag for each of the objects listed in the report:

Object Install Flag Value Description
0 The object was not updated because the existing object in the environment is more recent that the object in the software update.
1 The object is selected to be applied to the environment. (This is the status of all objects in the list before the upgrade starts, but should not be observed when the update process is complete.)
2 Updated object was applied to the environment.

For Tools Release 9.2.1.x and after, also, note the value of the Update Repository Table column for each of the objects listed in the report:

Update Repository Table Value Description
Not Applicable The object was not updated by the spec merge so there was no need to save it to the F98780R and F98780H tables.
Updated The object was updated in the F98780R and F98780H tables in central objects.
Not Updated There was an error saving the information to the F98780R and F98780H tables.