IBM B73.3 manual Installation Planner Defining the Installation Plan

appropriate user IDs, passwords, and other variables, then run the batch files to load the tables. The following steps must be performed on the deployment server:

1.Edit the batch files LOADDEVL.BAT, LOADPROD.BAT, LOADPRST.BAT, and LOADCRP.BAT in the \OneWorld\B733\Database\Exports\Oracle\NT directory to reflect your environment by completing steps 2 - 4.

Note: For Oracle8, you must change the references from imp73 to imp80, and from plus33 to plus80.

2.In the JDESET.BAT file, check the machine name (identified by machinename) and connectstring. The machine name should be the name of your enterprise server and the connectstring should be your database SID (orc1). The connectstring should be updated for each path code.

For example, XXX_SPEC_DB=orc1 and JDE_SRV=IBM5500ES.

3.Edit the LOADALL.BAT script. It’s located in the d:\OneWorld\B733\Database\Exports\Oracle\NT subdirectory.

Note: The LOADALL.BAT is a script that will load production, pristine, and Conference Room Pilot (CRP) sets of specifications tables. If you want to load development, or do not load other specifications, edit LOADALL.BAT appropriately. For this example, only CRP and Production will be used, therefore, do not remark them.

4.Run the batch file to load the data by double-clicking the LOADALL.BAT file. After completion, check the log files that it created for errors.

Note: This step can take from two to four hours to process each path code.

7.3.2Installation Planner - Defining the Installation Plan

The Installation Planner is a OneWorld application that runs as a stand-alone program on the deployment server. It is also a system administration tool. The Installation Planner lets you manage the following processes:

•Location revisions

•Deployment server revision

•Enterprise server revision

•Machine server types

•Data source setup

•Environment selection

•Data load parameters

•Validation plan

•Running Release Master

The Installation Planner will guide you in a step-by-step process toward defining your installation plan. In the example below, we used it to define and set up the enterprise and deployment server, data sources, Conference Room Pilot (CRP) and Production package builds and environments. After completing your plan, you will load OneWorld on the enterprise server.

Implementing Oracle8 and J.D. Edwards’ OneWorld 115