1. Software Updates Guide
  2. Deploying Packages

Deploying Packages

Before deploying a package, you should check whether the prerequisites or dependencies for the package have been deployed. This information is displayed on the Dependencies tab.

When you click the Deploy button, the activity log is checked to determine whether any of the selected packages have been superseded. If so, a list of these packages is displayed. Also, the log is checked to determine whether all prerequisites for the selected packages have been deployed. If not, a list of these dependencies is displayed and you can continue or cancel deployment.

To deploy packages:

  1. Select Deploy.

  2. From the Deploy drop-down list menu, select one of these two options:

    • Deploy

      Select Deploy to search for a previous batch for the current object at an "in process" status. The system will restart that deployment where it left off or if it cannot find any batches with an "in process" status, it will start a new batch. This is typically used in an Oracle Business Accelerator (OBA) where there is a question and answer session that may require input from multiple sessions, but the "logical" session remains intact.

    • New Batch Deploy

      Select New Batch Deploy to start deployment of a new batch.

  3. Select Run All to deploy all of the packages.

  4. If multiple packages are selected, a new window is launched and the packages are deployed as an aggregate.

  5. If a single package is selected and if the package is suitable for deployment, one of the following processes will occur, depending on the type of package that is selected:

    • If the package is a documentation package, the documentation link is displayed in a new documentation window, and clicking the link launches the associated application.

      If the link points to an HTML page that resides inside the package itself, it is directly displayed in the window.

    • If the package only contains some files that need to be extracted to the disk, the extract window is displayed.

    • If the package is a PAR file that contains some deployment tasks or is an EXE file, a new window is displayed that enables you to view the documentation for these tasks and run them.

      Configurations and packages with JD Edwards EnterpriseOne tables or objects are validated for their release level. If the source and target release do not match, a warning is displayed. If you choose to ignore this warning, you must give careful consideration to changed table formats, object dependencies, and so forth.

      During the deployment of configurations that contain versions, the Versions tab appears. Use this tab to change the version prefix. Enter the From Prefix and the To Prefix values in the grid.

      Note: The new prefix string must be the same length as the old prefix.

    • If the package is an ESU, a new window is displayed that prompts you to select the target deployment environments and the following deployment options:

      Batch Deployment Option

      Description

      Backup

      Select the backup check box to create a backup of object specifications included in the updates. Backups are used with the compare/merge tools to aid the retrofitting process and to examine changes made by the update. Backup is selected by default.

      Environment

      Select the environments to which you want to deploy the update. It is recommended to apply updates to the Pristine and Development environments using Change Assistant. After retrofitting custom objects, you can transfer the objects to the Prototype and Production environments using OMW.

      Notes

      Use this tab to add any runtime notes that you would like displayed on activity reports and during restart of a deployment.

      Skip Spec Merge

      Select this option if you would like to skip the spec merge for objects for a particular environment.

      Skip OMW and Package Build Data

      Select this option to skip the creation of OMW projects and package build definitions.

      Summary

      Select this option to deploy the group automatically with minimal status information. If you do not select this option, you step through each task of the deployment with full status. The manual mode requires clicking the Run or Run All button before starting the deployment.

      Unattended

      Select this option to deploy a group of updates in a single process. If you do not select this option, you step through each task of the deployment manually (attended mode). The unattended mode requires no further input after clicking the OK button. The status of each update displays as the application runs.