1. Implementing 64-bit Processing with a 32-bit Deployment Server in JD Edwards EnterpriseOne Learning Path
  2. Upgrading Deployment Server (32-bit)

Upgrading Deployment Server (32-bit)

Uploading Software Component

  1. Log on to Server Manager.
  2. On Managed Homes and Managed Instances page, on left of page, under INSTALL, click on Manage Software.
  3. Select Browse to browse to a downloaded jar file, “<release>Release.DS.Win32_<date>.jar” and select upload. This will take a few minutes to complete. When complete, the downloaded file will display under the Managed EnterpriseOne Software Components Section as “EnterpriseOne Deployment Server <version> <bitness> <date>”, for example: “EnterpriseOne Deployment Server 9.2.3.0 X86 07-18-2018_06_57”.
  4. Under Managed EnterpriseOne Software Components, check the downloaded jar file, “EnterpriseOne Deployment Server <version> <bitness> <date>” and click on Distribute.
  5. On Managed Software Component page, check the box associated with the EnterpriseOne Deployment Server and click Distribute Software. This will distribute the component to the Server Manager Agent.
  6. Select Management Dashboard in upper left to return to the Managed Homes and Managed Instances page.

Change Tools Release Software Component

  1. On Managed Homes and Managed Instances page, under the Managed Instances column, locate the EnterpriseOne Deployment server and select on the deployment server.
  2. In the General section of the page, under EnterpriseOne Deployment server: <deployment server>, click the Change button.
  3. On the Change Tools Release dialog box, select the Software Component radio button for the version that was downloaded.
  4. Select the second radio button “Component Change and Backup Current System for Multi-foundation”. This will save the current system and OneWorld Client Install files to a “foundation_<version>” directory and copy in the new downloaded system and OneWorld Client Install to the directories.
  5. A dialog box will prompt for the user name and password for the SYSTEM datasource. Enter the user name and password and click, Ok.
  6. Various dialog boxes will occur indicating the step it is on. Be patient thru this process.
  7. When complete, it will have backed up the previous system and OneWorld Client install into a “foundation_<version>” directory and copied down the new system and OneWorld Client install into the current install location. Also, it creates a new foundation item/record of the new system for package build.

View New Foundation Directory

  1. Navigate to the <deployment server>\E920 directory.
  2. Validate there is a “foundation_<version>” directory created by Server Manager. The contents of this directory is the previous artifacts of the deployment server. The directory will contain all of the proper artifacts required for the deployment server:
    • System
    • SystemComp
    • OneWorld Client Install
    • CD Templates\ESU&ASU
  3. Validate that the existing directories under <deployment server>\E920 were updated with the new version:
    • System - validate system\bin32\ptf.log is the correct downloaded version.
    • SystemComp - validate system\bin32\ptf.log is the correct downloaded version.
    • OneWorld Client Install – validate the date and time stamps has changed.
    • CD Templates\ESU&ASU -¬ validate the date and time has changed.
  4. Navigate to the <deployment server>\E920\package_inf file and open an existing package definition file, for example: DV920FA.inf. Notice the path for the SSYS value now contains the path to the version path that was created, keeping the match between the package and foundation it was built against, consistent.