Understanding the Upgrade of the Production Environment
Use this procedure after all testing has been successfully completed. This procedure brings your live production environment from the previous release to the newly upgraded release, which in this document is Release 9.2.
In a normal upgrade, there is an upgrade environment, such as development or CRP\PY, and then there is the live environment such as production. During the first phase of an upgrade, all modifications and customizations that are to be kept for the new release are transferred into the upgrade environment. The upgrade then converts the central objects with the table conversions and specification merge, business data table conversions, and control table merges. Once this upgrade is successfully tested, the production environment is ready to be brought up.
The new production environment borrows the already successfully merged central objects containing all your mods and customizations, and can borrow the successfully merged control tables as well. This leaves the business data table conversions as the only merge or conversion that needs to be run in order for Production to be successfully prepared. However, if you decide not to copy the control tables from the PY to the PD, then you will have to rerun the control table merge.
For Release 9.2 on the Deployment Server, Security Server should be turned off during the workbench. The may be security issues if you are using Signon Security during the workbench. There may be password issues when there is not a database sign in as JDE with password JDE.
During both the Upgrade and the Update of the production environment, the workbench begins with the Initial Tasks. The initial tasks runs four reports explained below. However, since these reports have been previously run during the initial upgrade, the Batch Application will run, but do not copy over any data by default. Alternatives to the way these run by default are discussed below the Batch explanations.
Normally after you have upgraded all other environments, you upgrade the live production environment. This chapter explains how to upgrade the production environment with a minimum amount of production downtime.
Before proceeding:
Apply Planner Update to PS920 and PY920
Build and deploy full server package to PS920 and PY920
Test all custom modifications in PY920
During the first phase of an upgrade, all modifications and customizations are transferred into the upgrade environment. The upgrade then converts the central objects with the table conversions and specification merge, business data table conversions, and control table merges. Once the upgrade is successfully tested, the production environment is ready to be brought up. The new production environment will borrow the already successfully merged Central Objects containing all your modifications and customizations, and can borrow the successfully merged Control Tables as well.
The Production Upgrade only converts business data. All shared data, system data, control tables, etc. needs to be converted. Objects and version are copied from the PY920 environment. Then, the Business Data Table conversions is the only merge or conversion that needs to be run in order for Production to be successfully prepared. However, if you opt not to copy the Control Tables from the PY to the PD, then you will have to run the Control Table Merge again.
You cannot use the Updating the Production Environment section if you need to bring any additional object specification changes. This is a distinguishing factor between an upgrade and an update of the production environment.