Deployment Server Recovery When There Is NO Backup

1. Install Deployment Server

2. Install the latest Planner ESU (DO NOT apply - just double click on the setup.exe to expand only the planner ESU or download and install from change assistant, but do not go into E1 Software Updates application P96470 to apply it to pathcodes. Also, be sure to run the setup.exe using the 'Run as Administrator' option.)

3. Install the Service Pack / Tools Release - the one which matches the Service Pack / Tools Release level on the enterprise server

4. Manually create System- XX Data source in Planner Data Source before running R9840C report as this report requires System -XX data source in Processing Option. Define the Data Source in Work With Data Sources (P986115) Application.

5. Copy the CNC System information from the DB server to JDEPLAN (R9840C). 

Run UBE R9840C XJDE0001 from the Deployment Server - JDEPLAN Environment to Copy System Information as following:

== Fast path to ‘BV’ for batch versions. Type as the Batch Application R9840C; click Find.

a. Highlight the XJDE0001 batch version.

b. Click the Select button.

c. Click on Form exit | Advanced.

d. Click the Override Location check box and click OK.

e. Click the Submit button.

f. Highlight the LOCAL Data Source and click the Select button.

A Processing Option form will appear. It is critical that the processing option be properly updated so as to synchronize your ‘System – xxx’ relational database with your local ‘JDEPLAN’ database. This UBE will produce a Adobe PDF file to summarize some changes that were made. Modify the processing options as per Table "R9840C Processing Options" shown directly below. Then click OK to launch the UBE.

"R9840C Processing Options"

TAB: From->To:

         From Data Source: System – XXX =  System DB

         To Data Source:     Planner – XXX =  Planner DB

TAB: Components:

        Copy ALL Plan Components (Y/N): Y

        Enter a 'A' to only add related data (no records will be replaced) or a 'C' (default) if records are to be replaced.

        Related Data: Add or Change: C

TAB: Data Sources:

        Copy Plan Data Sources (Y/N): Y

        Related Records:

       Copy Data Source Records (Y/N): Y

TAB: Environments:

       Copy Plan Environments (Y/N): Y

       Related Records:

       Copy Environment Master Records (Y/N): Y

       Copy OCM Records (Y/N): Y

       Copy Object Path Master Records (Y/N): Y

6. Back-up Central Objects.

7. Apply ALL the Software Updates - ESUs to DV. 

The recommendation is to apply the ESUs to one path code - then, copy the source / include / res and the ESU patch history to the other path codes.  

UBE R9672 XJDE0001 allows you to copy ESU history from one path code to another.

Run R9672\XJDE0001 via Batch versions in later releases of E1.  If you log into JDEPLAN it will update the tables in System Local and if you log into a non-JDEPLAN environment it will update them in System - 910.

For the Processing Options, just enter the source and target pathcodes.

Before running this you may also want to backup the F9671 and F9672 tables in local and system.

8. If there are any custom business functions,  custom Tables that had a *.h file, or, custom changes to the JDE business functions, then these *.c  and *.h files need to be restored from the client machine OR from the enterprise server manually by copying them back to the deployment server to  <pathcode>/include and <pathcode>/source. If restored from the enterprise server,  just note that if the custom business function was marked as "Client Only" then will need to be retrieved from a client machine. They will not be on the enterprise server. It is best to copy them from a client machine from the last FULL package that was built and deployed.

9. Build FULL packages for each environment

Until you apply the ESUs, the source and include directory under the pathcodes on the deployment server do NOT have the include and source files in the ESUs. After ESUs are implemented and objects merged to the pathcodes, we recommend to build a full package for each environment.

reference: Doc ID 1271758.1