|JD Edwards EnterpriseOne Tools Software Updates Guide
Release 8.98 Update 4
Part Number E14719-02
|PDF · Mobi · ePub|
This chapter contains the following topics:
Do not include additional environments when updating the live production environment. The purpose of isolating the update of production is to minimize production downtime.
Oracle's JD Edwards EnterpriseOne Global Support Center maintains several documents that describe how to manage and promote Software Updates. These documents address many details of the update process and complement the current documentation.
To access these documents, log on to My Oracle Support, and click the Knowledge tab. Perform a search for the following documents:
Best Practice for Managing Software Updates
Applying and Promoting Software Updates
Understanding and Managing Planner ESUs
This section discusses how to:
Update the production environment.
Prepare to use the updated production environment.
The software update process creates an OMW project for this update. To update the production environment, promote the project in OMW to the appropriate status as defined by the activity rules. (For example, if you are using Oracle's default JD Edwards EnterpriseOne conventions, you can promote a project from Development to Prototype by changing the status from 21 to 26. For more information about your organization's activity rules, see your JD Edwards EnterpriseOne administrator.)
Note:If the software update process runs the table and index creation batch application (R98407 in F9843) and you are using OMW to promote the project to the production environment, you must manually create and regenerate the table and index in OMW.
This table lists the requirements to use the updated production environment:
|Personnel||Installer or system administrator|
|Logon status||On the enterprise server, logged on as user JDE with the database password for user JDE.|
|Prerequisites||Run the installation plan for the production environment.|
To prepare to use the updated production environment:
Create a new package.
Deploy the new production package to the workstation.
Surface test the updated production environment.
After you finish testing the environment, you can deploy the package to other workstations.