Manually Update Installers
If you are on Tools Release 9.2.3.3 only, you will have to perform the following steps manually. Server Manager was updated in Tools Release 9.2.3.4 to automatically perform the steps, therefore Oracle highly recommends that you update to at least Tools Release 9.2.3.4. If you cannot move to 9.2.3.4 or higher and are moving to 9.2.3.3, continue to the steps below.
If you are moving to Tools Release 9.2.3.3, do these steps:
- On the Deployment Server, rename the old installers’ directories BEFORE
applying the Tools Release.
The Tools Release 9.2.3.3 and higher Development Client, WLSH4A, and WASH4A installers are not compatible with installers from prior Tools Releases; therefore, the new installers must be placed into empty directories on the Deployment Server.
Rename the following directories under <E1_dep_svr_install_directory>\OneWorld Client Install (for example, add “_backup” to the end of their names). Ignore any that you are not using (for example, those for WLSH4A or WASH4A).
\install
\stage
\ThirdParty\WebDevFeature\WLSH4A\install
\ThirdParty\WebDevFeature\WLSH4A\response
\ThirdParty\WebDevFeature\WLSH4A\stage
\ThirdParty\WebDevFeature\WASH4A\install
\ThirdParty\WebDevFeature\WASH4A\response
\ThirdParty\WebDevFeature\WASH4A\stage
- In Server Manager Console, apply the new Tools Release to the Deployment Server. Instructions are provided in the JD Edwards EnterpriseOne Server Manager Guide.
- Update the new Development Client installer’s oraparam.ini with the section/key
pairs shown in the table in Section 2.3.1: “Update the oraparam.ini File for the
Development Client Installer”.
Important: Be sure to start with the new oraparam.ini that came with the new Tools Release because the new file contains some values that must match with the new installer. You should only update those settings in the table.
No changes are required to the oraparam.ini
or response files for the
WLSH4A and WASH4A installers. Use the files that came with the installers.