Skip Headers
JD Edwards EnterpriseOne Tools Software Updates Guide
Release 8.98 Update 4

Part Number E14719-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

8 Updating Environments

This chapter contains the following topics:

8.1 Understanding How to Update the Production Environment

Before proceeding with these instructions, you should test the new modifications with a copy of production data in the prototype environment.

Update the production environment after you update and test development and prototype environments.

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:

8.2 Updating the Production Environment

This section discusses how to:

8.2.1 Updating the Production Environment Using OMW

You update the production environment (and other environments) using Oracle's JD Edwards EnterpriseOne Object Management Workbench (OMW).

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.

See "Understanding JD Edwards EnterpriseOne OMW Administration" in the JD Edwards EnterpriseOne Tools System Administration Guide.

8.2.2 Preparing to Use the Updated Production Environment

After you update the production environment, you create a new package, deploy the new package to a workstation, and test the modifications there.

This table lists the requirements to use the updated production environment:

Action Details
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.
Concurrent Tasks None

To prepare to use the updated production environment:

  1. Create a new package.

    See "Building Packages" in the JD Edwards EnterpriseOne Tools Package Management Guide.

  2. Deploy the new production package to the workstation.

  3. Surface test the updated production environment.

    After you finish testing the environment, you can deploy the package to other workstations.