Вы находитесь на странице: 1из 484

8 February 2002

Update

Installation
Guide
(AS/400 Systems)
Release
OneWorld Xe

Augus

J.D. Edwards World Source Company


One Technology Way
Denver, CO 80237

EJ.D. Edwards World Source Company, 1995 - 2001


All Rights Reserved
J.D. Edwards is a registered trademark of J.D. Edwards & Company.
The names of all other products and services of J.D. Edwards used
herein are trademarks or registered trademarks of J.D. Edwards World
Source Company.
All other product names used are trademarks or registered trademarks
of their respective owners.

The information in this guide is confidential and a proprietary trade


secret of J.D. Edwards World Source Company. It may not be copied,
distributed, or disclosed without prior written permission. This guide
is subject to change without notice and does not represent a
commitment on the part of J.D. Edwards & Company and/or its
subsidiaries. The software described in this guide is furnished under
a license agreement and may be used or copied only in accordance
with the terms of the agreement. J.D. Edwards World Source Company
uses automatic software disabling routines to monitor the license
agreement. For more details about these routines, please refer to the
technical product documentation.

Table of Contents

Overview
Additional Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Updates: The Help You Install Web Page . . . . . . . . . . .
Minimum Technical Requirements (MTRs) . . . . . . . . . . . . . . . . .
Other OneWorld Information on the Help You Install page . . . .
J.D. Edwards Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Premier Maintenance Customer Procedures . . . . . . . . . . . . . . . .
Standard Maintenance Customer Procedures . . . . . . . . . . . . . .
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assumptions Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Considerations Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tips and Techniques Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fonts and Type Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12
13
14
14
14
15
15
16
16
17
18
18
18
19
19

Whats New in the Installation Process


Whats New in OneWorld Xe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New and Changed Features in OneWorld Xe . . . . . . . . . . . . . . . . . .
General OneWorld changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AutoPilot/OneWorld Scripting Tool . . . . . . . . . . . . . . . . . . . . . . . .
Retrofitting Custom Modifications . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Planner Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Standard Name Changes . . . . . . . . . . . . . . . . . . . . . . . . . .
Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Path Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Sources - Central Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Sources - Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Sources - Business Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Sources - Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Sources - Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Local Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OneWorld Xe UPDATE (8 February 2002)

23
23
23
24
24
25
25
25
25
26
26
26
27
27
28
28
28
29
29
210
210

Installation Guide

Table and Index Changes (Oracle Databases) . . . . . . . . . . . . . . 211


SQL Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Temporary Environment Information . . . . . . . . . . . . . . . . . . . . . . . 213

Customer Overview
Customer Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Workstation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environments Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How OneWorld Environments Work Together . . . . . . . . . . . . . . . . . .
The Planner Environment (JDEPLAN) . . . . . . . . . . . . . . . . . . . . . . . .
Planner Path Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planner Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Deployment Environment (DEP7333) . . . . . . . . . . . . . . . . . . . . .
The Test Environment (TS7333) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Development Environment (DV7333) . . . . . . . . . . . . . . . . . . . . .
The Prototype (CRP) Environment (PY7333) . . . . . . . . . . . . . . . . . .
The Production Environment (PD7333) . . . . . . . . . . . . . . . . . . . . . . .
The J.D. Edwards Pristine Environment (JD7333) . . . . . . . . . . . . . .
Language Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Language Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Base Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alternate Language Components . . . . . . . . . . . . . . . . . . . . . . . . .
Language Preference Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Language Installation Process Flow . . . . . . . . . . . . . . . . . . . . . . .
Database Character Set and Code Page Considerations . . . . . . . .
Code Page Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
National Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single-Byte and Double-Byte Considerations . . . . . . . . . . . . . . .
Font Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Display Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

33
36
36
37
38
39
310
310
310
313
314
315
315
315
316
316
317
317
317
317
319
319
320
320
321
323
324
325
326
327
328
329

Pre-Installation Procedures
Finalizing the Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the OneWorld Verification Tool (Environment Checker) . .
Verifying Software and Hardware Requirements . . . . . . . . . . . . . . . .
Windows NT Deployment Server Requirements . . . . . . . . . . . . .
AS/400 Enterprise Server Requirements . . . . . . . . . . . . . . . . . . .
AS/400 Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Desktop Platform/Workstation Requirements . . . . . .
OneWorld Web/Java Client Requirements . . . . . . . . . . . . . . . . .

43
43
49
49
412
414
416
420

OneWorld Xe UPDATE (8 February 2002)

Table of Contents

OneWorld Web/Java Development Workstation


Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Net Web Server Requirements . . . . . . . . . . . . . . . . . .
Windows Terminal Server Edition Requirements . . . . . . . . . . . .
Windows 2000 Terminal Services Requirements . . . . . . . . . .
Verifying OneWorld Disk Space Requirements . . . . . . . . . . . . . . . . .
Completing the Installation Detail Worksheet . . . . . . . . . . . . . . . . . .
Data Sources - Shared for All Environments . . . . . . . . . . . . . . . .
Environments - OneWorld Xe Production . . . . . . . . . . . . . . . . . .
Environments - OneWorld Xe Test . . . . . . . . . . . . . . . . . . . . . . . .
Environments - OneWorld Xe Prototype . . . . . . . . . . . . . . . . . . .
Environments - OneWorld Xe Pristine . . . . . . . . . . . . . . . . . . . . .
Environments - OneWorld Xe Development . . . . . . . . . . . . . . . .

420
422
425
427
431
435
435
437
439
441
443
445

Installing the Deployment Server


Installing OneWorld on the Deployment Server . . . . . . . . . . . . . . . . . . . .
Chapter Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . .
To install and configure the file transfer protocol (FTP) . . . . . . .
Installing the Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing an Alternate Language on the Deployment Server . . . . .
Installing the Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up the TCP/IP Protocol for the Enterprise Server . . . . . . . .
Installing the OneWorld Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing and Installing Oracle for Windows NT . . . . . . . . . . . . . . . .
Verifying Code Page Settings for Oracle Database . . . . . . . . . .
Preparing the Oracle Database for OneWorld . . . . . . . . . . . . . . .
Creating the Database Users and Owners for Oracle . . . . . . . .
Loading Central Objects for Oracle . . . . . . . . . . . . . . . . . . . . . . . .
Preparing and Installing OneWorld for SQL Server . . . . . . . . . . . . .
Verifying Code Page Settings for SQL Server . . . . . . . . . . . . . . .
Creating Databases for SQL Server 7.0 . . . . . . . . . . . . . . . . . . . .
Creating Database Logons and Users for SQL Server 7.0 . . . .
Loading Central Objects for SQL Server 7.0 . . . . . . . . . . . . . . . .
Preparing and Installing DB2/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading Central Objects in DB2/400 . . . . . . . . . . . . . . . . . . . . . . .

53
53
53
54
512
520
522
526
529
529
530
532
537
538
540
541
542
544
545
547
547

Planning the Installation


Overview of Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Language Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enterprise Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Source Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Typical Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding the Typical Installation Process . . . . . . . . . . . . . . . . .
Assumptions about Defining a Typical Installation Plan . . . . . . .

OneWorld Xe UPDATE (8 February 2002)

63
63
64
64
65
65
69
611
611

Installation Guide

Starting Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Entering a Plan Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Location Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Deployment Server Information . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Remote Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finalizing the Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Custom Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding a Custom Installation Plan . . . . . . . . . . . . . . . . . . . . .
Assumptions about Defining a Custom Installation Plan . . . . . .
Starting Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Plan Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Location Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Deployment Server Information . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Data Source Information . . . . . . . . .
Defining Machine/Server Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specify Machine/Server Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Data Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Java Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Windows Terminal Server (Optional) . . . . . . . . . . . . . . .
Entering Shared Data Source Information . . . . . . . . . . . . . . . . . . . . .
Setting Up Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Environment Data Sources . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Remote Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finalizing the Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining AS/400 Common OneWorld Data Sources . . . . . . . . . . . .

611
612
614
615
617
620
620
623
625
625
626
627
629
631
633
633
635
637
637
638
640
642
644
648
654
659
659
661

Running Installation Workbench


Running Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing to Run Installation Workbench . . . . . . . . . . . . . . . . . . . . . .
Verifying the Language Code Character Set . . . . . . . . . . . . . . . .
Editing the Windows registry setting for ODBC
data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Processing Option Text File for Languages . . . . .
Selecting Unattended or Attended Workbench Mode . . . . . . . .
Setting Tasks Breaks in Unattended Workbench Mode . . . . . . .
Running Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Workbench Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Environments . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Control Tables . . . . . . . . . . . . . . . . . . . . . . . . . .
Merging Your Specification Tables . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Your Remote Locations . . . . . . . . . . . . . . . . . . . . . . .

75
75
75
76
76
78
79
711
711
713
715
716
717
719
720
722
723
724

OneWorld Xe UPDATE (8 February 2002)

Table of Contents

Finishing Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . 726

Installing the Enterprise Server


Configuring and Installing OneWorld on the Enterprise Server . . . . . . .
Configuring the Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing OneWorld on the Enterprise Server, and Verifying . . . . . .
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PORTTEST Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the OneWorld Enterprise Server . . . . . . . . . . . . . . . . . . . . . .
Setting Up a Printer on the OneWorld Enterprise Server . . . . . . . . .
Copying Language Specifications to the Enterprise Server . . . . . .

83
83
87
813
815
817
819
832

Installing OneWorld on the Workstations


Configuring and Installing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding Workstation Installation . . . . . . . . . . . . . . . . . . . . . . . .
OneWorld Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . .
Third-party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Profile and Language Considerations . . . . . . . . . . . . . . . . . . . .
Modifying the Workstation JDE.INI File on the Deployment
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cataloging DB2/UDB Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing OneWorld in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . .
Installing OneWorld in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . .

93
93
94
94
95
95
97
97
912

Preparing Packages
Using Visual ER Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Launching Visual ER Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding the Visual ER Compare Interface . . . . . . . . . . . . . . .
Working with Visual ER Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Your Target ER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing a Visual ER Compare Report . . . . . . . . . . . . . . . . . . . . .
Using AutoMerge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building and Testing Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Pre-Package Build Issues . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Post-Package Build Issues . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building an Alternate Language Package . . . . . . . . . . . . . . . . . . . . . .
Package Build Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Package Deployment Considerations . . . . . . . . . . . . . . . . . . . . . .

OneWorld Xe UPDATE (8 February 2002)

103
103
104
105
106
106
107
109
1011
1017
1017
1017
1018
1020
1020
1021

Installation Guide

Completing the Installation


Setting Up Windows NT Security on OneWorld Directories . . . . . . . . . .
Client Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pathcode Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Dictionary Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helps Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hosts Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mediaobj Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planner Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printqueue Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying OneWorld After the Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Media Object Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resetting SQL Server Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying Data Dictionary Files to the Enterprise Server . . . . . . . . . .
Expanding the Distribution Flexible Files . . . . . . . . . . . . . . . . . . . . . .
Updating the Ledger Type Master File (F0025) - P09940 . . . . . . . .
Running the Accounts Receivable Conversion Process . . . . . . . . .
Conversion Audit Envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Work File Build Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the R4094A Batch Application . . . . . . . . . . . . . . . . . . . . . . .
Building Menu and Task Word Search Tables . . . . . . . . . . . . . . . . . .
Configuring OneWorld to Run Autopilot (J.D. Edwards
OneWorld Scripting Tool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up the Solution Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up the Solution Explorer HTML Documentation Path . . . . .
Running the Word Search Generation Program . . . . . . . . . . . . . . . .
Setting Up the Home Page for the Solution Explorer . . . . . . . . . . . .
Configuring OneWorld for Use with Vertex Quantum
Tax Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the OneWorld Database Connections for
Vertex Quantum Tax Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mapping Objects to the Enterprise Server . . . . . . . . . . . . . . . . . . . . .
Testing the Vertex Quantum Connection from OneWorld . . . . . . . .

113
113
114
114
114
115
115
115
115
116
116
117
117
1110
1111
1115
1117
1118
1118
1118
1118
1121
1122
1124
1129
1129
1130
1131
1133
1134
1137
1137

Installation Planner Utilities


Creating a Remote Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding a Remote Installation Plan . . . . . . . . . . . . . . . . . . . . .
Assumptions about Defining a Remote Installation Plan . . . . . .
Starting Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Information into Installation Planner . . . . . . . . . . . . . . . . . .
Entering Plan Location Information . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying a Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying an Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Data Source Information . . . . . . . . .

123
123
125
125
126
128
129
1212
1212
1215

OneWorld Xe UPDATE (8 February 2002)

Table of Contents

Defining Machine/Server Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Specify Machine/Server Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Data Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Java Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Windows Terminal Server . . . . . . . . . . . . . . . . . . . . . . . .
Choosing Replication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Shared Data Source Setup Information . . . . . . . . . . . . . . .
Setting Up Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Environment Data Sources . . . . . . . . . . . . . . . . . . . . . . . .
Concluding the Remote Installation Plan Setup . . . . . . . . . . . . . . . .
Finalizing the Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Server to an Existing Configuration . . . . . . . . . . . . . . . . . . . . . .
Understanding Adding a Server to an Existing Configuration . . . . .
Assumptions about Adding a Server to an Existing
Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering a Plan Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering a Plan Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting Additional Server Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Deployment Server Information . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Information . . . . . . . . . . . . . . . . . . . .
Entering Enterprise Server Data Source Information . . . . . . . . .
Define a Java Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define a Windows Terminal Server . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting an environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Environment Data Sources . . . . . . . . . . . . . . . . . . . . .
Finalizing the Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Additional Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Installation Planner Processing Options . . . . . . . . . . . . . . . .
Understanding Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assumptions about Reviewing Installation Planner
Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting Processing Options Values . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Pieces of an Installation Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Language-Only Installation Plan . . . . . . . . . . . . . . . . . . . . . . .
Understanding a Language-only Installation Plan . . . . . . . . . . . . . . .
Reviewing Requirements for a Language Installation . . . . . . . . . . .
Installing Languages on the Deployment Server . . . . . . . . . . . . . . . .
Running Installation Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying Enterprise Server Requirements . . . . . . . . . . . . . . . . . . . . .
Verifying Workstation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Language Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Building and Deploying Alternate Language Packages . . . . . . . . . .

OneWorld Xe UPDATE (8 February 2002)

1217
1217
1218
1220
1222
1223
1226
1228
1233
1238
1239
1241
1241
1242
1242
1243
1244
1246
1246
1248
1248
1251
1253
1254
1256
1256
1257
1262
1264
1265
1265
1265
1266
1266
1277
1279
1279
1280
1280
1281
1285
1286
1286
1287
1287

Installation Guide

Installation Utilities
Revalidating Software Protection Codes . . . . . . . . . . . . . . . . . . . . . . . . . .
Revalidating the Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . .
Revalidating Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling OneWorld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping OneWorld on the Enterprise Server . . . . . . . . . . . . . . . . . . . . .
Granting Disk and Registry Access for Windows NT . . . . . . . . . . . . . . .

133
133
134
137
139
1311

OneWorld Xe UPDATE (8 February 2002)

Overview
This guide explains how to install J.D. Edwards OneWorld Xe. The first four
sections describe how to prepare for the process. The remaining sections
describe how to install OneWorld on the deployment server, the enterprise
server, and workstations.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

11

Installation Guide

This guide is designed for management information system (MIS) managers and
installers. It outlines the procedures to install OneWorld for the first time. It also
describes the procedures to migrate from existing J.D. Edwards WorldSoftware
for the AS/400 to OneWorld. To successfully install OneWorld, you must have a
working knowledge of the following topics:


Hardware and software requirements

Database setup and management

Enterprise platforms and operating systems

Success also depends on your understanding of certain concepts and


procedures. The recommended method to obtain this information is to attend
the relevant training courses. Information about course offerings, dates, and
locations is available on the J.D. Edwards Web site. At a minimum, read the
following guides before beginning:


OneWorld Foundation Guide

Configuration Planning and Setup suite:


-

Configurable Network Computing Implementation Guide

System Administration Guide

Package Management Guide

Server and Workstation Administration Guide

Reference information for the installation and upgrade processes is included in


the Installation Reference Guide.
In addition, J.D. Edwards recommends completing the database product courses
that your database vendors provide.

Additional Installation Options


The following list briefly describes additional options for installing OneWorld
software. Installation methods for these options are not explained in detail in this
guide.


Push installation
Push installation is a procedure that enables the system administrator to
schedule an automatic installation for a OneWorld package to
workstations. Package information is pushed from the deployment server

12

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

to the workstation, rather than the workstation requesting (pulling) an


installation from the deployment server. The advantage of push installation
is that, unlike other deployment methods, no interaction with the user is
required. This means that the administrator can schedule a package to
deploy to workstations at times when network traffic is reduced.


Windows NT terminal server edition installation


A Windows terminal server allows multiple thin clients, or workstations, to
run from a single copy of OneWorld.

Webbased options
Installing the OneWorld Java Server allows the use of webenabled
functions in OneWorld. For more information, see Running Installation
Planner" and Installing a Web/Java Server" in this guide.

See Also
For more information on each option, see the guides listed below:


Package Management Guide, and Deployment" and Configuring and


Installing Workstations" in this guide for more information about the push
installation process.

Server and Workstation Administration Guide

OneWorld on Windows NT Terminal Server Edition"

SnapShot Multiclient Installer"

WebBased Solutions Guide


-

OneWorld Java Server"

Document Updates: The Help You Install Web Page


The OneWorld Help You Install" Web page contains document updates and
other information about installing and upgrading OneWorld. You access the Help
You Install page from the J.D. Edwards Knowledge Garden (KG),
https://knowledge.jdedwards.com.
To reach the Help You Install page from the KG:
Home | Product | OneWorld | Suport | Help You Install
Before starting the installation or upgrade process, review the Help You Install
page to check for recent document updates.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

13

Installation Guide

The Help You Install page also contains links to online copies of this guide and
other OneWorld guides.

Minimum Technical Requirements (MTRs)


The Help You Install page contains a link to a listing of the OneWorld minimum
technical requirements (MTRs). You can also access the MTR listing from the
following KG location:
Home | Product | OneWorld Online | Minimum Technical Requirements.

Other OneWorld Information on the Help You Install page


Besides document updates, the Help You Install Web page contains links to
other information that can help you install or upgrade OneWorld, including:


Breaking News

Software update documentation (including ASUs, ESUs, and other types of


updates)

Software Action Requests (SARs)

FAQs about OneWorld installation and upgrade

Review this information before installing or upgrading OneWorld.

J.D. Edwards Support


The Knowledge Garden contains a link to customer support functions and
information. Click on the Support link (lefthand side navigation area) or Support
icon (top navigation bar) to view information about issues and SARs that you
have initiated, and to access the J.D. Edwards Update Center. Through the
Update Center, you can research and download ESUs, and view SARs and
objects.
If you need further assistance with OneWorld installation or upgrade, you can
contact J.D. Edwards customer support by phone, fax, or email at the locations
shown in the table below. Limit questions to those regarding J.D. Edwards
software. For questions about operating systems, databases, and other software
products, contact the appropriate vendor.
During normal business hours, a confirmation is sent within one hour of
submitting issues via the Web, email, or fax. An issue number is assigned
immediately when reporting by telephone, and this number references all
activity related to the issue.

14

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Premier Maintenance Customer Procedures


Premier maintenance customers can submit support issues at the following
email address: premier_customer_support@jdedwards.com. Outside normal
business hours, (MondayFriday, 8:00 a.m. 5:00 p.m. MST), premier customers
should use the telephone for the most prompt afterhours service.

Standard Maintenance Customer Procedures


Standard maintenance customers should send support issues via phone, fax, or
email to the appropriate service provider location listed below:

Location

Telephone Number

Fax Number; Email Address

North America

18002892999

3033344141;
denver_customer_support@jdedwards.com

Latin America (except


below)

0013033344000

3033344141;
denver_customer_support@jdedwards.com

Mexico

958007844260

3033344141;
denver_customer_support@jdedwards.com

Chile

12300205124

3033344141;
denver_customer_support@jdedwards.com

Colombia

980153560

3033344141;
denver_customer_support@jdedwards.com

Venezuela

80012743

3033344141;
denver_customer_support@jdedwards.com

Argentina

0018003331111, then
30348846399194, then
18007844260

3033344141;
denver_customer_support@jdedwards.com

Ecuador

999170, then
30348846399194, then
18007844260

3033344141;
denver_customer_support@jdedwards.com

Peru

170 (199 for cellular phone),


then 30348846399194, then
18007844260

3033344141;
denver_customer_support@jdedwards.com

Brazil

0008145502779

3033344141;
denver_customer_support@jdedwards.com

441494682682

441494682698;
london_customer_support@jdedwards.com

France

33-144742015

441494682698;
london_customer_support@jdedwards.com

Germany

49-6103762110

441494682698;
london_customer_support@jdedwards.com

Europe EMEA (except


below)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

15

Installation Guide

Location

Telephone Number

Fax Number; Email Address

Holland

31355480222

441494682698;
london_customer_support@jdedwards.com

Italy

39-0226967612

441494682698;
london_customer_support@jdedwards.com

658959656

65227-2698;
singapore_customer_support@
jdedwards.com

China (Bejing,
Shanghai)

108006500099

65227-2698;
singapore_customer_support@
jdedwards.com

China (other
provinces)

108657, or 108650, then follow


voice prompts to dial Singapore
at 8959656

65227-2698;
singapore_customer_support@
jdedwards.com

Hong Kong

800-903055

Malaysia

1800801557

Japan

81332657143

Australia

1800145200

Asia Pacific (except


below)

81332657145;
japan_customer_support@jdedwards.com

Documentation Conventions
The following sections explain the typographic and design conventions used in
this guide.
Note that some references refer users to the appropriate installation or upgrade
guide: IBM AS/400, Microsoft Windows NT, or UNIX.

OneWorld Releases
This release of OneWorld is OneWorld Xe. Xe was preceded by OneWorld
B73.3.2, released 1999.
The following list shows previous releases of OneWorld:
OneWorld
OneWorld
OneWorld
OneWorld

Xe
B73.3.2
B73.3.1
B73.3

J.D. Edwards does not support OneWorld releases prior to B73.3. For
information about previous releases of OneWorld, contact J.D. Edwards.

16

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Assumptions Tables
Assumptions tables list basic information about each task and are included with
each task that must be performed.
The information in the assumptions tables provides estimates to plan and
prepare for each task. Actual times and resources might vary significantly.
The following example is an assumptions table from this guide:
Labor Hours

12

Computer Hours

12

Personnel

Installer or database administrator

Logon status

In OneWorld, signed in as user JDE with password JDE.

Prerequisites

Access to the libraries listed in this task.

Concurrent Tasks

None. This task must complete before continuing.

Labor Hours The approximate number of hours it takes a person with


the recommended skill type to complete the task. The skill types are listed
in the Personnel row of the table.

Computer Hours The approximate number of hours it takes the


recommended computer to complete the task. Since this number can vary
depending on the system configuration, the actual time may be different
than indicated.

Personnel The skill level that is required to complete the task


successfully. For example, someone with specific skills, such as an Oracle
database administrator, might be needed. Unless otherwise noted, tasks
can be completed by the installer. The personnel types used in these
tables are defined below:
-

Installer The installer performs most installation tasks.

Database administrator The database administrator has special


skills or training in one or more database management systems such
as SQL Server or Oracle. J.D. Edwards recommends that someone
with database administration skills perform or assist with some
tasks.

System administrator The system administrator has authority to


perform tasks such as issuing logon names and maintain security.
Where noted in the assumptions tables, someone with system
administration rights may be required to complete a task.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

17

Installation Guide

Logon Status Indicates the machine, software, and OneWorld


environment, if applicable, that must be logged on to begin the task. For
example, the use of Microsoft Windows Explorer, SQL Server, or
OneWorld may be required. When applicable, this line also tells you the
user ID and password to use.

Prerequisites The tasks or steps, if any, that must be completed before


beginning this task. The line indicates if there are no prerequisites.

Concurrent Tasks The tasks, if any, that may be completed while this
task processes.

Considerations Boxes
Considerations boxes draw attention to information regarding coexistence,
databases, parallel releases, language options, or other items that can apply to
the OneWorld setup. This information is important to a successful installation. If
the title of the box applies, please read the contents carefully. An example is
shown below:
Data Source Considerations
J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.

Tips and Techniques Boxes


Tips and techniques boxes contain information that can help make the
OneWorld setup process easier. Tips and techniques are nice to know"
information that is optional. An example is shown below:
Tips and Techniques
After transferring the objects into PY7333, build and install a full or partial
prototype (CRP) package (for example, PY7333FB or PY7333PB), and then log
on to either the prototype or test environment for additional testing.

Troubleshooting Boxes
Troubleshooting boxes contain information related to the task or process. The
troubleshooting information can help work through potential problems with the
installation. An example is shown below:

18

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Troubleshooting
In some cases, the reboot does not finish updating the DLLs. If this happens,
manually shut down and restart the deployment server to finish the process.

Icons
The following icons provide visual cues to the content of a topic or paragraph:
Note: Identifies supplemental information, such as a hint or a suggestion. The
Note icon also refers to unexpected results or implications.
The Caution icon identifies specific consequences that require attention. The
Caution icon also provides an alert to circumstances in which a given action has
serious implications, such as irrevocable loss of data.
The Flag icon identifies procedures, tasks, or steps that require completion when
installing or upgrading a language as part of the OneWorld configuration. When
an additional language is not being used, ignore information marked by this
icon.

Fonts and Type Styles


The following special fonts and type styles are used in this guide:
Note: Nearly all commands in this guide are case sensitive. Enter them exactly as
written. In addition, all the commands described illustrate the recommended
directory structure. If your machine's directory structure is different, modify the
commands to match your directory structure.
Italic style designates variables used in the guide. For example, for the variable
deploymentserver in a command, substitute the actual name of your deployment
server. Also, the names of other J.D. Edwards OneWorld guides are in italic type
style, for example, the OneWorld System Administration Guide.
Courier font indicates commands or other information that must be typed
into the system. For example,
Type the name of the environment being installed, such as DVTEMP.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

19

Installation Guide

110

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in the Installation Process


This section explains what has changed in the OneWorld installation process for
this release.
All naming conventions are now 7333, not 733.
For OneWorld Xe, this section consists of the following topics:
- What's New in OneWorld Xe
- OneWorld Xe Documentation Changes

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

21

Installation Guide

22

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

This chapter explains what is new in the installation process for OneWorld Xe.
This chapter consists of the following topics:
- New and changed features in OneWorld Xe
- OneWorld Xe standard name changes

New and Changed Features in OneWorld Xe


The following features have been added or changed in OneWorld Xe.
Update note: Some of the changes noted below were not included in the
September 2000 release of OneWorld Xe, and have been added since that time.

General OneWorld changes




Added: Support for the IBM DB2 Universal Database (UDB), on the
OneWorld Xe UNIX, Windows NT, and Windows 2000 platforms. This
support was added to OneWorld Xe with Service Pack 17 (September
2001).

Changed: Environment Checker is now the OneWorld Verification Tool.

Changed: Elimination of the OneWorld Cumulative Update" procedure


(OneWorld Xe)
Older versions of OneWorld used the Cumulative Update procedure (as
distinct from the Upgrade procedure) to update cumulative versions. This
distinction has been eliminated. Upgrade from any cumulative or base
OneWorld version is now known as an Upgrade," and is described in the
OneWorld Upgrade guides.
Note that smaller updates are issued periodically between major releases.
These updates are known as ASUs, ESUs, and Service Packs. Contact J.D.
Edwards for information about applying these updates to OneWorld.

Added: Object Management Workbench, for all object management tasks


(OneWorld Xe)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

23

Installation Guide

Older versions of OneWorld used Object Librarian (OL) to check objects in


and out. OneWorld Xe uses Object Management Workbench (OMW) to
manage all object tasks, including checkin and checkout. OMW uses an
integrated and simplified graphical user interface for OneWorld
development to provide better control of OneWorld objects, especially
Object Librarian objects. For more information about Object Management
Workbench, see the OneWorld Xe System Administration Guide, Object
Management Workbench Configuration."


Changed: Many of the standard names for environments, path codes, data
sources, and OneWorld features (OneWorld Xe)
A complete list of all name changes is included in OneWorld Standard
Name Changes," below.

Installation Planner


Added: Automatic Plan Generation feature (OneWorld Xe)


For upgrades, OneWorld Installation Planner now gives you the option of
allowing automatic entry of locations and machines from the previous
OneWorld version into your plan. For more information about automatic
plan generation, see Running Installation Planner," section Entering plan
description."

Installation Workbench


Added: Unattended Workbench option, with optional task breaks


(OneWorld Xe)
The unattended workbench option has been added to the Installation
Workbench procedure. Using unattended workbench, you can start
Installation Workbench and allow all workbenches to proceed without
intervention. If an error is encountered, Installation Workbench stops and
you are notified, so that you can fix the error and proceed. Unattended
workbench is described in Running Installation Workbench."

Added: Remote Location Workbench (OneWorld Xe)


The new Remote Location Workbench loads business (master and
constant), control, data dictionary, and system tables from base location to
remote location servers, by launching different versions of R98403
(XJDE0043, XJDE0044, XJDE0045, XJDE0046, and XJDE0047). It also
pushes delivered packages to primary deployment servers at remote
locations by launching the multitier UBE (R98825C). This workbench is
processed only if you opted to install remote locations and chose to load
replicated data and push packages.

24

Changed: Elimination of most manual table conversions

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

Older versions of OneWorld required several manual table conversions for


upgrades, in addition to Table Conversion Workbench. Nearly all of these
have been eliminated. Manual conversions remain only for certain tables
in an AS/400 coexistence environment. Manual table conversions are
described in Running Installation Workbench."

AutoPilot/OneWorld Scripting Tool




Changed: AutoPilot is now OneWorld Scripting Tool (OneWorld Xe)


The name of the AutoPilot tool has been changed to OneWorld Scripting
Tool." This tool is described in Completing the Installation."

Retrofitting Custom Modifications




Added: Visual ER Compare utility, for retrofitting custom modifications


(OneWorld Xe)
The new Visual ER Compare utility replaces the old Work with Changed
Objects form used for retrofitting custom modifications during an upgrade.
The new utility provides a simple and easytouse interface for identifying
event rule modifications and incorporating them into the OneWorld Xe
upgrade. For information about the Visual ER Compare utility, see
Custom Modifications and Packages."

Completing the Upgrade




Added: Solution Explorer


The Solution Explorer is a windowsbased interface that provides access to
OneWorld applications, rolebased menus, implementation and
configuration options, documentation, and training materials. Like
OneWorld Explorer, the Solution Explorer provides you with a convenient
window into OneWorld. You can access the Solution Explorer to search
and navigate quickly through OneWorld applications. You can also
customize the Explorer to create your own tasks and link tasks to other
webbased information. Setting up the Solution Explorer is described in
Modifying OneWorld After the Upgrade." For more information about
understanding and using the Explorer, see OneWorld Solution Accelerator
Suite Implementation.

Installation Planner Utilities




Changed: Creating a remote installation plan

Changed: Adding a server to an existing configuration

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

25

Installation Guide

Both of these procedures changed in OneWorld Xe. You should review


Installation Planner Utilities" carefully before creating a remote installation
plan or adding a server to an existing configuration.

OneWorld Standard Name Changes


Many of the standard names used in previous versions of OneWorld have been
changed. The following lists show all the name changes.

Environments

Original Environment

New Environment

Description

CRP733

PY7333

B7333 Prototype (CRP) Environment

DEPB733

DEP7333

B7333 Deployment Server Environment

DEV733

DV7333

B7333 Development Environment

JCRP733

JPY7333

B7333 JAS Prototype Environment

JDEPLAN

JDEPLAN

Planner

JDEV733

JDV7333

B7333 JAS Development Environment

JPRT733

JJD7333

B7333 JAS Pristine Environment

JPRD733

JPD7333

B7333 JAS Production Environment

JTST733

JTS7333

B7333 JAS Test Environment

PRD733

PD7333

B7333 Production Environment

PRT733

JD7333

B7333 Pristine Environment

TST733

TS7333

B7333 Test Environment

WDEV733

WDV7333

B7333 WTS Development Environment

WPRT733

WJD7333

B7333 WTS Pristine Environment

WPRD733

WPD7333

B7333 WTS Production Environment

WCRP733

WPY7333

B7333 WTS Prototype Environment

WTST733

WTS7333

B7333 WTS Test Environment

Original Path Code

New Path Code

Description

CRPB733

PY7333

B7333 WTS Prototype Pathcode

CRPB733

PY7333

B7333 WTS Test Pathcode

CRPB733

PY7333

B7333 Prototype Pathcode

CRPB733

PY7333

B7333 Test Pathcode

Path Codes

26

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

CRPB733

PY7333

B7333 JAS Prototype Pathcode

CRPB733

PY7333

B7333 JAS Test Pathcode

DEVB733

DV7333

B7333 Development Pathcode

DEVB733

DV7333

B7333 JAS Development Pathcode

DEVB733

DV7333

B7333 WTS Development Pathcode

PLANNER

PLANNER

Planner

PLANNER

PLANNER

B7333 Deployment Server Pathcode

PRISTB733

JD7333

B7333 Pristine Pathcode

PRISTB733

JD7333

B7333 JAS Pristine Pathcode

PRISTB733

JD7333

B7333 WTS Pristine Pathcode

PRODB733

PD7333

B7333 Production Pathcode

PRODB733

PD7333

B7333 JAS Production Pathcode

PRODB733

PD7333

B7333 WTS Production Pathcode

Packages

Original Package

New Package

Description

CRPB733FA

PY7333FA

Prototype full package A

CRPB733PA

PY7333PA

Prototype partial package A

DEVB733FA

DV7333FA

Development full package A

DEVB733PA

DV7333PA

Development partial package A

PRISTB733FA

JD7333FA

Pristine full package A

PRISTB733PA

PD7333PA

Production partial package A

PRISTB733PA

JD7333PA

Pristine partial package A

PRODB733FA

PD7333FA

Production full package A

Data Sources - Central Objects

Environment

Original Data Source

New Data Source

Description

DV7333

Central Objects - DEVB733

Central Objects - DV7333

Development Central Objects

JD7333

Central Objects - PRISTB733

Central Objects - JD7333

Pristine Central Objects

PD7333

Central Objects - PRODB733

Central Objects - PD7333

Production Central Objects

PY7333

Central Objects - CRPB733

Central Objects - PY7333

Prototype Central Objects

PY7333

Central Objects - CRPB733

Central Objects - PY7333

Test Central Objects

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

27

Installation Guide

Data Sources - Versions

Environment

Original Data Source

New Data Source

Description

DV7333

Versions - DEVB733

Versions - DV7333

Development Versions

JD7333

Versions - PRISTB733

Versions - JD7333

Pristine Versions

PD7333

Versions - PRODB733

Versions - PD7333

Production Versions

PY7333

Versions - CRPB733

Versions - PY7333

Prototype Versions

PY7333

Versions - CRPB733

Versions - PY7333

Test Versions

DV7333

Versions - DEVB733 DNT

Versions - DV7333 - DNT

Development Versions [AS/400


only]

JD7333

Versions - PRISTB733 - DNT

Versions - JD7333 - DNT

Pristine Versions [AS/400 only]

PD7333

Versions - PRODB733 - DNT

Versions - PD7333 - DNT

Production Versions [AS/400


only]

PY7333

Versions - CRPB733 - DNT

Versions - PY7333 - DNT

Prototype Versions [AS/400 only]

PY7333

Versions - CRPB733 DNT

Versions - PY7333 - DNT

Test Versions [AS/400 only]

Data Sources - Business Data

Environment

Original Data Source

New Data Source

Description

DV7333

Business Data - TEST

No change

Development Business Data

JD7333

Business Data - JDE

No change

Pristine Business Data

PD7333

Business Data - PROD

No change

Production Business Data

PY7333

Business Data - CRP

No change

Prototype Business Data

PY7333

Business Data TEST

No change

Test Business Data

DV7333

Business Data - TEST - DNT

No change

Development Business Data


[AS/400 only]

JD7333

Business Data - JDE - DNT

No change

Pristine Business Data [AS/400


only]

PD7333

Business Data - PROD - DNT

No change

Production Business Data


[AS/400 only]

PY7333

Business Data - CRP - DNT

No change

Prototype Business Data [AS/400


only]

PY7333

Business Data - TEST - DNT

No change

Test Business Data [AS/400 only]

Data Sources - Control Tables

Environment

Original Data Source

New Data Source

Description

DV7333

Control Tables - Test

No change

Development Control Tables

DV7333

Control Tables - Test - DNT

No change

Development Control Tables [AS/400]

28

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

DV7333

AS/400 COMMON - Test

No change

Development Control Tables [coexistence]

JD7333

Business Data - JDE

No change

Pristine Business Data Tables

JD7333

Business Data - JDE

Control Tables
JDE

Pristine Control Tables

JD7333

Business Data - JDE - DNT

No change

Pristine Control Tables [AS/400 only]

PD7333

Control Tables - Prod

No change

Production Control Tables

PD7333

Control Tables - Prod - DNT

No change

Production Control Tables [AS/400 only]

PD7333

AS/400 COMMON - Production

No change

Production Control Tables [coexistence]

PY7333

Control Tables - CRP

No change

Prototype Control Tables

PY7333

Control Tables - Test

No change

Test Control Tables

PY7333

Control Tables - CRP - DNT

No change

Prototype Control Tables [AS/400 only]

PY7333

Control Tables - Test - DNT

No change

Test Control Tables [AS/400 only]

PY7333

AS/400 COMMON - CRP

No change

Prototype Control Tables [coexistence]

PY7333

AS/400 COMMON - Test

No change

Test Control Tables [coexistence]

Data Sources - Miscellaneous

Environment

Original Data Source

New Data Source

Description

ALL

System - B733

System - B7333

System Data Source

ALL

System - B733 DNT

System - B7333 DNT

System Data Source (do not


translate)

ALL

Data Dictionary - B733

Data Dictionary - B7333

Data Dictionary Data Source

ALL

Object Librarian - B733

Object Librarian - B7333

Object Librarian Data Source

ALL

AS/400 COMMON

No change

AS/400 Common Data Source

ALL

AS/400 COMMON - xxx

No change

AS/400 Common Data Source

OneWorld Local Data Sources

ENvironment

Original Data Source

New Data Source

Description

DV7333

OneWorld Local - DEVB733

OneWorld Local - DV7333

OneWorld Local Data Source for


Development

JD7333

OneWorld Local PRISTB733

OneWorld Local - JD7333

OneWorld Local Data Source for


Pristine

PD7333

OneWorld Local PRODB733

OneWorld Local - PD7333

OneWorld Local Data Source for


Production

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

29

Installation Guide

PY7333

OneWorld Local - CRPB733

OneWorld Local - PY7333

OneWorld Local Data Source for


Prototype

PY7333

OneWorld Local - TESTB733

OneWorld Local - PY7333

OneWorld Local Data Source for


Test

Libraries

Environment

Original Library

New Library

Description

DV7333

DEVB733DNT

DV7333DNT

Versions for Development

JD7333

PRSB733DNT

JD7333DNT

Versions for Pristine

PD7333

PRDB733DNT

PD7333DNT

Versions for Production

PY7333

CRPB733DNT

PY7333DNT

Versions for Prototype

DV7333

CODEVB733

CODV7333

Central Objects in DB2 for Development

JD7333

COPRTB733

COJD7333

Central Objects in DB2 for Pristine

PD7333

COPRDB733

COPD7333

Central Objects in DB2 for Production

PY7333

COCRPB733

COPY7333

Central Objects in DB2 for Prototype

DV7333

TESTDTA

No change

Business Data for Development

JD7333

PRISTDTA

No change

Business Data for Pristine

PD7333

PRODDTA

No change

Business Data for Production

PY7333

CRPDTA

No change

Business Data for Prototype

DV7333

TESTCTL

No change

Control Tables for Development

PD7333

PRODCTL

No change

Control Tables for Production

PY7333

CRPCTL

No change

Control Tables for Prototype

JD7333

PRISTDTA

No change

Control Tables for Pristine

ALL

DDB733

DD7333

Data Dictionary

ALL

SYSB733

SYS7333

System

ALL

B733MAP

SVM7333

Server Map

ALL

OLB733

OL7333

Object Librarian

Users

Path Code

Original User

New User

Description

DV7333

DEVB733

DV7333

Development user for central objects

JD7333

PRISTB733

JD7333

Pristine user for central objects

210

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

JD7333

PRISTDTA

No change

Pristine user for control tables

JD7333

PRISTDTA

No change

Pristine user for business data

PD7333

PRODB733

PD7333

Production user for central objects

PD7333

PRODDTA

No change

Production user for business data

PD7333

PRODCTL

No change

Production user for control tables

PY7333

CRPB733

PY7333

Prototype user for central objects

PY7333

CRPDTA

No change

Prototype user for business data

PY7333

TESTDTA

No change

Test user for business data

PY7333

CRPCTL

No change

Prototype user for control tables

PY7333

TESTCTL

No change

Test user for control tables

ALL

OBJB733

OBJ7333

Object Librarian user

ALL

SVMB733

SVM7333

Server Map user

ALL

DDB733

DD7333

Data Dictionary user

ALL

SYSB733

SYS7333

System user

Table and Index Changes (Oracle Databases)

Path Code

Original Table and Index

New Table and Index

Description

ALL

SYSB733T

SYS7333T

Tablespace for System Tables

ALL

SYSB733I

SYS7333I

Tablespace for System Indexes

ALL

SVMB733T

SVM7333T

Tablespace for Server Map Tables

ALL

SVMB733I

SVM7333I

Tablespace for Server Map Indexes

ALL

OBJB733T

OBJ7333T

Tablespace for Object Librarian


Tables

ALL

OBJB733I

OBJ7333I

Tablespace for Object Librarian


Indexes

ALL

DDB733T

DD7333T

Tablespace for Data Dictionary


Tables

ALL

DDB733I

DD7333I

Tablspace for Data Dictionary Indexes

DV7333

DEVB733T

DV7333T

Tablespace for Development


Central Object Tables

DV7333

DEVB733I

DV7333I

Tablespace for Development


Central Object Indexes

JD7333

PRISTB733T

JD7333T

Tablespace for Pristine Central


Object Tables

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

211

Installation Guide

JD7333

PRISTB733I

JD7333I

Tablespace for Pristine Central


Object Indexes

JD7333

PRISTDTAT

No change

Tablespace for Pristine Business


Data Tables

JD7333

PRISTDTAI

No change

Tablespace for Pristine Business


Data Indexes

JD7333

PRISTDTAI

PRISTCTLI

Tablespace for Pristine Control


Tables

JD7333

PRISTDTAT

PRISTCTLT

Tablespace for Pristine Control


Tables

PD7333

PRODB733T

PD7333T

Tablespace for Production Central Object Tables

PD7333

PRODB733I

PD7333I

Tablespace for Production Central Object Indexes

PD7333

PRODDTAT

No change

Tablespace for Production Business Data Tables

PD7333

PRODDTAI

No change

Tablespace for Production Business Data Indexes

PD7333

PRODCTLT

No change

Tablespace for Production Control Tables

PD7333

PRODCTLI

No change

Tablespace for Production Control Indexes

PY7333

CRPB733T

PY7333T

Tablespace for Prototype Central


Object Tables

PY7333

CRPB733I

PY7333I

Tablespace for Prototype Central


Object Indexes

PY7333

CRPDTAT

No change

Tablespace for Prototype Business Data Tables

PY7333

CRPDTAI

No change

Tablespace for Prototype Business Data Indexes

PY7333

CRPCTLT

No change

Tablespace for Prototype Control


Tables

PY7333

CRPCTLI

No change

Tablespace for Prototype Control


Indexes

PY7333

TESTDTAI

No change

Tablespace for Test Business


Data Tables

PY7333

TESTDTAT

No change

Tablespace for Test Business


Data Indexes

PY7333

TESTCTLT

No change

Tablespace for Test Control


Tables

PY7333

TESTCTLI

No change

Tablespace for Test Control Indexes

212

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Whats New in OneWorld Xe

SQL Databases

Path Code

Original Database

New Database

Description

ALL

JDEB733

JDE7333

Database for System, Server


Map, Object Librarian, Data Dictionary Tables

DV7333

JDE_DEVB733

JDE_DV7333

Database for Development Central Objects

DV7333

JDE_DEVELOPMENT

No Change

Database for Development Business Data and Control Tables

JD7333

JDE_PRISTB733

JDE_JD7333

Database for Pristine Central Objects

JD7333

JDE_PRISTINE

No Change

Database for Pristine Business


Data and Control Tables

PD7333

JDE_PRODB733

JDE_PD7333

Database for Production Central


Objects

PD7333

JDE_PRODUCTION

No Change

Database for Production Business


Data and Control Tables

PY7333

JDE_CRPB733

JDE_PY7333

Database for Prototype Central


Objects

PY7333

JDE_CRP

No Change

Database for Prototype Business


Data and Control Tables

Temporary Environment Information

Original User

New User

Original Database Info

New Database Info

crptemp

pytemp

crptemp

pytemp

prodtemp

pdtemp

prodtemp

pdtemp

devtemp

dvtemp

devtemp

dvtemp

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

213

Installation Guide

214

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Customer Overview
The OneWorld support structure consists of components such as databases,
operating systems, and hardware. To install OneWorld successfully, set up the
support structure before starting the installation process. The tasks in this section
are designed to prepare the customer's system for the installation process. Some
of the tasks, such as checking that the appropriate hardware and software are
available, can take some time to complete. Other tasks are quick and easy.
Note: You must complete these preparation tasks before the installation team
arrives.
This section consists of the following tasks and topics:
- Process overview
- Environment overview
- Language process overview
- Customer checklist

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

31

Installation Guide

32

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Customer Checklist

You must complete the tasks in Customer Overview" before the installation
team arrives. This checklist helps organize the required preinstallation
preparation.
Use this checklist to keep track of completed tasks:
- Review Process Overview"
- Review Environment Overview"
- Review Language Process Overview" if the installation involves a
secondary language
- Assess the network
- Run OneWorld Verification Tool
- Verify that the deployment server hardware and Windows NT software
meet requirements
- Verify that the enterprise server hardware and software meet requirements
- Verify that the workstation hardware and software meet requirements
- Verify that the Windows terminal server (WTS) hardware and software
meet requirements (required when using WTS)
- Verify that the deployment server disk space meets requirements
- Verify that the enterprise server disk space meets requirements
- Complete the detail worksheet in the PreUpgrade Preparation" section of
this manual

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

33

Installation Guide

34

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Install Process Overview


This guide explains the process used to install OneWorld software.
The installation process consists of the following steps:


Installing OneWorld from the CD to the deployment server

Setting up the installation plan by running Installation Planner

Installing OneWorld by running Installation Workbench

Installing OneWorld on the enterprise server

Installing OneWorld on the workstations

Installing OneWorld on OneWorld Java Servers

Installing OneWorld on the Windows terminal servers

Choose multilingual options when setting up your installation plan criteria.


You can set up your OneWorld configuration in many ways. J.D. Edwards
recommends following the typical setup and naming conventions wherever
possible, unless there is a strong business case that supports the need to change.

See Also


Typical Customer Configuration" in the Configurable Network Computing


Implementation Guide, for more information about the typical customer
configuration that J.D. Edwards ships with OneWorld.

When the guide refers to coexistence, it means the ability to run WorldSoftware
and OneWorld software at the same time on an IBM AS/400 platform. The
following graphic shows how this works with OneWorld:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

35

Installation Guide

WorldSoftware

OneWorld

Business Data
Object
Librarian

Central
Object

Data
Dictionary

Menus

Data Dictionary Merge

Data
Dictionary

UDCs
System

This chapter consists of the following topics:


- Installation processes
- Process flow

Installation Processes
The installation processes consist of the following:


Deployment server installation

Installation Planner

Installation Workbench

Enterprise server installation

Workstation installation

Deployment Server Installation


The deployment server is the focus of the OneWorld installation process. The
installation program for the deployment server copies the OneWorld software

36

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

and a language, if applicable, from the CD to the deployment server. From the
deployment server, the OneWorld software is distributed to one or more
enterprise servers and the workstations.
The deployment installation program guides you through the following
processes:


The authorization process, which requires an authorization code and the


number of licensed users.

The OneWorld installation process, which installs OneWorld based on the


information provided by the user.

The program updates the Windows registry with information about the
OneWorld installation and languages, if applicable. When the program finishes, a
OneWorld selection form appears in the Windows Programs list, which guides
you through the remaining processes.

Installation Planner
The Installation Planner is a OneWorld application that runs as a standalone
program on the deployment server. It also is a system administration tool that
stores all information about the installation plan in a set of preloaded tables in
the OneWorld Planner data source. Installation Planner guides you through
setting up the installation plan stepbystep. When you choose the types of
operations to include in a plan, Installation Planner guides you through the
proper setup steps for the chosen options.
Languages are installed using the Installation Planner. The Language CD is
required to implement this new functionality.
Installation Planner manages the following processes:


Language setup

Location setup

Deployment server setup

Enterprise server setup

Additional server setup (data servers, OneWorld Java servers, and


Windows terminal servers)

Data source setup (both enterpriseserverspecific and shared environment


data sources)
Some data sources remain the same between releases:
-

Business Data

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

37

Installation Guide

Control Tables

Other data sources are release specific:

System and Data Dictionary

Server Map is now machine-specific and release-specific if separate


environments are maintained

Environment setup (all environments for a typical customer configuration)


Creates new environments for OneWorld B9 (such as PD7333). This
process ensures that the Object Configuration Manager (OCM) mappings
are correct and the new environments point to the correct path codes.

Control table merges (for AS/400 coexistent environments)


The control table planner program offers the following merges for
customers upgrading to OneWorld B9 from B73.2:

Data Dictionary merge (R989200P)

User Defined Code merge (R987241)

Menu merge (R989751B)

User Overrides merge (R9898950)

Package setup and builds


J.D. Edwards delivers prebuilt packages for each path code which can be
deployed directly to a workstation.

Installation Planner concentrates on environmentlevel operations that deal


primarily with processing activity on the enterprise server platforms. Set up user
profiles and workstation installations after installing the enterprise server.

Installation Workbench
Installation Workbench runs the plan created using Installation Planner. It
functions as a central point for all the processes required to install environments.
Some processes that install environments might require procedures to be
performed manually. However, Installation Workbench assures that procedures
are performed in the proper order, and insulates you as much as possible from
platformspecific environment setup.

38

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

The following graphic shows the processes that occur when running Installation
Workbench:

Enterprise Server Installation


After creating your plan using Installation Planner, you load OneWorld to the
enterprise server. OneWorld enterprise software is loaded to the enterprise server
using a separate CD provided for that purpose, rather than transferring all the
software from the deployment server. This moredirect installation method
increases performance during this part of the process. It is especially beneficial
in situations in which the enterprise server is connected to the deployment
server using a wide area network (WAN).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

39

Installation Guide

Workstation Installation
The Client Workstation Installation program is a standalone Windows
application that reads the deployment preferences information from the system
tables to drive the workstation installation process. OneWorld is installed on the
client workstations from the deployment server. Workstations can use Microsoft
Windows 95, Windows 98, Windows NT, or Windows 2000 for their operating
systems.
The following connectivity is required:


Read/write access to the \client directory on the primary deployment


server in the base location

Read access to the System tables

Read access to the subdirectories located under the \pathcode\package


directories, for example, \\deployment\b7333\PD7333\package

Process Flow
The chart on the following pages shows the process flow for a OneWorld B9
installation, including the order of tasks during an installation. Use this chart to
better understand the overall process, as well as to track the progress of the
installation. This chart takes the place of Installation at a Glance" in previous
releases of this guide.

Install Process Flow


Customer Preparation

310

Customer checklist

Process overview

Environment overview

Language process overview

Preparing the support structure

OneWorld hardware and software requirements

OneWorld disk space requirements

Detail worksheet

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Deployment Server Installation




Install OneWorld on the deployment server

Install the OneWorld Databases


You can continue with Installation Planner while this runs.

Planning and Configuring Servers




Run the Installation Planner

Run Installation Workbench

Enterprise Server Installation




Install OneWorld on the enterprise server

Set Up Home Page for Solution Explorer

Install the Data Repository

Configure OneWorld for use with Vertex

Workstation Installation


Configure workstations

Completing the Installation




Modify OneWorld after the Installation

Package Management

Install Vertex Software for OneWorld

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

311

Installation Guide

312

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Environments Overview

The OneWorld installation software includes several environments that represent


the typical customer configuration as defined in the Configurable Network
Computing Implementation Guide. These environments are preset to make the
installation process as easy as possible. This chapter contains more information
about these environments and their role in the installation process.
Follow the setup recommendations and naming standards described in this
guide. This minimizes confusion when communicating with those outside of
your implementation team. In addition, future upgrades are simpler if you use
J.D. Edwards naming conventions. If you customize your configurations during
the process, J.D. Edwards strongly recommends changing only the descriptions
that J.D. Edwards sends with a typical setup.
This chapter consists of the following topics:
- How OneWorld environments work together
- The Planner environment (JDEPLAN)
- The Deployment environment (DEP7333)
- The Test environments
- The Development environment
- The Prototype environment
- The Production environment
- The J.D. Edwards Pristine environment
- Previous release environment charts
- OneWorld multitiered location environment charts
Note the difference between J.D. Edwards path codes and environment name
abbreviations. Path codes use a longer abbreviation, such as PRODB733 for
production. Environments are abbreviated as PD733. This distinction is important
during OneWorld installation.
J.D. Edwards provides the following preset environments:
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

313

Installation Guide

Deployment (DEP7333)

Planner (JDEPLAN)

Prototype or CRP (PY7333)

J.D. Edwards Pristine (JD7333)

Development (DV7333)

Test (TS7333)

Production (PD7333)

Corresponding JAS (J) and WTS (W) Environments

How OneWorld Environments Work Together


Each environment shipped with OneWorld has a specific use. The following
graphic shows the interaction between the recommended environments during
installation and live use of OneWorld software.

Start here
Planner Installing , upgrading or
updating OneWorld
Deployment Running OneWorld on
the deployment server
Production Using OneWorld
applications

You can repeat this inner


loop an unlimited number
of times to modify
OneWorld software

Pristine Testing unaltered objects or


conducting training

Development Testing development


objects
Test Testing modifications and
conversions, conducting training,
testing development objects
CRP Populating constants and
master tables

314

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Environments Overview

Each installation or upgrade begins by using the planner environment to plan


the OneWorld setup for your company. After the plan is configured, run
OneWorld on the deployment server using the deployment environment.
Depending on your business needs, you might also begin customizing OneWorld
using the development environment and testing these customizations against the
original data stored in the pristine environment. The pristine environment and its
untouched data are always available for refreshing data in other environments.
After developing customizations in the development environment, test them in
the test environment. The test environment makes sure customizations work
correctly with your company's OneWorld setup before adding them to the
production environment. The production environment is where employees do
their daily work in OneWorld. After the initial OneWorld installation, run the
production environment continually while users design and test customizations
in the production and test environments.
The following sections explain each environment in more detail.

The Planner Environment (JDEPLAN)


The OneWorld installation process which includes a planning stage called the
planner environment, allows the definition of the main components of your
OneWorld configuration without impacting the production environment.
Every environment must have an associated path code and a set of Object
Configuration Manager (OCM) mappings. The planner environment uses a
planner path code, which is shipped with OneWorld, and a set of OCM
mappings that point to a planner database.

Planner Path Code


OneWorld provides a full set of runtime OneWorld objects which can be used
during the installation process. OneWorld stores these objects on the deployment
server in the planner directory. The planner pathcode contains the only
complete set of runtime central objects or replicated objects on the deployment
server.
The planner path code includes preloaded packages used during the update
specification merge process. A package indicates the necessary objects for a
workstation, a pointintime snapshot of the central objects on the deployment
server, and where the installation program finds them.

Planner Database
All information created and updated during the planning stage is saved in a
Microsoft Access database, called JDEPLAN.MDB on the deployment server.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

315

Installation Guide

When using the planner environment to change your configuration after


finishing the process:


Planner database tables are updated with the change

Define and run a plan to move the change to the production environment

When using the deployment or production environment to change your


configuration after you finish the process:


Production environment System tables are updated in real time

Planner database tables are not updated


For the deployment and production environments, the Object
Configuration Manager (OCM) and data source information comes from
the planner database when working on the deployment server.

J.D. Edwards recommends using the production environment System (technical)


tables to make changes to environments, path codes, packages, and OCM.

The Deployment Environment (DEP7333)


Use the deployment environment to run OneWorld on the deployment server.
The deployment environment uses the planner path code, and has OCM
mappings to the production environment System tables and local data. Only one
deployment environment is required because all environments created by the
installation process share common data sources.
The deployment environment uses the system information, such as
environments, packages, and user profiles. The OCM mappings and data source
information are supplied by the planner database when working on the
deployment server.

The Test Environment (TS7333)


Use the test environment (TS7333) to test:

316

The software during a conference room pilot.

The modifications made in the development environment and transferred


to the prototype environment (PY7333). These modifications have not yet
been transferred to your production path code and, therefore, are not
released to end users.

Test table conversions (converting foreign tables into J.D. Edwards tables).

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Environments Overview

When authorized to access the test environment, data can safely be changed.
Also, training classes may be conducted in this environment. Customer
application testing and conversion testing populates this environment.

The Development Environment (DV7333)


The development environment (DV7333) is for development objects (DV7333
path code). This environment shares the test data used by TS7333. Log on to this
environment to modify and test objects before transferring them to the prototype
environment (PY7333) path code. After transferring the objects into PY7333,
build and install a full or partial prototype package (for example, PY7333FB or
PY7333PB), then log on to either the prototype or test environment for
additional testing.

The Prototype (CRP) Environment (PY7333)


The prototype environment (PY7333) is the staging environment for production.
Constants tables and master tables, such as company constants, fiscal date
patterns, and item master are populated with production data during the
prototype process. Copy the tables to the production environment before going
live. Note that the prototype environment was called the CRP environment in
previous releases of OneWorld.
After running Installation Workbench, no business data exists until it is entered.
When appropriate, refresh the data this environment uses from your production
environment (PD7333).

The Production Environment (PD7333)


The production environment is PD7333. Production users have a tested and
released package on their system. Replicated data includes user defined codes,
menus, and data dictionary at a minimum. Batch applications can run on the
enterprise server.

The J.D. Edwards Pristine Environment (JD7333)


Use the J.D. Edwards pristine environment (JD7333) to test pristine (unaltered)
objects with J.D. Edwards demonstration data or for training classes. This
environment is required to compare modified objects to pristine objects. When
encountering a software problem that J.D. Edwards Worldwide Customer
Support cannot duplicate, they will ask you to sign on to the pristine
environment to duplicate the problem. On a routine basis, either monthly or
quarterly, refresh the J.D. Edwards data for this environment by using the J.D.
Edwards demonstration data on the software CD.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

317

Installation Guide

318

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

The language installation process automatically copies the text from a language
database to the production OneWorld database and merges the alternate
language text with the original English base. These automated processes are
described throughout this guide. When installing language for the first time, a
language-only plan may be chosen after completing the initial plan.
This chapter consists of the following topics:
- Language architecture
- Database character set and code page considerations
- National language support

See Also


Running Installation Planner"

Creating a LanguageOnly Installation Plan" for the tasks that must be


completed when choosing to install an alternate language after completing
the base installation.

Language Architecture
The OneWorld language architecture incorporates multinational language
functionality for international customers. The software specifies the language
preference for forms and reports. For example, users that share the same
environment may want to view the same text in different languages, such as
French, Spanish, and English. All language text is stored in a central location and
deployed to the individual workstation.
J.D. Edwards currently ships all software with a base language of English. The
package build process allows the building of packages for multiple languages.
Multiple languages can be installed using the processes outlined in this guide.
Language text is accessed by the language preference code settings in the user
profile associated with the alternate language installed.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

319

Installation Guide

Base Language
OneWorld language support works in conjunction with the English base
language. The base release contains English and must be installed before
creating custom modifications to include changes or additions to the translated
text. All control files must also have an English record prior to adding an
alternate language text record.
User

Alternate
Language
(French)

Base
Language
(English)

Alternate
Language
(Spanish)

J.D. Edwards Forms


and Reports

Alternate Language Components


Two major components are included with an alternate language:


Standard packages, which are installed on the deployment server, include


both English and the alternate language. These language packages, which
contain the desired language, are installed to the workstation to access the
selected language. Customers then display data in the installed language
by setting the active language preference code in the user profile.
When installing more than one alternate language, the last language
installed is the language available with the standard package. When the

320

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

ability to access more than one language within the same package is
required, build a custom package that includes all languages.


Language text is stored in the Central Objects, System, Control Table, and
Data Dictionary data sources. The data is loaded to the deployment server
during the installation and copied to the Central Objects and the other
data sources through the language installation process.

In OneWorld, J.D. Edwards provides 21 languages. Singlebyte languages run on


singlebyte or doublebyte operating systems, but doublebyte languages must
run on doublebyte operating systems.
Instructions in this guide explain how to set up these features.
See Also


Package Build" in the Package Management Guide for more details on


how to build a language package.

Language Preference Codes


The language preference codes are the standard language codes used
throughout the software. The language preference code field located in the
OneWorld user profile determines which language is displayed on forms or
reports. All users are assigned a language preference code within the user
profile.
A blank language preference code specifies the base language of English.
Alternate language records always have a value in the language preference code.
The alternate language text tables have records that contain language preference
codes. These tables contain several records for each item, such as a user defined
code value as well as possible multiple records for a code value, with each code
representing a different language.
If the language preference code does not have a corresponding translated
language record, the system defaults to the base English record.
In the example below, the record in user defined code (UDC) table F0004 does
not contain a language preference code. This indicates that this record is the
base language. The UDC table F0004D contains only records for the multiple
languages (in this example, French and Spanish, where Code Type CN
represents the country).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

321

Installation Guide

UDCs (F0004)

Alternate UDCs (F0004D)


(TEXT ONLY)

Code Type CN
(No Language
Preference Code)

Code Type CN
(Language Preference
Code F)
Code Type CN
(Language Preference
Code S)

Certain database tables, such as the Business Unit Master, AAIs, Account Master,
and Item Master, also contain the language preference code in an additional
description table. This information is not translated in the J.D. Edwards
demonstration data.
OneWorld applications support the use of languages. Refer to the individual
applications to set up and use multiple languages.

322

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

Language Installation Process Flow


The following graphics illustrate the installation process flow for language on the
deployment server and on the workstation:
Deployment Server Installation
Contents of CD Per
Language is
installed by Server
Install Process

For Workstation
installation See
Next Diagram

Deployment Server

Language Database
FRENCH.MDB
(example)

Add language tables to


English tables F0004D,
F0005D, F00165, F9202,
F9203, F0083, F98800D,
F98810D, F91100D,
F83100, F83110

Central Object
(Enterprise Server)
F98750, F98760, F98306

Enterprise Server

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

323

Installation Guide

Workstation
From Deployment
FRENCH.MDB (example)

Data Dictionary
Specifications

Partial Package
Installation
PRODB733PA
Specifications FDA,
RDA, DD, POTEXT,
JDEB7.MDB with
language

Full Package
installation
PRODB733FA
Specifications
FDA, RDA, DD,
POTEXT,
JDEB7.MDB

OR

Workstation

Replicated
Local Objects
(packed specs)
rdatext

Server Package
Build (from full
package
installation)

Enterprise Server
where the
distributed
processes are
located

Database Character Set and Code Page Considerations


Data within a database has a set of parameters to define it. Each character within
the database is identified by a specific language preference code value. A
collection of characters within a defined database is called a character set or
code page. A character set or code page setting is a scheme for encoding
character data. Every character is defined by a unique hexadecimal value. These
values may change between databases and languages. Every language is
represented by at least one character set. Some character sets may contain
multiple languages.
For example, the Western European character set contains all characters common
to the Western European languages (Aa Zz), and all special characters unique
to the specific languages, such as , , , and . Asian character sets are all
specific to one language.
Within OneWorld, J.D. Edwards uses code page conversions to control the
consistent or desired display of data. A code page conversion adjusts the
hexadecimal values of different characters so that the appearance of text on the
desktop is the same with different code pages.

324

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

When installing the database, set up the code page for the language before
loading your language specifics for OneWorld.
See Also


Installing the OneWorld Databases" to verify the LocalCodeSet and code


page settings for your database machine environment.

Code Page Settings


J.D. Edwards recommends the following code page settings. The correct code
page should be set accordingly when the database is created.
SQL Server
The Mircosoft codepage setting of the database needs to be set correctly
depending on the language used. See the following table for the correct
Microsoft SQL codepage settings.
Oracle
The Oracle character set of the database needs to be set correctly depending on
the language used. See the following chart for the correct Oracle character set
settings.
Both the NLS_characterset and NLS_LANG environment variables need to be set
correctly.
DB2 UDB
The IBM code-set of the database and OS Locale needs to be set correctly for
the language used. See the following table for the correct DB2 code-set settings.
DB2/400
The IBM CCSID value of the tables needs to be set correctly depending on the
language used. See the following chart for the correct CCSID values.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

325

Installation Guide

Tier

Language

Encoding/character set/locale
SQL
Oracle
(code (NLS_CHARACTERSET)
page)

DB2 UDB
(Code-Set)

DB2/400
(CCSID)

1252

WE8MSWIN1252

1252

37

Japanese

932

JA16SJIS

IBM-943

939

Danish

1252

WE8MSWIN1252

1252

37

Tier 1

English
French

German
Italian

Spanish

Portuguese

Tier 2

Dutch

Finnish

Norwegian
Swedish

Tier 3

Korean

949

KO16MSWIN949

1363

933

Traditional
Chinese

950

ZHT16MSWIN950

big5

937

Simplified
Chinese

936

ZHS16GBK

GBK

935

Arabic

1256

AR8MSWIN1256

1256

N/A

1250

EE8MSWIN1250

1250

870

Greek

1253

EL8MSWIN1253

1253

875

Russian

1251

CL8MSWIN1251

1251

1025

Turkish

1254

TR8MSWIN1254

1254

1026

Czech

Hungarian
Polish

For Workstations

Code page settings for individual languages are specified by Microsoft in


Windows System locale.

National Language Support


National Language Support (NLS) is a set of common standards that allow data to
be entered, displayed, stored, retrieved, and printed in multiple languages, in
different databases, and on different platforms.

326

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

NLS is information that requires the set up of code pages and JDE.INI files for
the enterprise server and workstations. By using NLS standards, J.D. Edwards
maintains consistent data within all databases and hardware platforms.
For example, French data is entered on a Microsoft Windowsbased workstation,
which is converted to EBCDIC on the IBM AS/400 system. In this example, IBM
Client Access automatically converts the data. The text is stored in a specific
character set that uniquely describes the data as French. The same database can
store alternate language text along with French, relying on NLS standards to
manage the text storage and retrieval. J.D. Edwards uses NLS on all supported
platforms, so you can interact with any computer system (hardware and
software) within your own environment.
In order for the workstation to reflect the language installed on the deployment
server, perform the tasks for both the enterprise server and workstations in
addition to the procedures to verify and modify the JDE.INI settings. These
procedures are described throughout this guide.

Single-Byte and Double-Byte Considerations


Many singlebyte languages support either national code pages or multinational
code pages. The doublebyte languages support specific individual national code
pages by language.
Singlebyte character sets use a collection of phonetic characters that require one
byte to create a single character. Conversely, the doublebyte character sets use
ideographic characters and require two bytes to create a single character.
Singlebyte languages can generally be run on single or doublebyte systems.
Doublebyte languages, such as Japanese, Chinese, and Korean, must run on
machines configured to support a doublebyte system. For example, a
doublebyte SQL or Oracle database is required for Chinese and Japanese
languages.
OneWorld can perform a Query By Example (QBE) on any character. However,
when using a doublebyte language, this process may not necessarily use an
understandable collating sequence, although it can still use QBE for any
doublebyte column.
For workstationtoAS/400 session software, J.D. Edwards requires a 32bit
ODBC driver when using a doublebyte language. J.D. Edwards recommends
IBM Client Access for 32bit ODBC drivers, which supports both singlebyte and
doublebyte languages.
The following table shows the languages that OneWorld supports and the
LocalCodeSet values set in the jde.ini file for each platform:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

327

Installation Guide

Tier

Language

Lang.
Lang
C d
Code

LocalCodeSet Value

Tier 1

Tier 2

Tier 3

English

French

German

Italian

Spanish

Portuguese

Japanese

Windows and UNIX

AS/400

WE ISO88591
WE_ISO88591

US EBCDIC
US_EBCDIC

JA_SJIS

JA_EBCDIC

WE_ISO88591

US_EBCDIC

Danish

DN

Dutch

DU

Finnish

FN

Norwegian

NO

Swedish

Korean

KO

KO_KSC

KO_EBCDIC

Traditional
Chinese

CT

TC_BIG5

TC_EBCDIC

Simplified
Chinese

CS

SC_GB

SC_EBCDIC

Arabic

AR

AR_CP1256

N/A

Czech

EECP1250

EE_EBCDIC

Hungarian

HU

Polish

PO

Greek

GR

GR_CP1253

GR_EBCDIC

Russian

RU

RS_CP1251

RS_EBCDIC

Turkish

TR

TK_CP1254

TK_EBCDIC

Font Considerations

J.D. Edwards includes standard language fonts in a separate file. Some languages
(such as doublebyte) require certain fonts to display and print correctly.
OneWorld software stores the font settings in files according to language.
Individual OneWorld users can select fonts by language for forms, grids, and
reports.

328

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Language Process Overview

User Display Preferences


User display preferences are individually defined sets of OneWorld
characteristics that are stored in the user profile. OneWorld uses these
preferences to determine how menus and forms are presented to individual
users and where language is to be used in OneWorld for that user. After user
display preferences are set up for a given user, the values remain the same on
any workstation that the user accesses. See System Administration Guide for
information about modifying user profiles.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

329

Installation Guide

330

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Pre-Installation Procedures
The OneWorld support structure consists of components such as databases,
operating systems, and hardware. To install OneWorld successfully, set up the
support structure before you start the process.
You must complete these preparation tasks before the installation team arrives.
This section consists of the following task:
- Finalizing the preparation

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

41

Installation Guide

42

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

J.D. Edwards recommends you complete the tasks in this chapter before the
installation team arrives.
This chapter consists of the following tasks:
- Running the OneWorld Verification Tool (Environment Checker)
- Verifying hardware and software requirements
- Verifying OneWorld disk space requirements
- Completing the installation detail worksheet

Running the OneWorld Verification Tool (Environment Checker)


Note: Do not run the Verification Tool if you are installing the DB2 UDB
database.
The OneWorld Verification Tool (previously called the Environment Checker) is a
standalone application that you run before installing or upgrading OneWorld on
each platform. The Verification Tool diagnoses any OneWorld configuration and
setup issues you might have at the operating system level. For example, it
verifies that you have enough disk space to install OneWorld to various
machines. The Verification Tool application has an executable file located in the
Verification Tool folder on the root of the OneWorld Installation CD.
Run the Verification Tool for both the deployment and enterprise servers.
When you run the Verification Tool, the interface prompts you for information
about your system. Once the application finishes, the tool creates an output
report, which contains information about your system and any warning
messages that need attention. You do not make modifications to system files or
database tables from the tool.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

43

Installation Guide

OneWorld Verification Tool Process Flow

Requirements File

Report File

Message File

User Input

Log Files

Version 1.2 of the Verification Tool supports Microsoft Windows NT and Intel
platforms only and includes OneWorld versions B71.4, B73.1, B73.2, and B73.3.
This version is also intended to be run before OneWorld is installed on each
platform. Later versions of the tool will include support for milestones
throughout the installation or upgrade process.
To run the OneWorld Verification Tool

Labor Hours

0.5

Computer Hours

0.5

Personnel

Installer or system administrator

Logon status

On the deployment server, logged on as system administrator

Prerequisites

None

Concurrent Tasks

None

Note: Do not run the Verification Tool if you are installing the DB2 UDB
database.
The Verification Tool bases its report on the current disk space requirements for
an installation.
1. Insert the OneWorld Setup CD into the CD drive of deployment server.
2. At the command prompt, navigate to the Environment Checker directory,
and type the path where the Verification Tool file is located.
3. At the command prompt, type ec_winintel.exe.
The Verification Tool command prompt form appears. Enter the following
information as prompted by the tool, and press Enter after each.

44

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

4. Enter the directory where you want the results to be created (for example,
C:\temp).
Type the name of the working directory where you want the Verification
Tool to save the report, log, and message files.
5. Would you like to use the previous set of answers for this test? (Y/N)
Type Y for Yes if you have already run the Verification Tool and want to
use the information you gave at that time. When you answer these
questions, your answers are stored in the User Option File (ec_opts.dat). If
you answer Yes, skip to step 8.
Type N for No if you have not run the Verification Tool already or if you
have run the tool but want to use new settings.
6. Enter the version of OneWorld you plan to install (enter B73.3 for
OneWorld Xe).
Bxx.x is the version you are installing or upgrading from. The base
version number tells the Verification Tool which set of specifications to
check your system against.
The Verification Tool disk space calculation is accurate only for SQL Server
7.0. Refer to the chapter OneWorld Hardware and Software
Requirements" for disk space requirement information.
7. How will this machine be used?
Enter one of the following values:
Value

Description

Deployment server

Host (enterprise server)

Desktop (workstation)

Demonstration

8. Depending on how you answered the question in the previous step, you
will continue with one of the following sets of questions:
A. If you specified that this machine will be used as a deployment
server, answer the following questions, skip parts B and C and
continue with the next step:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

45

Installation Guide

Which environment will this deployment server be running?


Choose AS/400

Which database product will you be using on this server?


Choose one of the following:

Value

Description

Oracle

DB2/400

SQL Server

DB2 UDB

If you chose Oracle, the Verification Tool asks what version of


Oracle will you be using.
Enter the version number, such as 8.1.5, that you will use.

How many path codes will you be loading?


Enter the number of path codes.

What is the host (enterprise) server's name? (Example: app1)


Enter the name of your enterprise server.

Skip parts B and C and continue with the following step.


B. If you specified that this machine will be used as an enterprise
server (host), answer the following questions, skip part C, and
continue with the folloing step:


Which database product will you be using on this server?


Choose one of the following:

46

Value

Description

Oracle

DB2/400

SQL Server

DB2 UDB

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

If you chose Oracle, the Verification Tool asks: What version of


Oracle will you be using? (Example: 8.1.5)
Enter the version number, such as 8.1.5, that you will use.

How many path codes will you be loading?


Enter the number of path codes.

What is the deployment server's name? (Example: deploy2)


Enter the name of your deployment server.

Skip part C and continue with the following step.


C. If you specified that this machine will be used as a workstation,
answer the following questions and continue to step 10:


Will this machine be used for development?


Type Y for Yes if this machine will be used for development, or N
for No if the machine will not be used for development. If you
answer yes, answer the following question.


Will this machine be installing a partial or full package?

Type F if this machine will be installing a full package, or P if the


machine will be installing a partial package.


What is the deployment server's name? (Example: deploy2)


Enter the name of your deployment server.

What is the host (enterprise) server's name? (Example: app1)


Enter the name of your enterprise server.

Which database products this machine will be connecting to?


Choose from the following:
Value

Description

Oracle

DB2/400

SQL Server

DB2 UDB

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

47

Installation Guide

If you chose Oracle, the Verification Tool asks: What version of


Oracle will you be using? (Example: 8.1.5)
Enter the version number, such as 8.1.5, that you will use.

Enter the path where setup.exe is located. The path should be in


Universal Naming Convention format (for example,
\\servername\jdedwardsoneworld\b7333).
Enter the path where your setup.exe file is located. Use the format
shown above. If you enter an incorrect path, a message will appear
asking for the path again. The Verification Tool will not continue
until the correct path is found.

How many path codes will you be loading?


Enter the number of path codes.

D. If you specified that this machine will be used as a demonstration


machine, answer the following questions and continue to step 10:


Will this machine be used for development?


Type Y for Yes if this machine will be used for development, or N
for No if the machine will not be used for development.

9. How much detail would you like on this report?


Enter one of the following:
Value

Description

Low. The smallest amount of detail.

Medium. An average amount of detail.

High. The greatest amount of detail.

After you answer all of the questions that pertain to your setup, the
Verification Tool begins running. When it finishes, a list appears with the
names of the files created by the program.
10. Press Enter to view the ec_rpt.txt file automatically. You can review the
other files individually through Windows Explorer.
The ec_rpt.txt file contains informational messages and warning messages
that explain the results of the tests the Verification Tool ran. For more
information about each numbered test or about customizing the tests, see
the Installation Reference Guide.

48

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Verifying Software and Hardware Requirements


You must meet certain hardware and software requirements to run OneWorld on
various operating systems and servers. Verify that the deployment server,
enterprise servers, and workstations meet the hardware and software
requirements.
This section consists of the following topics:
- Windows NT deployment server requirements
- AS/400 enterprise server requirements
- OneWorld desktop platform/workstation requirements
- OneWorld Web/Java client requirements
- OneWorld Web/Java development workstation requirements
- OneWorld Web/Java Server requirements
- Windows Terminal Server Edition requirements
- Cluster requirements

See Also


OneWorld Disk Space Requirements in this section and OneWorld


Directory Structures" in the Installation Reference Guide, for more
information about hardware and software requirements.

Windows NT Deployment Server Requirements


The OneWorld deployment server must be on an Intel Pentiumbased machine
running the Microsoft Windows NT Server operating system. Every OneWorld
installation must have one deployment server, which you use to install and
maintain OneWorld on all machines on the network.
To guarantee the pristine quality of the software, and to protect the performance
of operational systems during the installation process, dedicate this server to
deploying and operating OneWorld software. You should not use it for any other
purposes. In addition, you should not use your current production server as the
deployment server.
Use the deployment server to store the OneWorld help files if:


You do not have enough space on your workstations to store the


OneWorld help files (currently a minimum of 22 MB)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

49

Installation Guide

You want to update the help files periodically and redistribute them to the
workstations

Deployment Server Hardware Requirements


The following table lists the minimum hardware requirements for a OneWorld
deployment server.
Hardware

Requirements

Notes

CPU

Intel Pentium 300 processor

500 Mhz or higher


(recommeded)

RAM

128 MB (minimum)

256 MB (recommended)

Virtual memory

300 MB (minimum)

600 MB and up (maximum)

Hard drive

Contact your system


representative for optimal
hard drive specifications.

Review OneWorld Disk


Space Requirements."

Screen resolution

800 x 600 pixels

CDROM

Required

Token Ring or Ethernet


connection

Connect the client and server


using one of these methods.

Language Considerations
The system locale of a deployment server needs to be the same language (codepage)
as the one being installed. For example, the system locale of the machine needs to be
set to Japanese to install OneWorld with Japanese language. Note that the language
version of Windows 2000 does not affect any of the language installation processes.
Multitier Deployment Considerations
For multitier deployment environments, you need 300 MB of disk space for the
secondlevel deployment location. You need approximately 200 MB for a full package
and 50 for a partial package. The required disk space also varies depending on the
amount of data you replicate to a Microsoft Access database. For information, see
Multitier Deployment in the Package Management Guide.

Deployment Server Software Requirements


The following table lists the minimum software requirements for a OneWorld
deployment server.

410

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Software

Requirements

Notes

Operating system

Window NT Server 4.0 with


Service Pack 4 or higher

Windows NT SP5, or SP6a is


strongly recommended.

ANSI C Compiler

Microsoft Visual C++ 6.0


with SP1 or higher

Database

Microsoft SQL Server 7.0 SP2


+ Hot Fix 851, or
Oracle 8.0.6 or higher,
including Oracle 8.1.5
(Oracle 8I), or
IBM DB2 Universal Database
(UDB), Administration
Client, version 7.2 Fixpack 4

See "Additional
Requirements"(Database
Systems) below.

Microsoft Access 97 or
Microsoft Access 2000

Access 2000 runs under


Windows NT SP5 or higher.

Database

SQL 7.0 SP2 requires


Windows NT SP5 or higher.
For more information, see
Informational Web Sites,"
below.

For Windows NT SP4 or


higher, Access 2000 and
Access 97 require MDAC 2.1
SP2 (file version
2.1.2.4202.3)
MDAC 2.1 is available from
Microsoft. For more
information, see
Informational Web Sites,"
below.
Client Access Express
(optional)

An AS/400 Operating
Systemrelated version of
Client Access Express

Client Access Express is


present only if DB2/400 is
used on the enterprise
server. For details see,
"OneWorld Xe Technical
Requirements for the AS/400
Enterprise Server."
See Informational APAR
Web Sites" for listings of
required PTFs.
For more information, see
Informational Web Sites,"
below.

Internet browser

Microsoft Internet Explorer


5.0 or higher, or Netscape
Navigator 4.73 or higher

PDF Reader

Adobe Acrobat Reader 4.0

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

411

Installation Guide

Additional Requirements (Database Systems)


The following table shows specific requirements for each database.
To store your central objects (specifications) on your deployment server, you
need one of the following databases.
If DB2/400 is used on the enterprise server, an AS/400 Operating Systemrelated
version of Client Access Express must reside on the deployment server. For
details on versions of Client Access Express for AS/400 Operating Systems, see
Informational APAR Web Site" under AS/400 Enterprise Server Requirements."
Database

Requirements

Notes

Microsoft SQL Server 7.0 MDAC 2.5 SP2 (file version


with Service Pack 2 + Hot 2.1.1.4202.3)
Fix 851

SQL 7.0 SP2 requires


Window NT SP5 or higher.
Use of an uncorrect version
may result in data
corruption.
MDAC 2.5 is available from
Microsoft. For download
information, see
Informational Web Sites,"
below.

Oracle 8.0.6 or higher,


including Oracle 8.1.5
(Oracle 8I)

Networking: Oracle Client


Software CD
Database Administration:
Oracle SQL*Plus.

Your Oracle Client CD must


match your release version
of Oracle and Oracle RDBMS
Your version of Oracle
SQL*Plus must match your
release version of Oracle.
SQL*Plus is on the database
CD, but licensed separately.

AS/400 Enterprise Server Requirements


The following tables list recommended network hardware and software to
support clienttoserver traffic.
AS/400 Enterprise Server Hardware Requirements
The following table lists the minimum hardware requirements for all OneWorld
AS/400 enterprise servers.

412

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Hardware

Requirements

CPU, RAM, hard drive

Contact your IBM


representative for optimal
system hardware
specifications.

CDROM
Printer support

Notes

Required
PostScript, PCL, or line

AS/400 Enterprise Server Software Requirements


The following table lists the minimum software requirements for all OneWorld
AS/400 enterprise servers.
Software

Requirements

Notes

Operating system
(OS/400)

V4R5

See Informational APAR


Web Sites" for listings of
required PTFs.
V4R4 and V4R5 are
recommended.

Client Access Express

OS/400 releasespecific
version

See Informational APAR


Web Sites" for specific
service pack information.

Database

DB2/400

DB2/400 is included in the


AS/400 operating system.

Networking software

TCP/IP

TCP/IP is included in the


AS/400 operating system.

J.D. Edwards software


(optional)

WorldSoftware release A7.3


with Cume update 9
(A73PC00009) or higher.

This software is required


for coexistence only.

OneWorld Cumulative
Coexistence Update
A73PC000x3 or higher

The latest Cume update is


recommended.
For more information, see
Informational Web Sites,"
below.

OptiConnect Considerations
IBM's OptiConnect APIs allow remote database access between AS/400s using either a
fiberoptic link or TCP/IP. You must install OptiConnectrelated PTFs prior to
installing and configuring OneWorld. Make certain the correct PTFs are used for the
appropriate operating system level.
See the Informational APAR Web Site" for required PTF listings.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

413

Installation Guide

Informational APAR Web Site


The following web site allows quick access to the IBM AS/400 Informational
APARs for J.D. Edwards OneWorld application. Reference this site and select
your operating system level to review required PTFs, DLLs, and specific release
versions of Client Access Express, and updated instructions on installing Client
Access Express.
http://www.as400.ibm.com/service/bms/jdesupport.htm
J.D. Edwards recommends that OneWorld AS/400 client sites frequently access
this URL to acquire the most current information.
In addition, there are links to:


IBM AS/400 Client Access Express web page

IBM DB2/400 Group PTF information web pages

Redbook for One World on the AS/400

AS/400 Web Server Requirements


The following table lists the minimum requirements for the OneWorld Web
Server running on an AS/400 platform. These requirements are for a production
system; the requirements for a development platform may be less, depending on
the need of the developers.
AS/400 Web Server Hardware Requirements
The following table lists the minimum hardware requirements for all OneWorld
AS/400 web servers.

414

Hardware

Requirements

Notes

CPU, RAM, hard drive

Contact your IBM


representative for optimal
system hardware
specifications.

For the latest hardware


requirements, refer to the
following link.
http://www.as400.ibm.com/p
roducts/websphere/docs/as40
0v302std/docs/instprrq.html

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

AS/400 Web Server Software Requirements


The following table lists the minimum software requirements for all OneWorld
AS/400 enterprise servers.
Software

Requirements

Notes

Operating System

V4R4 or later.

AS/400 user profile with


*ALLOBJ authority is
required to install
Websphere Application
Server

AS/400 Developer Kit for


Java

AS/400 Developer Kit for


Java (5769-JV1) Version 1.1.7
(option 2)

OS/400 Qshell Interpreter OS/400 Qshell Interpreter


(5769-SS1, option 30)

Needed for local installation


(installing to the AS/400
system from the CDROM of
the AS/400 system)

OS/400 Host Servers

Needed for remote


installation (installing to the
AS/400 system from the
CDROM of the AS/400
system)

OS/400 Host Servers


(5769-SS1, option 12)

QSERVER subsystem must be


running on AS/400 for
installing to your AS/400
system from the CD-ROM of
another workstation.
AS/400 TCP/IP
Connectivity Utilities

AS/400 TCP/IP Connectivity


Utilities/400 (5769-TC1)

Web Server

IBM HTTP Server for AS/400


(5769-DG1)

Servlet Application Server WebSphere 3.02.1 Standard


Edition for AS/400
Database

IBM DB2 version 7.2 Fix


Pack 4 Universal Database
(UDB) for AS/400

DB2 Query Manager and


SQL Development Kit for
AS/400

DB2 Query Manager and


SQL Development Kit for
AS/400 (5769-ST1)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

Is required for remote


installation (installing to your
AS/400 system from the
CDROM of another
workstation). It is also
required to configure and
run Websphere Application
Server 3.02.

WebSphere 3.02.1 setup is


documented separately.

This software is optional


requirement for developing
client applicatoins.

415

Installation Guide

Software

Requirements

Java Application Server


(JAS)

B733.3 SP13

JDBC Driver

AS/400 Toolbox for Java


(5769-JC1)

PTF

For the latest PTFs refer to


PTFs required to run
the following link:
WebSphere 3.02.
http://www.as400.ibm.com/
products/websphere/services
/service.htm

Database:
DB2/400

Notes

AS/400 ODBC Driver: IBM


Client Access Express

For version information, see


Informational Web Sites,"
below.

OneWorld Desktop Platform/Workstation Requirements


The following tables list recommended network hardware and software to
support workstationtoserver traffic.
J.D. Edwards supports the DoubleByte Character Set (DBCS) on Windows NT,
Windows 95 and 98.
Workstation Hardware Requirements
The following table lists the minimum hardware requirements for a OneWorld
desktop platform or workstation.
Hardware

Requirements

Notes

CPU

Intel Pentium 233


(minimum)

Pentium 500 (recommended)

RAM

128 MB (minimum)

256 MB (recommended)

Hard drive

450 MB 2.1 GB free space

450 MB Partial without


development objects
1.34 GB Full without
development objects
1.65 GB Full with
development objects
2.1 GB Standalone with
development objects

416

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Hardware

Requirements

Notes

Display colors

256 colors 8 color panes


(minimum)

65536 colors 16 color panes


(recommended)

Screen resolution

800 x 600 pixels (minimum)

Printer support

PostScript, PCL, or line

Workstation Software Requirements


The following table lists the minimum software requirements for a OneWorld
desktop platform or workstation.
Windows NT is recommended for all development workstations. It is designed
for larger applications, strong security, ample process protection, and is
Microsoft-recommended for development. Development on Windows 98 and
Windows 95 is not recommended.
J.D. Edwards recommends that all new OneWorld installations using Microsoft
Windows NT upgrade to Windows NT with Service Pack 5 or higher (SP6a
highly recommended).
See Also


Additional Requirements (Development Workstations) in this chapter.

Additional Requirements (Web/Java Development Workstations) in this


chapter

Software

Requirements

Notes

Operating system

Windows 95 or
Windows 98 or
Windows NT 4.0 Workstation
w/ SP 5 or higher
Windows 2000 Professional

For Windows NT SP6a, is


strongly recommended.
Do not use OEM versions of
Microsoft Windows 95 and
98.
Mircosoft Windows 98
desktops must utilize Oracle
Client Software 8.0.6 (or
higher) with all Oracle server
releases.
Development on Windows
98 and Windows 95 is not
recommended.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

417

Installation Guide

Software

Requirements

Notes

Database

Microsoft Access 97 or Micro Optional


soft Access 2000
For Windows NT SP4 or
higher, Access 2000 and
Access 97 require MDAC 2.5.
MDAC 2.5 is available from
Microsoft. For download
information, see
Informational Web Sites,"
below.
Dependent on the enterprise For desktop platform
server database.
workstation database
requirements, see Additional
Requirements (Database
Systems).

Internet browser
(optional)

Microsoft Internet Explorer


5.0 or higher, or Netscape
Navigator 4.73 or higher

Optional

PDF Reader

Adobe Acrobat Reader 4.0

Required

Additional Requirements (Database Systems)


Depending on the enterprise server database, OneWorld desktop
platform/workstations may require certain database components. The following
table lists specific database requirements for OneWorld workstations.
Enterprise Server
Database

Workstation Requirements Notes

DB2/400

AS/400 ODBC driver: IBM


Client Access Express

All 32-bit versions of Client


Access Express are
supported.
See Informational Web
Sites" for more information.

418

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Additional Requirements (Development Workstations)


This table lists additional software requirements for OneWorld development
workstations.
Software

Requirements

Notes

Operating system

Windows NT 4.0 Workstation Windows NT SP6, and SP6a


w/ SP5 or higher
is strongly recommended.
Standalone PCs (including
laptops) used for OneWorld
technical demonstrations do
not require Windows NT 4.0.

ANSI C and C++


Compiler

Microsoft Visual C++ 6.0 SP1


or higher

Required for programming,


only.
MS Visual C++ meets the
requirement for both C and
C++ compilers.

Additional Requirements (Web/Java Development Workstations)


This table lists additional software requirements for OneWorld Web/Java
development workstations. For more details see OneWorld Web/Java
Development Workstation Requirements.
Software

Requirements

Notes

Operating system

Windows NT 4.0 Workstation Windows NT SP6 is strongly


w/ SP5 or higher.
recommended.

Java Compiler

MS Virtual Machine (JView)


5.00.3176

Recommend 5.00.3309

ANSI C and C++


Compiler

Microsoft Visual C++ 6.0 SP3


or higher

Required for programming,


only.
MS Visual C++ meets the
requirement for both C and
C++ Compilers.

Class Libraries

OneWorld Xe UPDATE (8 February 2002)

Netscape's IFC

Installation for AS/400 Systems

These libraries are free from


Netscape's web site. For
download information, see
Informational Web Sites,,"
below.

419

Installation Guide

OneWorld Web/Java Client Requirements


The following tables list recommended network hardware and software to
support OneWorld Web/Java clientstoserver traffic.
Web/Java Client Hardware Requirements
The following table lists the minimum hardware requirements for a OneWorld
Web/Java client.
Hardware

Requirements

Notes

CPU

Pentium 166

RAM

32 MB (minimum for
workstation with Microsoft
Internet Explorer 4.0)

Network Computer (NC)

12 MB (minimum for NC)


Hard Drive

10 MB free (minimum for


workstation only)

This size limit is not required


for the Network Computer.

Web/Java Client Software Requirements


The following table lists the minimum software requirements for a OneWorld
Web/Java Client.
Software

Requirements

Notes

Operating system

Any operating system that


can support the Java Virtual
Machine (JVM) for Java
Development Kit (JDK) 1.1.6,
1.1.7, 1.1.8, or 1.1.9

Internet browser

Microsoft Internet Explorer


5.0 or higher, or Netscape
Navigator 4.73 or higher

Browsers are for PCs only.

OneWorld Web/Java Development Workstation Requirements


The following tables list recommended network hardware and software to
support OneWorld Web/Java development workstationtoserver traffic.
Web/Java Development Workstation Hardware Requirements
The following table lists the minimum hardware requirements for a OneWorld
Web/Java development workstation.

420

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Hardware

Requirements

Notes

CPU

Intel Pentium 120


(minimum)

Pentium 166 or highter


(recommended)

RAM

64 MB (minimum)

96 MB (recommended)

Hard drive

450 MB 2.1 GB free space

450 MB Partial without


development objects
1.34 GB Full without
development objects
1.65 GB Full with
development objects
2.1 GB Standalone with
development objects

Display colors

256 colors 8 color panes


(minimum)

Screen resolution

800 x 600 pixels (minimum)

Printer support

PostScript, PCL, or line

65536 colors 16 color panes


(recommended)

Web/Java Development Workstation Software Requirements


The following table lists the minimum software requirements for a OneWorld
Web/Java development workstation.
J.D. Edwards recommends that all new OneWorld installations using Microsoft
Windows NT upgrade to Windows NT with Service Pack 5.
Software

Requirements

Notes

Operating system

Windows NT 4.0 Workstation Windows NT SP5 is strongly


recommended.
w/ SP4 or higher

Java Compiler

MS Java++ 1.1

ANSI C and C++


Compiler

Microsoft Visual C++ 6.0 SP1

Required for programming


only.
Microsoft Visual C++ meets
the requirement for both C
and C++ compilers.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

421

Installation Guide

Software

Requirements

Notes

Class Libraries

Netscape's IFC

Download these libraries for


free from Netscape's web
site. For download
information, see
Informational Web Sites,"
below.

Internet browser

Microsoft Internet Explorer


5.0 or higher or Netscape
Navigator 4.73 or higher
Adobe Acrobat Reader

OneWorld Net Web Server Requirements


The OneWorld Web Server allows you to use OneWorld using a Web browser.
To do this, you must have the proper hardware and software installed on the
machine where you are installing the OneWorld Java Server. The following tables
list recommended network hardware and software to support OneWorld
Web/Java server traffic.
Web/Java Server Hardware Requirements
The following table lists the minimum hardware requirements for a OneWorld
Web/Java Server.
Hardware

Requirements

Notes

CPU, RAM, Hard Drive

Contact your IBM


representative for optimal
system hardware
specifications.

Web/Java Server Software Requirements


The following table lists the minimum software requirements for a OneWorld
Web/Java Server.
J.D. Edwards recommends that all new OneWorld installations using Microsoft
Windows NT upgrade to Windows NT with Service Pack 5.

422

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Software

Requirements

Notes

Operating system

Windows NT Server 4.0 SP4,


SP5 or SP6

Windows NT SP6 is strongly


recommended.

Microsoft Java Virtual


Machine (JVM)

JVM Build 3167 or higher

This JVM build is available


from Microsoft.
For more information, see
Informational Web Sites,"
below.

Web server

Internet Information Server


(IIS) release 4.0

Servlet application server

WebSphere 3.0.2.1 - Stan


dard Edition

Either Standard or Advanced


editions.

Java Development Kit


(JDK)

Microsoft 1.1.7

IBM's JDK is included with


WebSphere 3.x.
The Microsoft JDK can be
downloaded from their web
site. See Informational Web
Sites" for more information.

Internet browser

Microsoft Internet Explorer


5.0 or higher, or Netscape
Navigator 4.73 or higher

OneWorld Client

OneWorld B73.3.2 SP9 (GA Required only for develop


release) or later
ment (i.e., generating Java ob
jects).
OneWorld SP17 or later

OneWorld Client (DB2


UDB)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

423

Installation Guide

Additional Requirements (Database Systems)


Depending on the database used, the OneWorld Web/Java Server may require
additional database components. The following table shows specific
requirements for each database.
Database

Requirements

Notes

Microsoft SQL Server 7.0


SP2 + Hot Fix 851

MDAC 2.5

SQL 7.0 SP2 requires


Windows NT SP5, and Hot
Fix 851.
MDAC 2.5 is available from
Microsoft. For download
information, see
Informational Web Sites,"
below.

WebLogic JDBC driver


jdbcKona/MSSQLServer4
release 5.1 or higher.

Acquire the WebLogic JDBC


driver directly from BEA
Logic, not from J.D.
Edwards.
For more information, see
Informational Web Sites" or
in the U.S., call toll free:
800WEBLOGIC.

Oracle 8.0.6 or higher,


including Oracle 8.1.5
(Oracle 8I)

Oracle JDBC drivers

Use the JDBC drivers that


match your Oracle version.
These drivers are delivered
with the NT Oracle
Installation and are available
from Oracle.
See Informational Web
Sites" for more information.

Client Access Express (If


running DB2/400 on an
enterprise server.)

AS/400 Java Toolkit


AS/400 JDBC Driver: IBM
Client Access Express
(optional)

Client Access Express is


required if running DB2/400
on an enterprise server.
The AS/400 JDBC Driver is
included in the AS/400 Java
Toolkit.
The AS/400 Java Toolkit is
available free from IBM.
See Informational Web
Sites" for more information.

424

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

See Also


OneWorld Java Server Installation and Troubleshooting Guide (for IIS and
JRunPro Web Server Environments)

Windows Terminal Server Edition Requirements


Microsoft Windows NT Server 4.0 Terminal Server Edition (TSE), allows multiple
users to access a single OneWorld workstation.
To run OneWorld client functionality within a server running TSE, users must
install a separate and independent Intelbased hardware server(s) dedicated to
this functionality. While the hardware choices for both the OneWorld enterprise
server and the OneWorld deployment server is of a wider variety, the terminal
server must be Intelbased.
MDAC 2.5, which contains the versions of ODBC drivers, is not supported for
Windows terminal server. However, MDAC 2.5 is now required for all other
servers and workstations if you use SQL Server. Please use your current ODBC
drivers for the Windows terminal server and use the following resolutoin to
resolve conflicts.
Issue: Client installation ODBC conflict when installing on a Windows terminal
server (MDAC 2.5 not supported for Windows terminal server).
Resolution: Before installing a client on a Windows terminal server, perform the
following steps, which allow you to successfully run clients from your Windows
terminal server without using MDAC 2.5:
Language Considerations
The system locale setting for the Terminal Server needs to be the same codepage as
the language being used for OneWorld on that particular machine. Users can only use
the language which resides in the OS's default codepage (system locale).
For example, if an environment has Japanese and English installed, then English
Terminal Server (English NT with system language set to English) can only handle
English. If users try to use Japanese on the machine they will get garbage font
characters.

To run clients on a Windows terminal server without MDAC 2.5


1. On the deployment server, go to the \oneworld\b73x client directory.
2. In the \client directory, create a new subdirectory called \olddlls.
3. Move the following .dlls from the \client directory to the \client\olddlls
directory: odbc32.dll, odbccp32.dll, odbccr32.dll, odbcint.dll.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

425

Installation Guide

4. Perform the client installation on the Windows terminal server.


TSE Hardware Requirements
The following table lists the minimum hardware requirements for a OneWorld
TSE.
Hardware

Requirements

Notes

CPU

2way Pentiumclass Intel


server

Above 15 users, a 4way


CPU is recommended.

RAM

50 MB per user
128 MB for the operating
system

Hard drive

Contact your hardware


representative for optimal
system configurations.

Network card

Required

See the chapter OneWorld


Disk Space Requirements.

TSE Software Requirements


The following table lists the minimum software requirements for a OneWorld
TSE.

426

Software

Requirements

Notes

Operating system

Windows NT 4.0 Terminal


Server Edition (TSE) SP5 or
SP6

Service Packs are available


from Microsoft.

Citrix MetaFrame
(optional)

Optional

MetaFrame 1.8 is
recommended.

Database

Dependent on the enterprise For Windows TSE platform


server database used
database requirements, see
Additional Requirements
(Database Systems."

OneWorld

For DB2 UDB, SP17 or later is The latest Service Pack for
required.
your version of OneWorld is
recommended.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Additional Requirements (Database Systems)


Depending on the enterprise server database, OneWorld Windows NT Terminal
Server platforms may require certain database components. The following table
lists these requirements.
Enterprise Server
Database

Windows Terminal Server


Requirements

Notes

Microsoft SQL Server 7.0


SP2 + Hot Fix 851

MDAC 2.5

SQL 7.0 SP2 requires


Windows NT SP5 or higher,
and Hot Fix 851.
Use of the incorrect version
may result in data
corruption.
The following additional
JDE.INI is also required:
[DB SYSTEM SETTINGS]
TDSError=1
ConnectionPooling=0
MDAC 2.5 is available from
Microsoft. See Informational
Web Sites."

Oracle 8.0.6 or higher,


including Oracle 8.1.5
(Oracle 8I)

Oracle Client Software CD

Your Oracle Client Software


CD must match your specific
release of Oracle, and the
version on your servers.

DB2/400

AS/400 ODBC driver: IBM


Client Access Express

See Informational Web


Sites" for more information.

See Also


OneWorld on Windows NT Terminal Server Edition (TSE) in the Server


and Workstation Administration Guide for more information on the use of
this server.

Windows 2000 Terminal Services Requirements


The following tables list minimum requirements for OneWorld Windows 2000
Server - Terminal Services.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

427

Installation Guide

TSE Hardware Requirements


This table lists the minimum hardware requirements for OneWorld Windows
2000 Server - Terminal Services. The installation must be an Intel-based
server(s) separate from the OneWorld enterprise server.
Hardware

Requirements

Notes

CPU

2way Pentiumclass Intel


server

For optimal CPU


specifications, contact your
system representative.

RAM

50 MB per user
128 MB for the operating
system

Hard drive

Contact your hardware


representative for optimal
system configurations.

TSE Software Requirements


The following table lists the minimum software requirements for a OneWorld
Windows 2000 Server - Terminal Services.
Software

Requirements

Operating system

Windows 2000 Server or


Advanced Server

Citrix MetaFrame

Optional

OneWorld

428

Notes

MetaFrame 1.8 is
recommended.
The latest Service Pack for
your version of OneWorld is
recommended.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Additional Requirements (Database Systems)


Database

Requirements

Notes

Microsoft SQL Server 7.0


SP2 + Hot Fix 851

MDAC 2.5

Use of the incorrect version


may result in data
corruption.
The following additional
JDE.INI is also required:
[DB SYSTEM SETTINGS]
TDSError=1
ConnectionPooling=0
MDAC 2.5 is installed with
Windows 2000.

Oracle 8.1.6 or higher

Networking: Oracle Client


Software CD
Database Administration:
Oracle SQL*Plus

Your Oracle Client Software


CD must match your specific
release of Oracle, and the
version on your servers.

DB2/400

AS/400 ODBC driver: IBM


Client Access Express

See Informational Web


Sites" for more information.

Language Considerations
The system locale setting for Windows 2000 needs to be the same codepage as the
language being used for OneWorld on that machine. Users can only use the language
which resides in the OS's default codepage (system locale).
For example, if an environment has Japanese and English installed, then Windows
2000 Terminal Services (Windows 2000 with system language set to English) can only
handle English. If users try to use Japanese on the machine, then they will get garbage
font characters.

The following table lists informational web sites for issues concerning J.D.
Edwards OneWorld software technical requirements, Microsoft products,
Netscape products, and IBM AS/400 Informational APARs for J.D. Edwards
OneWorld applications. Client sites are advised to frequently access these URLs
to acquire the most current information.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

429

Installation Guide

Subject

Web Site

IBM AS/400
Informational APARs

http://www.as400.ibm.com/service/bms/jdesupport.htm
Reference this site and select your operating system level to
review required PTFs, DLLs, and specific release versions of
Client Access Express, and updated instructions on installing
Client Access Express.
In addition, there are links to the IBM AS/400 Client Access
Express web page, IBM DB2/400 Group PTF information web
pages, and Redbook for One World on the AS/400.

Microsoft

http://www.microsoft.com
From Microsoft's Home Page, select either the Downloads or
the Search option, then drill to the required product
informaiton.

Microsoft Hardware
Compatibility List

http://www.microsoft.com/hwtest.hcl

Netscape Download

http://home.netscape.com/download/

OneWorld Technical
Requirements

http://knowledge.jdedwards.com/JDEContent/TechMarketingC
U/information/bjtechreqs.htm

OneWorld and NT
Terminal Servers

OneWorld Online NT TSE Web Site

Oracle

http://www.oracle.com

SQL Server Hot Fix


851

ftp://ftp.microsoft.com/bussys/sql/transfer/sql70/sqlservr/s7085
1I.exe. The password for this fix is 7.00.851
First, install the base service pack, then apply hot fix 851.
Expand the hot fix from a command prompt, supplying the
password as a command line argument. Installation
instructions are in the Readme.txt file included with the fix.
Please note that service pack 2 contains a base component
and an OLAP services component. OneWorld requires the base
component only. However, a customer's installation may
require the OLAP component. J.D. Edwards has not certified
any of the OLAP components of the service pack.

Sun JDK

430

http://www.java.sun.com/jdk/1.1

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Subject

Web Site

WebLogic JDBC Driver http://www.weblogic.beasys.com/index.htm

Verifying OneWorld Disk Space Requirements


The following tables help you calculate the amount of disk space you need for
OneWorld software on the deployment and enterprise servers. Disk space
requirements vary according to database. Size values are in gigabytes (GB).
The space listed must be available on a single drive. Having the correct amount
of space available, but not on a single drive, is not adequate.
All numbers in this section are approximate.
This section contains requirements for the following:
- Deployment server disk space requirements
- BLOB support disk space requirements
- Data server disk space requirements
- Enterprise server disk space requirements
- Language installation disk space requirements

Deployment Server Disk Space Requirements

Description

Size (GB)

Planner and other objects


Database exports

Your requirements
2 GB

Oracle: 1.30 GB
SQL Server: 1.30 GB
DB2 UDB 1.37 GB

Prototype (CRP) path code

3.7 GB*

Development path code

3.7 GB*

Pristine path code

3.7 GB*

Production path code

3.7 GB*

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

431

Installation Guide

Description

Size (GB)

Additional path codes

Your requirements
3.7 GB*

Subtotal

Each path code size includes space for two sets of full and partial packages.
A full package requires approximately 1.5 GB and a partial package requires
approximately 170 MB.

BLOB Support Disk Space Requirements


On the deployment server, no SQL Server or Oracle is needed. Disk space for
the SQL or Oracle database does not need to be allocated.
On the AS/400 server, 2 GB of DASD per path code is needed for the B73.3.x
central objects.

Data Server Disk Space Requirements


If you are using an Oracle database for your Central Objects, use the following
table to calculate the amount of disk space required for your deployment server
database. Base the total on the central objects data sources you require.

Description (Data Source)

Oracle (MB)

Your requirements

Central objects for pristine path code


(Central Objects JD7333)

1650

Central objects for production path


code (Central Objects PD7333)

1650

Central objects for prototype path


code (Central Objects PY7333)

1650

Central objects for development path


code (Central Objects DV7333)

1650

Central objects for any additional


path codes

1650

Subtotal

If you are using a SQL Server database for your Central Objects, use the
following table to calculate the amount of disk space required for your
deployment server database. Base the total on the central objects data sources
you require.

432

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Data Source (Database)

SQL Server
7.0 (GB)

Your
requirements

Central objects for pristine path code


(Central Objects JD7333)

2.2

Central objects for production path


code (Central Objects PD7333)

2.2

Central objects for prototype path


code (Central Objects PY7333)

2.2

Central objects for development path


code (Central Objects DV7333)

2.2

Central objects for any additional


path codes

2.2

Subtotal

Having separate databases will require the ODBC data sources to be set up
differently. OneWorld data sources will need to have their ODBC data sources
set up to point at the correct SQL Server database.

See Also


Creating ThirdParty ODBC Data Sources"

Enterprise Server Disk Space Requirements


Use the following chart to calculate the amount of additional space required for
your enterprise server database. Base the total on the data sources and path
codes you require.

Description

Size

Your requirements

xxxxxSYS* library (server objects)

105 MB

OL7333 library (Object Librarian


B7333)

35 MB

DD7333 library (Data Dictionary


B7333)

90 MB

JD7333

3.4 GB*

PD7333

3.4 GB*

PY7333

3.4 GB*

DV7333

3.4 GB*

Additional libraries

OneWorld Xe UPDATE (8 February 2002)

3.4 GB

Installation for AS/400 Systems

433

Installation Guide

Description

Size

Your requirements

SYS7333 library (System B7333)

135 MB**

PRODDTA Business Data

275 MB**

TESTDTA Business Data

275 MB**

CRPDTA Business Data

275 MB**

PRISTDTA Business Data

275 MB**

PRODCTL Control Tables Prod

50 MB**

TESTCTL Control Tables Test

50 MB**

CRPCTL Control Tables CRP

50 MB**

SUM7333 (Server map)

2 MB

Subtotal

Totals include space for each path code library, IFS specification files and
DNT versions library. This library already exists and there is no additional
space requirement.

**

If you have coexistence libraries, sizes will vary.

Language Installation Disk Space Requirements


Prior to performing your language installation, ensure that your machines have
adequate disk space. Please note that the space requirements for singlebyte and
doublebyte languages are the same. The table below shows the requirements to
load one alternate language.

OneWorld machine

Disk space requirements


(per language)

Deployment server

250 MB

Client workstation

100 MB

Database

Central objects for pristine path code


(Central Objects JD7333)

300 MB

Central objects for production path code


(Central Objects PD7333)

100 MB

Central objects for prototype path code


(Central Objects PY7333)

100 MB

Subtotal

434

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Completing the Installation Detail Worksheet


Use this worksheet to record names, passwords, path codes, and other important
information you will refer to during the installation process. Fill in the system
information and check off the appropriate choices as you prepare for your
installation process.

Data Sources - Shared for All Environments


In the following tables, the Type column should contain for the following
database types:
Value

Description

Access

Oracle

Client Access Express

SQL Server

DB2 UDB

*The object owner ID for a DB2 UDB database will be SY7333, not SYS7333."
DB2 UDB does not allow a schema starting with the letters SYS."

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

435

Installation Guide

System
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

System B7333

SYS7333

System B7333CRP
DNT

SYS7333DNT

Object Librarian
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Object Librarian
B7333

OL7333

Data Dictionary
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Data Dictionary
B7333

DD7333

Distributed Processing (Enterprise Server)


Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

enterpriseserver

SUM7333

Replicated Local Data


Data source name

Type

AS/400
database name

Server name

Platform

OneWorld Local
PD7333

N/A

LOCAL

LOCAL

OneWorld Local
PY7333

N/A

LOCAL

LOCAL

436

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Data source name

Type

AS/400
database name

Server name

Platform

OneWorld Local
JD7333

N/A

LOCAL

LOCAL

OneWorld Local
DV7333

N/A

LOCAL

LOCAL

Environments - OneWorld Xe Production


Environment Description
name

Path code

Central objects data


source

Load
data

PD7333

PD7333

Central Objects PD7333

Prod

OneWorld Xe production
environment

Data Sources
Business Data
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Business Data
PROD

PRODDTA or
existing library

Business Data
PROD DNT

PRODDTA or
existing library

Central Objects Specifications


Data source name

Type

AS/400
database name

AS/400 Library

N/A

N/A

AS/400
database name

AS/400 Library

Connectstring

Central Objects
PD7333

Control Tables
Data source name

Type

Connectstring

Control Tables
Prod

OneWorld Xe UPDATE (8 February 2002)

PRODCTL

Installation for AS/400 Systems

437

Installation Guide

Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

AS/400 COMMON
Production

Existing AS/400
Common library

Version Tables
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Versions PD7333

PD7333

Versions PD7333
DNT

PD7333DNT

Object Mappings

Object class

Description

Data source name

Default

Business data (translate)

Business Data PROD

Business data (do not translate)

Business Data PROD DNT

OneWorld System tables (translate)

System B733

OneWorld system tables (do not translate)

System B733 DNT

Data Dictionary

OneWorld data dictionary

Data Dictionary B733

Menus

OneWorld menus

OneWorld Local PD7333

User Defined Codes

OneWorld user defined codes

OneWorld Local PD7333

Versions Tables

OneWorld versions tables (Translate)

Versions PD7333

OneWorld versions tables (do not translate)

Versions PD7333 DNT

Object Librarian

Object Librarian

Object Librarian B733

Next Numbers (F0002)

OneWorld next numbers

AS/400 COMMON
Production

Batch Applications

Batch reports

enterpriseserver

System

Packages

Package name

Description

Path code

Central objects data source

PD7333FA

OneWorld Xe production package


(full)

PD7333

Central Objects PD7333

438

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Package name

Description

Path code

Central objects data source

PD7333PA

OneWorld Xe production package


(partial)

PD7333

Central Objects PD7333

Environments - OneWorld Xe Test


Environment Description
name

Path code

Central objects data


source

Load
data

TS7333

PY7333

Central Objects PY7333

Prod

OneWorld Xe test environment

Data Sources
Business Data
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Business Data
TEST

TESTDTA or
existing Library

Business Data
TEST DNT

TESTDTA or
existing library

Central Objects Specifications


Data source name

Type

AS/400
database name

AS/400 Library

N/A

N/A

AS/400
database name

AS/400 Library

Connectstring

Central Objects
PY7333

Control Tables
Data source name

Type

Connectstring

Control Tables Test

TESTCTL

AS/400 COMMON
Test

Existing AS/400
Common library

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

439

Installation Guide

Version Tables
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Versions PY7333

PY7333

Versions PY7333
DNT

PY7333DNT

Object Mappings

Object class

Description

Data source name

Default

Business data (translate)

Business Data TEST

Business data (do not translate)

Business Data TEST DNT

OneWorld System tables (translate)

System B7333

OneWorld System tables (do not translate)

System B7333 DNT

Data Dictionary

OneWorld data dictionary

Data Dictionary B7333

Menus

OneWorld menus

Control Tables Test

User Defined Codes

OneWorld user defined codes

AS/400 COMMON Test

Versions Tables

OneWorld versions tables (translate)

Versions PY7333

OneWorld versions tables (do not translate)

Versions PY7333 DNT

Object Librarian

Object Librarian

Object Librarian B7333

Next Numbers (F0002)

OneWorld next numbers

AS/400 COMMON Test

Batch Applications

Batch reports

enterpriseserver

System

Packages
Package name

Description

Path code

Central objects data source

PY7333FA

OneWorld Xe CRP package (full)

PY7333

Central Objects PY7333

PY7333PA

OneWorld Xe CRP package


(partial)

PY7333

Central Objects PY7333

440

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Environments - OneWorld Xe Prototype


Environment Description
name

Path code

Central objects data


source

Load
data

PY7333

PY7333

Central Objects PY7333

Prod

OneWorld Xe prototype (CRP)


environment

Data Sources
Business Data
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Business Data CRP

CRPDTA or
existing library

Business Data CRP


DNT

CRPDTA or
existing library

Central Objects Specifications


Data source name

Type

AS/400
database name

AS/400 Library

N/A

N/A

AS/400
database name

AS/400 Library

Connectstring

Central Objects
PY7333

Control Tables

Data source name

Type

Connectstring

Control Tables CRP

CRPCTL

AS/400 COMMON
CRP

Existing AS/400
Common library

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

441

Installation Guide

Version Tables
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Versions PY7333

PY7333

Versions PY7333
DNT

PY7333DNT

Object Mappings

Object class

Description

Data source name

Default

Business data (translate)

Business Data CRP

Business data (do not translate)

Business Data CRP DNT

OneWorld System tables (translate)

System B7333

OneWorld System tables (do not translate)

System B7333 DNT

Data Dictionary

OneWorld data dictionary

Data Dictionary B7333

Menus

OneWorld menus

OneWorld Local PY7333

User Defined Codes

OneWorld user defined codes

OneWorld Local PY7333

Versions Tables

OneWorld versions tables (translate)

Versions PY7333

OneWorld versions tables (do not translate)

Versions PY7333 DNT

Object Librarian

Object Librarian

Object Librarian B7333

Next Numbers (F0002)

OneWorld next numbers

AS/400 COMMON CRP

Batch Applications

Batch reports

enterpriseserver

System

Packages
Package name

Description

Path code

Central objects data source

PY7333FA

OneWorld Xe CRP package (full)

PY7333

Central Objects PY7333

PY7333PA

OneWorld Xe CRP package


(partial)

PY7333

Central Objects PY7333

442

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Environments - OneWorld Xe Pristine


Environment Description
name

Path code

Central objects data


source

Load
data

JD7333

JD7333

Central Objects JD7333

Demo

OneWorld Xe pristine
environment

Data Sources
Business Data
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Business Data JDE

PRISTDTA

Business Data JDE


DNT

PRISTDTA or
existing library

Central Objects Specifications


Data source name

Type

AS/400
database name

AS/400 Library

N/A

COJD7333

Connectstring

Central Objects
JD7333

Control Tables

Data source name

Type

AS/400
database name

AS/400 Library

Control Tables - JDE

PRISTCTL

Control Tables - JDE


DNT

PRISTCTL

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

Connectstring

443

Installation Guide

Data Dictionary
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Data Dictionary JDE (Mappings are


delivered as
inactive)

PRISTCTL

Version Tables

Data source name

Type

AS/400
database name

AS/400 Library

Versions JD7333

JD7333DNT

Versions JD7333
DNT

JD7333DNT

Connectstring

Object Mappings
Object class

Description

Data source name

Default

Business data (translate)

Business Data JDE

Business data (do not translate)

Business Data JDE DNT

OneWorld System tables (translate)

System B7333

OneWorld System tables (do not translate)

System B7333 DNT

Data Dictionary

OneWorld data dictionary

Data Dictionary B7333

Menus

OneWorld menus

OneWorld Local JD7333

User Defined Codes

OneWorld user defined codes

OneWorld Local JD7333

Versions Tables

OneWorld versions tables (translate)

Versions JD7333

OneWorld versions tables (do not translate)

Versions JD7333 DNT

Object Librarian

Object Librarian

Object Librarian B733

Next Numbers (F0002)

OneWorld next numbers

Business Data JDE

System

444

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Object class

Description

Data source name

Batch Applications

Batch reports

enterpriseserver

Packages

Package name

Description

Path code

Central objects data source

JD7333FA

OneWorld Xe pristine package


(full)

JD7333

Central Objects JD7333

JD7333PA

OneWorld Xe pristine package


(partial)

JD7333

Central Objects JD7333

Environments - OneWorld Xe Development


Environment Description
name

Path code

Central objects data


source

Load
data

DV7333

DV7333

Central Objects DV7333

Prod

OneWorld Xe development
environment

Data Sources
Business Data
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Business Data
TEST

TESTDTA or
existing library

Business Data
TEST DNT

TESTDTA or
existing library

Central Objects Specifications


Data source name

Type

AS/400
database name

AS/400 Library

N/A

N/A

Connectstring

Central Objects
DV7333

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

445

Installation Guide

Control Tables
Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Control Tables Test

TESTCTL

AS/400 COMMON
Test

Existing AS/400
Common library

Version Tables

Data source name

Type

AS/400
database name

AS/400 Library

Connectstring

Versions DV7333

DV7333

Versions DV7333
DNT

DV7333DNT

Object Mappings

Object class

Description

Data source name

Default

Business data (translate)

Business Data TEST

Business data (do not translate)

Business Data TEST DNT

OneWorld System tables (translate)

System B7333

OneWorld System tables (do not translate)

System B7333 DNT

Data Dictionary

OneWorld data dictionary

Data Dictionary B7333

Menus

OneWorld menus

OneWorld Local DV7333

User Defined Codes

OneWorld user defined codes

OneWorld Local DV7333

Versions Tables

OneWorld versions tables (translate)

Versions DV7333

OneWorld versions tables (do not translate)

Versions DV7333 DNT

Object Librarian

Object Librarian

Object Librarian B7333

Next Numbers (F0002)

OneWorld next numbers

AS/400 COMMON Test

Batch Applications

Batch reports

enterpriseserver

System

446

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Finalizing the Preparation

Packages
Package name

Description

Path code

Central objects data source

DV7333FA

OneWorld Xe development
package (full)

DV7333

Central Objects DV7333

DV7333PA

OneWorld Xe developmnt package DV7333


(partial)

Central Objects DV7333

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

447

Installation Guide

448

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the Deployment Server


OneWorld resides on an Intel Pentiumbased deployment server running
Windows NT. The OneWorld installation program allows you to create and
maintain installation plans and deploy OneWorld to the enterprise servers and
workstations. The installation program loads OneWorld on the deployment
server, and then guides you to load central objects (specifications) tables into
your Oracle, SQL Server, or AS/400 database.
Note that you must install the deployment server locally; you cannot install the
deployment server to a remote machine.
This section consists of the following tasks:
- Installing OneWorld on the deployment server
- Installing the OneWorld databases
The installation process for the deployment server:


Installs the objects from the OneWorld CDs

Creates the path code directory structures (such as JD7333 and PD7333)
based on your selections

Creates directories for the following enterprise server types:


-

AS/400

Intel processor on Windows NT

HP 9000

RS/6000

Sun Solaris

Updates the Windows NT registry

Creates the ODBC data sources

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

51

Installation Guide

52

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

After you verify the support structure, you can install OneWorld on the
deployment server.

Chapter Contents
This chapter consists of the following tasks:
- Configuring the deployment server
- Installing the objects
- Installing an alternate language on the deployment server
- Installing AS/400 libraries and the data dictionary
- Setting up the TCP/IP protocol for the enterprise server
- Copying your specification files

See Also


Detail Worksheet" to record information that will be needed as you


proceed through the Installation Workbench application

Note that you must install the deployment server locally; you cannot install the
deployment server to a remote machine.

Configuring the Deployment Server


Before you install OneWorld, you must configure the deployment server. To do
this:


Create the user JDE as a system administrator, which lets you perform all
thirdparty installation tasks while you are logged on as user JDE

Install FTP if it is not already installed, and configure FTP correctly to be


sure that all file transfers work correctly

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

53

Installation Guide

Unless otherwise instructed, from now on, log on as JDE to install OneWorld
and thirdparty products.
To create a JDE user

Labor Hours

0.5

Computer Hours

0.5

Personnel

System administrator

Logon status

On the deployment server, logged on as the system


administrator.

Prerequisites

None

Concurrent Tasks

None

1. From the deployment server, log on as the system administrator.


2. On Administrative Tools, choose User Manager for Domains.
3. To configure the deployment server, create a user JDE with password JDE.
The password is case sensitive.
4. Give system administrator privileges to user JDE.
5. To apply these changes, log off, then log on again as JDE.
6. If you do not have a printer device, see the appropriate Windows and
printer documentation to create one.
Print Considerations
When you set up printer names on the deployment server or workstations,
they must not exceed 30 characters in order for OneWorld to run properly.

To install and configure the file transfer protocol (FTP)


Complete one of the following procedures to install and configure the file
transfer protocol (FTP) on your system:


Installing and configuring Microsoft Internet Information Server 3.0

Installing and configuring Microsoft Internet Information Server 4.0


If FTP is already installed on your deployment server, continue with
"Installing the Objects."

54

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

To Install and configure Microsoft Internet Information Server 3.0

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

From Windows NT, on the Control Panel, logged on as system


administrator.

Prerequisites

None

Concurrent Tasks

None

1. From the deployment server, log on as the system administrator.


2. From Control Panel, choose Network.
3. Click the Services tab.

4. Select one of the following options:




f Microsoft Internet Information Server 3.0 is listed in network


services, skip to the next step.

If Microsoft Internet Information Server 3.0 is not listed in network


services, click Add. Doubleclick on Microsoft Internet Information
Server 3.0. Version 3.0 is available through Microsoft or with
Windows NT Service Pack 3.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

55

Installation Guide

5. From Windows Explorer, access the drive on which Windows resides.


6. Locate inetmgr.exe in the directory path \winnt\system32\inetsrv.
7. Doubleclick inetmgr.exe.

8. On Microsoft Internet Service Manager, rightclick the FTP service of the


name of your deployment server.
9. From the menu that appears, choose Service Properties.

56

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

10. On FTP Service Properties, make sure the following options are set
correctly:


Allow Anonymous Connections should be turned on.

Allow only anonymous connections should be turned off.

A message may prompt you to confirm that you want to continue. Click
Yes.
11. Click the Directories tab.

12. Click on the Directory Listing Style you prefer.




UNIX

MS-DOS

13. Determine the next step:




If the drive to which you want to install OneWorld does not appear,
click Add. (To determine the amount of disk space you need, see
"Data Server Disk Space Requirements" in the previous chapter.)

If the drive does appear, highlight it and click Edit Properties.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

57

Installation Guide

14. On Directory Properties, make sure the following options are set correctly:


Directory
Type the drive on which you want to install OneWorld, or click
Browse to find the drive.

Alias
Type the drive location preceded by a slash (for example, /d:).

In the Access box


Turn on the Read and Write options.
You must have both a virtual and a home directory, even if they are
defined on the same drive.

15. Click OK.


16. On FTP Service Properties, click OK.
17. Reboot if a message prompts you to do so.

58

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

To Install and configure Microsoft Internet Information Server 4.0


and 2000

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

From Windows NT, on the Control Panel, logged on as system


administrator.

Prerequisites

None

Concurrent Tasks

None

Microsoft Internet Information Server version 4.0 is included with the Microsoft
Windows NT 4.0 Option Pack and is available through Microsoft. On Windows
2000, Microsoft Internet Information Server comes with the Server Operating
System.
1. On the deployment server, open the Microsoft Windows NT 4.0 Option
Pack and install at least the following components and subcomponents:


Internet Information Server (IIS)




FTP Server

Internet Service Manager

World Wide Web Server

Microsoft Data Access Components

Microsoft Management Console

NT Option Pack Common Files

Transaction Server

2. After installing the components, restart the computer if requested.


3. For IIS 4.0: From the Windows Start Menu, choose Programs - Windows
NT 4.0 Option Pack - Microsoft Internet Information Server - Internet
Service Manager
The program displays the IIS screen.
For Windows 2000: From the Windows Start Menu, choose Programs Administration Tools - Internet Services Manager
4. Expand the directory structure in the left pane to display the following
directory path: Internet Information Server - servername - Default FTP
Site (where servername is the name of your deployment server).
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

59

Installation Guide

5. Right click on the Default FTP Site folder and choose New - Virtual
Directory

The program displays the New Virtual Directory Wizard window.

6. Enter the alias used to access the virtual directory (for example, enter d:,
where d is the drive where OneWorld is installed on the Deployment
Server).
7. Click Next.

510

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

8. Enter the physical path to the drive where OneWorld is installed (for
example, d:\).
9. Click Next.

10. Ensure that Allow Read Access and Allow Write Access are selected
(checked).
11. Click Finish.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

511

Installation Guide

Installing the Objects


This process installs OneWorld from two CDs to the deployment server. The first
CD installs OneWorld and the path codes. The second CD installs Oracle and
SQL Server import files.
Note: If central objects will reside in DB2, it is not necessary to run second setup
CD.
Before you run the installation program, shut down all programs running on the
deployment server that could cause DLL conflicts (such as Microsoft SQL
Services, Internet Explorer, or Adobe Acrobat). You can restart these programs
after you finish installing the second setup CD on the deployment server.
To install the objects

Labor Hours
Computer Hours
Personnel

0.25
1.5 2 (depending upon your system)
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for JDE.

Prerequisites

Create JDE user.

Concurrent Tasks

If you are installing central objects on the AS/400, you can


complete the procedure Loading Central Objects" in the next
chapter.

1. If the computer has an older version of Adobe Acrobat installed (less than
4.0), use Add/Remove Programs in the Control Panel to remove it before
installing the deployment server.
2. Log on to the deployment server with system administrator privileges.
3. Insert the first setup CD into the CD drive.
Setup starts automatically.

512

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

The installation program verifies whether several system DLLs are current.
If they are not current, you receive a message to reboot your system.
When you reboot, the system updates the DLLs in your Windows
directories. After the updates finish, rerun the setup.exe program.
Troubleshooting
In some cases, the reboot does not finish updating the DLLs. If this happens,
manually shut down and restart the deployment server to finish the process.
4. Click Xe Deployment Server Install. The JDEdwards OneWorld
Deployment Server Setup form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

513

Installation Guide

5. Click Next. The JDEdwards OneWorld Deployment License Setup form


appears.

6. Complete the following fields:




Expiration Date
Enter the date on which OneWorld software expires. This date
applies to the deployment server as well as to workstations.


514

Number of Licenses

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

Enter the number of installations allowed. The number is based on


the authorization code.


Authorization Code
Enter the code that lets you access OneWorld software. The code is
based on your contract.
To obtain the required authorization code, call J.D. Edwards Global
Support Services, 8002892999, Monday through Friday 8:00am
5:00pm U.S. Mountain Time (GMT-7:00). J.D. Edwards asks for the
following:


The serial number that appears on OneWorld Deployment


License Setup

The number of licenses as shown on your contract

Other pertinent information about your company

Each time you rerun the setup program, the serial number changes.
This requires you to obtain a new authorization code from J.D.
Edwards. Avoid stopping and rerunning the installation program
after you obtain an authorization code.
To revalidate authorization codes for the deployment server and
workstations, see the chapter Revalidating Software Protection
Codes."
7. Click Next.
If you do not have the latest versions of Microsoft Internet Explorer or
Adobe Acrobat Reader installed, the JDEdwards OneWorld Deployment
Server Setup Third Party Application form appears. The options to install
these applications will be turned on.
If you have both of these applications installed, you will not see the
following form. You can skip the next step.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

515

Installation Guide

8. Click Next. The package size is calculated. This can run for several
minutes.

9. On OneWorld Deployment Server Setup Type, choose one of the


following setup type options:

516

OneWorld and All Path Codes

OneWorld and the Pristine Path Code

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

Custom

10. In the Target Folder field, enter the directory where you want the files
installed on your deployment server, for example,
c:\JDEdwardsOneWorld\b7333 or d:\JDEdwardsOneWorld\b7333.
If this directory does not already exist, the setup program will create it for
you.
11. Click Next.
If you choose an option other than Custom as your setup type, skip the
following step.

12. On OneWorld Deployment Server Setup Component Selection, verify the


appropriate components are installed, and click Finish.
Note: OneWorld Files contain system files and must be installed.
The OneWorld Deployment Server Setup Progress form appears as files
are loaded.
13. After the programs finish, a message appears telling you that the
installation was successful. Click OK and exit Installation Manager.
Note: When the first CD completes, it does not prompt you to insert the
second CD. For DB2/UDB, the second CD is labelled "SetupCD UDB
Database 1 of 1."
14. Insert the second CD.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

517

Installation Guide

If you are installing your central objects on a DB2 database, do not insert
the second CD. Instead, skip to the section "Installing the Data Dictionary"
later in this chapter.
Setup starts automatically.

15. On JDEdwards OneWorld Installation Manager, doubleclick OneWorld Xe


Deployment Server Install.

16. On JDEdwards OneWorld Deployment Server Setup, click Next.

518

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

If you are using an Oracle database, the disk space calculation may show
a negative number, due to a smaller dump file used in this version. You
can ignore this calculation.
17. On JDEdwards OneWorld Deployment Server Setup Type, choose from
the following setup type options:


Oracle Data Files

SQL*Server Data Files

Custom

This setup selection reflects the enterprise server database, not the
deployment server database.
If you choose "Oracle Data Files" or "SQL*Server Data Files," click finish
and skip to step 20.
Central Objects Considerations
If you want to install central objects on the AS/400, you must choose the
Custom option and not install the Oracle and SQL Server databases
automatically. Once this task is complete, complete the procedure Loading
Central Objects" in the next chapter.
You can run the procedure Loading Central Objects" while completing the
deployment server installation.
18. If you chose "Custom," Click Next.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

519

Installation Guide

19. On JDEdwards OneWorld Deployment Server Setup Component Selection,


choose one of the following database types and click Finish:


Oracle

SQL*Server

20. When the installation finishes, the JDEdwards OneWorld Deployment


Server Setup form tells you if the installation was successful.
If it is needed, OneWorld will prompt you to restart your computer.

Installing an Alternate Language on the Deployment Server


Perform this procedure only if you are installing an alternate language. If you are
not installing an alternate language, continue to the next section in this chapter.
Installing an alternate language on the deployment server performs the following
tasks:

520

The language.mdb file for the language you are installing is copied into
the \Planner\Data directory.

The spec.cab file replaces the spec.cab file in the selected path code
\package directory.

The jdeb7.mdb replaces the jdeb7.mdb in the selected path code


\package\Data directory.

The ActivEra Summary files for the language you are installing are copied
into the \ActivEra\Data\(Language Code) directory.
Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

The Help files for the language you are installing are copied into the
\Helps directory.

The Data.cab replaces the data.cab in the selected path code


\PACKAGE\DATACOMP directory.
To install an alternate language on the deployment server

Labor Hours

0.5

Computer Hours

0.5

Personnel

Installer

Logon status

In Windows Explorer, logged on as the JDE user.

Prerequisites

OneWorld must be installed on the deployment server.

Concurrent Tasks

None

1. Insert the language CD into the CD drive.


2. Run the setup.exe file for language.
The JDEdwards OneWorld Deployment Server Setup Progress form
appears as files are loaded.

When the installation finishes, the JDEdwards OneWorld Deployment


Server Setup form tells you if the installation was successful.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

521

Installation Guide

If you are installing more than one alternate language, the last
language installed will be the language available with the standard
package.
If you want the ability to access more than one language within the
same package, you need to build a custom package that includes all
available languages.

Installing the Data Dictionary


Before running Installation Planner, you can install the data dictionary to the
AS/400 enterprise server. This process is now automated. Rather than creating
each library manually, the libraries are created when loading the first enterprise
server CD.
The following chart provides additional information about each library:

522

Library

Description

DD7333

Contains data dictionary tables for OneWorld. The OneWorld data


source name is Data Dictionary B7333. This data source is created
during installation.

PRISTDTA

Contains pristine data for OneWorld. Pristine data is different from


the demonstration data in JDFDATA. The OneWorld data source
name is Business Data JDE.

CRPDTA

Contains CRP data for OneWorld and WorldSoftware. The OneWorld


data source name is Business Data CRP.

TESTDTA

Contains test data for both OneWorld and WorldSoftware. The


OneWorld data source name is Business Data TEST.

PRODDTA

Contains production data for both OneWorld and WorldSoftware.


The OneWorld data source name is Business Data PROD.

PRODCTL

Contains menu tables for the OneWorld production environment.


The OneWorld data source name is Control Tables Production.

TESTCTL

Contains menu tables for the OneWorld test environment. The


OneWorld data source name is Control Tables Test.

CRPCTL

Contains menu tables for the OneWorld prototype (CRP)


environment. The OneWorld data source name is Control Tables
CRP.

PD7333DNT

Contains the versions tables (F983051 and F98306) for the


production path code. The Versions PD7333 DNT data source
points to the F983051 table. The Versions PD7333 data source
points to the F98306 table.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

Library

Description

PY7333DNT

Contains the versions tables (F983051 and F98306) for the prototype
(CRP) path code. The Versions PY7333 DNT data source points
to the F983051 table. The Versions PY7333 data source points to
the F98306 table.

JD7333DNT

Contains the versions tables (F983051 and F98306) for the pristine
path code. The Versions JD7333 DNT data source points to the
F983051 table. The Versions JD7333 data source points to the
F98306 table.

DV7333DNT

Contains the versions tables (F983051 and F98306) for the pristine
path code. The Versions DV7333 DNT data source points to the
F983051 table. The Versions DV7333 data source points to the
F98306 table.

To install the data dictionary

Labor Hours

less than 0.25 hours

Computer Hours

less than 0.25 hours

Personnel

Installer

Logon status

Logged on to the AS/400 as QSECOFR.

Prerequisites

None

Concurrent Tasks

You can complete any of the tasks in this chapter.

1. Log on to the AS/400 as QSECOFR.


2. Insert the CD AS/400 Direct Enterprise Server Install 1 of 7" into the CD
drive.
3. Enter the following command, where OPTxx is the optical device name:
LODRUN DEV(OPTxx)
for example, OPT01

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

523

Installation Guide

AS/400 Libraries Considerations


Once you have entered LODRUN OPTxx" in the task above, the following
libraries are created automatically:
DD7333, SYS7333, SVM7333, OL7333, PRODDTA, TESTDTA, CRPDTA,
PRISTDTA, PRODCTL, TESTCTL, CRPCTL, PD7333DNT, JD7333DNT,
PY7333DNT and DV7333DNT
These libraries are populated at various points in the process. However, most
of these libraries will be populated during Installation Workbench.
A menu appears.
4. Enter selection 2 to install the Data Dictionary.

5. Change the device name to match the name of the optical device, for
example, OPT01.
If you are installing a double byte language, specify *YES in the Double
Byte option field in the Install Data Dictionary screen. This will ensure that
the Data Dictionary tables are restored with the necessary Double Byte
Data Type "O" (DBCS-Open Data).
6. Press Enter.
This is an interactive program, not a batch job. It will run for three to four
minutes.

524

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

Tips and Techniques


DB2 users can create journals that track changes made to AS/400 tables. For
more information about creating journals on the AS/400, see Backing Up
OneWorld Tables" in the Server and Workstation Administration Guide.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

525

Installation Guide

Setting up the TCP/IP Protocol for the Enterprise Server


To set up the TCP/IP protocol for the enterprise server

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer or system administrator

Logon status

On the enterprise server, logged on as QSECOFR.

Prerequisites

None

Concurrent Tasks

None

J.D. Edwards recommends you set up the TCP/IP service to start automatically
each time you IPL the AS/400. For more information about setting it up, contact
your system administrator or see the appropriate IBM documentation.
1. Log on to the enterprise server as QSECOFR (or as any user who can
access the Configure TCP/IP menu).
2. On Current OneWorld Versions, choose the version of OneWorld for
which you are setting up the TCP/IP protocol.
3. To access the Configure TCP/IP menu, enter CFGTCP.
4. Choose Work With TCP/IP Host Table Entries.
5. On Work With TCP/IP Host Table Entries, find the network (Internet)
address for the enterprise server. A single machine could have more than
one entry for the same network address. Verify that an entry exists for the
enterprise server network address, and that it matches the format that
follows. Search for the enterprise server network address by entering the
enterprise server name only (for example, SYS1). If one does not exist,
you must add one by choosing Add.
In the Host Name field, your enterprise server (machine) name should
appear in the following format:
hostname.domainname
where hostname is the name of your machine and domainname is the
local domain of the machine on the network (for example,
SYS1.MFG.ABC.COM in which SYS1 is the enterprise server name and
MFG.ABC.COM is the domain name). The combined enterprise server
526

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Deployment Server

name and local domain name represent the location of the enterprise
server on the network.
Network Considerations
To avoid problems when applications running on separate machines need to
communicate with other applications running on other machines on the same
network, make sure that each machine name (host name) has a single unique
dot decimal address. For example, SYS1 could have a dot decimal address of,
for instance, 140.252.13.33, but you could not assign any other address to it.
6. To verify that the local domain and enterprise server names represent the
correct location of the AS/400, choose Change Local Domain and Host
Names from the Work With TCP/IP Host Table Entries form.
Verify that the Local Domain Name and Local Host Name fields match the
combined hostname.domainname network address. (Following the
example in this task, the local domain name would be MFG.ABC.COM and
the local host name would be SYS1.)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

527

Installation Guide

528

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

This chapter explains how to manage the enterprise and deployment databases
for OneWorld. System administrators, database administrators, and system
implementation personnel should read this chapter to plan and install the
enterprise or deployment relational database management systems (RDBMS) for
OneWorld.
The database administrator must install the RDBMS before the OneWorld
implementation team arrives.
OneWorld installation guidelines recommend that a qualified database
administrator be present when the databases are installed, loaded, configured,
and maintained for use with OneWorld. The database administrator must
understand how to maintain the OneWorld database. Do not confuse this guide
with an installation manual for the RDBMS.
- Preparing and installing Oracle for Windows NT
- Preparing and installing OneWorld for SQL Server
- Preparing and installing DB2/400 for AS/400

Preparing and Installing Oracle for Windows NT


This task consists of the procedures necessary to prepare and load Oracle for
Windows NT RDBMS with the OneWorld database:
- Verifying code page settings for Oracle database
- Preparing the Oracle database for OneWorld
- Creating the database users and owners for Oracle
- Loading Central Objects for Oracle
Install Oracle according to Oracle's Optimal Flexible Architecture (OFA) rules.
You should also have a strong working knowledge of Windows NT.
Run the scripts that J.D. Edwards provides for Oracle using an acceptable SQL
environment (such as SQL Plus). Log on as a user with database administrator
privileges. For example, the SQL Plus command syntax is SQLPLUS>
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

529

Installation Guide

e:\path\script where e:\path describes the Windows NT path tree with the
location of the script, and script is the name of the script to be run.
The following procedures outline the minimum requirements of an Oracle
environment on Windows NT for OneWorld. After completing these procedures,
the database might still require significant modification, such as tuning the
system, creating backup or recovery procedures and jobs, and maintaining or
expanding the Oracle database system. When installing an alternate language,
first verify that the code page settings are accurate.

Verifying Code Page Settings for Oracle Database


If installing a non-English language, the correct code page parameters must be
set in the Oracle database and on the Windows or UNIX operating systems. In
this section you will verify and set the NLS_CHARACTERSET parameter in Oracle
and set the NLS_LANG parameter in your operating system to be used in
conjunction by the Oracle database.
Verifying the NLS_CHARACTERSET parameter in Oracle
You will need to determine the appropriate NLS_CHARACTERSET value for the
language being installed on the Oracle database and set the NLS_LANG value
accordingly for both the Oracle client and Oracle database server.
You must set the NSL_Characterset parameter for the appropriate language
before loading your Central Objects specification objects for OneWorld.
To verify code page settings of the Oracle Database

Labor Hours

0.25

Computer Hours

0.25

Personnel
Logon status

Database administrator
Logged on as the jdedba user

Prerequisites
Concurrent Tasks

None

You can verify the code page setting of the Oracle database by executing the
following SQL command from SQL Plus:
select parameter, value from v$nls_parameters where
parameter = NLS_CHARACTERSET
Set the NLS_CHARACTERSET value in accordance with the correct code page to
be used in the language environment. If the character set is incorrect,

530

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

reconfigure the master database. This parameter is fixed by instance and decided
by database creation.
Set up of NLS_LANG parameter for Oracle
In order for OneWorld environments with languages to function properly, the
NLS_LANG parameter also must be set correctly for Oracle. These settings must
be set for your Oracle client workstations and Oracle database server.
To set up the NLS_LANG parameter for Oracle

Labor Hours

0.25

Computer Hours

0.25

Personnel
Logon status

Installer
From Windows on the Control Panel, logged on as system
administrator.

Prerequisites
Concurrent Tasks

None

The NLS_LANG parameter can be added or edited by accessing the 'System' from
the Control Panel. You may need to add the NLS_LANG variable, if it does not
exist. For Windows NT, the setting may be found under the 'Environments' tab.
For Windows 2000 and XP, it may be located under the 'Advanced' tab and then
selecting the 'Environment Variables' button.
The system variable name is NLS_LANG and the variable value (prefixed by a
period) should be equal to the code page value set for the NLS_CHARACTERSET
in the Oracle database. See previous step to review the code page value.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

531

Installation Guide

For example, if your database is using the code page JA16SJIS (Japanese), then
the NLS_LANG variable parameter setting would look like this:

Remember to add a period in front of the NLS_LANG variable value for


the given code page.
See Also


Language Process Overview" in this guide for these values and additional
information found in the National Language Support tables.

Preparing the Oracle Database for OneWorld


The next procedure to prepare the RDBMS for OneWorld is to verify that the
system has the appropriate configuration for data space and data use. For
Oracle, this means setting rollback and tablespace parameters.
This procedure includes the following tasks:


532

Prepare the Oracle database for OneWorld

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

Verify Oracle system tablespaces

Preparing the rollback segments

Creating the tablespaces


To prepare the Oracle database for OneWorld

Labor Hours

0.5

Computer Hours

1.0

Personnel

Database administrator

Logon status

On the Windows NT server, logged on as user JDE

Prerequisites

The database is installed.

Concurrent Tasks

None

7. To reduce the number of variables in the OneWorld installation process,


log on as the Windows NT Administrative user JDE when installing
OneWorld. Either log on as JDE when installing Oracle for Windows NT or
have the database installer verify that JDE has full privileges and rights to
the Oracle objects and services on the Windows NT server.
8. Use TCP/IP. OneWorld communications middleware (JDENET) is based
exclusively on TCP/IP Berkeley Sockets. TCP/IP must be installed on all
OneWorld servers. Adjust the LISTENER.ORA and TNSNAMES.ORA files to
reflect this communications protocol.
9. Verify control files. Verify that the SERVICES and HOSTS files are defined
correctly.
10. Define block size in c:\Orant\Database\INITORCL.ORA. Your default
database should have a block size of 4K to 8K.
11. Enter the following command (Oracle 8.0.6):
alter tablespace TEMPORARY_DATA default storage
(maxextents unlimited);
For Oracle 8.1.5 and above, change TEMPORARY_DATA to TEMP in
above command.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

533

Installation Guide

Verify Oracle system tablespaces

Labor Hours

0.25

Computer Hours

0.25

Personnel

Database administrator

Logon status

Logged on using the Oracle user ID

Prerequisites

Preparing the database environment for OneWorld

Concurrent Tasks

None

Verify the Oracle system tablespaces, and if needed, create new tablespaces to
hold your rollback segments.
1. Verify that the Oracle system tablespaces have at least the following space
configurations and are partitioned appropriately for maximum
performance:
Tablespace name

Minimum size (MB)

SYSTEM

80

ROLLBACK_DATA

500

TEMPORARY_DATA

350 (set MAX Extents to


unlimited)

USER_DATA

15

2. Verify that the maximum open files parameter for DB_FILES allowed in
Oracle is at least 100 (the default is 25). Check in the init.ora file.
When creating tablespaces with different names than those described
above, you might need to modify some scripts described in the
procedures that follow to reference the correct names.
3. Start database.
4. Verify that the Oracle instance starts.
5. Start listener.
6. Verify that the listener program starts.

534

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

To prepare the rollback segments

Labor Hours

0.5

Computer Hours

1.0

Personnel

Database administrator

Logon status

Logged on as database administrator

Prerequisites

Database installed. Tablespaces for rollback segments created.

Concurrent Tasks

None

To prepare rollback segments, J.D. Edwards provides a script for verifying Oracle
has the appropriate rollback segment setup. The script deletes existing rollback
segments, creates larger rollback segments, and alters them online.
1. Using Windows Explorer, locate the rollback script. It is in the directory
path \JDEdwardsOneworld\B7333\Database, rbs_redo.nt on the
deployment server.
2. Make a copy of the script.
3. Review and edit the script in Notepad or a similar editor. You might need
to change directory paths to match your directory structure, or you might
need to make additional changes based upon your naming conventions.
Customization Considerations
When using a nonJ.D. Edwards naming convention, either modify the
delivered scripts or develop a custom process for your naming conventions.
4. To run the script, from the Start menu in Windows NT, choose Programs,
then Oracle for Windows NT, then SQL Plus.
5. Log on as a user with administrator privileges.
6. At the SQL prompt, enter the following to run your edited script:
SQL>
@e:\JDEdwardsOneworld\B7333\Database\yourscript
where e is the drive where OneWorld is installed and yourscript is the
name of your edited rollback script.
7. Adjust Oracle startup files for rollback and cursors. After the rollback
segments have been created and started, adjust the INITORCL.ORA file in
the directory path C:\Orant\Database to correctly begin the new rollback
segments when Oracle starts. Be sure the file includes the following line:
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

535

Installation Guide

rollback_segments=(rbs1,rbs2,rbs3,rbs4)
8. J.D. Edwards recommends increasing the number of available cursors to at
least 255. Be sure the INITORCL.ORA file includes the following line:
open_cursors=255
9. Adjust the parameter for the number of maximum files open. Increase the
maximum number of DB_FILES allowed in Oracle to 200. The default
value for maximum DB_FILES is set to 32.
10. Restart the database to initialize the new setting for the open cursors
parameter.
11. Create a new rollback segment. Alter this new rollback segment offline.
The initial size should be set at 50M with the next size of 50M. Alter this
rollback segment online and all other rollback segments offline. This
forces Oracle to use the larger rollback segment, which is needed during
the table conversion process. Once the table conversions are complete,
alter the larger rollback segment that was just created offline, and alter the
other rollback segments online.
To create the tablespaces

Labor Hours

0.25

Computer Hours

0.25

Personnel

Database administrator

Logon status

Logged on using the Oracle user ID

Prerequisites

OneWorld setup must be complete. Rollback segments must be


created.

Concurrent Tasks

None

To create the tablespaces, J.D. Edwards provides scripts for creating two
tablespaces for each Oracle owner. One tablespace stores table data and the
other stores indexes. These tablespaces match those defined in the OneWorld
installation procedure.
1. Using Windows Explorer, locate the tablespaces script on the deployment
server in the directory \JDEdwardsOneworld\B7333\Database\crtabsp.nt.
Your system administrator may need to create the appropriate file systems
so your script matches that directory structure.
2. Make a copy of the script.

536

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

3. Using an editor such as Notepad, edit the script, crtabsp.nt, prior to


running it. For the AS/400, you can edit out all but the tablespaces for
Central Objects. Those files are of the form type7333x.dat, where type is
PD, PY, DV or JD, and x is either t or i, for example, PD7333t.dat and
PD7333i.dat. Properly editing the script before running it can save up to
two gigabytes of space on your AS/400 server.
4. Once you have finished editing the script, save and close it.
5. To run the script, from the Start menu in Windows NT, choose Programs,
then Oracle for Windows NT, then SQL Plus.
6. Log on as a user with administrator privileges.
7. At the SQL prompt, enter the following to run the edited script:
SQL>
@e:\JDEdwardsOneworld\B7333\Database\yourscript
where e is the drive where OneWorld is installed and yourscript is the
name of your edited script.

Creating the Database Users and Owners for Oracle


To prepare the relational database management system for OneWorld, verify that
the system has the appropriate database users and owners, because several data
sets are loaded automatically by the installation procedure, these database users
and owners must be created and assigned the appropriate privileges.
Customization Considerations
When using a different naming convention, either modify the delivered scripts
or develop a custom process for your naming conventions.
Complete the following tasks:


Create the database users for Oracle

Create the database owners for Oracle


To create the database users for Oracle

1. Create a DBA user.


J.D. Edwards provides a script for creating the necessary JDEDBA user
with appropriate privileges. Go to the directory
\JDEdwardsOneworld\B7333\Database\crdbausr.nt on the deployment
server and open the script.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

537

Installation Guide

2. Review and edit the script for your environment.


3. Save and close the script.
4. In SQL Plus, log on as a user with administrator privileges.
5. At the SQL prompt, enter the following to run the script:
SQL>
@e:\JDEdwardsOneWorld\B7333\Database\crdbausr.nt
where e is the drive where OneWorld is installed.
To create the database owners for Oracle
1. J.D. Edwards provides a script for creating the remaining roles and users
required for the install of OneWorld. Go to the directory
\JDEdwardsOneworld\B7333\Database\crusrs.nt on the deployment
server, and open the script.
2. Review and edit the script for your environment.
3. Save and close the script.
4. In SQL Plus, log on as a user with administrator privileges.
5. At the SQL prompt enter the following to run the script:
SQL>
@e:\JDEdwardsOneworld\B7333\Database\crusrs.nt

Loading Central Objects for Oracle


In configuring the database for OneWorld the final step is loading the Central
Objects. In the first step, modify the batch files with the appropriate user IDs,
passwords, and other variables. In the second step, run the batch files to load
the tables.

538

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

To load Central Objects for Oracle

Labor Hours
Computer Hours
Personnel

Less than 0.5


4.0 - 11.0 depending upon number of path codes
Database administrator

Logon status

Logged on as user JDE with the database password for user


JDE

Prerequisites

Prepare database environment for Windows NT.

Concurrent Tasks

While the loadall.bat script runs, you can proceed with the
Installation Planner. However, do not run Installation
Workbench until the script finishes.

1. Edit the jdeset.bat file with the appropriate user IDs, passwords, and other
variables.
The installation process copies the necessary batch files to the deployment
server under the directory path
\JDEdwardsOneworld\B7333\Database\Exports\Oracle\NT.
Using Windows Notepad or another text editor, access the file jdeset.bat in
this subdirectory. Verify the variables in this batch file are correct.
Specifically, modify the following variables to match your environment:
E. Check for all user passwords (identified by _PSSWD), and change if
necessary.
F. Check for and replace all database connect strings (search for the
word connectstring).
G. Check for and replace the enterprise server name (identified by
machinename) where your Central Objects are located.
H. Review and edit the following environment variables in the jdeset
files:


JDE_DTA
This is the path where the Oracle import files reside when
following the J.D. Edwards standards for naming logical volumes
and directory structures.

JDE_LOG
This is the path where logs are recorded.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

539

Installation Guide

JDE_ERR
This is the path where error information is recorded.

I. Review the Oracle_version at the end of the file. Uncomment


correct version (80 = 8.0.6, 81 = 8.1.5 or higher).
The loadall.bat script is set up to load production, pristine, and prototype
(CRP) sets of specification tables. When loading a development set of
specifications, or when not loading other specifications, edit loadall.bat
appropriately. For example, to load specifications for development, add
the following line to loadall.bat:
Call loaddv
Language Tips and Techniques
Doublebyte consideration: To perform loadall for doublebyte databases (for example,
Chinese and Japanese) temporarily set the NLS_LANG setting. On the machine where
you will be running loadall, edit the following registry section for Oracle (Local
Machine/Software/Oracle). Set the NLS_LANG parameter to:
NLS_LANG=AMERICAN_AMERICA.US7ASCII
After loadall finishes, reset this parameter to the appropriate code page value for your
database.

2. Run the batch file to load the data. From Windows Explorer, doubleclick
the \Database\Exports\Oracle\NT\loadall.bat file.
3. To verify that the central object (specification) tables loaded successfully,
review the *.log files located in the same directory as loadall.bat.
Language Considerations
When using a doublebyte language with an Oracle database, the following error
message may be displayed for each record. Ignore this message and complete the
loadall process.
IMP00019: row rejected due to ORACLE error 1401
IMP00003: ORACLE error 1401 encountered
ORA01401: inserted value too large for column

While the loadall.bat script runs, you can proceed with the Installation
Planner. However, do not run Installation Workbench until the script
finishes.

Preparing and Installing OneWorld for SQL Server


The following procedures outline the minimum requirements of an SQL Server
environment to run OneWorld. After completing these procedures, the database
might still require significant modifications, such as tuning the system, creating

540

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

backup or recovery procedures and jobs, and maintaining or expanding the


database system.
This section explains what has changed for OneWorld Xe and how to create the
databases and their users. The procedures are as follows:
- Verifying code page settings for SQL Server
- Creating databases for SQL Server 7.0
- Creating database logins and users for SQL Server 7.0
- Loading Central Objects for SQL Server 7.0

Verifying Code Page Settings for SQL Server


To verify code page settings for SQL Server

Labor Hours

0.25

Computer Hours

0.25

Personnel
Logon status

Database administrator
Logged on to OneWorld as the jdedba user

Prerequisites
Concurrent Tasks

None

When installing an alternate language, the correct code page settings must be in
your database. When installing the database, set up the code page for the
language before loading your language specification objects for OneWorld.
Review the LocalCodeSet and code page settings for your database machine
environment.
From a ISQL window, enter the following command:
sp_helpsort
If the character set is incorrect, recreate the database with the correct character
set.
See Also


Language Process Overview" in this guide for these values and additional
information found in the National Language Support tables

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

541

Installation Guide

Creating Databases for SQL Server 7.0


To facilitate the creation of databases for OneWorld, a database creation script
has been provided. To use it, complete the following tasks:


Edit the database creation script

Run the database creation script


To edit the database creation script

Labor Hours

0.25

Computer Hours

0.25

Personnel

Database administrator

Logon status

On the deployment server, in SQL Server Query Analyzer

Prerequisites

Verify SQL Server 7.0 is installed.

Concurrent Tasks

None

1. Verify that the TCP/IP connection is functioning properly for the database.
OneWorld utilizes this connection.
2. Locate the database creation script DB_SQLSRVR70.sql in the
\JDEdwardsOneworld\b7333\database folder.
3. Make a backup copy of this script as insurance against error situations.
4. Open the script.
5. Go through the script and edit the paths to have the correct drive letter
(the default is z:) on the enterprise server and verify that the rest of the
directory path is correct.
6. Verify that the specified directory exists. The directory must be created
prior to running the script.
7. Delete the following sections of the script. These sections are not needed
for AS/400; only Central Object databases are used. (The same script is
used for both platforms.)
JDE7333
JDE_CRP
JDE_PRISTINE

542

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

JDE_PRODUCTION
JDE_DEVELOPMENT

8. Delete sections of the script that are not required. The script is clearly
marked with comments to make it easier to delete the unneeded
commands completely. To decide which sections to delete, see the chart
below:
Database Name

Environments that require this database

JDE_PY7333

Prototype (CRP), Test

JDE_JD7333

Pristine

JDE_PD7333

Production

JDE_DV7333

Development

For example, if you have the development, pristine, and production


environments, you will delete the section of the script for JDE_PY7333,
leaving the sections needed for development, pristine and production.
Because the same script is provided for AS/400 and Windows NT
platforms, delete the following sections that are used on the Windows NT
enterprise server only: JDE7333, JDE_CRP, JDE_PRISTINE,
JDE_PRODUCTION, and JDE_DEVELOPMENT.
To run the database creation script

Labor Hours
Computer Hours
Personnel

.5
2.0
Database administrator

Logon status

On the deployment server, in SQL Server Enterprise Manager

Prerequisites

Edit the database creation script.

Concurrent Tasks

None

After editing the database creation script for the environments being used, run it.
1. From the Windows Start button, choose Programs, then SQL Server, then
Query Analyzer.
2. In Query Analyzer or ISQL_w, connect as database administrator with the
correct password.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

543

Installation Guide

3. Click the Open Folder button.


4. Doubleclick your edited script to open it. Use browse to find it, if
necessary.
5. On the Query form, click the execute button.
The results scroll on the lower half of the form while the script runs.
6. Verify the results by looking at the final results in the lower half of the
form.

Creating Database Logons and Users for SQL Server 7.0


To facilitate the creation of logins and users for the OneWorld databases, a script
has been provided. To use it, complete the following tasks:


Edit the login and user creation script

Run the login and user creation script


To edit the logon and user creation script

Labor Hours

less than 0.25

Computer Hours

less than 0.25

Personnel

Database administrator

Logon status

On the deployment server, in SQL Server Enterprise Manager

Prerequisites

Verify the results of the database creation script.

Concurrent Tasks

None

1. Locate the appropriate database creation script in the


\JDEdwardsOneworld\b7333\database folder.
2. Make a backup copy of this script as insurance against error situations.
3. Open the USERS_SQLSRVR.sql script.
4. Search for the phrase Default_DB." Replace it with one of the Central
Objects databases, JDE_JD7333, JDE_PY7333, JDE_DV7333, or
JDE_PD7333.
5. Based upon the edit made to the database creation script, delete the
sections that create the logins and users you do not need.

544

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

If this script is not edited to match the database creation script, errors are
produced as the script tries to create users for databases that do not exist.
To run the logon and user creation script

Labor Hours
Computer Hours
Personnel

0.25
.50 hours per environment; varies depending on system.
Database administrator

Logon status

On the deployment server

Prerequisites

Editing the login and user creation script.

Concurrent Tasks

None

1. From the Windows Start button, choose Programs, then SQL Server, then
Query Analyzer.
2. Connect as a database administrator with the correct password.
3. Open your edited login and user creation script.
4. Execute the script.
5. Verify your results by looking at the lower half of the form.

Loading Central Objects for SQL Server 7.0


The final step to prepare the relational database management system for
OneWorld is loading the data. J.D. Edwards provides modifiable scripts for
importing data from archives to the appropriate databases.
To load Central Objects for SQL Server 7.0

Labor Hours
Computer Hours
Personnel

0.25
5.0
Database administrator

Logon status

On the deployment server, in Windows NT as user JDE

Prerequisites

Verify the results of the logon and user creation script.

Concurrent Tasks

OneWorld Xe UPDATE (8 February 2002)

While the loadall.bat script runs, you can proceed with the
Installation Planner. However, do not run Installation
Workbench until the script finishes.
Installation for AS/400 Systems

545

Installation Guide

1. Edit the batch variables in the jdeset.bat file.


The installation process copies the necessary batch files to the deployment
server in the directory path
\JDEdwardsOneworld\B7333\Database\Exports\Sqlsrvr\NT. From
Notepad or another text editor, access the file jdeset in this subdirectory.
Verify that the variables in this batch file are correct. Specifically, change
the following variables so they match your environment:
A. Check for all user passwords (identified by _PSSWD).
B. Check for all database names.
C. Replace machinename with the name of the server where your
Central Objects are located.
D. Also, review and edit the following environment variables in the
jdeset file:


JDE_DTA
This is the path where the SQL Server import files (.dta) reside
when following J.D. Edwards standards for naming logical
volumes and directory structures. By default, this is the previous
directory (..).

JDE_LOG
This is the path where logs are recorded.

JDE_ERR
This is the path where error information is recorded.

The loadall.bat script is set up to load production, pristine, and prototype


(CRP) sets of specification tables. If you do not want to load certain
specifications, edit loadall.bat appropriately. In the script, the development
specifications are commented out and will not load. You can also edit the
script to load all specifications (pristine, prototype) or only those you need
for the path codes you are installing now.
2. To load the data, from Windows Explorer, doubleclick the
\Database\Exports\Sqlsrvr\NT\loadall.bat script.
3. To verify that the Central Objects (specification) tables loaded successfully,
review the *.log files located in the same directory as loadall.bat.
While the loadall.bat script runs, you can proceed with the Installation
Planner. Do not run Installation Workbench until the script finishes.

546

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the OneWorld Databases

Preparing and Installing DB2/400


This task, which is needed for an installation only, consists of:


Loading Central Objects in DB2/400

Loading Central Objects in DB2/400


To load Central Objects in DB2/400

Labor Hours
Computer Hours
Personnel

0.5
.5
Database administrator

Logon status

On the enterprise server, as QSECOFR

Prerequisites

Confirm available disk space of 2 GB per path code.

Concurrent Tasks

None

1. Log on to the AS/400 as QSECOFR.


2. Verify the available disk space. You need 2 GB of disk space per path
code for Central Objects.
3. Insert the OneWorld Central Objects CD into the AS/400 CD drive.
4. Enter the following commands:
ADDLIBLE JDEOW
GO JDEOW/A98OWMNU
5. Choose option 3, Install Central Objects.
6. Enter the Central Objects library such as COPY7333, COJD7333,
COPD7333, CODV7333.
7. When prompted by the system, insert Central Objects CD #2.
8. Follow the prompts and insert the Central Object CDs as requested.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

547

Installation Guide

548

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Planning the Installation


This section consists of the following chapters:
- Overview of Installation Planner
- Creating a typical installation plan
- Creating a custom installation plan
Do not create a typical plan if your system is coexistent with World Software.
You must create a custom plan for coexistent environments.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

61

Installation Guide

62

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Overview of Installation Planner

Installation Planner is a OneWorld application that runs on the deployment


server. It is a system administration tool that guides you through the process of
configuring the machines on which your company will run OneWorld.
Installation Planner guides you through setting up:


Plan description

Language information

Location information

Deployment server information

Enterprise server information

Data server information

Windows terminal server information

OneWorld Java server information

Shared data sources

Environments

Environment data sources

Data load options

Advanced parameters

For AS/400 coexistent environments, you must plan your control table merges
during Installation Planner.

Language Information
The Installation Planner allows you to create a plan for installing an alternate
language or multiple languages as you create your master plan.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

63

Installation Guide

There are two options:




Follow the system prompts to select which languages will be installed for
each environment installed.

Complete your master plan and install languages later by creating a


languageonly plan. See Creating a LanguageOnly Installation Plan" for
more information about setting up an alternate language after the master
plan.

Location Information
Locations are userdefined groups of machines, databases, and environments.
Using multiple locations is recommended for configurations across a wide area
network (WAN).
There are two types of locations: base locations and remote locations. For each
installation plan, there is only one base location. It is the central point for
planning and executing the deployment process. The base location does not
have a parent location and does not use a location code. You can have any
number of tiered locations, each of which has a parent location and a location
code.
To set up locations for the installation plans, you must provide the OneWorld
installation program with the location, location description, location code (if
there is a secondary location), and parent location (if there is a secondary
location).
The location code is a threecharacter alphanumeric code you specify. This
location code is used as part of the name of the data sources for secondary
locations in the plan. Locations are stored in the Deployment Locations
Definition table (F9654).
See Also


Creating a Remote Installation Plan" for information about setting up


remote locations.

Deployment Server Information


To set up the plan information for the deployment server, you must provide the
OneWorld installation program with the machine name and the directory share
name. This information populates the Release Master (F00945) and Path Code
(F00942) tables, and stores additional deployment server information in the
F9650 and F9651 tables.

64

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Overview of Installation Planner

Enterprise Server Information


To set up the plan for the enterprise server, you must provide Installation
Planner with the name of the enterprise server, its platform type, and the
database that is used. Then, Installation Planner populates the enterprise server
tables (F9650 and F9651) and defines the data sources for the enterprise server.
The Data Source information is stored in the Data Source Master table (F98611).
You also set up the following data source once for each enterprise server:


Server Map
The data source for the replicated system tables for distributed processing
on your enterprise server (for example, machinename B7333 Server
Map). It is specific to each enterprise server, so you must create one for
each enterprise server.

Data Source Information


When you run Installation Planner, the following data sources are set up once
and shared across all environments:


System
The data source for the System tables. It is identified by the OneWorld
release (for example, System B7333).
The System B7333 data source contains some of the same tables that are
used in WorldSoftware, such as the user and environments tables (F0092,
F00921, F0093 and F0094). In addition, the System B7333 data source
contains other tables, such as host configuration and other control tables,
which do not exist in WorldSoftware. Although it is possible to share the
user and environments tables between OneWorld and WorldSoftware, J.D.
Edwards recommends that you maintain separate sets of tables. Note that
the instructions in Running Installation Planner" suggest that you use a
library name of SYS7333 instead of your existing WorldSoftware security
library name.

Object Librarian
The data source for the Object Librarian tables. It is identified by the
OneWorld release (for example, Object Librarian B7333).

Data Dictionary
The data source for the OneWorld data dictionary tables. It is identified by
the OneWorld release (for example, Data Dictionary B7333).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

65

Installation Guide

You also set up the following data sources for each environment:


Control Tables
The data source for the control tables. You can have multiples (for
example, Control Tables Prod, Control Tables Test, and Control Tables
CRP).
For AS/400 coexistent environments, you can use user defined code
(UDC) tables from your existing WorldSoftware libraries. Typically, these
files are located in the AS/400 Common library. When you define your
installation plan, configure the AS/400 COMMON data source to reflect
your AS/400 Common library name. When your plan is created, the
appropriate OCM mappings will be changed to point to your
WorldSoftware files.
The menu tables in the Control Tables data source have the same file
names as in WorldSoftware, but different formats.
The Control Tables data sources for the prototype (CRP), test, and
production environments normally contain the following files:

Table Name

Description

F0002

Next numbers

F00021

Next numbers by company fiscal

F0004, F0004D, F0005, F0005D

User defined codes and language user defined codes

F0082, F00821, F0083, F0084

OneWorld menu files

Central Objects
The data source for the central objects specification tables is identified by
the type and version number of OneWorld. You can have multiple sets of
central objects specifications (for example, Central Objects PD7333,
Central Objects JD7333, Central Objects DV7333, and Central Objects
PY7333). However, you can have only one Central Objects data source for
each path code.

Business Data
The data source for the business data tables. You can have multiple sets of
Business Data data sources (for example, Business Data CRP, Business
Data PROD, Business Data TEST, and Business Data JDE).
Depending on the environment you create, the Business Data data source
can be your test, production, or any other data library that resides on your
AS/400. When prompted for the Business Data data source during

66

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Overview of Installation Planner

Installation Planner, modify this data source to call the library on the
AS/400 for this environment. You can also create a new Business Data
library on your AS/400. This new Business Data data source may or may
not have data, depending on the type of OneWorld environment you
create. If you build additional environments on your AS/400 to use with
OneWorld, you will create one or more of the following libraries before
running Installation Workbench:

PRISTDTA

CRPDTA

TESTDTA

PRODDTA

Versions
The data source for the Versions List table (F983051). You can have
multiple sets of versions tables (for example, Versions PD7333, Versions
JD7333, Versions DV7333, and Versions PY7333). However, you can
have only one Versions data source for each path code.

AS/400 COMMON
For AS/400 coexistent environments, this data source (for example, AS/400
COMMON Production) is used rather than the Control Tables data source
(for example, Control Tables Production) to access the existing
WorldSoftware next numbers tables (F0002 and F00021).

DNT data sources


Installation Planner automatically creates additional DNT (Do Not
Translate) data sources when you create the plan. They access the same
libraries as their associated nonDNT data sources. However, when you set
up the matching ODBC data sources, you will configure them to not
translate CCSID 65535. The DNT data sources access tables on the AS/400
contain BLOBs (binary large objects). The following standard DNT data
sources are created automatically during Installation Planner.
-

System B7333 DNT

Business Data type DNT


where type is PROD, CRP, TEST, or JDE

Versions pathcode DNT


where pathcode is PD7333, PY7333, JD7333, or DV7333

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

67

Installation Guide

The ODBC data sources that correspond to the DNT data sources listed
above, as well as the machinename B7333 Server Map data source, must
be defined as DNT.
See Also


68

Major OneWorld Technical Tables" in the Installation Reference Guide for


more information on individual tables and their uses.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

This chapter contains processes for creating a typical installation plan.


- Understanding the typical installation process
- Starting Installation Planner
- Entering a plan description
- Entering location information
- Entering deployment server information
- Entering enterprise server information
- Define a data server
- Adding a remote location
- Finalizing the installation plan

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

69

Installation Guide

The following flow chart shows the high level process to create the installation
plan.

610

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

Understanding the Typical Installation Process


Do not create a typical plan if your system is coexistent with World
Software. You must create a custom plan for coexistent environments.
After installing the deployment server, you must define and run the installation
plan. Complete the steps in this section or the next section Creating a Custom
Installation Plan." Do not complete both sections.
Note: for DB2 UDB, you must download the latest Planner Update and follow
the update instructions before doing the installation plan.
The typical plan installs all environments. If you do not want all environments,
you must use the custom plan.
To remove pieces of an existing installation plan, see Installation Planner
Utilities: Deleting Pieces of an Installation Plan."
The forms appearing in this chapter assume you have SQL Server as the
database for your central objects. If you use Oracle, or choose to load central
objects on to the AS/400, the information on your forms will differ from what is
shown here.

Assumptions about Defining a Typical Installation Plan


The following table outlines assumptions for the Installation Planner phase as a
whole. Individual tasks might have their own assumptions.
Labor Hours

0.5

Computer Hours

0.5

Personnel
Logon status

Installer
On the deployment server, log on to OneWorld as user JDE
with the database password for user JDE, in the planner
environment.

Prerequisites
Concurrent Tasks

You can run the loadall script in the previous chapter to build
the database.

Starting Installation Planner


Begin your installation plan by logging onto OneWorld and starting Installation
Planner.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

611

Installation Guide

To start Installation Planner


1. Log on to OneWorld as user JDE with the database password for user JDE.
2. Access the planner environment (JDEPLAN).
3. If you are installing an alternate language, verify the processing options
for this typical installation by going to the processing options, Default
Mode tab, and making sure the value in the Default Language field is 2.
4. Go to the System Installation Tools Menu (GH961).
5. From the System Installation Tools menu, doubleclick Typical Installation
Plan.

6. On Work with Installation Plans, click Add.

Entering a Plan Description


After starting Installation Planner, enter a description of the plan, such as the
plan name and description, installation type, and included languages (if any).
To enter a plan description
The Installation Planner form appears.

612

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

As you open new screens in Installation Planner, OneWorld may


truncate the height of some of the field areas. To correct this
problem, minimize and then maximize the screen dimensions.

1. On Installation Planner, complete the following fields:




Name
The name of your installation plan.

Description
The description of your installation plan.

Status
Choose 10 (the default value) as the status of your installation plan.

Install Type
Click Install (the default value).

Coexistent with WorldSoftware


Verify the option is not checked.
If OneWorld is operating in a coexistent environment, you must exit
this plan and instead create a custom plan.

To Release
Verify the release number is B7333 (default value).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

613

Installation Guide

2. Tab out of the To Release field to view Include Language options. If you
are installing an alternate language, such as Spanish, under Include
Languages, click Yes.
If you prefer, after you have completed your master plan you can
install an alternate language later by creating a languageonly option
on this form. For more information, see Creating a LanguageOnly
Installation Plan."
3. Click OK.
OneWorld displays the Plan Generation window.
4. Click OK to continue.

Entering Location Information


Once basic plan installation information is entered, enter a plan location.
To enter location information
The Location Revisions form appears.

1. On Location Revisions, enter the following information:




614

Location

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

Enter the place to which this plan applies. The location could be a
city, company headquarters, or a division of the company.


Description
Enter a description for this location.

Location Code
If this is the base location, this field will be greyed out.

Parent Location
For the base location, this field will be greyed out.

2. Click OK.

Entering Deployment Server Information


Once a plan location is specified, complete the information for the primary
deployment server you will use in this plan.
To enter deployment server information
The Deployment Server Revisions form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

615

Installation Guide

1. In the top section of the Deployment Server Revisions form, complete or


verify the following fields:


Machine Usage
The default value of 15 indicates this is a deployment server.

Machine Name
The name of the deployment server appears in this field by default.

Description
Enter a long description for the machine. This includes the location
this deployment server is associated with, and whether or not it is
the primary server.

Release
Enter the OneWorld release number you are installing, or use the
visual assist button to choose one from the list. B7333 is the default.

Host Type
The default value of 50 indicates the server type as Intel NT.

Location
This field defaults to your current location.

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is listed in the JDE.INI file.

2. On the Deployment tab, complete the following fields:




Primary Deployment Server


Indicates the hierarchy of the servers. Valid values are:

616

Value

Description

Primary deployment server (default value)

Secondary deployment server

Server Share Path

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

The server share name of the directory to which you installed


OneWorld on your deployment server. Verify that the server share
name for OneWorld Xe is \b7333.
3. Click OK.
Troubleshooting
If you enter invalid information into a tab field, a red stop sign symbol
appears next to the tab name, such as deployment server. For more
information about the error, click on the red stop sign icon in the bottom
righthand corner of the form.
OneWorld asks if you want to add another deployment server.


To add another deployment server, click Yes.


Repeat Verifying Deployment Server Information."

To continue with Installation Planner setup, click No.

Entering Enterprise Server Information


After specifying deployment server information, complete the information for the
enterprise server you will use in this plan.
To enter enterprise server information
The Enterprise Server Revisions form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

617

Installation Guide

1. In the top section of the Enterprise Server Revisions form, verify or


complete the following fields:


Machine Name
The name of your primary enterprise server.
Because of naming restrictions on the AS/400, this name cannot
exceed ten characters.

Description
Enter a description for the machine.

Release
Enter the OneWorld release number to which this plan applies, or
use the visual assist button to choose one from the list. For
example, B7333, which is the default value.

Host Type
Click the visual assist button and choose the type of enterprise
server you are adding to the plan.
In this case, AS/400.

Location
The location chosen for this plan appears in this field by default.

618

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is listed in the JDE.INI file.

2. On the Enterprise tab, complete or verify the following fields:




Port Number
The port number value (6009) for this enterprise server appears by
default, from the JDE.INI file.
If you change the port number to a value other than 6009, you must
also change this setting in both the enterprise and client jde.ini files.

Logical Machine Name


Information defaults into this field when the host type is entered.

Database Type
Select "I"

Server Map Data Source


When host type is entered, machinename B7333 Server Map
appears in this field by default, where machinename is the name of
your machine.

Installation Path
Verify the default value is the installation directory path to which
you want to install OneWorld on your enterprise server. Make sure
the value is specific to your version of the release.
Example: For the OneWorld Xe release, the path ends with
B7333SYS the system library.

Deployment Server Name


Using the visual assist button, choose the name of the deployment
server to which this enterprise server is attached. A deployment
server name appears in this field by default, but can be changed if
necessary.

3. Click OK. If you are not using the DB2 UDB database, OneWorld asks if
you want to add another enterprise server. Proceed with Step 4, below.
4. Select one of the following options:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

619

Installation Guide

To add another enterprise server, click Yes. Repeat processes,


starting with Entering Enterprise Server Information."

To continue with Installation Planner, click No. Skip to Adding a


Remote Location," below.

Adding a Remote Location


Upon concluding server setup, you can choose to enter a remote location or to
finalize your installation plan.
To add a remote location
OneWorld asks if you want to add another (remote) location.


To add a remote location, click Yes.


Repeat all processes for adding a location, starting with Entering Plan
Location Information." Refer to Creating a Remote Installation Plan" in the
Installation Planner Utilities section for information about adding remote
locations to your plan.

To conclude the Installation Plan setup, click No.


Continue with Finalizing the Installation Plan."

Finalizing the Installation Plan


Installation Planner automatically finalizes your installation plan. This section
consists of the following tasks.:


Finalizing the plan

Concluding Validation Planner Report


To finalize the installation plan

1. A message appears indicating the installation plan has finalized.


When the plan is finalized:

620

The status is set to 20. This signals that several adjustments to OCM
mappings and tables are made according to your plan.

The following tables are upgraded:

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Typical Installation Plan

Release Master table (F00945)


Path Code Master table (F00942)
Package Plan table (F98404)
Machine Detail table (F9651)
Language table (F984031) - if you are installing a language
2. To exit the concluding message box, and initiate the Planner Validation
Report, click OK.


If processing option default was selected, Planner Validation Report


automatically prompts you to run this report.

If processing option default was not selected, on the tree view of


your plan, click Validate to initiate the Planner Validation Report.

To conclude Validation Planner Report


1. On Report Output Destination, choose On Screen or To Printer, and click
OK.
2. Review the report to confirm all records were validated.
3. After reviewing the report, on the Batch Versions form, click Close.
For more information about the Planner Validation Report, see Reports" in
the Installation Reference Guide.
4. On Work With Installation Plans, click Expand to review the plan you
created.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

621

Installation Guide

622

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

This chapter includes the following processes for creating a custom installation
plan.
- Understanding a Custom Installation Plan
- Starting Installation Planner
- Entering a plan description
- Entering location information
- Entering deployment server information
- Entering enterprise server information
- Defining machine/server types
- Entering shared data source information
- Setting up environments
- Setting up environment data sources
- Adding a remote location
- Finalizing the installation plan
- Defining AS/400 common OneWorld data sources

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

623

Installation Guide

The following flow chart shows the high level process to create the upgrade
plan.

624

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

Understanding a Custom Installation Plan


After installing the deployment server, you must define and run the installation
plan. Complete the steps in this chapter or the preceding chapter Creating a
Typical Installation Plan." Do not do both.
Within a custom installation plan, the information you provide on the Installation
Planner forms, such as database type and enterprise server type, determines the
information displayed on the remaining forms. The Installation Planner
processing options also determine which choices are given while setting up your
plan. For a complete description of the processing options, see Reviewing
Installation Planner Processing Options."
If you create a custom plan with a coexistent environment, note the following:


Do not add a second enterprise server that is not an AS/400. If you do so,
the plan will create AS/400 data sources on the second enterprise server.
Instead, create a separate plan to add non-AS/400 enterprise servers.

With the exception of pristine, do not add environments to your plan that
are not coexistent with World. Instead, create a separate plan for these
environments. The pristine environment is an exception since this
environment is never upgraded.

To remove pieces of an existing installation plan, see Installation Planner


Utilities: Deleting Pieces of an Installation Plan."
Data Source Considerations
J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.
The forms appearing in this chapter assume you have SQL Server as the
database for your central objects. If you use Oracle, or if you choose to load
central objects onto the AS/400, the information on your forms will differ from
what is shown here.

Assumptions about Defining a Custom Installation Plan


The following table outlines assumptions for the Installation Planner phase as a
whole. Individual tasks might have their own assumptions.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

625

Installation Guide

Labor Hours

Computer Hours

Personnel

Installer

Logon status

On the deployment server, logged on to OneWorld as user JDE


with the database password for user JDE, in the planner
environment.

Prerequisites

Verify the deployment server is installed.

Concurrent Tasks

The loadall script for building the database can be running.

Starting Installation Planner


Begin your installation plan by logging on to OneWorld and starting Installation
Planner.
To start Installation Planner
1. Log onto OneWorld as user JDE with the database password for user JDE.
2. Choose the planner environment (JDEPLAN).
3. Go to the System Installation Tools Menu (GH961).
4. If you are installing an alternate language, verify the processing options
for this custom installation by opening the processing options, Default
Mode tab, and ensuring the value in the Default Language field is 1.
5. From the System Installation Tools menu, doubleclick Custom Installation
Plan.

626

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

6. On Work with Installation Plans, click Add.

Entering Plan Description


After starting Installation Planner, enter basic plan information, such as plan
name and description, installation type, and included languages (if any).
To enter information into Installation Planner
The Installation Planner form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

627

Installation Guide

1. On Installation Planner, complete the following fields:




Name
The name of your plan.

Description
The description of your plan.

Status
Choose 10 (the default value) as the status of your plan.

Install Type
Click Install (default).

Coexistent with WorldSoftware


Uncheck this option if OneWorld is not operating in a coexistent
environment.

To Release
Verify the release number is B7333 (default).
For an AS/400 coexistent environment, you may need to change the
release number.

628

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

2. Tab out of the To Release field to view Include Language options. If you
are installing an alternate language, such as Spanish, under Include
Languages, click Yes.
If languages have not been installed before, you can install an
alternate language after you have completed your master plan by
choosing the languageonly option on this form. For more
information, see Creating a Languageonly Installation Plan."
3. Click OK.

Entering Location Information


Once basic plan installation information is entered, enter a plan location.
Once a location is defined, it will not be removed even if the plan is deleted. To
remove a location, see Installation Planner Utilities: Deleting Pieces of an
Installation Plan."
To enter plan location information
1. OneWorld asks if you want to enter new location information.
2. Select one of the following options:


To add a new location, click OK.

To select an existing location, click Select and choose a location


from the Location Search form.

The Location Revisions form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

629

Installation Guide

3. On Location Revisions, complete the following fields:




Location
Enter the place to which this plan applies. The location could be a
city, company headquarters, or a division of a company.

Description
Enter a description for the location.

Location Code
For the base location, leave this field blank.

Parent Location
If this is the base location, leave this field blank.

4. Click OK.

630

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

Entering Deployment Server Information


Once a plan location is specified, complete the information for the primary
deployment server you will use in this plan. This task consists of:
To enter deployment server information
1. Click OK to add a deployment server.
The Deployment Server Revisions form appears.

2. In the top section of the Deployment Server Revisions form, complete the
following fields:


Machine Name
The name of your deployment server should be listed as the default
value. The name must not exceed 10 characters.

Description
Enter a description of the machine. This includes the location that
this deployment server is associated with, and whether or not it is
the primary server.

Release
Enter B7333 (default value).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

631

Installation Guide

Location
The location chosen for this plan appears in this field by default.
The field will be greyed out if you are not adding a remote location.

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is located in the JDE.INI file.

3. On the Deployment tab, complete the following fields:




Primary Deployment Server


Indicates the hierarchy of the servers. Valid values are:

Value

Description

Primary deployment server (default)

Secondary deployment server

Server Share Path


The server share path to which you installed OneWorld on your
deployment server should be listed by default. Make sure this path
is specific to your version of the release. Example: For OneWorld
Xe, the path ends with \b7333.

4. Click OK.
Troubleshooting
If you enter invalid information into a tab field, a red stop sign symbol
appears next to the tab name, such as deployment server. For more
information about the error, click on the red stop sign icon in the bottom
righthand corner of the form.
5. OneWorld asks if you want to add another deployment server.


To add an existing deployment server, click Select.


Repeat Entering Deployment Server Information."

632

To continue with Installation Planner setup, click No.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

Entering Enterprise Server Information


To add an enterprise server to your plan, complete the following tasks:


Enter enterprise server information

Enter enterprise server data source information

Entering Enterprise Server Information


After specifying deployment server information, complete the information for the
enterprise server you will use in this plan.
To enter enterprise server information
OneWorld asks if you want to add new enterprise server information or select
existing information.
1. Click OK to add an enterprise server.
The Enterprise Server Revisions form appears.

2. In the top section of the Enterprise Server Revisions form, complete or


verify the following fields:


Machine Name

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

633

Installation Guide

The name of your primary enterprise server. The name must not
exceed 10 characters. The name is casesensitive.


Description
Enter a description for the machine.

Release
Enter B7333 (default)

Host Type
Click the visual assist button and choose the type of enterprise
server you are adding to the plan.
For example, AS/400.

Location
The location chosen for this plan appears in this field by default.

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is listed in the JDE.INI file.

3. On the Enterprise tab, complete or verify the following fields:




Port Number
The port number value (6009) for this enterprise server appears by
default, from the JDE.INI file.
If you change the port number to a value other than 6009, you must
also change this setting in both the enterprise and client jde.ini files.

Logical Machine Name


When the host type is entered appropriate information appears in
this field by default.

Database Type
Select "I"

634

Server Map Data Source

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

When host type is entered, machinename B7333 Server Map


appears in this field by default, where machinename is the name of
your machine.


Installation Path
The installation directory path to which you want to install
OneWorld on your enterprise server. The correct value should be
the default. Make sure this path is specific to OneWorld Xe.
Example: For the AS400, the path ends with B7333SYS the
system library.

Deployment Server Name


Using the visual assist button, choose the name of the deployment
server to which this enterprise server is attached. A deployment
server name defaults into the field, but can be changed if necessary.

4. Click OK. A message box appears and asks you whether you want to
define your data sources or take the default data sources. Proceed to task
To specify custom or default data source information," below.

Entering Enterprise Server Data Source Information


After specifying enterprise server information, enter the data source information
for the enterprise server you will use in this plan.
Complete the following tasks:
- Specify custom or default data source information
- Verify server map source information
- Add another enterprise server
To specify custom or default data source information
OneWorld asks you whether you want to enter custom data sources or take the
default data sources for the enterprise server you just added. Select one of the
following options:


To enter custom data sources, click OK. Skip to To verify custom server
map source information."

If you clicked Take Defaults, continue with To add another enterprise
server."

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

635

Installation Guide

If you are in a coexistent environment, do not take defaults for


AS/400.
To verify custom server map source information
The Data Source Setup form appears.

1. On Data Source Setup, verify your Server Map data source information.
Data Source Considerations
J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.
2. Click OK.
To add another enterprise server
OneWorld asks if you want to add another enterprise server.
Select one of the following options:


To add another enterprise server, click Yes.


Repeat processes, starting with Entering Enterprise Server Information."

636

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

In a coexistent environment, do not add an additional enterprise server


that is not an AS/400. If you do so, the plan will create AS/400 data
sources on the second enterprise server. Instead, create a separate plan to
add nonAS/400 enterprise servers.


To continue with Installation Planner setup, click No.


The Machine/Server Types form appears.

Defining Machine/Server Types


There are three machine/server types you can define for your installation plan:
data server, Java server, and Windows terminal server. To define any or all of
these server types, complete the appropriate processes. If you do not need to
define a machine/server, continue with Entering Shared Data Source Setup
Information."


Specify machine/server types


This task is required to continue Installation Planner setup.

Define a data server (if different from the enterprise server).

Define a Java server

Define a Windows Terminal server.

Specify Machine/Server Types


Begin the machine/server definition process by specifying the type of
machine/server you wish to add to your installation plan.
To specify machine/server types
The Machine/Server Types form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

637

Installation Guide

On Machine/Server Types, specify the machine/server types you want to define.




To add servers, check the desired server options, and then click OK.
Continue with the relevant tasks below.

If you do not want to add any of these servers, leave these options
unchecked, click OK, and then proceed to Entering Shared Data Source
Information."

Define a Data Server (Optional)


To define a data server for your installation plan, perform the following task.
To define a data server
If you checked Data Server on the Machine/Server Types form, OneWorld
prompts you to define your data server.
1. Click OK to continue.
The Data Server Revisions screen appears.

638

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

1. On the top section of the Data Server Revisions form, complete the
following fields:


Machine Usage
The default value of 25 indicates this is a data server.

Machine Name
Enter the name of the server where your central objects reside. If
you are using the AS/400 to store your central objects, enter the
name of this server.

Description
Enter a description of the machine.

Release
Enter the OneWorld release number you are installing. For example,
B7333.

Host Type
Choose the type of data server you are adding to the plan. Valid
values are:
Value

Description

10

AS/400

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

639

Installation Guide

Value

Description

20

HP 9000

25

Sun Solaris

30

RS/6000

40

Compaq AlphaServer

50

Windows NT or Windows 2000 (Intel)

Location
This field defaults to the location chosen for this plan.

Primary User
Identifies the user to send email to once a package has been
deployed. The default for primary user is listed in the JDE.INI file.

2. On the Data tab, complete the following field:




Data Source Type


Choose the type of data source. Valid values are:
Value

Description

Client Access Express

Oracle

SQL Server

3. Click OK.
OneWorld asks if you want to add another data server.
4. Select one of the following options:


To add another data server, click Yes.


Repeat the steps in To define a data server."

To continue with Installation Planner setup, click No.

Define a Java Server (Optional)


To define a JAS server for your installation plan, perform the following task.

640

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

To define a Java server


If you checked JAS Server on the Machine/Server Types form, OneWorld
prompts you to define your JAS server.
1. Click OK to continue.
The JAS Server Revisions form appears.

2. In the top part of the JAS Server Revisions form, complete the following
fields.


Machine Usage
The default value of 30 indicates this is a OneWorld Java Server.

Machine Name
The name of your OneWorld Java Server. The name is case sensitive
and must not exceed 10 characters.

Description
Enter a description of the machine.

Release
Enter the OneWorld release number you are installing. For example,
B7333.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

641

Installation Guide

Host Type
The default value of 50 specifies server type as Intel NT.

Location
The location you chose for this plan defaults into this field.

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is listed in the JDE.INI file.

3. On the JAS tab, complete the following field:




Installation Path
The installation directory path to which you are installing OneWorld
on your OneWorld Java Server. Make sure this is specific to your
version of the release. Example: For OneWorld Xe the path ends
with \b7333.

4. Click OK.
OneWorld asks if you want to add another Java Server.
5. Select one of the following options:


To add another OneWorld Java Server, click Yes.


Repeat the steps in To define a Java server."

To continue with Installation Planner setup, click No.

Define a Windows Terminal Server (Optional)


To define a Windows Terminal server for your installation plan, perform the
following task.
To define a Windows terminal server
If you checked WTS Server on the Machine/Server Types form, OneWorld
prompts you to define your WTS server.
1. Click OK to continue.
The WTS Server Revisions form appears.

642

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

1. In the top part of the WTS Server Revisions form, complete the following
fields.


Machine Usage
The default value of 35 indicates this is a Windows Terminal server.

Machine Name
The name of your Windows Terminal server. The name is case
sensitive and must not exceed 10 characters.

Description
Enter a description of the machine.

Release
Enter the OneWorld release number you are installing. For example,
B7333.

Host Type
The default value of 50 specifies server type as Windows NT on an
Intel platform.

Location
This field defaults to the location chosen for this plan.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

643

Installation Guide

Primary User
Identifies the user to send email to when a package has been
deployed. The default for primary user is listed in the JDE.INI file.

2. On the WTS tab, complete the following field.




Installation Path
The installation directory path to which you are installing OneWorld
on your server. Make sure this is specific to your version of the
release. For example, the path could end with \b7, similar to a
workstation installation path.

3. Click OK.
OneWorld asks if you want to add another Windows Terminal server.
4. Select one of the following options:


To add another Windows Terminal server, click Yes.


Repeat the steps in To define a Windows Terminal server."

To continue with Installation Planner Setup, click No.

Entering Shared Data Source Information


To enter or confirm information for data sources that are shared across all of
your environments, complete the following tasks:
Specify (custom or default) shared data source setup information
Verify the AS/400 Common data source
Verify the OWJRNL data source
Verify the Data Dictionary data source
Verify the Object Librarian data source
Verify the System data source
To specify (custom or default) shared data source setup information
OneWorld prompts you for the data source information for the shared data
sources. Choose one of the following options:

644

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

To use the OneWorld default data sources, click Take Defaults and
continue with Setting Up Environments." This option limits your
customization choices.
If you are in a coexistent environment, do not take defaults.

Click OK to enter the data sources. Verify the following data source
information.
To verify the AS/400 Common data source

If you selected Coexistent in the plan description, the AS/400 Common Data
Source Setup form appears.

On Data Source Setup, verify the accuracy of the AS/400 Common data source,
and then click OK.
To verify the OWJRNL data source
The OWJRNL Data Source Setup form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

645

Installation Guide

On Data Source Setup, verify the accuracy of the OWJRNL data source, and then
click OK.
To verify the Data Dictionary data source
The Data Dictionary Data Source Setup form appears.

On Data Source Setup, verify the accuracy of the Data Dictionary data source,
and then click OK.

646

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

The library name in the Library Name field is the OneWorld data
dictionary library (DD7333). It is not the WorldSoftware library that
contains your data dictionary files.
To verify the Object Librarian data source
The Object Librarian Data Source Setup form appears.

On Data Source Setup, verify the accuracy of the Object Librarian data source,
and then click OK.
To verify the system data source
The System Data Source Setup form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

647

Installation Guide

On Data Source Setup, verify the accuracy of the settings for the System data
source, and then click OK.
For more information about System data source fields, or fields for other
data sources mentioned in this process, see Data Source Charts" in the
Installation Reference Guide.
The Environment Selection screen appears.

Setting Up Environments
By default, OneWorld configures your system using values for typical
environments. Depending on the options you select when you set up your plan,
OneWorld displays one or more of the following parameters which you can
customize in the following tasks:


Environments

Data Load options

Advanced Parameters

Languages

You can customize any of these parameters by unchecking the default option
on the Environment Selection screen. As you run through the plan, OneWorld
will display a customization screen for each parameter that you uncheck.

648

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

1. On Environment Selection, uncheck the boxes for those parameters you


want to customize.
The parameters that display may vary depending on what options you
select at the beginning of the planning process.
2. Click OK.
The following tasks walk you through the steps to customize each of the
parameters listed above. However, OneWorld displays customization
screens only for those parameters which you unchecked the default
options. Skip the tasks below for those parameters that you left checked.
3. Continue with the relevant tasks below:
Select an environment
Specify environment data load parameters
Verify advanced parameters
Select language environments
If you checked the default option for all parameters, skip to "Setting Up
Environment Data Sources."
To select an environment

The Select Environment form appears.


OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

649

Installation Guide

Wxxxxxx environments appear if there is a Windows Terminal server in


the plan.
Jxxxxxx environments appear if there is a OneWorld Java Server in the
plan.
Tips and Techniques
You can only add or delete environments from the tree view of your plan.

On Select Environments, doubleclick the environment you want to define.




To set up multiple environments, choose and define them one at a time.


OneWorld brings you back to this screen after you complete the following
tasks.
To specify environment data load parameters

If you unchecked Default Data Load on the Environment selection screen, the
Data Load Parameters form appears.

650

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

1. From Data Load Parameters, each environment setup must indicate


whether to load the environment with production data, demonstration
data, or no data. Options are explained below:


Do Not Load Data


This option does not create any tables nor load any data for the
environment you are upgrading. This option is not used to upgrade
typical environments.

Load Production Data


This option loads J.D. Edwards configuration and control data.
Created application transaction tables, such as Accounts Payable
tables, remain empty. This is the default option for all environments
except Pristine.

Load Demo Data


This option loads J.D. Edwards demonstration data into the control
and application tables that are created. Use this option if you want
to add sample data (such as mock inventory) to the environment
you are upgrading. This is the default option for the Pristine
environment.
For all environments except pristine, tables that do not currently
exist in your environment are created during the table conversion
workbench.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

651

Installation Guide

For the pristine environment, the version that appears in the Version
field is XJDE0024. For all other environments, XJDE0001 appears in
this field.
2. Click OK.
For an AS/400 coexistent environment, the Advanced Parameters form
appears. Continue with To verify advanced parameters."
If you are installing languages, the Language Selection form appears. Skip
to To select language environments."
For the Pristine environment or for all other environments where you are
not installing languages, OneWorld prompts you for data source
information. Skip to Setting up Environment Data Sources."
To verify advanced parameters
If you unchecked Default Advanced Parameters on the Environment
selection screen, the Advanced Parameters form appears.

1. On Advanced Parameters, verify the following:




Coexistent Environment
For a coexistent environment only, verify this option is checked.
For the pristine environment, verify this option is turned off
(unchecked).

652

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

None
Turn on (check) this option if you do not want to run any control
table merges for this environment.

Coexistent Merges
For an AS/400 coexistent environment, to merge your data
dictionary and user defined code tables turn on (check) this option.

2. Click OK.
If you unchecked Default Languages on the Environment selection screen,
continue with To select language environments."
If you are not installing languages, OneWorld prompts you for data source
information. Skip to Setting up Environment Data Sources."
To select languages
The Language Selection form appears.

1. On Language Selection, to set up a language for the selected environment,


highlight the appropriate languages.
2. From the Row menu, choose Select.
3. Repeat steps 1 and 2 until all your languages are selected.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

653

Installation Guide

4. Click OK.

Setting Up Environment Data Sources


To set up environment data sources, complete the following tasks:
Choose an environment data source setup option
Set up the AS/400 Common data source
Set up the Control Tables data source
Set up the Central Objects data source
Set up the Business Data data source
Verify the Versions data source
Select another environment
To choose an environment data source setup option
OneWorld asks if you want to set up data sources for the environment you just
configured.
1. Select one of the following options.


To manually enter the data sources, click OK, and continue with the
task below.
If the environment you selected is coexistent with World, you must
click OK.

To accept the OneWorld default data sources, click Take Defaults,


and continue with To select another environment." This option
limits your customization choices. Repeat this task for all the
environments you want to add to your plan.

To set up the AS/400 Common data source


The Data Source Setup form for AS/400 Common appears.

654

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

On Data Source Setup, set up and/or verify your AS/400 Common data source,
and then click OK.
For an AS/400 coexistent environment, enter the name of the
WorldSoftware library you want to use in the Data Library Name field.
To set up the Control Tables data source
The Data Source Setup form for the Control Tables appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

655

Installation Guide

1. On Data Source Setup, verify the accuracy of the Control Tables data
source.


Data Source Name


Name of the data source

Server Name
Name of the enterprise server

Data Source Type


Type of database you are using
(Type I for Client Access Express)

AS/400 Database Name


Type the name of the data source (such as Control Tables Test) in
the Database Name field.

Control Tables data sources are specific to the environment and path code.
2. Click OK.
To verify the Versions data source
The Data Source Setup form for Versions appears.

656

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

On Data Source Setup, verify the accuracy of the Versions data source, and then
click OK.
To set up the Central Objects data source
The Data Source Setup form for Central Objects appears.

On Data Source Setup, set up your Central Objects data source, and then click
OK.


If you are putting central objects on the AS/400, verify the data library
name is COpathcode, for example, COPY7333 or CODV7333.
The central objects data source must be set to Do Not Translate, regardless
the server type.
To set up the Business Data data source

The Data Source Setup form for your Business Data appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

657

Installation Guide

On Data Source Setup, verify the data source for your Business Data, and then
click OK.
To select another environment
The Select Environments form appears and the word Selected" appears next to
the environment you just configured.

1. Select one of the options below:

658

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

To select another environment, choose the next environment that


you want to define, and repeat the steps in To set up your
environment" and To set up environment data sources."

To conclude the set up of your environments, click Close, and


continue with Adding a Remote Location."
OneWorld will run the Installation Workbench on all environments
marked Selected."

Tips and Techniques


You can only add or delete environments from the tree view of your plan.

Adding a Remote Location


Upon concluding environment setup, you can choose to either enter a remote
location or to finalize your installation plan.
To add a remote location
OneWorld asks if you want to add another (remote) location.
1. Select one of the following options:


To add a remote location, click Yes.


Repeat all processes for adding a location starting with Entering
Plan Location Information." Refer to Creating a Remote Installation
Plan" in the Installation Planner Utilities section for information
about adding remote locations to your plan.

To conclude the Installation Plan setup, click No.

2. Continue with Finalizing the Installation Plan."

Finalizing the Installation Plan


Installation Planner automatically finalizes your installation plan. This section
consists of the following tasks.:


Finalizing the plan

Concluding Validation Planner Report

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

659

Installation Guide

To finalize the installation plan


1. A message appears to let you know that the installation plan has been
finalized.
When the plan is finalized:


The status is set to 20. This signals that several adjustments to OCM
mappings and tables are made according to your plan.

The following tables are upgraded:


Release Master table (F00945)
Path Code Master table (F00942)
Package Plan table (F98404)
Machine Detail table (F9651)
Table Conversion Scheduler (F98405)
Language table (F984031) - if you are installing an alternate
language

2. To exit the concluding message box and initiate the Planner Validation
Report, click OK.


If processing option default was selected, Planner Validation Report


automatically prompts you to run this report.

If processing option default was not selected, on the tree view of


your plan, click Validate to initiate the Planner Validation Report.

To conclude Validation Planner Report


1. On Report Output Destination, choose On Screen or To Printer, and click
OK.
2. Review the report to confirm all records were validated.
3. After reviewing the report, on the Batch Versions form, click Close.
For more information about the Planner Validation Report, see Reports" in
the Installation Reference Guide.
4. On Work With Installation Plans, click Expand to review the plan you
created.

660

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

Defining AS/400 Common OneWorld Data Sources


For an AS/400 coexistent environment, perform the following tasks:
Define the AS/400 Common OneWorld data sources
Define the Client Access Express ODBC data sources
Through these tasks, you define the data sources that will be used when the
coexistent data dictionary merge runs during Control Table Workbench.
This AS/400 COMMON data source is different than the AS/400 COMMON
data source (AS/400 COMMON Production, for example) that you
configured when defining the installation plan.
To define the AS/400 Common OneWorld data sources
1. On the System Installation Tools menu (GH961), doubleclick Advanced
Operations.
2. Doubleclick Database Data Sources.
3. On Machine Search Select, click OneWorld Planner B7333.
4. Click Select.
5. On Work With Data Sources, in the Data Source Use field, change SVR to
DB.
6. Click Find.
7. Click AS/400 Common, and then click Select.
8. On Data Source Revisions, type the appropriate information using the
form below as an example.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

661

Installation Guide

In Library Name, type the name of the library that contains your
WorldSoftware data dictionary tables.

In Library List Name, type the RDB name of the AS/400.

In Server Name, type the name of the AS/400.

9. Click OK.
The Create New Data Source form appears.

662

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Custom Installation Plan

To define the Client Access Express ODBC data sources

1. On Create New Data Source, verify the System Data Source option is
selected.
2. Click Next.
3. Complete all forms that appear for Client Access Express AS/400 Common
Data Source.
For instructions on setting up ODBC data sources, see Creating
Thirdparty ODBC Data Sources."
4. On the last form, click Finish.
5. Log off, and then log on to OneWorld.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

663

Installation Guide

664

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench


After you plan the OneWorld installation or upgrade using Installation Planner,
you run the plan using another OneWorld application, Installation Workbench.
This application helps you allocate and configure software and resources.
Installation Workbench runs the workbench programs listed on the next page
according to the plan you create. For example, if you are performing a dataonly
upgrade, you do not incorporate the specification merges into your plan, so the
Specification Table Merge Workbench is not displayed.
You can run Installation Workbench in attended mode or unattended mode. In
attended mode, you start each workbench after the previous workbench finishes.
In unattended mode (the default), each individual workbench runs without user
intervention. You can set task breaks before or after any specific workbench if
you want to stop the process at any point. Note that, if you use unattended
mode, you must check that each individual task ran correctly, and rerun any
tasks that did not complete.
The flow chart on the following page shows the highlevel process to run
Installation Workbench.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

71

Installation Guide

72

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Workbench Components: Summary


Installation Workbench comprises the following components. Some or all of
these components may be used for your installation or upgrade, depending on
your installation plan:


Additional Workbench Tasks are preliminary Workbench tasks carried out


before Location Workbench begins. If you are using unattended
workbench mode, these tasks are performed after Workbench is started.
The tasks performed are Release Master (installation and upgrade), Copy
Data Dictionary (upgrade only), Copy System Tables (upgrade only), and
Security Copy (upgrade only; applies to upgrades from OneWorld version
B73.3 and above).

Location Workbench copies all locations that are defined in the plan from
the Deployment Locations Definition table (F9654) in the Planner data
source to the System - B7333 data source. It also updates the Location
Plan Detail table (F984021).

Data Source Workbench copies all data sources that are defined in the
plan from the Data Source Master table (F98611) and Table and Data
Source Sizing table (F986115) in your Planner data source to your System
- B7333 data source. It also updates the Data Source Plan table (F98401)
to indicate completion.

Environment Workbench copies the F0094, F00941, and F00942


Environment Information tables, as well as the Object Configuration
Master table (F986101) for each environment, from your Planner data
source to your System - B7333 data source. It then updates the
Environment Plan Detail table (F98403) to indicate completion. Depending
on the plan settings, it also runs a batch application to copy new generic
text and to create and populate Object Management Workbench and
version tables.
Environment Workbench can run multiple batch applications
simultaneously, which allows OneWorld to load multiple environments at
the same time. This reduces the amount of time it takes to load
environments. For more information, see the task Configuring Your
Environments" in Starting Installation Workbench."

Machine Workbench copies the Server Configuration tables (F9650 and


F9651) from the Planner data source to the System - B7333 data source. It
then updates the Host Plan Detail table (F98402) to indicate completion
and uses the environment information to populate the Object
Configuration Master (F986101) and Data Source Master (F98611) tables in
the Server Map data source. (Only valid environments, data sources, and
server map tables are created.)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

73

Installation Guide

Control Table Workbench runs the batch application for the planned
control table merges to update language files.
For AS/400 users, the Control Table Workbench also runs the batch
applications for the planned merges to update the data dictionary. It then
updates the Table Conversion Scheduler table (F98405) to indicate
completion and writes a conversion log record.

Specification Table Merge Workbench runs the batch applications for the
planned merges to update language files. This workbench runs only for
users who are adding an alternate language to their installations.

Package Workbench transfers the F9603 and F9631 Package Information


tables from the Planner data source to the System - B7333 data source. It
then updates the Package Plan Detail table (F98404) to indicate
completion.

Remote Location Workbench loads business (master and constant),


control, data dictionary, and system tables from base location to remote
location servers, by launching different versions of R98403 (XJDE0043,
XJDE0044, XJDE0045, XJDE0046, and XJDE0047). It also pushes delivered
packages to primary deployment servers at remote locations by launching
the multitier UBE (R98825C). This workbench is processed only if you
opted to install remote locations and chose to load replicated data and
push packages.

See Also


74

Major OneWorld Technical Tables" in the Installation Reference Guide for


more information about individual tables and their uses.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

After you create the installation plan, you use the Installation Workbench, which
comprises a series of individual workbenches, to update various tables. The
information you set up in your installation plan determines which workbenches
run during this process.

Preparing to Run Installation Workbench


This section describes the following preparation tasks, which are run before you
run Installation Workbench:
- Verifying the Language Code Character Set
- Editing the Windows registry setting for ODBC data sources
- Creating the Processing Option Text File for Languages
- Selecting unattended or attended workbench mode
- Setting task breaks
In addition, if you are running Installation Workbench in unattended mode, you
should familiarize yourself with the individual tasks by reading this chapter
carefully before running Workbench.

Verifying the Language Code Character Set


On the AS/400, verify that the code character set ID for your preferred language
is set using the following commands:


WRKUSRPRF JDE

Use option 2 to edit.

Press F10 to verify and edit all fields.

Scroll to the character set ID (CCSID)

Change the setting to your preferred language character set, for example,
CCSID=37 (English language). For more information about this task, refer
to the Code Page Setting section in the Customer Overview chapter.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

75

Installation Guide

This setting will be returned to its original value before starting OneWorld
on your enterprise server.

Editing the Windows registry setting for ODBC data sources


To load double-byte data correctly via ODBC, edit the following registry setting
in: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini


Value Name: DBCSNoTruncErr

Value Data: 1

If your ODBC Data Sources does not have this registry value, some records will
not be inserted into tables, and "Insert Record Failed" errors will appear. These
errors will be written to the JDE.LOG during the Control Table Merge and
Specification Table Merge.

Creating the Processing Option Text File for Languages


To add or retrieve data from the Processing Option Text table (F98306),
language customers must recreate this table with an appropriate CCSID value.
This procedure requires Central Objects be loaded first. See Loading Central
Objects for DB2/400," above.
To create the Processing Option text file for languages

Labor Hours
Computer Hours
Personnel

.5
Database administrator

Logon status

On the enterprise server, as QSECOFR

Prerequisites

Confirm available disk space of 2 GB per path code.

Concurrent Tasks

76

0.5

None

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

1. Log on to the AS/400 as QSECOFR.


2. Confirm that the user profile "JDE" is set to the correct CCSID value.
For example, CCSID=939 (Japanese Language). For more information
about this task, refer to the Code Page Setting section in the Customer
Overview chapter.
3. Log on to the deployment server OneWorld Planner environment as JDE.
4. Type `OMW' in the fast path to open the Object Management Workbench.
5. In Object Management Workbench (OMW), type your User ID in the User
field, and click the Find icon at the top of the screen.
See Object Management Workbench in the OneWorld Tools guide
for more information about the OMW.
The system displays your Default Project in the Project window.
6. Click the + icon to the left of your Default Project to display the project
components.
7. Choose the Objects icon.
8. Click on the Search tab in the right-hand pane of Object Management
Workbench
9. Complete the following fields:


Category
Select Object Librarian

Search Type
Select Object Name

Search
Type F98306

10. Click the Search icon to the right of the Search field.
The F98306 table appears in the search window.
11. Select the F98306 table and click on the left arrow to the left of the Search
pane.
Object Management Workbench copies the table icon to the Object folder.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

77

Installation Guide

12. Select the F98306 table in the Object folder, and click the Design button
that appears to the right of the Project pane.
You must add yourself to the project in the Developer role to access
the Design function.
The system displays the Object Librarian Table Design screen.
13. Click the Table Operations tab, then click the Copy Table icon.
The Copy Table form appears.
14. Enter the `OneWorld Local' for the Source data source.
15. Enter the Central Objects data source for the destination.
For example, Central Objects PY7333.
16. Click OK to copy the table.
Run this `Copy Table' for the Central Objects library you have installed.
This process drops the F98306 table in the Central Objects Library and
creates a new format of the table with the character set ID.
17. Use the following AS/400 command to verify the table's CCSID:
Enter: DSPFFD yyyyy/F98306
where yyyyy is the Central Objects Library name, such as COPY7333.
18. Repeat the Copy Table process (steps 15 19) for each Central Objects
Library.

Selecting Unattended or Attended Workbench Mode


You can run the workbenches manually (attended workbench mode), or
automatically (unattended workbench mode). If you run workbench unattended,
you will start Installation Workbench as described below, and then the status of
each individual workbench will be displayed as the workbench begins.
Unattended workbench is the default.
In unattended workbench, if an error is encountered in any of the individual
workbenches, the process stops. After you fix the error, unattended workbench
resumes.
Note: It is possible for unattended wrokbench to fail a task but continue to the
next one. If you select unattended mode for Installation Workbench, at the
conclusion you must check that each individual task ran successfully. If a task
did not complete, you must rerun that task.

78

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

You can select attended workbench mode with a processing option.


To select attended workbench mode
19. Open the System Installation Tools menu (GH961).
20. Rightclick on Installation Workbench.
21. Choose Prompt For, and then Values. The Processing Options panel
appears.
22. In the appropriate field, enter 1 for unattended workbench mode, or 0
(zero) for attended workbench mode. 1 (unattended) is the default.
23. Click OK. Work with Installation Plan appears.

Setting Tasks Breaks in Unattended Workbench Mode


You can set task breaks in unattended workbench, before or after any of the
individual workbenches. You can use the task break to verify successful
completion of a workbench or for other tasks. For example, you can set a task
break after Table Conversion Workbench to verify that all table conversions
completed successfully. An automatic task break occurs after Control Table
Workbench, preceding Specification Merge.
To set a task break in unattended workbench mode
1. Open the System Installation Tools menu (GH961).
2. Choose Advanced Operations.
3. Doubleclick Work with Task Breaks. The Work with Task Breaks panel
appears.
4. Click Find. A list of the workbenches appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

79

Installation Guide

5. To set a break before or after a workbench, choose the workbench name,


and, on the Row menu, select Break Before or Break After. (You can also
clear existing task breaks on the Row menu.) Task Break Revisions
appears.
6. On Task Break Revisions, specify the following fields:


Email Address Number (optional)


Specify the address book number (or choose from a list) of the
person who is to be notified when the task break occurs.

Task Break (optional)


Specify 0 (zero) for no task break, or 2 for a task break. If you leave
this field blank, no task break will be configured.

Task Break Short Text (required)


Type a short text description of the task break.

Optional Detail (optional)


Type detailed information about the task break.

7. Click OK. Task Break Revisions closes, and Work with Task Breaks
reappears. Specify any further task breaks, and then click Close.

710

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

Running Installation Workbench


Installation Workbench runs all the individual workbenches that put your
installation plan into place. If you specified attended workbench, you start each
individual workbench when the previous one finishes. If you specified
unattended workbench, the individual workbenches begin automatically and
continue until all are complete (or until a task break or error occurs).
Note: If you select unattended mode for Installation Workbench, at the
conclusion you must check that each individual task ran successfully. If a task
did not complete, you must rerun that task.
This chapter consists of the following tasks:
- Starting Installation Workbench
- Performing additional (preliminary) Workbench tasks
- Configuring locations (Location Workbench)
- Configuring data sources (Data Source Workbench)
- Configuring environments (Environment Workbench)
- Configuring machines (Machine Workbench)
- Configuring remote locations (Remote Location Workbench)
- Finishing Installation Workbench

Before You Begin: SQL Server Considerations


SQL Server Considerations
If you use a SQL Server database, be sure the following database options are checked
(that is, are turned on) before you run Installation Workbench:
 Select Into/Bulk Copy
 Truncate Log on Checkpoint

Starting Installation Workbench


Do not lock the deployment server during Installation Workbench processes (for
example, with a screen saver password) because doing so pauses some
processes. In addition, do not minimize any of the workbench forms, or Installation
Workbench will not continue to the next workbench form until it is again maximized.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

711

Installation Guide

To start Installation Workbench

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

Verify that a printer is set up for your deployment server. If not,


see the appropriate Microsoft Windows documentation. Also,
verify that the loading of central objects is complete, that is, the
loadall script finished successfully. Make sure Oracle
ArchiveLog is turned off during Installation Workbench.

Concurrent Tasks

None

1. From the System Installation Tools menu (GH961), choose Installation


Workbench.
When this application is run the first time, the system will JITI down
required objects.

2. On Work with Installation Plan, doubleclick your plan. The Additional


Workbench Tasks panel appears.
3. Determine your next step:

712

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

If you have specified attended workbench mode, use the following


procedures to complete the workbenches, including the additional
workbench tasks.

If you have specified unattended workbench mode, the process


begins and all workbenches are completed automatically (unless
you have set task breaks). If you did not set any task breaks,
continue with "Merging Your Specification Tables."

Additional Workbench Tasks


The Additional Workbench Tasks panel lets you complete the following
preliminary tasks before the individual workbenches begin:


Copy data dictionary (upgrade only)

Copy system tables (upgrade only)

Security copy (upgrade only; applies to upgrades from version B73.3 and
above)

Release Master (installation and upgrade)

You can also change the status of any of the additional tasks, for example, if you
need to run a task.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Additional Workbench Tasks.
To perform additional workbench tasks

Labor Hours

0.25

Computer Hours

0.50

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

713

Installation Guide

1. On Additional Workbench Tasks, from the Form menu click Configure.


The tasks are performed, and the Location Workbench panel appears.
To change the status of additional workbench tasks

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

You may want to change the status of one or more of the additional workbench
tasks. To change the status of a task, use the following procedure:
1. In the fast path, type GH961 to open the System Installation Tools menu.
Doubleclick Custom Installation Plan. Work with Installation Plans
appears.
2. On Work with Installation Plans, choose your installation plan.
3. On the Row menu, click Expand. The plan components are displayed,
including the additional tasks.

714

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

4. Choose the task whose status you want to change.


5. On the Row menu, click Disable, Enable, or Complete (see the table
below). The task status changes.
Row menu option

Meaning

Disable

Status 70. The task is incomplete, and will


not be rerun.

Enable

Status 20. The task will be rerun.

Complete

Status 60. The task is complete, and will


not be rerun.

Configuring Your Locations


Location Workbench copies all locations that are defined in the plan from the
Deployment Locations Definition table (F9654) in the Planner data source to the
System - B7333 data source. It also updates the Location Plan Detail table
(F984021).
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Location Workbench.
To configure your locations

Labor Hours
Computer Hours
Personnel

0.25
Less than 0.25
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. On Location Workbench, verify that all of your locations are listed.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

715

Installation Guide

2. From the Form menu, choose Configure. Locations are configured, and the
Data Source Workbench panel appears.
OneWorld updates the Detail Status to 60 and changes the Status
Description from Validated to Installed.

Configuring Your Data Sources


Data Source Workbench copies all data sources that are defined in the plan from
the Data Source Master table (F98611) and Table and Data Source Sizing table
(F986115) in your Planner data source to your System - B7333 data source. It
also updates the Data Source Plan table (F98401) to indicate completion.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Data Source Workbench.
To configure your data sources

Labor Hours

0.25

Computer Hours

0.25

Personnel

716

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

1. On Data Source Workbench, verify that all of your data sources are listed.

2. From the Form menu, choose Configure. Your data sources are
configured, and the Environment Workbench panel appears.
When the system has configured your data sources, it changes the detail
status to 60, and Status Description changes from Validated to Installed.

Configuring Your Environments


Environment Workbench copies the F0094, F00941, and F00942 Environment
Information tables, as well as the Object Configuration Master table (F986101) for
each environment, from your Planner data source to your System - B7333 data
source. It then updates the Environment Plan Detail table (F98403) to indicate
completion. Depending on the plan settings, it also runs a batch application to
copy new generic text and to create and populate Object Management
Workbench and version tables.
Environment Workbench can run multiple batch applications simultaneously,
which allows OneWorld to load multiple environments at the same time. This
reduces the amount of time it takes to load environments.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Environment Workbench.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

717

Installation Guide

To configure your environments

Labor Hours
Computer Hours
Personnel

0.25
3 hours per environment; 4 hours to run all environments
simultaneously
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

You can run Environment Workbench at the same time you run
the enterprise server installation process, although performance
will be affected.

1. On Environment Workbench, review each environment and its associated


parameters to make sure the values are correct.

For coexistence, this batch job also updates the WorldSoftware user
defined code (UDC) tables with the new values shipped with OneWorld.
2. After you review the environments, choose Configure.
3. When Environment Workbench has completed, verify that the status of
each environment has been updated to 60 and that the status description
has changed from Validated to Installed.

718

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

4. Using Adobe Acrobat, review all XJDE reports, and confirm that all
configuration statuses indicate Success."

Configuring Your Machines


Machine Workbench copies the Server Configuration tables (F9650 and F9651)
from the Planner data source to the System - B7333 data source. It then updates
the Host Plan Detail table (F98402) to indicate completion and uses the
environment information to populate the Object Configuration Master (F986101)
and Data Source Master (F98611) tables in the Server Map data source. (Only
valid environments, data sources, and server map tables are created.)
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Machine Workbench.
To configure your machines

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. On Machine Workbench, review each server and its associated parameters


for the correct values.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

719

Installation Guide

2. From the Form menu, choose Configure.


When the system has configured your servers, it changes the detail status
to 60, and Status Description changes from Validated to Installed.

Configuring Your Control Tables


If you are installing an alternate language, Control Table Workbench runs the
batch application for the planned control table merges to update language files.
For AS/400 users installing to a coexistent environment, the Control Table
Workbench also runs the batch applications for the planned merges to update
the data dictionary. It then updates the Table Conversion Scheduler table
(F98405) to indicate completion and writes a conversion log record. All users
installing to a coexistent environment (or installing an alternate language) must
complete this task.
This information applies to users installing an alternate language. The distributed
language tables consist of control tables, system tables, and data dictionary
tables. The UDC tables contain only the desired language text, while the menu
text and data dictionary files add the desired language on top of the
alreadyinstalled English records.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Control Table Workbench.

720

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

To configure your control tables

Labor Hours
Computer Hours
Personnel

0.25
0.25 hour per path code
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. On Control Table Workbench, OneWorld displays all control table merges


in the detail area.

If you are installing an alternate language, on the Control Table


Workbench form, the Plan Name field will contain the name of your
language plan.
2. If you want to do one merge at a time, choose the appropriate grid row,
then click Merge. Otherwise, choose Merge All from the Form menu.
For an explanation about how the merges work, see the Installation
Reference Guide.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

721

Installation Guide

If you are running Installation Workbench in unattended mode, a task break


automatically occurs after Control Table Workbench, and before Specification
Merge.

Merging Your Specification Tables


Specification Merge runs only if you are installing an alternate language. Users
who are not installing an alternate language can skip to the next section. Users
who are loading an alternate language with the installation must load language
records into the central objects tables to enable that language.
The central objects tables contain the alternate language records needed for
displaying text in the selected language. Languageenabled tables include the
Processing Option Text table (F98306), the Report Design Aid Text Information
table (F98760), and the Forms Design Aid Text Information table (F98750).
Depending upon the environment choices during the English installation, you
might have several sets of central objects, for example, one set for each
environment loaded during the Englishlanguage installation.
Note: If you run Specification Merge using multiple threads, and you are using
unattended workbench, you must set a task break after the Specification Merge.
This allows all threads to complete. You then start Package Workbench.
To merge your specification tables

Labor Hours
Computer Hours
Personnel

0.25
15 per path code
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. On Specification Table Merge Workbench from the Form menu, choose


Merge All.

722

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

2. After the merge finishes, verify that the output of the report that is
produced.

Configuring Your Packages


Package Workbench transfers the Package Information tables F9603 and F9631
from the Planner data source to the System - B7333 data source. It then updates
the Package Plan Detail table (F98404) to indicate completion.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Package Workbench.
To configure your packages

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. On Package Workbench, review your packages.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

723

Installation Guide

2. From the Form menu, choose Configure.

See Also


Package Management Guide for complete information about building and


configuring packages.

Configuring Your Remote Locations


Remote Location Workbench loads business (master and constant), control, data
dictionary, and system tables from base location to remote location servers, by
launching different versions of R98403 (XJDE0043, XJDE0044, XJDE0045,
XJDE0046 and XJDE0047). It also pushes delivered packages to primary
deployment servers at remote locations by launching the multitier UBE
(R98825C). This workbench is processed only if you opted to install remote
locations and chose to load replicated data and push packages.
You use this procedure if you are running Workbench in attended mode, or if
you have set a task break before Remote Location Workbench.

724

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Running Installation Workbench

To configure your remote locations

Labor Hours
Computer Hours
Personnel

0.25
0.25 hour per path code
Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

All base location environments should have been loaded


(through Environment Workbench).

Concurrent Tasks

None

1. On Remote Location Workbench, OneWorld displays all remote location


activities in the detail area.

2. On the Form menu, click Configure to launch the workbench.


3. After all remote location activities are complete, click Next.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

725

Installation Guide

Finishing Installation Workbench


To finish Installation Workbench

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the JDEPLAN environment.

Prerequisites

None

Concurrent Tasks

None

1. From Congratulations, on the Form menu, click Finish.


2. From Work with Installation Plans, click Close.

726

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing the Enterprise Server


After you define and run your plan to configure OneWorld, you configure and
install OneWorld on the enterprise server.
This section consists of the following task:
- Configuring and installing OneWorld on the enterprise server
The flow chart on the following page shows at a high level the process used to
configure and install OneWorld on the enterprise server:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

81

Installation Guide

82

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the


Enterprise Server

This chapter consists of the following tasks:


- Configuring the enterprise server
- Installing OneWorld on the enterprise server, and verifying the installation
- Starting the OneWorld enterprise server
- Setting up a printer on the OneWorld enterprise server
- Copying language specifications to the enterprise server

Configuring the Enterprise Server


This section describes the following tasks:
- Create OneWorld user profiles
- Set up the TCP/IP protocol
- Set up Client Access Express on the server to use with OneWorld

See Also


Language Process Overview" for the National Language Support tables


and other information related to multilingual installations.

Before You Begin




Install IBM AS/400 upgrades.

Install J.D. Edwards WorldSoftware upgrades. This task applies only if you
are running OneWorld in coexistence with WorldSoftware.

Verify that you have met the hardware and software requirements for the
OneWorld release you are installing. See OneWorld Hardware and
Software Requirements."

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

83

Installation Guide

If you prefer to perform these configuration tasks in a language other than


the language for which the AS/400 is currently configured, change the
value for the code character set ID. For example, to perform these
configuration tasks in English, set the code character set ID to 37. After
completing these configuration tasks, reset the code character set ID to its
original value.

Make a list of modifications you have made to your existing


WorldSoftware, because you might need to modify it again to guarantee
compatibility with OneWorld software. For more information about the
necessary modifications, contact the appropriate J.D. Edwards OneWorld
specialist.

If you are an AS/400 coexistence customer, carefully review AS/400


Coexistence Setup Issues" in this guide.
To create OneWorld user profiles

Labor Hours

0.25

Computer Hours

0.25

Personnel

System administrator or installer

Logon status

On the AS/400, logged on as QSECOFR.

Prerequisites

None

Concurrent Tasks

None

The installation process automatically creates a user profile named ONEWORLD


with user class of *PGMR and group profile of QPGMR.
You cannot substitute the JDE user ID for the ONEWORLD user ID because the
AS/400 objects are designed specifically with ONEWORLD as the owner.
3. For each OneWorld user that accesses a OneWorld AS/400 server, create a
user profile with a USRPRF and PASSWORD that are identical to those of
the OneWorld user.
4. Assign *JOBCTL authority to user profiles that access OneWorld.

84

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

To set up the TCP/IP protocol

Labor Hours

0.25

Computer Hours

0.25

Personnel

System administrator or installer

Logon status

On the enterprise server, logged on as QSECOFR.

Prerequisites

None

Concurrent Tasks

None

J.D. Edwards recommends that you set up the TCP/IP service to start
automatically each time you IPL the AS/400. For more information about setting
it up, contact your system administrator or see the appropriate IBM
documentation.
5. Log on to the enterprise server as QSECOFR, or as any user who can
access the Configure TCP/IP menu.
6. To access the Configure TCP/IP menu, enter the following command:
CFGTCP
7. Choose Work With TCP/IP Host Table Entries.
8. On Work With TCP/IP Host Table Entries, find the network (Internet)
address for the enterprise server.
A single machine could have more than one entry for the same network
address.
9. Verify that an entry exists for the enterprise server network address, and
that it matches the format shown in step 4. Search for the enterprise server
network address by entering the enterprise server name only, for example,
SYS1.
10. If an entry does not exist, choose Add.
In the Host Name field, your enterprise server name should appear in the
following format:
hostname.domainname
where hostname is the name of your machine and domainname is the
machine's local domain on the network, for example,
SYS1.MFG.ABC.COM in which SYS1 is the enterprise server name and
MFG.ABC.COM is the domain name. The combined enterprise server
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

85

Installation Guide

name and local domain name represent the location of the enterprise
server on the network.
Network Considerations
To avoid problems when applications running on separate machines need to
communicate with other applications running on other machines on the same
network, make sure that each machine name (host name; for example, SYS1)
has a single unique TCP/IP address.
11. To verify that the local domain and enterprise server names represent the
correct location of the AS/400, choose Change Local Domain and Host
Names from the Work With TCP/IP Host Table Entries form.
Verify that the Local Domain Name and Local Host Name fields match the
combined hostname.domainname network address. Following the
example in this task, the local domain name would be MFG.ABC.COM and
the local host name would be SYS1.
To set up Client Access Express on the server to use with OneWorld
The IBM Client Access Express terminal emulation program allows workstations
to communicate with AS/400 servers. This task describes the procedure to set up
the component of Client Access Express that runs on the AS/400 server.
Labor Hours

0.25

Computer Hours

0.25

Personnel

System administrator

Logon status

On the enterprise server, logged on as QSECOFR.

Prerequisites

You must create user profiles and set up TCP/IP protocol.

Concurrent Tasks

None

The QSERVER subsystem should reside in its own memory pool. For more
information, see the IBM Work Management Guide.
1. To determine the number of prestart jobs that are available and have been
submitted for program QZDASOINIT, enter the following command:
For V4R5 and earlier:
DSPACTPJ QSERVER QIWS/QZDASOINIT
or, for V5R1:
DSPACTPJ QUSRWRK QSYS/QZDAONIT
86

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

where QZDASOINIT or QZADAONIT is the program name.


Information about the number of your system's prestart jobs, prestart jobs
submitted, and program start requests appears.
The number of prestart jobs depends on the number of concurrent and
active ODBC user connections. This change is iterative as users or
applications are added or removed. If you do not have enough prestart
jobs, your system could be slow to make connections. If connections fail,
they could be successful with the second attempt. If too many prestart
jobs are waiting, the system will end some of them automatically. Also, the
system initiates prestart jobs as additional ones are submitted.
Troubleshooting
To determine the number of prestart jobs you should set up, be aware that
each OneWorld user typically uses three to five ODBC connections. Each
ODBC connection uses one QZDASOINIT program. Therefore, the initial value
for QZDASOINIT could be set to four times the number of expected
concurrent connected users.
The current maximum number of prestart jobs is 9,999. If more jobs are
needed, they will be created as necessary.
2. To see the current settings, enter the following command:
DSPSBSD QSERVER
3. Choose option 10, and then choose option 5 for program
QIWS/QZDASOINIT.
4. To access the form on which you can change the number of prestart jobs,
enter the following command:
CHGPJE SBSD(QSYS/QSERVER) PGM(QIWS/QZDASOINIT)
5. Change the number of prestart jobs as needed, and then press Enter.
6. Restart the QSERVER subsystem for your changes to take effect.

Installing OneWorld on the Enterprise Server, and Verifying


The following procedures describe how to install OneWorld on the enterprise
server and verify the installation using PORTTEST.
This section describes the following tasks:
- Modify the enterprise server JDE.INI file on the deployment server
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

87

Installation Guide

- Copy OneWorld files to the enterprise server


- Create an output queue for the AS/400 default printer
- Create the job queue
- Verify the installation using PORTTEST
To modify the enterprise server JDE.INI file on the deployment
server

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE.

Prerequisites

None

Concurrent Tasks

You can run Environment Workbench at the same time.

To facilitate the administration and maintenance of the JDE.INI files for the
possibly numerous enterprise servers, all JDE.INI files are stored on the
deployment server. Whenever you need to make a change to a JDE.INI file for
an enterprise server, change the original file on the deployment server. The file
is then copied from the deployment server to its respective enterprise server.
This task describes modifications you need to make to the enterprise server
JDE.INI file before installing OneWorld on the enterprise server. Use a text editor
to modify the file.
1. Using Windows NT Explorer, locate the JDE.INI file that will be copied to
the enterprise server.
By default, it is located in:
\jdedwardsoneworld\b7333\hosts\AS400\enterpriseserver
where enterpriseserver is the name of your enterprise server.
2. Using a text editor, modify the JDE.INI file as follows:


88

In the [INSTALL] section, verify that your LocalCodeSet parameter is


set to the appropriate value. Also, verify that your code page is set
up properly. For appropriate values and code pages, see the
National Language Support tables in the Language Process
Overview" chapter in the Customer Preparation" section of this

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

guide. These values are set automatically, with the first language
installed. For multiple languages, the first language, alphabetically, is
the default, and may need to be modified.


In the [NETWORK QUEUE SETTINGS] section, ensure that the QEnv


setting specifies a valid environment.

The DefaultEnvironment parameter in the [SECURITY] section must


match a valid environment in the plan (for example, DV7333).

The number of simultaneous builds should not exceed the number


of compiler licenses. In the [BSFN BUILD] section, change
"SimultaneousBuilds" to 5 or less (the default is zero, which allows
unlimited builds).

Ensure that the port number specified in the [JDENET] section of the
JDE.INI file (for ServiceNameListen and ServiceNameConnect values)
matches the port number you specified during Installation Planner .
See Entering Enterprise Server Information" in the Installation
Planner chapter.

3. Save the JDE.INI file, and then close it.


To copy OneWorld files to the enterprise server

Labor Hours
Computer Hours
Personnel

0.5
Up to 4 hours
Installer

Logon status

On the AS/400, logged on as QSECOFR.

Prerequisites

None

Concurrent Tasks

The enterprise server installation process copies OneWorld system and path
code files directly from the enterprise server CD. This option significantly
reduces the time that was required in previous releases to transfer the software
from the deployment server.
If you are using Simplified Chinese, Korean or Turkish languages, change the
CCSID of QSECOFR to CCSID=37. If you log onto AS/400 as QSECOFR with
CCSID "933", "935" or "1026" respectively, and try to install the host CDs, FTP
will fail and the errors will be logged in JDEOW/FTPOUTPUT.
1. Log on to the AS/400 as QSECOFR.
2. Insert the CD AS/400 Direct Enterprise Server Install 1 of 7" into the
optical device (CD drive), and enter the following command:
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

89

Installation Guide

GO JDEOW/A98OWMNU
This first CD was used to load libraries during the deployment server
installation. The ADDLIBLE JDEOW LODRUN command should not be
necessary.
A menu appears.
3. Enter selection 4 to Install the OneWorld Server Libraries.
The Install OneWorld Libraries form appears.
OneWorld Server Libraries include SYS7333, the path code libraries, and
the Integrated File System (IFS).
4. Type or verify the following information:


Device Name
The name of the optical device (CD drive), for example, OPT01.

Release Number
The OneWorld release number you are installing or upgrading.

Deployment Server Name


The name of your deployment server.

OneWorld Deployment Path


Replace the question mark on this line with the drive letter where
OneWorld is installed on the deployment server.

Deployment Server User ID


The user ID for the deployment server. The default is JDE.

Deployment Server Password


The correct password for the user in the line above. It will not
display on the form.

Change Messages to Break Mode


Type *YES (the default value). This will send installation status
messages in the middle of the process (break mode).

810

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

Tips and Techniques


The F3 key will end the installation process. For more detailed information
about this form, press the Help or F1 keys.
5. Press Enter to continue the installation process.
A File Transfer message will appear.
6. If the current version of the OneWorld libraries is found, a message
appears asking you to verify if the OneWorld libraries should be replaced.
If the replace existing OneWorld libraries message appears, enter G to
replace the libraries. (C will cancel the process.) In some cases the display
will not update unless you press Enter twice after pressing the G key.
7. The installation process will submit the J98OW20 to batch when the library
and INI files have been transferred to the AS/400 from your deployment
server.
Tips and Techniques
The FTPOUTPUT file also contains file transfer messages. To display this job
log information, enter DSPPFM for file FTPOUTPUT in library JDEOW.
Installation status messages will appear in break mode if you chose that
option.
After the job is submitted to batch, a menu appears.
Tips and Techniques
To access the installation menu (A98OWMNU) in the future, use the command
ADDLIBLE JDEOW to add the correct library for your user. Once the JDEOW
library is added, you can access the menu by using GO JDEOW/A98OWMNU.
Do not delete the JDEOW library after installation. In past releases of
OneWorld, this library could be deleted, but if you do so for release B73.3
forward, you will not be able to access the installation menu (A98OWMNU).
8. After approximately 30 minutes, you will be prompted for the second CD.
Insert the second CD (Direct Enterprise Server Install 2 of 7).
9. After an additional 30 minutes, you will be prompted for the third CD.
Insert the third CD (Direct Enterprise Server Install 3 of 7).
10. After an additional 30 minutes, you will be prompted for the fourth CD.
Insert the fourth CD (Direct Enterprise Server Install 4 of 7).
11. After the job finishes, verify the installation status in the job log.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

811

Installation Guide

This job will run for approximately four hours.


To create an output queue for the AS/400 default printer

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer or system administrator

Logon status

On the AS/400, logged on as QSECOFR, at the A98OWMNU


menu.

Prerequisites

OneWorld must be installed on the enterprise server.

Concurrent Tasks

Installing the OneWorld enterprise server

1. Log on to the AS/400 as the QSECOFR.


2. Enter the following commands:
ADDLIBLE JDEOW
GO JDEOW/A98OWMNU
3. Enter selection 7 to configure an output queue. Complete the following
fields and press Enter:


Outqueue Name
The outqueue name for the printer.

Printer IP Address
The network address of your printer.

Remote Printer Queue


You are required to set the remote printer queue (parameter
RMTPRTQ) to something other than ` ' for some printers. For
example, you must set this parameter to PASS for the IBM network
Printer 4317. See the printer's user manual for additional
information.
If the CCSID of the server jde.ini file is 37, you must change the
CCSID value to 65535 after you complete the installation
If the CCSID of PRINTQUEUE is 37, you must change the CCSID
value to 65535 after you complete the installation If you don't

812

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

change this value, you will get the following error message when
you open the PDF:

To create the job queue

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer or system administrator

Logon status

On the AS/400, logged on as QSECOFR.

Prerequisites

None

Concurrent Tasks

Installing the OneWorld enterprise server.

1. Log on to the AS/400 as the QSECOFR.


2. Enter the following commands:
ADDLIBLE JDEOW
GO JDEOW/A98OWMNU
3. From the menu, choose option 8 Create Job Queue.
Tips and Techniques
To determine the unused sequence number, enter DSPSBSD SBSD(QBATCH)
Choose option 6 for the Job Queue Entries, and then record an unused
sequence number.

Verifying the Installation


This section describes the following tasks:


Verify the AS/400 libraries

Verify the OneWorld installation using PORTTEST

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

813

Installation Guide

Note: If Security Server is on, then OneWorld services must be running before
PORTTEST can be run. Start OneWorld services with the STRNET command.
To verify the AS/400 libraries

Labor Hours
Computer Hours
Personnel

0.25
None
Installer or system administrator

Logon status

On the AS/400, logged on as QSECOFR.

Prerequisites

OneWorld must be installed on the enterprise server.

Concurrent Tasks

None

To verify that you have transferred the installation files to the AS/400
successfully, review the following libraries:


B7333SYS (assuming you used the J.D. Edwards recommended name


during setup)

The library for your environment path code (for example, DV7333)
Depending on the number of environments you have installed, you could
have multiple path code libraries, for example, DV7333 and JD7333.
For more information about what these libraries contain, see System
Administration AS/400" in the Server and Workstation Administration
Guide.
To verify the OneWorld enterprise server installation (PORTTEST)

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the AS/400 enterprise server, logged on as ONEWORLD or


other user with logon privileges (see note below).

Prerequisites

OneWorld must be installed on the enterprise server.

Concurrent Tasks

None

To verify that OneWorld is installed correctly, you must run the PORTTEST
program for each environment.

814

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

Note: If you are performing an upgrade, and OneWorld AS/400 Database


Security (SETOWAUT) was implemented in the previous release of OneWorld,
the ONEWORLD logon will not work. In this case, see your AS/400 administrator
to obtain a OneWorld logon and password for the AS/400 enterprise server.
1. Log on to the AS/400 enterprise server as ONEWORLD (or other
OneWorld user).
2. On Current OneWorld Versions, choose the version of OneWorld you want
to use, and press Enter.
3. To verify that OneWorld is installed correctly on the enterprise server,
enter the following command:
GO JDEOW/A98OWMNU
The A98OWMNU menu appears.
4. Choose selection 12 to run porttest.
This program initializes a user and an environment (assuming you
installed and configured OneWorld correctly). The program selects records
from the F0902 table, which appear as messages on your screen. If
messages that indicate your selections do not appear, review the jde.log
file.
Troubleshooting
If PORTTEST fails to run, see PORTTEST Checklist" for diagnostic assistance.

PORTTEST Checklist
If PORTTEST fails to run, use this checklist to diagnose the problem before you
call J.D. Edwards Worldwide Customer Support. Please have the answers to
these questions as well as copies of error messages, your JDE.INI, and any error
logs, such as JDE.log or JDE_xxx.log.
PORTTEST may fail if replication, security server, or transaction processing have
been installed incorrectly. If problems occur after the installation of one or more
of these services, check the setup of those services for incorrect parameters.
General Issues

Yes/No

Is the user logged on with administrator privileges?


On the AS/400, the user may need to log on as ONEWORLD to perform
some operations.
Are all the environment variables set?
Is the C compiler installed?
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

815

Installation Guide

General Issues

Yes/No

Can you query the database on the enterprise server?


Is a PostScript or PCL printer connected to this machine?
Are the printer drivers for this printer installed?
Is this printer configured as the default printer?

JDE.INI issues

Yes/No

Is your JDE.INI file located in the correct library?


Does JDE.INI have the correct permissions?
Are the following JDE.INI parameters set properly?
[Network Queue Settings]
Default Printer=your printer
[UBE] (if you use PostScript, is the correct filter set up?)
[DB System Settings] (verify all parameters, especially the following:)
Default Env= your default environment
Default Pathcode = your default path code
Server = database server name
[JDENET]
serviceNameListen = port number
serviceNameConnect = port number
[INSTALL]
B7333=your path

Communications Issues

Yes/No

Do the workstations and server agree on the server's IP address?

Other Issues

Yes/No

Have your server map tables (F98611 and F986101) been edited properly?
Run the Verify OCM application and verify:
Do only host databases exist?
There are no entries for batch applications.
Are OneWorld tables accessible to the host?

816

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

Other Issues

Yes/No

Can you query the F0902 table?


Does PORTTEST run without error for each valid path code?
Does the user name match that of a valid OneWorld account? Remember
that the user name is casesensitive.
Is the password valid for the given OneWorld account?
Does the environment name match a valid OneWorld environment?
Remember that the environment name is casesensitive.
Does JDEnet start and stop properly?

If you answered no to any of the above questions, your batch application


probably will not run. If you can answer yes to all the questions, submit a batch
application now.
If your batch application does not run correctly, turn on error logging and
resubmit the batch. This log helps J.D. Edwards Worldwide Customer Support
diagnose the exact problem.

Starting the OneWorld Enterprise Server


After you install OneWorld on the AS/400 enterprise server, you can start the
server.
If you changed the value for QCCSID at the beginning of Installation
Workbench, set it back to its original value now.

See Also


Stopping OneWorld on the Enterprise Server" for more information about


stopping the AS/400 enterprise server.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

817

Installation Guide

To start the OneWorld enterprise server

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

On the AS/400 enterprise server, logged on as ONEWORLD or


other user with OneWorld logon privileges (see note below).

Prerequisites

OneWorld must be installed on the enterprise server.

Concurrent Tasks

None

Note: If you are performing an upgrade, and OneWorld AS/400 Database


Security (SETOWAUT) was implemented in the previous release of OneWorld,
the ONEWORLD logon will not work. In this case, see your AS/400 administrator
to obtain a OneWorld logon and password for the AS/400 enterprise server.
1. Log on to the AS/400 enterprise server as ONEWORLD (or other
OneWorld user).
2. On Current OneWorld Versions, choose the version of OneWorld you want
to use, and press Enter.
3. The first time you start the AS/400 enterprise server, enter the following
commands and options:
ADDLIBLE JDEOW
GO JDEOW/A98OWMNU
Choose selection 14 to end JDE Server.
Choose selection 15 to clear the IPC.
4. To start the enterprise server, use the following options:
Choose selection 13 to start the JDE Server.
Choose selection 17 to display active jobs.
5. Verify that the entry NETWORK is running with a PGMJDENET_N in
SELW status.
6. Verify that the entry SENTINEL is running with a PGMMONITOR in SELW
status. The status will be SIGW.
Until you perform a net request, the CPU is 0 (zero).

818

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

See Also
Stopping OneWorld on the Enterprise Server" for information about stopping
these processes.

Setting Up a Printer on the OneWorld Enterprise Server


Labor Hours

0.5

Computer Hours

0.5

Personnel

System administrator or installer

Logon status

On the deployment server, logged on as user JDE, in the


deployment environment.

Prerequisites

OneWorld must be installed on the enterprise server.

Concurrent Tasks

None

This section describes the following tasks. Perform the tasks in the deployment
environment:


Add a new printer

Define a default printer

You can also print OneWorld reports, modify existing printers, and delete
printers. These tasks are described in detail in the OneWorld System
Administration Guide. Refer to that document to learn more about setting up a
printer to run from the OneWorld enterprise server.
To add a new printer
OneWorld provides a Printer Setup director to help you add printers. Instructions
appear on each form of the director to guide you through the printer addition
process. The following procedure should be used in conjunction with the steps
that appear on the forms of the Printer Setup director.
If you are installing your first printer, you must complete this task and then the
task Define a default printer" in this chapter.
1. On the Printers menu (GH9013), choose Printers (P98616).
The Printers form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

819

Installation Guide

2. On the Printers form, click Add Printer.


The welcome page for the Printer Setup director appears. This page
describes the tasks the director helps you perform.

3. Review the welcome page and click the Next button.


The Platform Information form appears. The Platform Type may appear
automatically by default depending on which operating system your
OneWorld is running on.

820

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

4. On the Platform Information form, complete the following field:




Platform Type
Type the platform type you are installing on, or use the visual assist
to select a platform type.

5. Click Next. Other fields appear on the same form.

6. Complete the following fields and click Next:




Library Name
For the AS/400, the physical printer name must be the same as the
outqueue name. If you use the default QGPL library to store your
outqueues, you need only enter the outqueue name in this field.
This information must be entered in upper case. Example:
DEVDES3A. Valid characters are all alpha (A-z), numeric (0-9), at (
@ ) and underscore ( _ ).

Ouputqueue Name
If your outqueues reside in a library other than the default QGPL
library, you need to enter the library name and the outqueue name
in this field. Example: QUSERSYS/DEVDES3A. Valid characters are
all alpha (A-z), numeric (0-9), at ( @ ) and underscore ( _ ). Note:
When you qualify your outqueue name with the library name, you
avoid possible name conflicts that might result in the submission of
your report at an unexpected outqueue.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

821

Installation Guide

The Printer Setup form appears. Use this form to set information for the
printer such as the printer model, physical location of the printer, printer
definition language, paper types, and encoding selection (AS/400 only).

7. On the General tab, complete the following fields, and then click the
Details tab:

822

Printer Model

Printer Location

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

8. On the Details tab, in the box labeled Printer Definition Language, choose
PostScript, PCL, Line Printer, or Custom. In the Default box, specify one of
the Printer Definition Languages as the default.
Note: You can choose multiple printer definition languages (PDLs), but
only one default PDL. A user can override this default PDL at the time a
batch process is submitted.
If you choose PostScript or PCL, OneWorld disables the Line Printer
option. If you choose Line Printer, OneWorld disables the PostScript and
PCL options.
When you choose the Line Printer option, the following happens:


OneWorld disables the grid at the bottom of the form and any paper
types you have chosen are cleared. OneWorld automatically
provides a printer type of *JDE LINE PAPER for the printer.

Fields appear within a box labeled Line Printers that you use to set
the paper dimensions and line parameters. This is explained in the
following steps.

When you choose the Line Printer option along with the AS/400
platform type, fields appear within a box labeled AS400 Only" that
you use to set the AS/400 encoding that your printer supports. This
is explained in the following steps.

The custom option uses advanced features of the Printers application. This
is explained in the following steps.
9. On the Details tab, when you choose the PostScript option, the Paper
Source box appears and you can change the following options:


Max Number of Paper Sources


Enter a numeric value in this field to indicate the number of paper
trays this printer has available.

Default Paper Source


Enter a numeric value in this field to indicate which tray number
you want OneWorld to draw paper from as the default.

10. On the Details tab, when you choose the Line Printer option, fields appear
within a box labeled Line Printers that you use to set the paper
dimensions and line parameters. Complete the following fields:


Characters Per Inch


The value you enter in this field determines the number of
characters the given physical printer allows in one horizontal inch.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

823

Installation Guide

Columns Per Page


The value you enter in this field determines the number of
characters that appear in one line text in the given report.

Lines Per Inch


The value you enter in this field determines the number of lines of
text that the given physical printer allows in one vertical inch.

Lines Per Page


The value you enter in this field determines the number of lines of
text that the given physical printer allows on one printed page.

Printer Paper Width


The value in this field is calculated automatically based on the
numbers you enter in the Line Printers box.

Printer Paper Height


The value in this field is calculated automatically based on the
numbers you enter in the Line Printers box.

11. On the Details tab, when you choose the Line Printer option along with an
AS/400 server, fields appear within a box labeled AS400 Only" that you
use to set the AS/400 encoding that your printer supports. Choose one of
the following:


ASCII Encoding

EBCDIC Encoding
Note: If you choose a PostScript or PCL printer along with an
AS/400 server, the ASCII Encoding option is checked and the AS400
Only" box is disabled.

12. On the Details tab, the Custom option lets you specify a conversion filter
to use.
When you select the Custom option, a field appears beneath the Custom
checkbox. Enter the name of the conversion filter you want to use, or use
the visual assist to select a filter from the Conversion Program Search and
Select form.
13. (If you do not want to change or add a conversion filter, skip to the
following step.) To change or add a conversion filter, from the Form
menu, choose Advanced. The Advanced option is enabled only when
Custom has been chosen.

824

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

The Work With Conversion Programs form appears.

Either click Add or highlight one of the filters, and click Copy or
Select.
The Advanced Conversion Program form appears.

Change one or both of the following fields:




Conversion Program

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

825

Installation Guide

If you clicked Add or Copy on the previous form, the


Conversion Program field is enabled. Enter the name of the
conversion program you want to add or copy. If you are
making a copy, the Parameter String field is populated with the
string you highlighted on the previous form.


Parameter String
The parameter string is entered automatically. It is based on the
host you are printing from (AS/400, HP9000, etc.) and the type
of printer (PostScript, PCL, or line). For example:
-s string_name -l library_name -f convertPDFToPS

where s defines the string name, l defines the library name


(letter l," not the numeral 1"), and f defines the function
name.


Click OK. The Work with Conversion Programs form appears. Click
Close. The Printer Setup form appears.

14. In the grid at the bottom of the Printer Setup form, doubleclick the row
header for each paper type that your printer supports. A checkmark
appears in the row header for each paper type that you select.
Note: You can add new paper types as necessary. Instructions are
included later in this task.

15. In the Default Type column, type the numeral 1" in the row for the paper
type you want to use as the default. You can choose only one paper type

826

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

to be your default. A user can override the default paper type when a
batch process is submitted.

16. To add a new paper type, complete the following:




From the Form menu, choose New Paper Type.


The Work With Paper Types form appears.

Click Add.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

827

Installation Guide

The Paper Type Revisions form appears.

Complete the following fields, and click OK:




Paper Type

Paper Height

Paper Width

Unit of Measure

OneWorld saves the new paper type. Click to return to the Work
With Paper Types form, and then Close to return to Printer Setup.
The new paper type is available in the grid on the Printer Setup
form. All previous paper type selections are cleared and must be
reselected if you want to use them again.
17. When you finish entering information for the printer on the Printer Setup
form, click End.
OneWorld saves the new printer and returns you to the first form in the
Printers application.

828

Field

Explanation

Platform Type

The type of physical hardware the database resides on.

AS400 Library Name

AS400 Library Name for setting up the printer

AS400 Outputqueue Name

AS400 Outputqueue Name for setting up the printer

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

Field

Explanation

Server Name

Refers to the computer that receives documents from


clients.

Printer Name

A name that refers to a shared resource on a server. Each


shared directory on a server has a share name, used by PC
users to refer to the directory.

Printer Model

Printer capabilities are as follows:


Printer Model: the model of the printer
Printer Location: where the printer physically
resides
Encoding: AS/400 users' only feature

Paper Type

A user defined code (H98/PT) that indicates the type of


printer paper, such as letter or legal. For example,
LETTER, LEGAL, and A4.

Paper Width

A value that specifies the width of the paper for this paper
type. This value is in the unit of measure specified by Unit
of Measure.

Paper Height

A value that specifies the height of the paper for this


paper type. This value is in the unit of measure specified
by Unit of Measure.

Unit of Measure

A user defined code (00/UM) that indicates the quantity in


which to express an inventory item, for example, CS
(case) or BX (box).
. . . . . . . . . . . . . Formspecific information . . . . . . . . . . . . . .
Indicates the unit of measure in which the paper height
and width are entered.
Example:

IN = Inches
MM = Millimeters

EBCDIC Encoding

Printer capabilities are as follows:


Printer Model: the model of the printer
Printer Location: where the printer physically
resides
Encoding: AS/400 users' only feature

Columns Per Page

A line printer parameter that specifies the number of


columns per page. For example, 80 or 132.

Characters Per Inch

The horizontal printing density. Enter the number of


characters per inch supported by your printer.

Line Per Page

A line printer parameter that specifies the number of lines


per page. For example, 60 or 66.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

829

Installation Guide

Field

Explanation

Line Per Inch

The line spacing should be entered as the number of lines


per inch and must be supported by your printer. The valid
values are:
4 IBM 5219, 5224, 5225, and 3287 printers only
6 IBM 5224 printer only
8 IBM 5224 printer only
9 IBM 5225 printer only
The standard computer print is 6 LPI and 10 CPI. If you
are printing on 8 1/2" x 11" paper, you would specify 8
LPI and 15 CPI.

The maximum number of


output tray

The maximum number of paper trays available on the


printer you are setting up.

The output tray name

The output tray that a user wants to use for a given batch
print job.

To define a default printer


1. On the Printers menu (GH9013), choose Printers (P98616).
2. On the Printers form, click Define Default Printer.
The Work With Default Printers form appears.
3. Click Add.
The Default Printer Revisions form appears.

830

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing OneWorld on the Enterprise Server

4. Complete the following fields, and then click OK.




User/Group
Click the visual assist to choose either a particular user for this
printer or to choose an entire group. If the field is left blank, the
default value is *PUBLIC.

Report Name
Click the visual assist to choose a specific report to print. If the field
is left blank, the default value is *ALL.

Version Name
Click the visual assist to choose a specific report to print. If the field
is left blank, the default value is *ALL. If the Report Name is *ALL,
the version name will default to *ALL and be disabled.

Environment
In this field, OneWorld automatically enters the environment that
you are currently logged onto. You can change this information.

Printer Name

Host Name
Include the host server where reports will process. The visual assist
displays the appropriate host names based on the printer name you
select.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

831

Installation Guide

Object Status
You can make this new printer the default printer by changing its
status to active. If an error occurs, it means that another printer is
currently the active default. You need to change the original default
printer to inactive before you can make the new printer active.
Perform multiple status changes from the Work With Default Printers
form as explained at the end of this task.

After you click OK, click Cancel to go to the Work With Default Printers
form.
5. To change the status of a default printer from the Work With Default
Printers form, choose a default record, and then from the Row menu
choose Change Status.
If another printer is already set as the active default, an error occurs. To
change the original default printer to inactive, choose it, from the Row
menu choose Change Status, and then make the new printer the default.

Copying Language Specifications to the Enterprise Server


This section is only for users who are installing an alternate language. All other
users can skip to the next section.
You must load the language specification files to the enterprise server in order to
create reports and to print in your desired language. The replicated local
specification files on your enterprise server contain the English language. The
replicated local specification file that contains your languages is RDATEXT.
The final step in preparing your enterprise server for an alternate language is to
copy the language specification files using the package management process.
Detailed instructions are provided in in the Package Management Guide,
Working with the Package Assembly Director" and Working with the Package
Build Definition Director."
To include language specifications in your package, you need to specify the
language. The package build process then uses the language preference code
specified as a parameter when building the package using the relational
database tables to build the Report Design Aid specifications. A language
package can be a full or update package.

See Also


832

Package Build" in the Package Management Guide for detailed


instructions for building and deploying server packages.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installing OneWorld on the Workstations


OneWorld software is first installed on the deployment server, and then
deployed from the deployment server to workstations. You can install OneWorld
on the workstations in interactive mode, silent mode, or push mode. Push mode
is described in the Package Management Guide.
You can install OneWorld on workstations that run Microsoft Windows 2000,
Windows NT Workstation, Windows 98, or Windows 95.
For the workstation to reflect the language installed on the deployment server,
you must perform tasks for both the enterprise server and workstations, in
addition to the procedures to verify and modify the JDE.INI settings.
This section consists of the following task:
- Configuring and installing OneWorld on the workstations
The flow chart on the following page shows at a high level the process used to
install OneWorld on the workstations.

See Also


Language Process Overview" for more information about how you enable
multilingual installations on workstations.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

91

Installation Guide

92

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

To prepare for the installation of OneWorld on individual workstations, you


complete some brief configurations and modifications: you modify the
workstation JDE.INI files on the deployment server; and the system administrator
creates a user profile for every user before that user can log on to OneWorld.
This chapter consists of the following topics and tasks:
- Understanding workstation installation
- User profile and language considerations
- Modifying the workstation JDE.INI file on the deployment server
- Cataloging DB2/UDB databases
- Installing OneWorld in interactive mode
- Installing OneWorld in silent mode

Before You Begin




Before installing OneWorld on a workstation used for development, install


Microsoft Visual C++ Compiler, Version 6.0. See the appropriate Microsoft
guides for more information.

Note: You do not need full administrator privileges to install OneWorld on the
workstation. However, you do need proper privileges for writing to the disk and
the registry. If you do not have these privileges you will receive a warning
during installation. In this case, you should contact your administrator, who can
perform the installation for you, or grant you proper disk and registry access. For
more information about granting disk and registry access, see Granting Access
to Disk and Registry for Windows NT."

Understanding Workstation Installation


The workstation installation program copies all necessary components of
OneWorld to a workstation. During installation, the installation program verifies

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

93

Installation Guide

that enough disk space exists, and if not, you are prompted to create more space
before continuing.

OneWorld Installation Methods


Choose one of the following methods to deploy OneWorld and to launch the
workstation installation program:


Interactive mode

Silent mode

Push installation

Interactive and silent modes of workstation installation are described in this


section. Unless you have a specific need to use the silent mode, you should use
the interactive mode. Silent mode will not detect or update Microsoft Internet
Explorer or Adobe Acrobat Reader. You must use interactive mode to detect that
the latest versions are installed.
The silent installation mode lets you specify the installation path by
commandline arguments instead of entering them on the Workstation
Installation forms. As a result, you can submit the silent installation from the
command line or through any scheduling service (such as Windows 95,
Windows 98, Windows NT, or Windows 2000 schedulers) that you have
installed.
The push installation process lets the administrator schedule an automatic launch
of the Workstation Installation program at a specified date and time. This
program requires no user interaction during the process.
See Also


Using Push Installation" in the Package Management Guide for


instructions about push installation options and the workstation Listener
program.

Third-party Products
The workstation installation program detects the latest version of Microsoft
Internet Explorer and Adobe Acrobat Reader on the workstation, and depending
upon the version, prompts you to update these applications during the
OneWorld installation process. The use of Microsoft Internet Explorer is optional.
Adobe Acrobat Reader is strongly recommended, so that you can view
OneWorld reports online.
Microsoft Internet Explorer provides:


94

An option for a Weblike menu view within OneWorld Explorer.

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

An option for an Internet connection capability directly from the


OneWorld Explorer interface.

User Profile and Language Considerations


OneWorld supports group preferences for user profile workstation configuration,
and environment assignment.
For user and group profiles, J.D. Edwards recommends you use the preloaded
users to perform the installation process. The system administrator needs to
create a user profile for every user before he or she can log on to OneWorld.
All users are assigned a language preference code within the user profile. The
language preference code field specifies which language is presented on the
applicable form or report. You can set up your users and groups when you
determine how you want groups to be organized, and what preferences you
want each group to have.
For languages, the JDE.INI files are updated automatically. For multiple language
usage, both the server and workstation JDE.INI files need to be modified for the
preferred language being installed.

See Also


System Administration Guide for more detailed information about setting


up group profiles and how to use them, as well as information about
defining user display preferences.

Modifying the Workstation JDE.INI File on the Deployment Server


To facilitate the administration and maintenance of the JDE.INI files for the
possibly numerous workstations, all JDE.INI files are stored on the deployment
server. Whenever you need to make a change to a JDE.INI file for a workstation,
change the original file on the deployment server. The file is then copied from
the deployment server to its respective workstation.
This task describes modifications you need to make to the workstation JDE.INI
file before installing OneWorld on the workstation.
If you are using a double byte language, modify the ODBCDataSource.inf on the
Deployment Sever by adding the following value to all ODBC Data Sources:
DBCSNoTruncErr=1
If the ODBC Data Sources do not have this registry value on the workstations,
some records will fail to be inserted into tables and Insert Record Failed" errors
will appear.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

95

Installation Guide

To modify the workstation JDE.INI file

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE.

Prerequisites

None

Concurrent Tasks

None

Use the following procedure to modify settings in the JDE.INI file in the
\JDEdwardsOneworld\B7333\OneWorld Client Install\Misc directory on the
deployment server.
1. Open the workstation JDE.INI file. Modify the following settings:


[NETWORK QUEUE SETTINGS]


Set the UBEQueue parameter appropriately. This setting should be
the same as set for the enterprise server, for example:
UBEQueue=QB7333

For language installations, ensure that your workstation is set up correctly


for language preferences to display and print forms. If multiple languages
are installed, verify that the appropriate JDE.INI values are set to your
preferred language. See Language Process Overview" for appropriate
values.


[INTERACTIVE RUNTIME]
For the language you are installing, enter:
Initial_Language_Code = x
where x is the value for the language installed, or for the preferred
language if multiple languages are installed.

[INSTALL]
Verify that the LocalCodeSet value and code page setting are set to
the appropriate values. The JDE.INI setting that will be read will be
the language installed.

96

[JDENET]

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

Verify that the port number specified for ServiceNameListen and


ServiceNameConnect matches the port number in the enterprise
server JDE.INI file.
Replicated Data Considerations
You can resynchronize replicated data by changing the ForcedSync value in
the [REPLICATION] section from 0 to 1. When workstations are installed, this
value is set to 0, meaning you do not want to resynchronize data.
2. Save and exit the file.

Cataloging DB2/UDB Databases


You can run the catalog_db.bat or use the DB2 Client Configuration Assistant.
1. Click on Start|Programs|IBM DB2|Client Configuration Assistant.
2. Close the Add Database screen if it pops up.
3. Click Import at the bottom of the screen.
4. Click on Network and browse to the B7333 directory on the Deployment
Server.
5. Open the oneworld.spf file in the Client Directory.

Installing OneWorld in Interactive Mode


Before You Begin
The OneWorld installation process installs the latest version of Adobe Acrobat
Reader, if it is not already installed. The process first asks you whether you want
Acrobat installed; if you do, you must uninstall any previous version of Acrobat
Reader before proceeding. To save time, you should uninstall a previous version
of Acrobat Reader before you begin the installation process.

See Also


System Administration Guide for more information on the InstallManager


tool, and the editing and configuration options.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

97

Installation Guide

To install OneWorld in interactive mode

Labor Hours
Computer Hours
Personnel

0.25
0.5 to 1.0
Installer or system administrator

Logon status

Choose one of two methods: InstallManager shortcut on the


desktop, or from the JDEdwardsOneWorld shared drive on
your deployment server.

Prerequisites

Verify that no other programs are active. Verify that the


appropriate hardware and software requirements are installed.

Concurrent Tasks

None

Close all other applications. The installation process may not run correctly if
other applications are open.
OneWorld can be installed to the workstation by either of two methods: desktop
shortcut or shared drive. Choose one of the following and then skip to step 3:
To use a desktop shortcut:
1. A system administrator can create a shortcut to InstallManager.exe from
the JDEdwardsOneWorld\B7333\OneWorld Client Install directory on the
deployment server, and can deploy the shortcut to the workstation. To
ensure that the shortcut works correctly, check that the Start in:" field
contains the location of the installmanager.ini file. To edit the Start in:"
field, select the shortcut (in Windows Explorer or on the desktop),
rightclick, and click Properties and then the Shortcut menu.
2. Doubleclick the OneWorld InstallManager shortcut to start the OneWorld
installation manager. (Skip to step 3, below.)
To use a shared drive:
1. An installer can connect to the \JDEdwardsOneWorld\B7333 shared drive
on your deployment server from Windows Explorer.
2. Doubleclick InstallManager.exe to start the OneWorld installation
manager.
The InstallManager.exe file is located in the OneWorld Client Install folder.

98

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

The JDEdwards OneWorld Installation Manager form appears.

3. Click Workstation Install. The Client Workstation Setup form appears.

4. On Client Workstation Setup, click Next.


If you do not have the latest versions of Microsoft Internet Explorer or
Adobe Acrobat Reader installed, the OneWorld Client Workstation Setup
Third Party Application form appears. The options to install Internet
Explorer and Acrobat Reader are turned on (checked). To install these
applications, click Next. If you do not want to install these applications at
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

99

Installation Guide

this time, turn off (uncheck) the option for one or both of them, and click
Next.
If the latest versions of Acrobat and Internet Explorer are already installed,
you will not see the Third Party Application form.
The Client Workstation Setup Package Selection form appears.
5. On the Client Workstation Setup Package Selectoin form, choose the
package you want to install and click Next.

Tips and Techniques


Click the Filters ON button to narrow the displayed list of available packages.
This can help you can find the package you want.
Notice that a short description of each package appears below the list.
The Client Workstation Setup Type form appears.

910

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

6. Click the Select Setup Type option for Development or Production for
each package you want to install on the workstation.
Click the option for Development only if you intend to develop OneWorld
applications.
7. To choose the drive on which to install the package, click the ellipsis
button next to the Install Path field.
You can change the drive where OneWorld is installed, but the directory
path is always \b7.
8. To install the package, click Finish.
InstallManager shows the status of the installation process through a series
of forms.
The Congratulations form indicates that the installation has finished
successfully. InstallManager creates a OneWorld shortcut in your Start
menu's Programs folder and on your desktop.
9. Reboot if a message prompts you to do so.
The OneWorld installation process verifies that several of the system DLL
files are current. If they are not current, you receive a message to reboot
your system. When you reboot, the system updates the DLL files in your
Windows directories.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

911

Installation Guide

Installing OneWorld in Silent Mode


OneWorld can also be installed to the workstation by the silent mode, which is
optional. Verify that you are connected to the JDEdwardsOneWorld shared drive
on the deployment server.
The silent installation does not prompt for installation of the latest versions of
Microsoft Internet Explorer or Adobe Acrobat Reader. To install them, connect to
the \JDEdwardsOneworld\B7333\OneWorld Client Install\THIRDPARTY
directory on the deployment server and run ie4setup.exe (for Microsoft Internet
Explorer) or ar40eng.exe (for Adobe Acrobat Reader).
To install OneWorld in silent mode

Labor Hours
Computer Hours
Personnel

0.25
1.0
Installer

Logon status

From a workstation, open Windows Explorer and connect to


the JDEdwardsOneWorld shared drive on your deployment
server.

Prerequisites

Verify that the appropriate versions of Microsoft Internet


Explorer and Adobe Acrobat Reader are installed. Verify that no
other open programs are active.

Concurrent Tasks

None

1. From the Start menu, choose Run.


2. Click Browse.
3. Locate the \JDEdwardsOneworld\B7333\OneWorld Client Install directory
on the deployment server, choose SETUP.EXE, and then click Open.
4. In the Run box, append the required parameters to setup.exe so that the
command line conforms to the following structure:
setup.exe -S -P packagename -D installpath
where packagename is a valid package name and installpath is the
installation path on the workstation where OneWorld should be installed
(for example, c:\b7).
You also can include the following optional parameters:


912

-t Typical

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring and Installing Workstations

Installs the development objects.




-t Compact
Does not install the development objects.

-r
Uninstalls previous installation before continuing. The results of the
uninstallation appear in c:\jdeinst.log.

If the specified installation path already exists, the directory structure


contents are overwritten.
5. To run the command line, click OK. During a silent installation, OneWorld
Client Installation appears in the Windows taskbar.
6. You can verify a successful installation by viewing the c:\jdeinst.log file.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

913

Installation Guide

914

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Preparing Packages
This section explains how to build and test the packages you will deploy to your
workstations.
The section consists of the following task:
- Building and testing packages

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

101

Installation Guide

102

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Using Visual ER Compare

Using Visual ER Compare

Visual ER Compare is a utility that lets you compare event rules (ER) on your
local workstation to ER in the central objects data source of any defined
pathcode, TAM specifications, or ESU backup. For example, if you make changes
to the ER for an application and then want to compare your changes to the ER
in the server application, you would use Visual ER Compare.
Visual ER Compare provides a linebyline, onscreen comparison. You can
change the target ER (your local version) within the utility by moving lines
directly from the source ER. You can also remove or disable lines. In addition to
providing an onscreen comparison, you can choose to print a report detailing
the changes as well.
Using Visual ER Compare comprises the following topics:
- Launching Visual ER Compare
- Understanding the Visual ER Compare interface
- Working with Visual ER Compare

Launching Visual ER Compare


Apply the following task only to objects with attachable ER (applications, UBEs,
tables, and business functions).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

103

Installation Guide

To launch Visual ER Compare

Labor Hours

Variable, depending on the number of custom modifications

Computer Hours

Variable, depending on the number of custom modifications

Personnel

Programmer - preferably the same one who did the custom


modifications

Logon status

On the workstation on which you will retrofit object


modifications, typically in the development or prototype
environment.

Prerequisites

The environment has been updated and a package has been


built and deployed to the desktop being used.

Concurrent Tasks

You can do nearly any other task at the same time.

From Cross Application Development Tools (GH902), choose Object


Management Workbench (P98220).
1. On Object Management Workbench, check out an object.
2. Select the object you checked out, and then click the Design button in the
center column.
3. On the Design form, click the Design Tools tab.
4. Click Visual ER Merge.
5. On Select the Location of Source Specifications, perform one of the
following actions:


Click Select PathCode, and then enter the server location of the
source object (the object to which you want to compare your local
ER).

Click Advanced TAM, and then enter the TAM location of the source
object (the object to which you want to compare your local ER).
ESUs are delivered in a TAM package, so use this method to
compare your local ER to an object packaged in an ESU.

Understanding the Visual ER Compare Interface


When you launch Visual ER Compare, the Visual ER Compare form appears. A
treestructured menu of the ER appears on the left. The rest of the form displays
the source ER (in the middle pannel) and the target ER (in the right pannel). The
target ER is your local ER.

104

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Using Visual ER Compare

In the ER menu, the system uses fonts of different colors to show the rules that
exist in both source and target but are different and the rules that exist in one
location but not the other. The system indicates a change in the parent node if
one or more of its children have been changed. In the ER panes, the system
highlights the lines that differ. If lines have been added to or deleted from one
side, blank lines appear on the other. Disabled lines are indicated with an
exclamation point. The system uses fonts of different colors to show the rules
that have changed in content or that have been added or deleted. You can
change the display colors by selecting User Options from the View menu, and
then selecting Set Colors.
Visual ER Compare uses an algorithm to compare lines to determine if a change
has occurred. If a certain percentage of the target line is different from the
source line, then the system marks the line as being different. You can change
the sensitivity of the comparison by choosing User Options from the View menu
and then choosing Comparison Factors. To include disabled ER lines in the
comparison, click Disable Partial Matching for Disabled ER. To change the
percentage of difference required to highlight a line as being changed, enter a
number in the Partial Match Ratio field. The default value of .50 means that a
minimum of 50% of the target line must vary from the source line to trigger the
system to mark it as being changed.
You can choose a different source by choosing Open Source from the File menu.

Working with Visual ER Compare


Use the ER menu to identify and display specific ER components that have
changed. If a parent node is identified as being changed, expand it to see which
of its children are different. Doubleclick an event in the ER menu to display its
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

105

Installation Guide

associated code. You can display more than one event at a time. Use the Tile
option in the Window menu to view different ER events simultaneously.
You can also move from change to change by rightclicking in either the source
or target pane and choosing Next ER Difference to move forward or Previous ER
Difference to move backwards.
You can change your target ER with Visual ER Compare. You can also print the
changes. If you want to copy all of the changes from the source to the target,
you can use the AutoMerge feature.
Working with Visual ER Compare is composed of the following topics:


Changing your target ER

Printing a Visual ER Compare report

Using AutoMerge

Changing Your Target ER


Perform any of the following actions to change your target ER:
To copy selected lines
from source to target

Select the lines to copy, rightclick in the source pane, and


then choose Copy Right.

To delete selected lines


from the target

Select the lines to delete, rightclick in the target pane, and


then choose Delete.

To enable or disable
selected lines in the
target

Select the lines to enable or disable, rightclick in the


target pane, and then choose Enable/Disable ER.

Note: Use the shift key to select multiple, contiguous lines and the control key
to select multiple, noncontiguous lines.
After making your changes, rightclick and choose Save ER. This action saves
your changes to a buffer. When you choose to open a new source or to exit
Visual ER Compare, the system prompts you to save your changes again. If you
elect to save your changes at this time, then the system updates the object on
your workstation; otherwise, your changes will be lost.

Printing a Visual ER Compare Report


You can print a report comparing the source and target ER. You can show the
comparison for a particular event or for all of the ER in the object.

106

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Using Visual ER Compare

To print a report for an event, doubleclick the event in the ER menu, rightclick
in either pane, and then choose Print ER.
To print a report for the entire object, choose Print ER from the File menu.

Using AutoMerge
Use AutoMerge when you want the system to change the target ER to match the
source ER. You can use AutoMerge to change a particular event or to update all
of the ER in the object.
Caution: Before performing an AutoMerge for an entire object, do a comparison
to be certain that you really want all of the changes that the system detects.
To use AutoMerge on an event, doubleclick the event in the ER menu,
rightclick in either pane, and then choose AutoMerge.
To use AutoMerge on an entire object, choose Advanced Operations from the
View menu, and then choose Auto Merge.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

107

Installation Guide

108

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

The process provides a method to create a package, to define and build a


package, to deploy packages to both servers and workstations, and to
troubleshoot the packages. The features use a stepbystep director process and
include package assembly, package build, and package deployment.
There are several instances in which you will need to upgrade or set up a
workstation or server with OneWorld software. For example, you may need to
set up a new workstation, to deploy custom solutions to all or to selected users,
to create a new path code for development, to deploy a fix, or to change the
package from a full to a partial package on some workstations.
These processes include the option to define three different package types, to
build and define packages with custom solutions, and to distribute through two
different deployment options. These options are available to a single server,
workstation or user, or for selected machines, groups, or individual users. These
options can be delivered using justintime or scheduled installation methods.
To include any modifications (changed or added business functions or
applications) into a package for deployment to workstations (for example,
DV7333FB or DV7333PB), define and build one of your own.
The system administrator is required to build and test packages at the server
level. An installer may complete the process for the workstations. These
processes can take several hours depending upon the scope of your business.
The procedures take place on the deployment server in the deployment
environment as user JDE. OneWorld installation must be completed on the
enterprise server prior to building and testing packages. The time required to
build packages to the workstation varies depending on the database being used.
The package build and assembly process includes many critical tasks that must
be successfully completed to install the packages correctly. This section includes
a list of known issues associated with the package build, assembly, and
deployment process and gives instructions for avoiding them. Before you build
a package, review these instructions to successfully complete this process.

See Also


Package Build" in the Package Management Guide for information about


how to build and deploy packages.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

109

Installation Guide

This chapter consists of the following topics:




Updating the system path

Reviewing prepackage build issues

Reviewing postpackage build issues

Reviewing troubleshooting tips

Building an alternate language package


To update the SYSTEM path

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

On the enterprise server, in the Windows Control Panel.

Prerequisites

None

Concurrent Tasks

None

1. On the enterprise server, on the Windows Start menu, open the Control
Panel.
2. Open System and click on the Environment tab.
3. Append the path from your user variables onto the path for your system
variables. (Note: do not replace the existing system path information.
Simply add a semi-colon to the end of the existing system path, and then
append the user path information.)
4. In your system settings, create the LIB and INCLUDE settings.
5. Copy the LIB and INCLUDE settings from your user to your system.
6. Change the drive letter to point to Visual C++ on your enterprise server.
7. Verify the following path settings (if the paths on your system are
different, change them to match these values):
INCLUDE:
c:\Program Files\Microsoft Visual Studio\vc98\atl\include;
c:\Program Files\Microsoft Visual Studio\vc98\mfc\include;

1010

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

c:\Program Files\Microsoft Visual Studio\vc98\include;


c:\Program Files\mts\include;
LIB:
c:\Program Files\Microsoft Visual Studio\vc98\mfc\lib;
c:\Program Files\Microsoft Visual Studio\vc98\lib;
c:\Program Files\mts\lib;
PATH:
C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;
C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;
C:\Program Files\Microsoft Visual Studio\Common\Tools;
C:\Program Files\Microsoft Visual Studio\vc98\bin

8. Reboot the computer.

Reviewing Pre-Package Build Issues


Check the following items before you build your packages in order to minimize
errors during package builds. Perform each of the relevant tasks on the machine
where the package will be built.
Delete CAPS.dll (if upgrading from B73.3 base release only)
1. Type `OMW' in the fast path to open the Object Management Workbench.
2. In Object Management Workbench (OMW), type your User ID in the User
field, and click the Find icon at the top of the screen.
See Object Management Workbench" in the OneWorld Tools guide
for more information about the OMW.
The system displays your Default Project in the Project window.
3. Click the + icon to the left of your Default Project to display the project
components.
4. Select the Objects icon.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1011

Installation Guide

5. Click on the Search tab in the right-hand pane of Object Management


Workbench
6. Complete the following fields:


Category Object Librarian

Search Type Object Name

Search CAPS

7. Click the Search icon to the right of the Search field.


CAPS appears in the search window.
8. Select the CAPS and click on the left arrow to the left of the Search pane.
Object Management Workbench copies the file to the Object folder.
9. Select the CAPS file in the Object folder and click the Design button that
appears to the right of the Project pane.
The system displays the Object Librarian Design screen.
You must add yourself to the project in the Developer role to access the
Design function. To perform this task, complete the following steps:
A. Click the + icon to the left of your Default Project to display the
project components, and select the Owners icon.
B. Click on the Search tab in the right-hand pane of Object
Management Workbench
C. Complete the following fields:


Category Owners

Search Type User ID, Address Book, or Alpha Description

Search Type the your name or address book number

D. Click the Search icon to the right of the Search field.


Your name or address book number appears in the search window.
E. Select your name or address book number and click on the left
arrow to the left of the Search pane.
Object Management Workbench copies the icon to the Owners
folder.

1012

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

F. Choose the icon you copied to the Owners folder and click the
Select button at the top of the screen.
The program displays the Add User to Project window.
G. Click the search icon in the Roles field, choose 02 (Developer) from
the search window and click Select.
H. On Add User to Project screen, click OK to add yourself as a
developer.
10. On the design screen of the CAPS.dll file, check if any business functions
are assigned to this dll.
11. If CAPS contains no business functions, delete it from Object Management
Workbench.
Verify the CLOG.dll setting (if upgrading from B73.3 base release only)
1. Type `OMW' in the fast path to open the Object Management Workbench.
2. In Object Management Workbench (OMW), type your User ID in the User
field, and click the Find icon at the top of the screen.
See Object Management Workbench" in the OneWorld Tools guide
for more information about the OMW.
The system displays your Default Project in the Project window.
3. Click the + icon to the left of your Default Project to display the project
components.
4. Select the Objects icon.
5. Click on the Search tab in the right-hand pane of Object Management
Workbench
6. Complete the following fields:


Category Object Librarian

Search Type Object Name

Search B4600510

7. Click the Search icon to the right of the Search field.


B4600510 appears in the search window.
8. Select B4600510 and click on the left arrow to the left of the Search pane.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1013

Installation Guide

Object Management Workbench copies the object to the Object folder.


9. Select the B4600510 from the Object folder and click the Design button
that appears to the right of the Project pane.
You must add yourself to the project in the Developer role to
access the Design function. See Delete CAPS.dll for instructions on
how to perform this task.
The system displays the Object Librarian Design screen.
10. Verify that the Product System Code and Product Code fields are both
`88'. If not, change them both to `88'.
11. Click OK.
Verify that the following UBEs are mapped locally
1. Open the OCM.
2. Find each of the following UBEs and make sure they are mapped locally
and are active: R9621, R9622, R98825C and R98825D.
Verify the OCM mapping
1. Verify that the F98826 table has been generated using Universal Table
Browser and all OCM mappings for all environments have been created.
Delete the BUSOBJ directories
1. Delete all BUSOBJ" directories from the Client and Deployment Server
that are running the packages. This directory is located under the
OneWorld pathcode directory.
Delete F98743 records (if upgrading from B73.3 base release only)
1. Open the F98743 table through Oracle, SQL or DB2.
2. In that table run a query against the column dttmplid to see if the
following records exist: 8002, 8003, 8004, 8005, 8006,8014,8015, 8018.
3. If they exist, delete them.
Modify the F9860 table (if upgrading from B73.3 base release only)
1. Open the F9860 table using Oracle, SQL, or DB2.
2. Run a query against it where SIOBNM = `D0900374.'

1014

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

3. Find the SIPARDLL column. If this field has a parent dll, run another
query to delete the parent dll name from this record.
4. Repeat steps 2 and 3 for the following object names:
D3400190, D3400200, D3400210, D3400220, D3400230, D3400250, D3400260,
D3400350.

Verify the F9631 table


1. Open F9631 table using UTB.
2. Verify that there are 16 records with PDPKGNAME = LITE".
3. If the table is missing any of these records, refresh that table by copying it
from the Access database in the planner pathcode directory. To complete
this task, perform the following steps:
A. Log on to the deployment server in the Planner environment.
B. Type `OMW' in the fast path to open the Object Management
Workbench.
C. In Object Management Workbench (OMW), type your User ID in
the User field, and click the Find icon at the top of the screen.
See Object Management Workbench" in the OneWorld Tools
guide for more information about the OMW.
The system displays your Default Project in the Project window.
D. Click the + icon to the left of your Default Project to display the
project components.
E. Select the Objects icon.
F. Click on the Search tab in the right-hand pane of Object
Management Workbench
G. Complete the following fields:


Category
Select Object Librarian

Search Type
Select Object Name

Search

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1015

Installation Guide

Type F9631
H. Click the Search icon to the right of the Search field.
The F9631 table appears in the search window.
I. Select the F9631 table and click on the left arrow to the left of the
Search pane.
Object Management Workbench copies the table icon to the Object
folder.
J. Select the F9631 table in the Object folder and click the Design
button that appears to the right of the Project pane.
You must add yourself to the project in the Developer role to
access the Design function.
The system displays the Object Librarian Table Design screen.
K. Click the Table Operations tab, then click the Copy Table icon.
The Copy Table form appears.
L. Enter `OneWorld Planner B7333' in the Source data source field.
M. Enter `System B7333' in the Destination data source field.
N. Click OK to copy the table.
Verify the jde.ini settings on the Enterprise Server
1. Open the JDE.INI file on the Enterprise Server.
2. Verify that the BuildArea setting in the [BSFN Build] section points to the
PACKAGES directory on the Enterprise Server.
i.e: G:\jde\jdedwardsoneworld\ddp\b7333\packages.
Configure the Enterprise Server
1. Open your jde.ini file on the server.
2. In the [BSFN BUILD] section of the INI file, change the
SimultaneousBuilds" to:
0 (zero)

1016

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

Reviewing Post-Package Build Issues


Check the following items after you build your packages in order to minimize
errors during package deployment.
Delete F98741 table records (if upgrading from B73.3 base release only)
You only need to perform this task if your system was originally at the B733
base release.
1. Open the builderror.txt file. This file is located under the package name
directory on the deployment server.
2. In the builderror.txt file, find the information about the GBRSPEC Build.
3. If the builderror.txt file contains exactly 2 records with GBRSPEC Build
errors, complete the following steps:
A. Copy or write down the long number following the word esevsk"
in the builderror.txt file.
B. Open the F98741 table through Oracle, SQL or DB2.
C. In the F98741 table, run a query against the column esevsk using
the long number in the builderror.txt file.
D. If the record exists, use SQL to delete it from the database.

Reviewing Troubleshooting Tips


The following troubleshooting tips are designed to help you avoid known
issues with the package build, assembly, and deployment process. Review these
tips as you work through the process. The tips are grouped into the following
categories:


User Tips

Deployment Tips

User Tips
Check the following items as you build and assemble your packages.
Complete the assemble process and the build process
After entering the package information on both the Assembly and Build screens,
click the End" icon button to save the information.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1017

Installation Guide

Complete the package definition screen


When selecting the servers on the Build Definition screen, make sure there is a
pink check mark next to each server selected. If not, highlight the server in the
grid and click select.
Update the parent packages
After building an update package that updates the parent package, you must
recompress the parent package. This does not happen automatically.
Update the server packages
When building an update server package, the specified parent package must be
stored under the package directory on the server. If the parent package is not
under the packages directory, the update package will not build.

Deployment Tips
Check the following items as you deploy your packages.
Deploy a package to a CD burner
When deploying the package to a CD burner, the target machine must be
created and the CD Burner must be attached to this new location. See the
OneWorld Installation Guide for details.
Approve the package
After building a package, change the Deployment Status in the [ATTRIBUTES]
section of the package.inf file from No Status Defined" to Approved." Without
this setting, you will not be able to see the package in the package list when
you try to install OneWorld from a client workstation.
1. Open the Package Deployment application.
2. Click the Package" radio button.
3. Enter the package name and click find.
4. Select the package.
5. Click Activate/Deactivate under the Row exit button.
This task sets the package to active.

1018

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

Copy the package INF files


If there are two or more package inf files that have the same package name
listed in the Attributes section, that package will not show up on the install
screen. (You might have created a duplicate package if you copied a
package.inf file to back it up.) Complete the following steps to fix this problem:
1. Open the package INF file for the package that is not showing up on the
install screen
2. Check the Attributes section in the other package's inf files and verify that
the package name listed in PackageName=" is not duplicated in another
package inf file.
3. If the package name is the same as listed in another package inf file,
change it.
Configure the client package inf file
If you schedule a package to be deployed to a client machine and the client is
not prompted for the package installation at login, there may be a conflict with
a registry setting. Complete the following steps to eliminate this problem.
1. Open the client package inf file.
2. Verify the FoundationBuildDate" is a few hours earlier than the
BuildDate." If it is not, change the time on one of these entries.
3. Verify that the DeploymentStatus" setting in the package inf is set to
Approved."
4. If the status is not Approved", set it to "Approved" and save the file.
5. Install the package again.
Deploy the update package
When you schedule a package for deployment on a client machine, the client is
prompted to install the package at logon. Occasionally, the installation fails with
an error or runs for only a few seconds then stops. This failure can occur if
there is a conflict with a registry setting. Complete one of the following tasks to
fix this problem:


Add a second deployment record for this machine and try again to install
the package.

Use uclient.exe on the deployment server


(B7333\system\bin32\uclient.exe) to uninstall OneWorld. Then use
regedit.exe to remove any remaining registry settings for J.D. Edwards or
OneWorld. Finally, reinstall OneWorld on this machine.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1019

Installation Guide

See Also


Package Build" in the Package Management Guide for detailed


instructions for building and deploying packages.

Building an Alternate Language Package


A package represents a copy of the central objects at a point in time. It contains
replicated objects which OneWorld reads at runtime. If custom modifications or
text overrides have been made at the time a software upgrade is to be
performed, or if you want to deploy development changes to a local
workstation including a specific language, you need to build a package and
specify which language or languages to include in that package. This involves
the following considerations:


Package build considerations

Package deployment considerations

Package Build Considerations


Before you begin to build a language package, verify that your language
installation is complete. To build the language package, you must first define
the package. This procedure can take several hours depending on the size of
the package and the number of languages used. This task is completed on the
deployment server, logged on as user JDE in DEP7333.
To include language specifications in your package, you need to specify the
language in the package definition. The package build process then uses the
language preference code specified as a parameter when building the package
using the relational database tables to build the form design aid text and report
design aid text specifications. A language package can be a full, update, or
partial package. When you build the package, the current data dictionary is
included in the package.
When you are building the client package with translated processing option
text, you must run the build using Windows NT language version or Windows
2000 with the system locale set to the appropriate language. If the system locale
on the operating system does not match the installed language, the translated
text in processing options (POTEXT) will be corrupted.
Building server packages that include languages other than English requires that
the LocalCodeSet value of the OneWorld client matches the LocalCodeSet value
of the jde.ini file on the enterprise server. If the LocalCodeSet value on the
local client is different from the one specified on the enterprise server, the
server package build will fail and errors will be logged in the jde.log on the
enterprise server.

1020

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Building and Testing Packages

Package Deployment Considerations


You cannot deploy a translated package to a workstation if the appropriate
character set is not installed on that workstation. For example, if you created a
package containing Japanese text, the workstation must be loaded with
Japanese Windows 95, Windows 98, or Windows NT to view the Japanese data
correctly.
To transfer translated objects to a server, complete the server package
installation procedures. You will need to define each object that you have
modified for languages. Therefore you must track the objects you have changed
so that you can include them in a package.
If you need to move all objects, call J.D. Edwards Worldwide Customer Support
for assistance.

See


Package Management Guide for more information about transferring


objects to the server.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1021

Installation Guide

1022

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Completing the Installation


You must modify specific applications after you finish the installation process.
This section consists of the following topics and tasks:
- Setting up Windows NT security on OneWorld directories
- Modifying OneWorld after the installation
- Setting Up the Solution Explorer
- Configuring OneWorld for use with Vertex Quantum tax applications
You need to perform the tasks in the Vertex chapter only if you have
installed the Vertex Quantum tax applications.
The flow chart on the following page shows at a high level the process used to
complete the installation or upgrade.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

111

Installation Guide

112

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Setting Up Windows NT Security on OneWorld


Directories

If you want to set up Windows NT security on the OneWorld directories and


files on your deployment server, use the following chart to determine what
permissions are required for the various types of OneWorld users. You can set
these permissions on the Security tab.
Note: Not all directories may be available.
The directory names listed in the table below are subdirectories of the
\JDEdwardsOneWorld\B7333 directory structure. You can apply the indicated
permissions to all subdirectories and files except where noted.

Client Directory
The Windows NT deployment server logon requires full control for security
setup.
User Type

Permissions

JDE

Change

(all files except jdeclnt.ddc and


jdeclnt.xdc)

Change

Production users

Read Only

(all files except jdeclnt.ddc and


jdeclnt.xdc)

Change

Development users

Read Only

(all files except jdeclnt.ddc and


jdeclnt.xdc)

Change

CNC administrators and application leads

Read Only

(all files except jdeclnt.ddc and


jdeclnt.xdc)

Change

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

113

Installation Guide

Pathcode Directory
User Type

Permissions

JDE

Change

(all subdirectories except \pathcode and


\package)

Change

Production users

Read Only

(all subdirectories except \pathcode and


\package)

Change

Development users

Change

(all subdirectories except \pathcode and


\package)

Change

CNC administrators and application leads

Change

(all subdirectories except \pathcode and


\package)

Change

Database Directory
User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

Data Dictionary Directory

114

User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

Change

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Setting Up Windows NT Security on OneWorld Directories

Helps Directory
User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Read Only

Hosts Directory
User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

Mediaobj Directory
User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Change

Planner Directory
User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

115

Installation Guide

Printqueue Directory
User Type

Permissions

JDE

Change

Production users

No Access

Development users

No Access

CNC administrators and application leads

No Access

System Directory

116

User Type

Permissions

JDE

Change

Production users

Read Only

Development users

Read Only

CNC administrators and application leads

Change

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

This chapter describes final modifications that must be carried out before you
can begin using OneWorld.
The chapter consists of the following tasks:
- Modifying media object queues
- Deleting ActivEra tables
- Resetting SQL Server options
- Copying Data Dictionary files to the enterprise server
- Expanding the distribution flexible files
- Updating the Ledger Type Master file (F0025) P09940
- Running the accounts receivable conversion process
- Running the R4094A batch application
- Building Word Search tables

Modifying Media Object Queues


Media objects allow you to attach information to OneWorld applications,
specifically the storage location of media objects to be tracked by reference as
opposed to physical network location. This allows easier administration of media
locations.
Media object queues provide the system administrator the ability to easily
manage the storage of media objects in a OneWorld configuration. Within
OneWorld, you must set up media object queues in order to use images that are
outside the domain of the imaging product (for example, scanned images).
You must define a media object queue to identify the pointer to the location
where the actual image files or OLE objects reside. For OLE objects, the name of
the queue must be OLEQUE. The media object queues must reside on a
Windows NT machine. A valid networkqualified path must exist for this

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

117

Installation Guide

machine. You can use the deployment server or any other Windows NT
machine.
If you use the deployment server to store media object queues, remember that
you must make the machine available for use daily by OneWorld applications.
Media object queue paths are shipped with generic server names. In order to
enable media object queues at the customer site, you must enter the deployment
server name in the media object queue path.

See Also


Media Objects and Imaging" in the System Administration Guide for more
information on the use of media objects.
To modify media object queues

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

From the workstation, logged on as user JDE with the database


password for user JDE.

Prerequisites

None

Concurrent Tasks

None

1. From System Administration Tools (GH9011), choose Media Object


Queues (P98MOQUE).

118

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

2. To define the location for a new OLE queue, on Work With Media Object
Queues click Add.
3. Complete the following fields:


Name

Path
The queue paths will include SERVER NAME and Queue name.
Replace SERVER NAME with the name of your deployment server or
the location of the media object queue. A valid queue path for a
network location might be \\servername\B7333\queuename,
where servername is your deployment server and queuename is the
name of the media object queue.
If you are using ComposerCBT, the media object queue path does
not require \\" or servername. ComposerCBT is shipped with an
X" for the drive name. To enable the Composer CBT queue,
replace the X" with the drive letter that the workstation uses to
access the server where the media object queues reside, for
example, N:\Mediaobj\ComposerCBT.

4. To change an existing media object queue, click Find to display a list of


queue names and their paths.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

119

Installation Guide

5. On Work With Media Object Queues, choose the queue name you want to
modify and click Select.

6. On Media Object Queues, change the information in the Path field to


reflect the new location.
7. Exit OneWorld and log back on to enable the changes.

Resetting SQL Server Options


If you use Microsoft SQL Server, you must reset the database options.

1110

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

See Also


What's New for B73.3.3" in this guide.


To reset SQL Server options

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer or database administrator

Logon status

On the deployment server, in SQL Enterprise Manager.

Prerequisites

The installation completed successfully.

Concurrent Tasks

None

1. In Enterprise Manager, doubleclick each JDE database.


2. Click the Options tab.
3. Uncheck the following SQL Server options (that is, turn them off):


Select Into/Bulk Copy

Truncate Log on Checkpoint

Repeat this process for each JDErelated database.

Copying Data Dictionary Files to the Enterprise Server


At this point in the process, the data dictionary files are copied back to the
enterprise server. This process consists of two tasks:


Recreating replicated data dictionary files

Transferring data dictionary files to your enterprise server

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1111

Installation Guide

To recreate replicated data dictionary files

Labor Hours
Computer Hours
Personnel

0.25
Variable, depending on the size of the files
Installer

Logon status

In OneWorld, logged on as user JDE with the database


password for user JDE.

Prerequisites

None

Concurrent Tasks

None

1. From the Data Dictionary Design menu (GH951), choose Recreate


Replicated Data Dictionary (R92TAM).
2. On Work with Batch Versions, choose version XJDE0001.
3. On Version Prompting, from the Row menu, choose Processing Options
and enter the following information, and then click OK:


Language Preference
Use the visual assist button to select the correct value for your
language.

All Languages
Type 1.

4. Choose version XJDE0001.


5. On Version Prompting, choose Advanced from the Form menu.
6. On Advanced Version Prompting, activate the Override Location option.
7. Click OK.
8. On Version Prompting, click Submit.
9. After the job has completed, log off OneWorld.

1112

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

To transfer data dictionary files to your enterprise server

Labor Hours

0.5

Computer Hours

0.5

Personnel

Installer

Logon status

On a workstation, in Windows Explorer.

Prerequisites

Recreate replicated data dictionary files.

Concurrent Tasks

None

1. From a workstation, locate the tamftp.exe program. It is typically in the


/b7/system/bin32 directory.
2. Doubleclick the program to run it.
3. Enter JDE as the user and password. Choose the environment you are
currently installing.
Troubleshooting
If you need to terminate this program after you have started it, use the X
button in the upper right corner of the DOS window.
4. You will be prompted with the following questions. The appropriate
response or choice of responses is noted beneath each.


Do you want to copy all of the supported spec types (y/n)?


Enter N.

(You are prompted for each type of specification file.)


Enter N to each type except for dddict and ddtext.

Do you want to copy dddict files (y/n)?


Enter Y.

Do you want to copy ddtext files (y/n)?


Enter Y.

Do you want to create a new database for each spec type to copy
(y/n)?
Enter Y.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1113

Installation Guide

Are the spec files to copy located in D:\b7\prod\spec (y/n)?


Enter N.
As prompted, enter the actual directory where the specification files
exist, for example, d:\b7. This is the \b7 directory on the
workstation.

Do you want to pack the files to go in c:\temp (y/n)?


If this is where packed files (.pak) are to be stored, enter Y. If you
want to specify a different directory, enter N.
If you entered N for the previous question, you are prompted to
enter the correct directory. Verify that the directory exists on the
workstation.

Do you want the pack files to be deleted at the end (y/n)?


If you want the .pak files to be deleted off the workstation in the
\temp directory specified in the previous step, enter Y. If you do
not want the .pak files deleted off your workstation, enter N.

Do you want the TAM FTP log file to go in c:\ (y/n)?


If you want the program to write the log file to the root directory on
the c: drive of your workstation, enter Y.
If you want to specify a drive or directory for the log file, enter N.
The name of the log file is tamftp.log.
If you specify no, you are prompted to enter a valid drive and path.

What machine do you want to TAM FTP to?


Specify the name of the enterprise server that is the target for the
specification file transfer. You can specify either a valid TCP/IP
name or an IP address.

In what directory do you want to put the specs to copy?


Specify a valid directory on the enterprise server that is the target for
the specification file transfer. J.D. Edwards recommends that you
create this directory before running tamftp and that the directory is
different from the specification directory of where OneWorld is
located. The unpacked specification files would then be moved after
completion.

1114

Do you want to unpack log entries made (y/n)?

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

Enter N. All necessary information is logged into the tamftp.log on


the workstation. You do not need to duplicate this information on
the enterpriser server.
5. When you press Enter following the last question above, the tamftp
program begins to execute and displays the following message:
OneWorld TAM FTP in progress...
When the tamftp program executes, the following message appears:
The spec copy is done.
Press the Enter key to quit.
6. Press Enter.
7. Review the tamftp log in the location you specified for results (for
example, c:\).
8. Move the dddict and ddtext specification files from the target directory on
the enterprise server to each path code spec directory (for example,
DEV733\spec).

Expanding the Distribution Flexible Files


If you are running OneWorld in coexistence with WorldSoftware, you must
expand the following distribution flexible files to include all fields:


F42019

F42119

F42199

F43199

Perform the following task from WorldSoftware, not from OneWorld.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1115

Installation Guide

To expand the distribution flexible files

Labor Hours

Variable, depending on the number of files

Computer Hours

Variable, depending on the number of files

Personnel

Installer

Logon status

On the AS/400, in WorldSoftware.

Prerequisites

None

Concurrent Tasks

None

1. In WorldSoftware, access the Flexible File Definition menu (G43A312).


2. Choose a distribution flexible file through Processing Options.
3. To display a list of available fields, choose the Define option.
4. Verify that the second processing option refers to the library containing the
flexible file.
5. Verify that all fields are preceded by option number 4.
6. If all fields are correct, press F3 to exit the program and continue with the
next flexible file.
If any option field is not set to 4:


In all option fields for that flexible file, type 4.

To create the necessary information for rebuilding the file, press F6.

The system displays the menu again.


7. To submit a batch job to rebuild the flexible file and related programs,
choose the Rebuild option for the file.
8. Verify the following processing options:


Enter the library which contains the flexible file.


Type the library name that you specified or verified in step 4.

Enter the library which contains the JDE programs. (Default of blank
will use the object library in the QJDF data area.)
Type the library where J.D. Edwards programs are located.

9. To verify that no errors occurred, access the job log.


1116

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

10. To exit the program and continue with the next flexible file, press F3.

Updating the Ledger Type Master File (F0025) - P09940


If you are running OneWorld in coexistence with WorldSoftware, you must
update the Ledger Type Master file (F0025) in WorldSoftware after you install
OneWorld.
Program P09940 should exist in the environment where you installed
A73PC000X0 on the AS/400, where the production version of your User Defined
Codes resides.
To update the Ledger Type Master file (F0025) P09940

Labor Hours
Computer Hours
Personnel

Less than 0.25


0.25
Installer

Logon status

On the AS/400, in WorldSoftware.

Prerequisites

Program P09940 should exist in the environment where you


installed A73PC000X0 on the AS/400, where the production
version of your User Defined Codes resides.

Concurrent Tasks

None

1. In WorldSoftware, access the Global Updates menu (G09316).


2. Choose Update Ledger Type.
The program analyzes the values in the following User Defined Codes
tables:


09/LT

09/LP

09/LA

00/LT

11/TL

The program also updates the new Ledger Type Master file (F0025) with
the correct values. OneWorld uses the Ledger Type Master file for editing
and posting.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1117

Installation Guide

Running the Accounts Receivable Conversion Process


If you choose to use the OneWorld Accounts Receivable system, you must
convert your existing WorldSoftware to OneWorld before you use the accounts
receivable database. The following sections explain more about the accounts
receivable conversion process.

Conversion Audit Envelope


The Conversion Audit Envelope automates the process of checking the integrity
of converted accounts receivable data. This automated process includes a series
of jobs that help track balances within the accounts receivable data files. It builds
balances by customer, company, and transaction currency for both
WorldSoftware and OneWorld systems. A report compares these balances, and
you can investigate accounts that could have problems with data integrity.
The Conversion Audit Envelope process, which is a segment of the overall A/R
conversion process, includes the following:


WorldSoftware Build (P03960)

OneWorld Build (P039601)

Conversion Audit Report (P03961), which processes the data the Build
program supplies to the work file

Work File Build Programs


Each build program includes processing options that allow you to choose
records from the A/R Ledger files you want to build into a work file (F03960).
The Build programs summarize the balances of the records you choose into a
single record, and then place the record into the work file. The system
summarizes records that have the same Customer Number, Company, and
Transaction Currency. The build programs create corresponding records from
each system and place them into the same work file. The result is two identical
sets of records (one for WorldSoftware and another for OneWorld) in the work
file.

Reporting Process
The report (P03961) compares the two records in the work file and prints both if
a discrepancy exists. This process lets you build the work file over the entire
database, but print only the records you choose. Through an option, you can
print all records in the work file or only those records that have discrepancies.
After a discrepancy is identified, you can rebuild the work file for a particular
customer at a detailed document level. The original document and its associated
matching documents are summarized into a single record in the work file. This

1118

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

lets you further isolate a discrepancy. The build programs delete only those
records that will be rebuilt, which allows you to rebuild a work file for one
customer without affecting the rest of the database.
Technical Considerations
WorldSoftware and OneWorld systems write chargeback records differently.
When the WorldSoftware system creates a chargeback record, the original
invoice (RI document) includes a chargeback matching document (RB). The
system uses the matching document to close the invoice.
The chargeback matching document (RB) does not exist in OneWorld. It is
replaced by the Chargeback Amount field. For this reason, there is a possible
discrepancy when you process the Conversion Audit Envelope at the
document level. You can see the discrepancy in the Payment and Chargeback
columns on the RB record. The discrepancy is offset on the record with the
original invoice record totals.

Before You Begin


Before you run the accounts receivable conversion process, do the following:
- Verify that for Release A7.3, you have installed the correct cumulative
update as well as the correct coexistence update (contact J.D. Edwards for
current information). This step is for customers who coexist with
WorldSoftware and OneWorld products other than accounts receivable.
- Verify that you are installing the most recent OneWorld release level
software.
- Finish processing all batch cash (auto cash) transactions and all accounts
receivable automatic debiting transactions.
- Finish processing any accounts receivable tape files on the system.

See Also


Batch Invoice Processing" and Automatic Debits" in the Accounts


Receivable Guide if you use auto cash.

A/R Conversion Process" in the Accounts Receivable Guide for detailed


information about the accounts receivable conversion process, including a
database diagram of WorldSoftware and OneWorld A/R files.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1119

Installation Guide

To run the accounts receivable conversion process

Labor Hours

12

Computer Hours

12

Personnel

Installer or system administrator

Logon status

On OneWorld, logged on as user JDE with the database


password for user JDE.

Prerequisites

None

Concurrent Tasks

None

The following steps are required unless otherwise indicated. J.D. Edwards
recommends that you complete all of the steps.
1. To prepare your accounts receivable data for conversion, post all A/R
batches for invoices, receipts, drafts, and balance forwards to the General
Ledger. This includes the following batch types:


Invoices (batch type I)

Receipts (batch type R)

Drafts (batch types * and &)

Balance forwards (batch type F)

2. In WorldSoftware, access the A/R AS/400 to OneWorld Conversion menu


(G0332) and run the A/R integrity report. Choose A/R to G/L by Batch.
Resolve any existing data issues.
3. On menu G0332, submit Convert Promises to Actv. Log. This job converts
PPAT Promises, Promises messages to the OneWorld Activity Log.


Submit the A/R batch conversion. This job converts the A/R batch
types in the General Ledger (F0911) and Batch Control (F0011)
tables.

Submit the Convert F03012 to Company 00000 (17/G0332).

Submitting these jobs while you run other conversion jobs for your A/R
tables will shorten the time of the conversion.
4. To build the conversion audit data for WorldSoftware, choose World A/R
Audit Build (5/G0332). This step is not required.
5. To convert the A/R Ledger invoice data, choose F0311 A/R Ledger
Conv/F03B11 (6/G0332).

1120

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

6. To convert the A/R Ledger receipts data, choose F0311 A/R Ledger
Conv/F03B14. (7/G0332). Wait until step 5 completes before submitting
this job.
7. To build the conversion audit data for OneWorld, choose OneWorld A/R
Audit Build (8/G0332). This step is not required. Wait until step 6
completes before submitting this job.
8. To check for data discrepancies, choose Conversion Audit Report
(9/G0332). This step is not required. You must complete the
WorldSoftware A/R Audit Build (5/G0332) and OneWorld A/R Audit Build
(8/G0332) before running this report.
9. To convert the generic text messages, choose F0016 Generic Text
Conversion (15/G0332).
10. To run the OneWorld Release Update jobs, log on to OneWorld and go to
the Batch Versions menu (GH905). Run R9603B11 and R9603B13.
11. Verify that system 03B has 10 Next Numbers indexes. The first nine should
be duplicated from system 03 Next Numbers.

Running the R4094A Batch Application


If you use OneWorld Inventory Management (system 41) or OneWorld Sales
Order Management (system 42), you must run the R4094A batch application,
version XJDE0001. This batch application inserts a record used by the Base Price
System into the F4094 table.
To run the R4094A batch application

Labor Hours

Variable, depending on the number of unique Business Data


data sources

Computer Hours

Variable, depending on the number of unique Business Data


data sources

Personnel

Installer, with update privileges.

Logon status

Logged on to the workstation as user JDE with the database


password for user JDE.

Prerequisites

None

Concurrent Tasks

None

1. Log on to OneWorld.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1121

Installation Guide

To perform this task, the user must have privileges to update the F4094
table.
2. For each environment that has a unique Business Data data source, run
the R4049A batch application, using versions XJDE0001.
This batch application does not generate a report.

Building Menu and Task Word Search Tables


The Menu Word Search Build program populates the Menu Word Search table
(F91013) from information in the menu tables (F00821 and F0083). The Task
Word Search Build program populates the Task Word Search table (F91014) from
information in the Task Master table (F9000) and Word Search Ignore Word table
(F91012).
Word Search helps you locate a OneWorld menu or task if you do not know its
name. The installation of these tables is optional.
When you run the Word Search Build programs, the system locates the menu or
task and word search tables for the environment you are logged on to.
If you follow the J.D. Edwards recommended environment builds during
installation, you build the Word Search tables using one or a combination of the
PD7333, PY7333, DV7333, and JD7333 environments.
The complete Word Search Build is approximately 7.5 MB. The batch process
can take several hours to complete.
To build Menu Word Search tables

Labor Hours
Computer Hours
Personnel

0.25
0.5 or more
Installer or system administrator

Logon status

Logged on to the OneWorld environment that points to your


pristine or publisher copy of your menus.

Prerequisites

The upgrade completed successfully.

Concurrent Tasks

None

1. Log on to the OneWorld environment that points to your pristine or


publisher copy of your menus. This environment would typically map
your menus to the data source Control Tables - Prod," the data source
where the Menu Word Search master table resides. Use an environment

1122

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

that points to your local workstation only if you have very recently
installed OneWorld; otherwise, you could be building from outofdate
menus.
2. On System Administration Tools (GH9011), choose Batch Versions
(P98305). The Work with Batch Versions form appears.
3. Type R95012 in the Batch Application field. This is the name of the batch
process that updates the Menu Word Search table.
4. Click Find to locate the versions available on your workstation.
5. Choose version XJDE0001, Build Menu Word Search Table, and click
Select.
The Version Prompting form appears. You can submit your job without
selecting any options on Version Prompting. However, if you want, from
Version Prompting you can specify Data Selection and Data Sequencing
and access the Advanced Version Prompting form.
6. Click Submit to send your job to the report processing location. If you
choose any options on Version Prompting, forms appear that allow you to
modify your report before processing.
7. On the Processing Options form, complete the following field:
Option 1
Enter 1 to clear the Menu Word Search table before you rebuild it (this is
recommended), or enter 0 or leave the field blank to not clear the table.
Make sure you have a backup of the table before you clear it.
The system takes the menu information from the Object Configuration
Management mappings on the environment you are logged onto and populates
the Menu Word Search table (F91013).
To build Task Word Search tables

Labor Hours
Computer Hours
Personnel

0.25
0.5 or more
Installer or system administrator

Logon status

Logged on to the OneWorld environment that points to your


pristine or publisher copy of your tasks.

Prerequisites

The upgrade completed successfully.

Concurrent Tasks

OneWorld Xe UPDATE (8 February 2002)

None

Installation for AS/400 Systems

1123

Installation Guide

1. Log on to the OneWorld environment that points to your pristine or


publisher copy of your tasks. This environment would typically map your
tasks to the data source Control Tables - Prod," the data source where
the Task Word Search master table resides. Use an environment that points
to your local workstation only if you have very recently installed
OneWorld; otherwise, you could be building from outofdate tasks.
2. On System Administration Tools (GH9011), choose Batch Versions
(P98305). The Work with Batch Versions form appears.
3. Type R91014 in the Batch Application field. This is the name of the batch
process that updates the Task Word Search table.
4. Click Find to locate the versions available on your workstation.
5. Choose version XJDE0001, Build Task Word Search Table, and click Select.
The Version Prompting form appears. You can submit your job without
selecting any options on Version Prompting. However, if you want, from
Version Prompting you can specify Data Selection and Data Sequencing
and access the Advanced Version Prompting form.
6. Click Submit to send your job to the report processing location.
The system takes the task information from the Object Configuration
Management mappings on the environment you are logged onto and populates
the Task Word Search table (F91014).

Configuring OneWorld to Run Autopilot (J.D. Edwards OneWorld


Scripting Tool)
The J.D. Edwards OneWorld Scripting Tool, also called Autopilot, is an
automated testing tool you can use to create scripts to test the execution of
OneWorld applications. Autopilot is included on the OneWorld installation
media; it is activated through purchase from J.D. Edwards. For more information
about purchasing Autopilot, contact your J.D. Edwards representative. If you
have not purchased Autopilot, skip this procedure.
For information about configuring Autopilot, see the J.D. Edwards OneWorld
Scripting Tool (Autopilot) Installation Guide.
To run Autopilot after it is installed, an ODBC data source must exist in the
ODBCDatasource.inf file that is installed on client workstations. You create the
data source in OneWorld, and then you create the corresponding ODBC data
source.
This procedure applies to Oracle databases only. The ODBC data source
and corresponding entry in the ODBCDatasource.inf file exists for SQL, AS/400,
and DB2 UDB platforms.
1124

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

To configure OneWorld to run Autopilot

Labor Hours

.25

Computer Hours

.25

Personnel

Installer

Logon status

In OneWorld, logged on as user JDE with the database


password for user JDE.

Prerequisites

Autopilot installed on this workstation.

Concurrent Tasks

None

To create the ODBC data source:


1. Log on to JDEPLAN on the deployment server as user JDE with the
database password for user JDE.
2. In the fast path, type GH9611.
3. Select Database Data Sources.

4. On Machine Search and Select, select data source OneWorld Planner B7333.
5. On Work with Data Sources, click Add.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1125

Installation Guide

6. On Data Source Revisions, add a data source with the following


information:
Data Source Use

DB

Data Source Name

Oracle_database_connectstring

Data Source Type

O [for Oracle]

Object Owner ID

sys7333

Library Name
Library List Name
DLL Name

JDBOCI80.DLL

Database Name

Oracle_database_connectstring [same
as Data Source Name, above]

Server Name

enterprise_server_name

Platform

server_platform

7. Click OK.
8. On Work with Data Sources, highlight the new Data Source and select
ODBC Data Source (on the menu bar), Row, ODBC Data Source.

1126

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Modifying OneWorld After the Installation

9. On Create New Data Source, select System Data Source and click Next.

10. On Create New Data Source, select a driver and click Next. (Microsoft
ODBC for Oracle is recommended. If you do not have this driver, consult
your database administrator.)

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1127

Installation Guide

11. Click Finish.

12. On Microsoft ODBC for Oracle Setup, the Data Source Name will default
to the selected data source. Enter the name of your Enterprise Server in
the Server field.
13. Click OK. The data source is added to the ODBCDatasource.inf file,
located in the /b7333/client directory.

1128

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Setting Up the Solution Explorer

The Solution Explorer (also known as ActivEra) is the windowsbased interface


that provides access to OneWorld applications, rolebased menus,
implementation and configuration options, documentation, and training
materials. Like OneWorld Explorer, the Solution Explorer provides you with a
convenient window into OneWorld.
Users can access the Solution Explorer to search and navigate quickly through
OneWorld applications. Users can also customize the Solution Explorer to create
their own tasks and link tasks to other webbased information.
For more information about the Solution Explorer, see the OneWorld Solution
Accelerator Suite Implementation guide.
This section includes the following installation tasks:
- Setting Up the Solution Explorer HTML documentation path
- Running the Word Search Generation program
- Setting Up the home page for the Solution Explorer

Setting Up the Solution Explorer HTML Documentation Path


When OneWorld is installed, the system automatically stores HTML
documentation hierarchically in folders located in a common documentation
directory. Using Media Object Queues, the Explorer locates these files and
displays the associated documentation in its own window whenever a user
selects a task.
The file path from the Explorer to the HTML documentation files is defined in
the Media Object Queue (F98MOQUE) table, and must be configured by
accessing the corresponding program called Work with Media Object Queues
(P98MOQUE). When OneWorld installs the documentation files, it creates an
entry in the Media Object Queue table that associates the Queue Name called
ActivEraData with a generic path to the documentation. In order for the Explorer
to associate each HTML file with the correct task, you must open this program
and change the server name for the directory path associated with the Queue
Name ActivEraData. The directory path has the structure
\\servername\B7333\ActivEra\Data, where servername is the name of your
server.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1129

Installation Guide

When the Queue Name ActivEraData is correctly mapped to the main HTML
documentation directory, the Explorer locates and displays the associated
documentation when a user accesses a Task Location or Task View Location. For
example, if a task named JDE001234 exists, the path to the HTML file of the
summary document for this task is
\\DEPSVR1\B7333\ActivEra\Data\JDE001234\summary.html, where DEPSVR1 is
the name of the deployment server.
For more information on setting up the documentation path, see Modifying
Media Object Queues" in the chapter Completing the Upgrade/Installation" in
the OneWorld Installation Guide or the OneWorld Upgrade Guide.

Running the Word Search Generation Program


The Find It! program is part of the Solution Explorer search feature that allows
you to search for a Solution Explorer task by entering a complete or partial Task
Name. For the Find It! Program to work, you must run the Word Search
generation program (R91014 with version XJDE0001). This UBE populates the list
of complete and partial Task Names used by the Find It! program. The Find It!
word search mechanism is the same as the one used for menu word search.
To install the Word Search generation program

Labor Hours
Computer Hours
Personnel

0.25
1.0
Installer

Logon status

In OneWorld, logged on as user JDE with the database


password for user JDE.

Prerequisites

The installation must be complete and the OneWorld menus


converted into Solution Explorer data.

Concurrent Tasks

None.

14. In OneWorld Explorer, type BV in the Fast Path and press Enter.
15. Go to Batch Versions List Application.
16. Perform a Find on R91014.
17. Doubleclick version XJDE0001 to run it.
18. On Processing Options, type 1 to clear the current list and eliminate
changed or deleted Task Names, or leave it blank to just add names to the
existing list.

1130

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Setting Up the Solution Explorer

Setting Up the Home Page for the Solution Explorer


The Home Page is generally the first screen a user sees when logging into the
Solution Explorer. This screen can be used to display information relevant to end
users in the enterprise. It can be an external web site, an intranet site, or even
HTML files stored on any server on the network.
During the installation process, a directory called PortalLite is created when the
deployment server is installed. This directory resides in the
<baseinstall>\ActivEra\PortalLite directory and includes a set of html files that
make up the default Home Page. Even though this directory is on the
deployment server, it can reside anywhere on the networ, such as on a web
server or even locally on a workstation.
When the OneWorld client is installed, the system updates the client jde.ini to
point to the location of the PortaLite directory. For example, if the name of the
deployment server is DepServer1" and the share name is B7333," the [Explorer]
section of the jde.ini is updated as follows:
[Explorer]
ExplorerHomeURL=\\DepServer1\b7333\activera\portallit
e\index.html
ExplorerStart=INTERNET
You can change the above parameters in the jde.ini file to display any html file
or URL as the default Home Page. The table below describes these parameters:
[Explorer] Parameter

Description

ExplorerHomeURL=

URL or filename of the Home Page that is displayed when


the user logs on. By default, the initial page is

\\Depserver1\b7333\activera\portalite\index.html
ExplorerStart=

Valid values are:


INTERNET: This is the default value. When you start the
Solution Explorer, it displays the internet view first.
TASK: When you start the Solution Explorer, it displays the
last task view the user viewed. To display a specific task
view, set ExplorerStart=TASK:xx, where xx is the task
view's task ID.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1131

Installation Guide

1132

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring OneWorld for Use with Vertex Quantum


Tax Applications

This chapter describes how to configure OneWorld to use the Vertex Quantum
tax applications. If you do not use these applications with OneWorld, you can
skip this chapter.
OneWorld can be used with the following Vertex Quantum tax applications:


Vertex Quantum for Payroll Tax

Vertex Quantum for Sales and Use Tax

The Vertex Quantum applications should be installed on your system before you
start the configuration tasks. For information about installing the applications,
see the publications listed under See Also," below.
This chapter comprises the following tasks:
- Configuring the OneWorld database connections for Vertex Quantum tax
applications
- Checking the mapping of objects to the enterprise server
- Testing the Vertex Quantum connection from OneWorld

See Also
For information about installing the applications, see one or both of the
following publications:


Vertex Quantum for Payroll Tax - Administrator's Guide

Vertex Quantum for Sales and Use Tax - Administrator's Guide

Before You Begin


Before configuring OneWorld for use with Vertex Quantum applications, install
Vertex Quantum for Payroll Tax, or Vertex Quantum for Sales and Use Tax, or
both, on the enterprise server. For information about installing the Vertex
Quantum applications, refer to the Vertex Quantum administration guides listed
above.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1133

Installation Guide

When you install the Vertex Quantum applications, note the following:


If you are using the Vertex ISAM database, note the directory path on the
enterprise server for the directory or directories in which the Vertex
Quantum application databases are created. This information will be
needed for establishing OneWorld database connectivity.

Configuring the OneWorld Database Connections for Vertex


Quantum Tax Applications
Use the following procedure to configure OneWorld database connections to use
the Vertex Quantum applications.
To configure the OneWorld database connections for Vertex
Quantum tax applications

Labor Hours

0.25

Computer Hours

0.25

Personnel

Installer

Logon status

Logged on to OneWorld.

Prerequisites

None

Concurrent Tasks

None

1. In OneWorld, go to Vertex Quantum Tax Processing, G731 (in the Fast


Path, type G731). The Vertex Quantum Tax Processing panel appears.
2. Highlight Database Connections (P7308), and click the right mouse button.
A context menu appears.
3. From the context menu, choose Prompt for Values. The Processing
Options dialog appears.
4. On Processing Options, Quantum tab, enter the following information:


Option #1: Enter which Vertex Quantum applications are installed:


[blank]
Both Vertex Quantum tax applications are installed.
1
The Vertex Quantum for Sales and Use Tax application is installed.

1134

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring OneWorld for Use with Vertex Quantum Tax Applications

2
The Vertex Quantum for Payroll Tax application is installed.


Option #2: Enter location information for the databases:


[blank]
Databases for both Vertex Quantum tax applications are in the same
location.
1
Databases for the Vertex Quantum for Payroll Tax and Vertex
Quantum for Sales and Use Tax applications are in separate
locations.
2
Databases for the Vertex Quantum for Payroll Tax and Vertex
Quantum for Sales and Use Tax applications are in separate
locations, and the four databases for the Vertex Quantum for Sales
and Use Tax application are in separate locations.

Option #3: If Processing Option #2 is set to 1 or 2 (i.e., if the Vertex


databases are in separate locations), specify the GeoCode database
location information:
[blank]
The Vertex Quantum Payroll Tax and Sales and Use Tax applications
will use the same GeoCode database.
1
Each of the Vertex applications will use a separate copy of the
GeoCode database, and the two copies are in separate locations.

5. Click OK. The Vertex Quantum Database Connection panel is displayed.


The Database Connection panel contains one or more tabs corresponding
to the database connections that must be defined. The tabs displayed are
determined by the values you entered in the processing options, in Step 4,
above.
Note that the GeoCode database is the only Vertex Quantum database that
can be shared between the Vertex Quantum Payroll Tax and Sales and Use
Tax applications. However, all of the Vertex Quantum databases can be
installed in the same location, or in different locations.
One or more of the following tabs appears on the Database Connection
panel:


All - All Vertex Quantum application databases for both applications


are located on the same server and in the same location.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1135

Installation Guide

GeoCode - The same GeoCode database is used by both


applications.

GeoCode-Sales and Use - The GeoCode database used by the Sales


and Use Tax application is located on this server and location. A
separate copy of the GeoCode database, at another location, is used
by the Payroll Tax application.

GeoCode-Payroll - The GeoCode database used by the Payroll Tax


application is located on this server and location. A separate copy of
the GeoCode database, at another location, is used by the Sales and
Use Tax application.

Sales and Use - The four databases used by the Sales and Use Tax
application are located together, on this server and location.

TDM - The TDM database, used by the Sales and Use Tax
application, is located on this server and location.

Register - The Register database, used by the Sales and Use Tax
application, is located on this server and location.

Rate - The Rate database, used by the Sales and Use Tax
application, is located on this server and location.

Payroll - The databases used by the Payroll Tax application are


located on this server and location.

6. On the Database Connection panel, select each of the tabs displayed, and
enter the following information:


Data Source
Enter the name of the library where the Vertex Quantum tables are
located. The location you enter should be the location on the server
used for the database when the Vertex applications were installed
(see Before You Begin," above).

Server
The name of the AS/400 machine where the Vertex Quantum tables
are located.

User ID
A user ID that can access the database.

Password
The password for the user ID specified above.

7. Via the form exit, use the form AS/400 Library to specify the Vertex
Quantum library that contains the Vertex Quantum APIs. For Vertex
Quantum for Sales and Use Tax, this library is typically called VERQSU.

1136

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring OneWorld for Use with Vertex Quantum Tax Applications

For Vertex Quantum for Payroll Tax, this library is typically called
VERQPRT.
8. Click OK. Changes don't take effect until you have logged off of your
system and logged back on.

Mapping Objects to the Enterprise Server


Objects that call the Vertex Quantum APIs must execute on the server on which
the Vertex Quantum APIs reside. Check that the following OneWorld objects are
configured in the system OCM to execute on the server. Do not change the
mappings:
For Vertex Quantum for Payroll Tax:


R07200 (Pre-payroll Driver)

B0700058

For Vertex Quantum for Sales and Use Tax:




X00TAX.c (Tax Calculator)

B7300002 (Validate Quantum GeoCodes)

B7300004 (Retrieve Quantum GeoCodes)

B7300012 (Validate Quantum Software Information)

B000182

B000183

Testing the Vertex Quantum Connection from OneWorld


Use the following procedures to test the Vertex Quantum connection from
OneWorld.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1137

Installation Guide

To test the Vertex Quantum connection from OneWorld

Labor Hours

0.50

Computer Hours

0.50

Personnel

Installer

Logon status

Logged on to OneWorld.

Prerequisites

None

Concurrent Tasks

None

For the Vertex Quantum for Payroll Tax interface:


1. Go to the Payroll Workbench menu (G07BUSP11) and choose Pay Cycle
Workbench. The Work with Payroll Cycle Workbench panel appears.
2. Specify pre-payroll information and submit the pre-payroll.
For information about the Payroll Workbench and submitting pre-payroll,
see Processing Pre-Payroll" in the OneWorld Payroll guide.
3. If no taxes are being calculated, there may be a setup or configuration
problem. Verify the following to make sure setup is correct:


UBE R07200 is being executed on the server where the Vertex


Quantum for Payroll Tax APIs reside.

Correct values are assigned to the Data Source, Server, User ID, and
Password fields on the Database Connection panel, as specified in
Configuring the OneWorld Database Connections for Vertex
Quantum Applications" in this chapter.

For the Vertex Quantum for Sales and Use Tax interface:
1. In the Fast Path, type P73GEO and press Enter. The Retrieve GeoCode
panel appears.
2. On the Retrieve GeoCode panel, enter CO in the State field and DENVER
in the City field, and click Find. The code 060310140 should appear in the
grid.
3. If nothing is displayed in the grid, there may be a setup or configuration
problem. Verify the following to make sure setup is correct:


1138

The following values are set in the Work with Quantum Constants
Revision table, accessed by the Constants application (P7306) on
menu G731:

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Configuring OneWorld for Use with Vertex Quantum Tax Applications

Quantum Active: Y
Canada Country Code: CA
Note that changes to the Work with Quantum Constants Revision
table don't take effect until you have logged off of your system and
logged back on.


Required OneWorld objects are mapped to the server where the


Vertex Quantum for Sales and Use Tax APIs reside, as specified in
Mapping Objects to the Enterprise Server" in this chapter.

Correct values are assigned to the Data Source, Server, User ID, and
Password fields on the Database Connection panel, as specified in
Configuring the OneWorld Database Connections for Vertex
Quantum Applications" in this chapter.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1139

Installation Guide

1140

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installation Planner Utilities


This section contains the following tasks:
- Creating a remote installation plan
- Adding a server to an existing configuration
- Reviewing Installation Planner processing options
- Deleting pieces of an installation plan
- Creating a languageonly installation plan

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

121

Installation Guide

122

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

This chapter consists of the following tasks:


- Understanding a remote installation plan
- Starting Installation Planner
- Entering information into Installation Planner
- Entering plan location information
- Specifying a deployment server
- Specifying an enterprise server
- Defining machine/server types
- Choosing replication options
- Entering shared data source setup information
- Setting up environments
- Setting up environment data sources
- Concluding the remote installation plan setup
- Finalizing the installation plan
- Running the Validation Planner Report

Understanding a Remote Installation Plan


Installation Planner is a OneWorld application that runs on the deployment
server. It is a system administration tool that guides you through the process of
configuring the machines on which your company will run OneWorld.
If you want to set up OneWorld for a remote location, you need to create a plan
that includes remote locations. The tasks in this chapter assume you have
already created and completed a basic installation plan, and you are adding the

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

123

Installation Guide

remote locations to the configuration. This chapter also assumes that you have
chosen to install an alternate language.
The following graphic shows one option for setting up remote locations:
Primary Location
Denver

Tier One Location


Miami

Tier One Location


Atlanta

Tier N Location
Atlanta Sales

Tier N Location
Atlanta Development

Tier N Location
Miami Sales

In the graphic, Tier One and Tier N refer to secondary or multitier locations.
You can map business functions to run on the enterprise server for your base
location. You can set this up in your processing options for Installation Planner.
Before you begin, decide whether you want to use OneWorld replication.
OneWorld replication copies the System, Data Dictionary, control, constant, and
master tables to your remote location. If you want to use OneWorld replication,
review the processing options for the Installation Planner to make sure that they
are set correctly for replication.
The information that you provide on the Installation Planner forms, such as
database type and enterprise server type, determines the information that you
see on the remaining forms.

See Also

124

Running Installation Planner" for more information about installation


plans and related processing options

Reviewing Installation Planner Processing Options" for more information


about how the processing options for Installation Planner also affect the
choices that you are given while setting up your plan

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Data Source Considerations


J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.
Only data sources that are referenced in the replication screens appear when
you create a remote plan.
The forms appearing in this chapter assume SQL Server as the database on your
deployment server. If you use Oracle or DB2400, the information on your forms
differs from what is shown here.
Installation Planner Considerations
Depending on the tables that you want to replicate, you are prompted for
different data source information. For example, if you choose to replicate the
control tables, you are asked to define the control tables data source.

Assumptions about Defining a Remote Installation Plan


The following table outlines assumptions for the remote Installation Planner
phase as a whole. Individual tasks might have their own assumptions.
Labor Hours

Computer Hours

Personnel

Installer

Logon status

On the deployment server, log on to OneWorld as user JDE


with the database password for user JDE, in the planner
environment.

Prerequisites

Determine if you want to use OneWorld replication. Verify that


the deployment server has been installed and the OneWorld
directory is shared.

Concurrent Tasks

None

Starting Installation Planner


Begin your remote installation plan by logging on to OneWorld and starting
Installation Planner.
To start Installation Planner
1. Log on to OneWorld as user JDE with the database password for user JDE.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

125

Installation Guide

2. Access the planner environment (JDEPLAN).


3. From the System Installation Tools menu (GH961), click Custom
Installation.

4. On Work with Installation Plans, click Add.


The Installation Planner form appears.

Entering Information into Installation Planner


After starting Installation Planner, enter basic plan information, such as plan
name and description, installation type, and included languages (if any).

126

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

To enter information into Installation Planner

1. On Installation Planner, in Plan Information, complete the following fields:




Name
The name of your remote plan.

Description
The description of your remote plan.

Status
Choose 10 as the status of your remote plan.

Install Type
Click Install.

Coexistent with WorldSoftware


Check this option only if OneWorld is operating in a coexistent
environment.

To Release
Verify that the release number is B7333.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

127

Installation Guide

For an AS/400 coexistent environment, you may need to change the


release number.
2. Click OK.

Entering Plan Location Information


Once basic plan installation information is entered, enter a new plan location or
select an existing plan location.
To enter plan location information
The Location Revisions form appears.

1. On Location Revisions, enter the following information:




Location
Enter the place to which this plan applies. The location could be a
city, company headquarters, or a division of a company.

Description
Enter a description of the location name.

128

Location Code

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

For a remote location, enter a 3character alphanumeric


identification code. This 3character code is used as a prefix for the
remote location's environments, and a suffix is attached for
replicated data sources. For example, you might use DAL if the
location were Dallas, Texas. In that case, the prototype environment
would be named DALPY7333 and the business data data source
would be named Business Data CRPDAL.


Parent Location
For a remote location, enter the parent location to which this remote
location is attached.

2. Click OK.
The Deployment Server Revisions form appears.

Specifying a Deployment Server


Once a plan location is specified, complete the information for the deployment
server that you use in this plan. You are given the option to enter a new
deployment server or select an existing one. For most situations, you have a
tiered deployment server for the remote location.
Complete the following tasks:


Enter deployment server information

Conclude deployment server setup

To enter deployment server information


OneWorld asks if you want to enter new deployment server information.
1. Click OK to add a deployment server.
The Deployment Server Revisions form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

129

Installation Guide

2. In the top section of the Deployment Server Revisions form, complete the
following fields:


Machine Usage
The default value of 15 indicates that this is a deployment server.

Machine Name
Enter the name of your deployment server.

Description
Enter a description of the machine name. This name includes the
location with which this deployment server is associated, and
whether or not it is the primary server.

Release
Enter the OneWorld release number that you are installing, or use
the visual assist button to choose one from the list. For example,
B7333 is the current release.

Host Type
The field's default value of 50 indicates that the server type is an
Intel NT.

1210

Location

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

This field defaults to the location chosen for this plan.




Primary User
Identifies the user to whom email is sent when a package is
deployed. The default for primary user is located in the JDE.INI file.

3. On the Deployment tab, complete the following fields:




Primary Deployment Server


Indicates the hierarchy of the servers. Valid values are:
Value

Description

Primary deployment server

Secondary deployment server

Type O (zero) if there is already a primary deployment server for


the location and this is a secondary server.
Type 1 if this is the primary deployment server for the location.


Server Share Path


Enter the server share path where you installed OneWorld on your
deployment server. Make sure that this path is specific to your
version of the release. Example: For OneWorld B73.3.3, the path
ends with \b7333.

4. Click OK.
Troubleshooting
If you enter invalid information into a tab field, a red stop sign symbol
appears next to the tab name, such as deployment server. For more
information about the error, click on the red stop sign icon in the bottom
righthand corner of the form.
To conclude deployment server setup
1. OneWorld asks if you want to add another deployment server.


To add another deployment server, click Yes.


Repeat Specifying Deployment Server Information."

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1211

Installation Guide

To continue with Installation Planner setup, click No.


Continue with the next step.

2. OneWorld asks if you want to add an enterprise server.




To add an enterprise server, click OK.


Continue with Specifying an Enterprise Server."
Add an enterprise server if you are using OneWorld replication.

To skip the enterprise server setup and continue with remote


Installation Planner, click Skip.
Continue with Defining Machine/Server Types."

Specifying an Enterprise Server


Once you've specified the deployment server that you use in this plan, you can
add an enterprise server by ompleting the following processes:


Enter Enterprise Server Information

Enter Enterprise Server Data Source Information

Conclude Enterprise Server Setup

Entering Enterprise Server Information


Enter the base information for the enterprise server that you use in this plan.
To enter enterprise server information
The Enterprise Server Revisions form appears.

1212

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

1. On the top section of the Enterprise Server Revisions form, complete or


verify the following fields:


Machine Usage
The default value of 20 indicates that this is an enterprise server.

Machine Name
The name of your primary enterprise server. The name is
casesensitive.
Because of naming restrictions on the AS/400, this name cannot
exceed ten characters.

Description
Enter a description of the machine.

Release
Enter the OneWorld release number to which this plan applies, or
use the visual assist button to choose one from the list. For
example, enter B7333.

Host Type
Click the visual assist button and choose the type of enterprise
server that you are adding to the plan.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1213

Installation Guide

For example, AS/400.




Location
This field defaults to the location chosen for this plan.

Primary User
This field identifies the user to whom email is sent when a package
is deployed. The default for primary user is listed in the JDE.INI file.

2. On the Enterprise tab, complete the following fields:




Port Number
A value defaults into this field from the JDE.INI file. Change the port
number for this enterprise server to a unique value. For example,
6009.

Logical Machine Name


Information defaults into this field when you enter the host type.

Database Type
The type of database that you want to use for data sources on the
enterprise server. Enter a valid value:

Value

Database

Client Access Express

Server Map Data Source


Information defaults into this field when you enter the host type.

Installation Path
Enter the installation directory path where you want to install
OneWorld on your enterprise server. Make sure that this path is
specific to your version of the release.
Example: For release B73.3.3, this path ends with B7333SYS
the system library.

1214

Deployment Server Name

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Using the visual assist button, choose the name of the deployment
server to which this enterprise server is attached. A deployment
server name defaults into the field, but can be changed if necessary.
3. Click OK. A message box appears and asks you whether you want to
enter custom data sources or take the default data sources. Proceed to task
To specify custom or default data source information," below.

Entering Enterprise Server Data Source Information


After specifying enterprise server information, enter the data source information
for the enterprise server you will use in this plan.
Complete the following tasks:
- Specify custom or default data source information
- Verify server map source information
- Add another enterprise server
To specify custom or default data source information
OneWorld asks you whether you want to enter custom data sources or take the
default data sources for the enterprise server you just added. Select one of the
following options:


To enter custom data sources, click OK. Skip to To verify custom server
map source information."

If you clicked Take Defaults, continue with To add another enterprise
server."
If you are in a coexistent environment, do not take defaults for
AS/400.
To verify custom server map source information

The Data Source Setup form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1215

Installation Guide

1. On Data Source Setup, verify your Server Map data source information.
Data Source Considerations
J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.
2. Click OK.
To add another enterprise server
OneWorld asks if you want to add another enterprise server.
Select one of the following options:


To add another enterprise server, click Yes.


Repeat processes, starting with Entering Enterprise Server Information."
In a coexistent environment, do not add an additional enterprise server
that is not an AS/400. If you do so, the plan will create AS/400 data
sources on the second enterprise server. Instead, create a separate plan to
add non-AS/400 enterprise servers.

To continue with Installation Planner setup, click No.


The Machine/Server Types form appears.

1216

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Defining Machine/Server Types


You can define three machine/server types for your installation plan: data server,
Java server, and Windows terminal server. To define any or all of these server
types, complete the appropriate processes:


Specify machine/server types

Define a data server (if different from the enterprise server)

Define a OneWorld Java Server

Define a Windows Terminal server

Specify Machine/Server Types


Begin the machine/server definition process by specifying the type of
machine/server you wish to add to your installation plan.
To specify machine/server types

On the Machine/Server Types form, specify the machine/server types that you
want to define.


To add servers, check the desired server options, and then click OK.
Continue with the relevant tasks below.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1217

Installation Guide

If you do not want to add any of these servers, turn off (uncheck) these
options, click OK, and then proceed to Entering Shared Data Source
Setup Information."

Define a Data Server


To define a data server for your installation plan, perform the following task.
To define a data server
If you checked Data Server on the Machine/Server Types form, OneWorld
prompts you to define your data server.
1. Click OK to continue.
The Data Server Revisions screen appears.

1. On the Data Server Revisions form, complete the following fields in the
top section:
You need to add a data server if your Central Objects are other than
Client Access Express on the AS/400.


Machine Usage
The default value of 25 indicates that this is a data server.

1218

Machine Name

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Enter the name of your data server.




Description
Enter a description of the machine.

Release
Enter the OneWorld release number you are installing. For example,
enter B7333.

Host Type
Choose the type of data server that you are adding to the plan. Valid
values are:

Value

Database

10

AS/400

20

HP 9000

25

Sun Solaris

30

RS/6000

50

Intel NT

Location
This field defaults to the location chosen for this plan.

Primary User
This field identifies the user to whom email is sent once a package
is deployed. The default for primary user is listed in the JDE.INI file.

2. On the Data tab, complete the following field:




Data Source Type


Choose the type of data source. Valid values are:
Value

Database

Client Access Express

SQL Server

3. Click OK.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1219

Installation Guide

OneWorld asks if you want to add another data server:


4. Select one of the following options:


To add another data server, click Yes.


Repeat the steps in To define a data server."

To continue with remote Installation Planner setup, click No.

Define a Java Server


To define a Java server for your installation plan, perform the following task.
To define a OneWorld Java Server
If you checked JAS Server on the Machine/Server Types form, OneWorld
prompts you to define your JAS server.
1. Click OK to continue.
The JAS Server Revisions form appears.

1. On JAS Server Revisions, complete the following fields in the top section
of the form:


1220

Machine Usage

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

The default value of 30 indicates this is a Java Application Server.




Machine Name
Enter the name of your Java Application Server. The name is
casesensitive.

Description
Enter a description of the machine.

Release
Enter the OneWorld release number you are installing. For example,
enter B7333. You might need to manually change the release.

Host Type
The default value of 50 indicates the server type as Intel NT.

Location
This field defaults to the location chosen for this plan.

Primary User
This field identifies the user to whom email is sent when a package
is deployed. The default for primary user is listed in the JDE.INI file.

2. On the JAS tab, complete the following fields:




Installation Path
Enter the installation directory path where you want to install
OneWorld on your JAS server. Make sure this is specific to your
version of the release. Example: For OneWorld B73.3.3, the path
ends with \b7333.

3. Click OK.
OneWorld asks if you want to add another Java server:
4. Select one of the following options:


To add another Java server, click Yes.


Repeat the steps in To define a JAS server."

To continue with remote Installation Planner setup, click No.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1221

Installation Guide

Define a Windows Terminal Server


To define a Windows Terminal server for your installation plan, perform the
following task.
To define a Windows Terminal server
If you checked WTS Server on the Machine/Server Types form, OneWorld
prompts you to define your WTS server.
1. Click OK to continue.
The WTS Server Revisions form appears.

1. On the WTS Server Revisions form, complete the following fields in the
top section:


Machine Usage
The default value of 35 indicates this is a Windows terminal server.

Machine Name
Enter the name of your Windows terminal server. The name is
casesensitive.

1222

Description

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Enter a description of the machine.




Release
Enter the OneWorld release number you are installing. For example,
enter B7333. You might need to manually change the release.

Host Type
The default value of 50 indicates that the server type is Intel NT.

Location
This field defaults to your current location.

Primary User
This field identifies the user to whom email is sent when a package
is deployed. The default for primary user is listed in the JDE.INI file.

2. On the WTS tab, complete the following fields:




Installation Path
Enter the installation directory path to which you want to install
OneWorld on your Windows terminal server. Make sure this is
specific to your version of the release. For example, the path could
end with \b7.

3. Click OK.
OneWorld asks if you want to add another Windows Terminal server:
4. Select one of the following options:


To add another Windows Terminal server, click Yes.


Repeat the steps in To define a WTS server."

To continue with remote Installation Planner setup, click No.

Choosing Replication Options


After concluding Machine/Server Type setup, use the following process to
choose options for replicating data.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1223

Installation Guide

To choose replication options


The Replication form appears.

1. On Control/System Replication, Replication Setup tab, choose from the


following options to replicate information to remote locations:


Use OneWorld Replication


Turn on (check) this option to use OneWorld's replication features.
Turn off (uncheck) the option if you do not want to use OneWorld
replication and want to use thirdparty replication.

Replicate System Tables


Turn on (check) this option to replicate the System tables
automatically. No additional steps are required on your part.
Turn off (uncheck) the option if you do not want to replicate the
System tables.

Replicate Data Dictionary Tables


Turn on (check) this option to replicate the data dictionary tables
automatically. Data sources and OCM mappings are set up also. No
additional steps are required on your part.

1224

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Turn off (uncheck) the option if you do not want to replicate the
data dictionary tables.
2. Click the Replication Load tab.

1. On the Replication Load tab, choose from the following options to copy
selected tables to the remote locations.


Load System Tables


Turn on (check) this option to automatically copy the system tables
from the base to the remote locations.
Turn off (uncheck) the option if you do not want to automatically
copy the system tables.

Load Data Dictionary Tables


Turn on (check) this option to automatically copy the Data
Dictionary tables from the base to the remote locations.
Turn off (uncheck) the option if you do not want to automatically
copy the Data Dictionary tables.
You can edit or change the versions of R98403 that copy the System
tables and Data Dictionary tables by clicking the Edit or Search
buttons next to their respective Versions.

2. Click OK.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1225

Installation Guide

Entering Shared Data Source Setup Information


To enter or confirm information for data sources that are shared across all of
your environments, complete the following tasks:


Specify (custom or default) shared data source setup information

Verify the Data Dictionary data source

Verify the System data source

To specify (custom or default) shared data source setup information


OneWorld prompts you for the data source information for the shared data
sources that you chose to replicate. Choose one of the following:


Click OK to enter the data sources.


Continue with To verify the Data Dictionary data source."

Click Take Defaults to accept the OneWorld default data sources. This
option limits your customization choices.
Recommended: Do not take defaults for AS/400.
To verify the Data Dictionary data source

The Data Dictionary Data Source Setup form appears.

1226

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

On Data Source Setup, verify the accuracy of the Data Dictionary data source,
and then click OK. The System Data Source Setup form appears.
The library name in the Library Name field is the OneWorld data
dictionary library (DD7333). It is not the WorldSoftware library that
contains your data dictionary files.
To verify the System data source

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1227

Installation Guide

On Data Source Setup, verify the accuracy of the settings for the System data
source, and then click OK.
If this is a DB2 UDB data source, the object owner ID will be SY7333, not
SYS7333." DB2 UDB does not allow a schema starting with the letters SYS."
For more information about System data source fields, or fields for other
data sources mentioned in this procedure, see Data Source Charts" in the
Installation Reference Guide.

Setting Up Environments
By default, OneWorld configures your system using values for typical
environments. Depending on the options you select when you set up your plan,
OneWorld displays one or more of the following parameters which you can
customize in the following tasks:


Environments

Data Load options

Advanced Parameters

Languages

Complete the following processes to specify default or custom selections for


your installation environments, data load options, advanced environment
parameters, and environment languages:


Specify (custom or default) environment parameters

Select an environment

Replicate information to remote locations

To specify (custom or default) environment parameters


The Environment Selection screen appears.

1228

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

1. On Environment Selection, accept the default or turn off (uncheck) the


option to enter your own environments.
2. Click OK.
3. Continue with To select an environment" below.
To select an environment
If you unchecked the default option, the Select Environment form appears.
Jxxxxxx environments appear if there is a Java Application Server in
the plan.
Wxxxxxx environments appear if there is a Windows terminal server
in the plan.
Tips and Techniques
You can only add or delete environments from the tree view of your plan.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1229

Installation Guide

On Select Environments, doubleclick the environment that you want to define.




To set up multiple environments, choose and define them one at a time.


To replicate information to remote locations
The Replication form appears.

1230

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

1. On Control/System Replication, Replication Setup tab, choose from the


following options to replicate information to remote locations:


Use OneWorld Replication


Turn on (check) this option to use OneWorld's replication features.
Turn off (uncheck) this option if you do not want to use OneWorld
replication and want to use thirdparty replication.

Replicate Control Tables


Turn on (check) this option to replicate the control tables
automatically. No additional steps are required on your part.
Turn off (uncheck) the option if you do not want to replicate the
control tables.

Replicate Constant Tables


Turn on (check) this option to replicate the constant tables
automatically. No additional steps are required on your part.
Turn off (uncheck) the option if you do not want to replicate the
constant tables.

Replicate Master Tables


Turn on (check) this option to replicate the master tables
automatically. No additional steps are required on your part.
Turn off (uncheck) the option if you do not want to replicate the
master tables.

2. Click the Replication Load tab.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1231

Installation Guide

3. Choose from the following to copy selected tables to the remote locations:


Load Control Tables


Turn on (check) this option to automatically copy the control tables
from the base to the remote locations.
Turn off (uncheck) the option if you do not want to automatically
copy the control tables.

Load Constant Tables


Turn on (check) this option to automatically copy the constant
tables from the base to the remote locations.
Turn off (uncheck) the option if you do not want to automatically
copy the constant tables.

Load Master Tables


Turn on (check) this option to automatically copy the master tables
from the base to the remote locations.
Turn off (uncheck) the option if you do not want to automatically
copy the master tables.
You can edit or change the versions of R98403 that copy the Control
Tables, Constant Tables, and Master tables by clicking the Edit or
Search buttons next to their respective versions.

1232

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

4. Click OK.

Setting Up Environment Data Sources


After specifying which tables to replicate, use the following processes to set up
environment data sources:


Begin the environment data source setup

Verify the Control Tables data source

Set up the Business Data data source

Select another environment

To begin the environment data source setup


OneWorld asks if you want to set up data sources for each environment that you
chose.
Select one of the following options.


To manually enter the data sources, click OK, and continue with To verify
the Control Tables data source" below.
If the environment that you selected is a coexistent with World, you
must click OK.

To accept the OneWorld default data sources, click Take Defaults, and
continue with To select another environment." This option limits your
customization choices.
To verify the Control Tables data source

If you chose to set up data sources, the Control Tables data source form
appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1233

Installation Guide

1. On Data Source Setup, verify your Control Tables data source.


2. When you ran Copy Plan, some field data changed to reflect release
B73.3.3 values. Change the following fields:


Data Source Type


Type I for Client Access Express.

AS/400 Database Name


Type the name of the data source (such as Control Tables
Testxxx).

3. Click OK.

1234

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

To set up the Business Data data source

1. From Data Source Setup, set up or verify the data source information for
your business data.
2. Be sure that this data source points to either the existing production data
source you want to upgrade or a copy of it. When you ran Copy Plan,
some field data changed to reflect release B73.3.3 values. Change the
following fields:


Data Source Type


Type I for Client Access Express.

AS/400 Database Name


Type the name of the data source (such as Business Data TEST).

3. Click OK.
The Select Environments form appears so you can define another
environment (if necessary).

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1235

Installation Guide

To select another environment

1. On Select Environments, choose the next environment that you want to


define.
2. Repeat all tasks in Setting up Environment" and Setting up Environment
Data Sources."
3. After defining all of your environments, click Close.
OneWorld displays the following window:

1236

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

OneWorld allows you to push delivered full packages to remote locations


when you run the Location Workbench.
4. Select one of the following options:


Click Yes to view a list of packages to push to the remote location.

Click Take Defaults to push all available packages to the remote


location. Continue with Concluding the Remote Installation Plan
Setup."

Click No if you do not want to push packages to the remote


location. Continue with Concluding the Remote Installation Plan
Setup."

If you click Yes, the Select Remote Location Packages screen appears:

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1237

Installation Guide

5. Choose a package from the list and click the Deselect icon in the Row
menu.
You can select or deselect a package by clicking the corresponding icon in
the Row menu.
6. Click Select to push the selected packages.

Concluding the Remote Installation Plan Setup


After concluding the environment setup, you can choose to enter another plan
location or finalize your remote installation plan.
To conclude the remote installation plan setup
OneWorld asks if you want to add another location.


To add another location, click Yes.


Repeat all tasks for adding a location, starting with Entering Plan Location
Information."

To conclude remote Installation Planner setup, click No.


Continue with Finalizing the Installation Plan" below.

1238

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Remote Installation Plan

Finalizing the Installation Plan


Installation Planner automatically finalizes your installation plan. This section
contains the following tasks:


Finalize the installation plan

Conclude the Validation Planner Report


To finalize the installation plan

1. A message appears to let you know that the installation plan has been
finalized.
When the plan is finalized:


The status is now set to 20. This value means that several
adjustments to OCM mappings and tables are made according to
your plan.

The following tables are now updated:


Release Master table (F00945)
Path Code Master table (F00942)
Package Plan table (F98404)
Machine Detail table (F9651)
Table Conversion Scheduler (F98405)
Language table (F984031) - if you are installing an alternate
language

2. To exit the concluding message box, click OK.


Clicking OK initiates the Planner Validation Report.


If processing option default was selected, Planner Validation Report


automatically prompts you to run this report.

If processing option default was not selected, on the tree view of


your plan, click Validate to initiate the Planner Validation Report.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1239

Installation Guide

To conclude Validation Planner Report


1. On Report Output Destination, choose On Screen or To Printer, and then
click OK.
2. Review the report to confirm that all records were validated.
3. After reviewing the report, on the Batch Versions form, click Close.
For more information about the Planner Validation Report, see Reports" in
the Installation Reference Guide.
4. On Work With Installation Plans, click Expand to review the plan that you
created.
5. Run Installation Workbench for this installation plan.
For more information about Installation Workbench, see Running
Installation Workbench."

1240

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

This chapter consists of the following tasks:


- Understanding adding a server to an existing configuration
- Starting Installation Planner
- Entering a plan description
- Entering a plan location
- Selecting additional server types
- Entering deployment server information
- Entering enterprise server information
- Defining a Java server
- Defining a Windows terminal server
- Setting up environments
- Finalizing the installation plan
- Configuring additional servers

Understanding Adding a Server to an Existing Configuration


This section contains the procedures for adding additional servers to your
configuration. Use these procedures only if you have already defined and run
your initial installation plan and set up your environments.
The forms appearing in this chapter assume you have SQL Server as the
database on your deployment server. If you have Oracle, the information on
your forms will differ from what is shown here.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1241

Installation Guide

Assumptions about Adding a Server to an Existing Installation Plan


The following table outlines assumptions for adding a server to an existing
Installation Plan phase as a whole. Individual tasks might have their own
assumptions.
Labor Hours

Computer Hours

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the planner environment.

Prerequisites

Verify that the deployment server has been installed and the
OneWorld directory is shared.

Concurrent Tasks

None

Starting Installation Planner


Begin your installation plan by logging on to OneWorld and starting Installation
Planner.
To start Installation Planner
1. Log on to OneWorld as user JDE with the database password for user JDE.
2. Access the planner environment (JDEPLAN).
3. From the System Installation Tools menu (GH961), doubleclick Addon
Servers Plan.

1242

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

4. On Work with Installation Plans, click Add.


OneWorld displays the following warning:

5. Click OK. The Installation Planner form appears.

Entering a Plan Description


After starting Installation Planner, enter basic plan information, such as plan
name and description.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1243

Installation Guide

To enter information into Installation Planner

1. On Installation Planner, in Plan Information, complete the following fields:




Name
Enter the name of your installation plan.

Description
Enter the description of your installation plan.

Status
Choose 10 as the status of your installation plan.

To Release
Verify that the release number is B7333.

2. Click OK. The Location Search form appears.

Entering a Plan Location


Once basic plan installation information is entered, you must select an existing
plan location. For most situations, select the location defined during your base
installation.

1244

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

To enter a plan location

1. On Location Search, choose a location, and then click Select.


The Location Revisions form appears.

2. On Location Revisions, click OK.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1245

Installation Guide

Selecting Additional Server Types


Once a plan location is specified, specify the types of servers you want to add to
your installation plan.
To select additional server types
The Add-on Servers Plan form appears.

1. On Server Add, check the types of servers that you want to add to your
configuration.
2. Click OK.
A Server Revisions form appears in the order listed on the Server Add
form for each type of server that you selected.
The following tasks assume you have already set up your data server. For
instructions on setting up a data server, see Specify Machine/Server
Types" in Planning the Upgrade.
3. Continue with the relevant sections that follow.

Entering Deployment Server Information


If you chose to add an additional deployment server to your plan, the
Deployment Server Revisions form appears.
1246

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

To enter deployment server information

1. On Deployment Server Revisions, complete the following fields:




Machine Name
Enter the name of your additional deployment server.

Description
Enter a description of the machine.

Release
Enter B7333.

Location
This field defaults to the location chosen for this plan.

Primary User
This identifies the user to whom email is sent when a package is
deployed. The default for primary user is located in the JDE.INI file.

2. On the Deployment tab, verify or complete the following fields:




Primary Deployment Server

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1247

Installation Guide

This field indicates the hierarchy of the servers. The field defaults to
0" for a secondary deployment server.


Server Share Path


Enter the server share path where you installed OneWorld on your
deployment server. Verify that this path matches your version of the
release. Example: For OneWorld Xe, the server share path is \b7333.

3. Click OK.
Troubleshooting
If you enter invalid information into a tab field, a red stop sign symbol
appears next to the tab name, such as deployment server. For more
information about the error, click on the red stop sign icon in the bottom
righthand corner of the form.
4. OneWorld asks if you want to add another deployment server.
Repeat Entering Deployment Server Information."


To continue with the additional server plan, click No.


Continue with the relevant sections that follow.

Entering Enterprise Server Information


If you chose to add an additional enterprise server to your plan, complete the
following tasks to define this server.


Enter Enterprise Server Information

Enter Enterprise Server Data Source Information

Entering Enterprise Server Information


Complete the information for the enterprise server that plan to use in this plan.
To enter enterprise server information
The Enterprise Server Revisions form appears.

1248

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

1. On Enterprise Server Revisions, complete the following fields on the top


section:


Machine Usage
The default value of 20 indicates that this is an enterprise server.

Machine Name
Enter the name of an enterprise server. The name is case sensitive.
Because of naming restrictions on the AS/400, this name cannot
exceed ten characters.

Description
Enter a long description of the machine.

Release
Enter B7333.

Host Type
Click the visual assist button and choose the type of enterprise
server you are adding to the plan.
For example, choose AS/400.

Location

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1249

Installation Guide

This field defaults to the location chosen for this plan.




Primary User
This identifies the user to whom email is sent once a package is
deployed. The default for primary user is listed in the JDE.INI file.

2. On the Enterprise tab, complete the following fields:




Port Number
A value defaults into this field from the JDE.INI file. Change the port
number for this enterprise server to a unique value. For example,
enter 60xx.

Logical Machine Name


Information defaults into this field when you enter the host type.

Database Type
The type of database that you want to use for data sources on the
enterprise server. Enter a valid value.

Value

Database

Client Access

Server Map Data Source


Information defaults into this field when you enter the host server
type.

Installation Path
Enter the installation directory path to which you want to install
OneWorld on your enterprise server. Make sure this path is specific
to your version of the release.
Example: For AS400, this path ends with B7333SYS the system
library.

Deployment Server Name


Using the visual assist button, choose the name of the deployment
server to which this enterprise server is attached. A deployment
server name defaults into the field, but can be changed if necessary.

1250

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

3. Click OK. A message box appears and asks you whether you want to
enter custom data sources or take the default data sources. Proceed to task
To specify custom or default data source information," below.
Troubleshooting
If you enter invalid information into a tab field, a red stop sign symbol
appears next to the tab name, such as enterprise server. For more information
about the error, click the red stop sign icon in the bottom righthand corner of
the form.

Entering Enterprise Server Data Source Information


After specifying enterprise server information, enter the data source information
for the enterprise server you will use in this plan.
Complete the following tasks:
- Specify custom or default data source information
- Verify server map source information
- Add another enterprise server
To specify custom or default data source information
OneWorld asks you whether you want to enter custom data sources or take the
default data sources for the enterprise server you just added. Select one of the
following options:


To enter custom data sources, click OK. Skip to To verify custom server
map source information."

If you clicked Take Defaults, continue with To add another enterprise
server."
If you are in a coexistent environment, do not take defaults for
AS/400.
To verify custom server map source information

The Data Source Setup form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1251

Installation Guide

1. On Data Source Setup, verify your Server Map data source information.
Data Source Considerations
J.D. Edwards configures your OneWorld data sources as completely as
possible. However, when you run Installation Planner, you might need to
modify some data source information to reflect your systemspecific
configuration.
2. Click OK.
To add another enterprise server
OneWorld asks if you want to add another enterprise server.
Select one of the following options:


To add another enterprise server, click Yes.


Repeat processes, starting with Entering Enterprise Server Information."
In a coexistent environment, do not add an additional enterprise server
that is not an AS/400. If you do so, the plan will create AS/400 data
sources on the second enterprise server. Instead, create a separate plan to
add non-AS/400 enterprise servers.

To continue with Installation Planner setup, click No.


Continue with Define a Java Server," or other relevant task, below.

1252

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

Define a Java Server


If you chose to add a Java server to your plan, complete the following task.
To define a Java server
The JAS Server Revisions form appears.

1. On JAS Server Revisions, complete the following fields in the top section:


Machine Usage
The default value of 30 indicates tha this is a Java Application
Server.

Machine Name
Enter the name of your OneWorld Java Server. The name is case
sensitive.

Description
Enter a long description of the machine.

Release
Enter B7333. You may need to manually change the release.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1253

Installation Guide

Host Type
Click the visual assist button and choose the type of server that
you are adding to the plan. The default value of 50 indicates the
server type as Intel NT.

Location
This field defaults to the location chosen for this plan.

Primary User
This identifies the user to whom email is sent once a package is
deployed. The default for primary user is listed in the JDE.INI
file.

2. On the JAS tab, complete the following fields.




Installation Path
Enter the installation directory path to which you are installing
OneWorld on your OneWorld Java Server. Make sure this path is
specific to your version of the release. For OneWorld Xe, the
path ends with \b7333).

3. Click OK.
OneWorld asks if you want to add another Java server.


To add another Java server, click Yes.


Repeat the steps in To define a Java server."

To continue with the additional server plan, click No.

Define a Windows Terminal Server


If you chose to add a Windows terminal server to your plan, complete the
following task.
To define a Windows terminal server
The WTS Server Revisions form appears.

1254

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

1. On WTS Server Revisions, complete the following fields in the top section:


Machine Usage
The default value of 35 indicates this is a Windows terminal server.

Machine Name
Enter the name of your Windows terminal server. The name is case
sensitive.

Description
Enter a long description of the machine.

Release
Enter B7333. You may need to manually change the release.

Host Type
The default value of 50 indicates that the server type is Windows NT
on Intel.

Location
This field defaults to the location chosen for this plan.

Primary User

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1255

Installation Guide

This identifies the user to whom email is sent once a package is


deployed. The default for primary user is listed in the JDE.INI file.
2. On the WTS tab, complete the following fields.


Installation Path
Enter the installation directory path where you are installing
OneWorld on your server. Make sure this path is specific to your
version of the release. For example, the path could end with \b7.

3. Click OK.
OneWorld asks if you want to add another Windows terminal server:
4. Select one of the following options:


To add another Windows terminal server, click Yes.


Repeat the steps in To define a Windows terminal server."

To select environments for the additional servers, click No.

Setting Up Environments
Complete the following sections to set up environments for the additional
servers:


Selecting an environment

Setting up Environment data sources

Selecting an environment
The Select Environment form appears.
Jxxxxxx environments will appear if a Java Application Server is in the
plan.
Wxxxxxx environments will appear if a Windows terminal server is in the
plan.
Tips and Techniques
You can only add or delete environments from the tree view of your plan.

1256

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

Doubleclick the environment that you want to define.


To set up multiple environments, choose and define them one at a time.
OneWorld brings you back to this screen after you complete the following
tasks.

Setting Up Environment Data Sources


After specifying which tables to replicate, complete the following tasks to set up
environment data sources:


Begin the environment data source setup

Verify the OWJRNL data source

Verify the Control Tables data source

Verify the AS/400 COMMON data source

Set up the Central Objects data source

Set up the Business Data data source

Verify the Versions data source

Select another environment

To begin the environment data source setup


OneWorld asks if you want to set up data sources for each environment that you
configured.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1257

Installation Guide

1. Select one of the following options:




To manually enter the data sources. click OK, and continue with the
tasks that follow.
If the environment that you selected is coexistent with World,
you must click OK.

To accept the OneWorld default data sources, click Take Defaults,


and skip to Select another environment."
This option limits your customization choices.

To verify the OWJRNL data source


The Data Source Setup form appears.

Verify the accuracy of the OWJRNL data source, and then click OK.

1258

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

To verify the Control Tables data source

On Data Source Setup, verify the accuracy of the Control Tables data source, and
then click OK.
To verify the AS/400 COMMON data source

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1259

Installation Guide

On Data Source Setup, verify the accuracy of the AS/400 COMMON data source,
and then click OK.
For an AS/400 coexistent environment, type the name of the existing
WorldSoftware library you want to use in the Data Library name field.
To set up the Central Objects data source

On Data Source Setup, set up your Central Objects data source, and then click
OK.

1260

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

To set up the Business Data data source

On Data Source Setup, set up the data source for your business data, and then
click OK.
To verify the Versions data source

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1261

Installation Guide

On Data Source Setup, verify the accuracy of the Versions data source, and then
click OK.
The Select Environments form appears so you can define another environment
(if necessary).
To select another environment

1. On Select Environments, select one of the following options:




Choose the next environment that you want to define, and repeat
the tasks in Setting up Environments."

After defining all of your environments, click Close.

Tips and Techniques


You can only add or delete environments from the tree view of your plan.

Finalizing the Installation Plan


Installation Planner automatically finalizes your installation plan. This section
consists of the following tasks.:

1262

Finalize the installation plan

Conclude the Validation Planner Report

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Adding a Server to an Existing Configuration

To finalize the installation plan


1. A message appears to let you know that the installation plan has been
finalized.
When the plan is finalized:


The status is set to 20. This signals that several adjustments to OCM
mappings and tables are made according to your plan.

The following tables are updated when the plan is finalized:


Release Master table (F00945)
Path Code Master table (F00942)
Package Plan table (F98404)
Machine Detail table (F9651)
Language table (F984031) - if you are installing an alternate
language

2. To exit the concluding message box, click OK.


Clicking OK initiates the Planner Validation Report.


If processing option default was selected, Planner Validation Report


automatically prompts you to run this report.

If processing option default was not selected, on the tree view of


your plan, click Validate to initiate the Planner Validation Report.

To conclude the Validation Planner Report


1. On Report Output Destination, choose On Screen or To Printer, and then
click OK.
2. Review the report to confirm that all records were validated.
3. After reviewing the report, click Close on the Batch Versions form.
For more information about the Planner Validation Report, see Reports in
the Installation Reference Guide.
4. On Work With Installation Plans, click Expand to review the plan that you
created.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1263

Installation Guide

Configuring Additional Servers


After you add additional servers, complete the following task to configure them.
For more information and detailed instructions, refer to Installing the OneWorld
Databases" for the appropriate database considerations.
To configure additional servers
1. Perform the appropriate set of operations for your database servers.
For AS/400:


Create server map Library (SVM7333) on additional enterprise


servers.

2. After configuring your database and server, use Installation Workbench to


allocate and configure software and resources. For complete information
about using the Installation Workbench, see Running Installation
Workbench."
When using the Installation Workbench for adding servers, the Table
Conversion and the Specification Merge workbenches do not appear
because they are not needed.
3. The final step for adding additional servers is to complete the necessary
steps for installing your host. For more information and detailed
instructions, see Installing OneWorld on the Enterprise Server."

1264

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

This chapter consists of the following tasks:


- Understanding processing options
- Accessing processing options
- Selecting processing option values

Understanding Processing Options


Processing options control how Installation Planner responds as you set up
plans. It also controls some of the options you get as you work through the
custom planner. If these options are not set up correctly for you, you will not
see the options that you need as you work through the planner. You set up
these processing options to control replication functions and business functions
mapping.
J.D. Edwards recommends that you review the default processing options for the
Installation Planner application before you begin to create the plan. Firsttime
users can set up the processing options to step through the planner with
informational messages. If you don't want to see these messages, you can turn
them off.

Assumptions about Reviewing Installation Planner Processing Options


Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the Planner environment.

Prerequisites

The deployment server must be installed.

Concurrent Tasks

OneWorld Xe UPDATE (8 February 2002)

The loadall script to build the database can be running.

Installation for AS/400 Systems

1265

Installation Guide

Accessing Processing Options


To review processing options you must first log on to OneWorld and specify
your installation plan type.
To access processing options
1. Log on to OneWorld as user JDE with the database password for user JDE.
2. Access the planner environment (JDEPLAN).
3. From the System Installation Tools menu (GH961), rightclick on either
Typical Installation or Custom Installation.
4. Choose Prompt for Values.
The Processing Options form appears.

Selecting Processing Options Values


Once you've accessed processing options, perform the following tasks to select
the processing options values:

1266

Specify prompt mode

Specify process mode

Specify default mode

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

Specify status change

Specify plan completion processes

Specify replication options

Specify business function options

Specify remote location package push options

To specify prompt mode


1. Select the Prompt Mode tab.

2. Choose the options for the type of prompting that you want when you
create your plan.
Type one of the following values:
Value

Description

Silent mode. This mode shows only the data entry


forms.

Additions Prompt mode. This default mode prompts


you for the addition of multiple servers.

Verbose mode. This mode directs you through creating


a plan with a series of prompting forms.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1267

Installation Guide

To specify process mode


1. Select the Process Mode tab.

2. On Process Mode tab, choose the options for the processes that you want
to run when you create your plan:


Additional Servers
Type 1 to display options in Installation Planner for adding
servers to your existing setup, or leave blank if you are not
adding servers.

Express Install
Type 1 to run Express Install, or 0 to Install OneWorld databases
manually. See the Express Install Guide for more information on
running this option.

To specify default mode


1. Select the Default Mode tab.
The Default Mode tab form appears.

1268

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

2. Complete the following:


Value

Description

Do not take defaults and do not prompt.

Prompt for default options at runtime.

Default mode. Always take defaults without prompting.

Default Data Source Information


For coexistence, set this option to 0 or 1 so that the existing data
libraries can be entered.

Default Environments
This option allows you to choose whether you want the ability
to select environments or take the defaults.

Default Data Load


This option allows you to choose whether you want the ability
to modify data load parameters or take the defaults.

Default Advanced Parameters


This option allows you to choose whether you want the ability
to modify advanced parameters or take the defaults.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1269

Installation Guide

Default Languages
This option allows you to choose whether you want the ability
to select an alternate language or take the defaults.

Upgrade/Update Plan Generation


This option allows you to choose whether you want the ability
to automatically generate a plan from locations and machines
defined in a previous version of the software.

To specify status change


1. Select the Status Change tab.
The Status Change tab form appears.

2. Complete the following:


Enter the default status, which is a numeric value, to change status
of the line when the following actions are taken:


Mark as Complete
This option signals that the line has been completed.

Disable
This option signals that the line is an inactive part of the plan.

1270

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

Enable
This option signals that the line is an active part of the plan.

To specify plan completion processes


1. Select the Completion tab.
The Completion tab form appears.

2. Complete the following:


After defining the plan, the options on this tab determine which
processes are run. Type one of the following values:
Value

Description

Do not run automatically.

Prompt to be run.

Run automatically.

Finalize Plan
Type the default option 2 to run automatically.

Validate Plan

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1271

Installation Guide

Type default option 2 to run automatically.


To specify replication options
1. Select the Replication tab.
The Replication tab form appears.

2. Type one of the following for each replication option below:


Value

Description

Do not use and do not prompt.

Prompt for option at runtime.

Always use without prompting.

OneWorld Replication
This field allows you to choose whether you have the option to
set up OneWorld replication in the plan.

Replicate System Tables


This field allows you to choose whether you have the option to
automatically replicate system tables for remote locations.

1272

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

Replicate Data Dictionary Tables


This field allows you to choose whether you have the option to
automatically replicate data dictionary tables for remote
locations.

Replicate Control Tables


This field allows you to choose whether you have the option to
automatically replicate control tables, menus, and user defined
codes for remote locations.

Replicate Constant Tables


This field allows you to choose whether you have the option to
automatically replicate constant tables for remote locations.
Business data tables are Object Librarian type 280.

Replicate Master Tables


This field allows you to choose whether you have the option to
replicate master tables automatically for remote locations.
Business data tables are Object Librarian type 210 and 211.

To specify business function options


1. Select the Functions tab.
The Functions tab form appears.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1273

Installation Guide

2. Type one of the following for each business function option below:
Value

Description

Heavy Client. All allowed business functions are


mapped to the workstation.

Light Client. All allowed business functions are mapped


to the enterprise server.

Optimized. All master and associated business functions


are mapped to the enterprise server. This is the default.

WTS Environments
Enter the number for the business functions setting that you
want to use for all environments on the Windows terminal
server.

Remote Environments
Enter the number for the business functions setting that you
want to use for all remote environments.

All OneWorld Java Server environments are set up as Light Clients.


You cannot change this setting.
To specify remote location package push options
1. Select the Packages tab.
The Packages tab form appears.

1274

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Reviewing Installation Planner Processing Options

2. Type one of the following options for remote location package push:
Value

Description

Do not push packages.

Prompt for pushing at runtime.

Do not prompt for pushing but display valid packages.

Always push default packages without prompting.

3. When you have chosen the options that you want, click OK.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1275

Installation Guide

1276

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Deleting Pieces of an Installation Plan

As you work through the Installation Planner application, you may find that you
need to delete a server or machine that you have created. You can delete pieces
of a plan as needed. However, this can affect related databases, shared
enterprise and deployment servers, and associated records.
To delete servers or machines from an installation plan

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

Installer

Logon status

On the deployment server, logged on as user JDE with the


database password for user JDE, in the Planner environment.

Prerequisites

You must have an installation plan.

Concurrent Tasks

None

1. In the OneWorld planner environment, type P9654A in the Fast Path and
press Enter.
2. On Work With Locations and Machines, click Find.
3. Expand the location.
A list of your locations, machines, or servers appears for your base
location in the tree view.
4. Choose the location, machine, or server you want to delete.
5. Click Delete.
6. To close the application, click Close.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1277

Installation Guide

1278

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Language-Only Installation Plan

This chapter consists of the following tasks:


- Understanding a language-only installation plan
- Reviewing requirements for a language installation
- Installing languages on the deployment server
- Running Installation Planner
- Running Installation Workbench
- Verifying enterprise server requirements
- Verifying workstation requirements
- Completing the language installation
- Building and deploying alternate language packages

Understanding a Language-only Installation Plan


Use the procedures in this chapter when installing an alternate language or
multiple languages for the first time.
Install alternate languages at the same time that you install OneWorld, or
after completing a working installation or upgrade.
A languageonly plan may be implemented only in installations where a
language has not been previously installed.
In order to make the languageonly installation as smooth and quick as possible,
J.D. Edwards strongly encourages you to complete the tasks provided in this
checklist. These tasks are designed to help you organize the required
preinstallation preparation that is necessary to complete a languageonly
installation process. Complete all tasks in order to achieve a successful language
installation.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1279

Installation Guide

Reviewing Requirements for a Language Installation


Review the basic requirements for performing a language installation as outlined.
To review requirements for a language installation
1. Review the language installation process.
The detailed information regarding the language installation process is
found in the chapter Language Process Overview."
2. Review the disk space requirements.
Verify that the disk space requirements are available for each language
and each environment that you are installing on the deployment and
enterprise servers.
3. Review the directory structure.
The detailed information regarding directory structures is found in
OneWorld Directory Structures" in the Installation Reference Guide.

Installing Languages on the Deployment Server


Once you've completed your requirements review, you must install languages on
the deployment server. The following task highlights the critical languagerelated
stages in this operation.
To install languages on the deployment server
1. Go to the chapter Installing OneWorld on the Deployment Server."
2. Complete the task Installing Language on the Deployment Server."
To install languages, use a server installation process to copy the
applicable contents of the language CD to the JDEdwardsOneWorld
directory on the deployment server.
3. Verify that all of the appropriate files on the language CD copied to the
correct JDEdwardsOneWorld directories.

1280

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Language-Only Installation Plan

Running Installation Planner


Once you've installed languages on the deployment server, run Installation
Planner. The following tasks highlight the critical languagerelated stages in this
operation.


Access Installation Planner

Enter information into Installation Planner

Select (custom / default) environments

Select an environment

Select a language

View the Installation Plan tree

To access Installation Planner


1. Go to the section Planning the Installation."
2. Begin defining a plan: choose either Defining a Typical Installation Plan"
or Defining a Custom Installation Plan."
If you choose a custom installation plan, you can choose which language
to install for each environment. This section assumes you are defining a
custom plan.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1281

Installation Guide

To enter information into Installation Planner

1. On Installation Planner, enter the basic plan information. In the Include


Language area, choose the Language Only option.
2. Continue through the Installation Plan until you reach additional language
options found at the Environment Selection option.

1282

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Language-Only Installation Plan

To select (custom / default) environments

From Custom Installation Plan, all environments and languages are the defaults.
Turn off the options for Default Environment and Default Languages if you want
to specify which language or languages to install for each environment.
To select an environment

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1283

Installation Guide

Choose the environment you wish to install a language, and the Language
Selection form appears.
To select a language

1. Doubleclick the language to install. A checkmark appears in the first


column to acknowledge the selection.
2. Click OK. The Select Environments form appears.
3. Repeat the processes To select an environment" and step 1 of To select a
language" for each environment and each language you want to install.
4. Choose Select.
5. Continue stepping through the planner options until the plan is complete.
The Planner Validation report will show the criteria defined in your
languageonly plan.

1284

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Language-Only Installation Plan

To view the Installation Plan tree

After the plan is complete, the Installation Plan tree will appear. Click Expand to
view.


J.D. Edwards ships OneWorld with a base language of English, which is


included in the normal installation process. However, if you already have
a language installed and you are performing an upgrade, refer to the
Upgrade Guide.

Running Installation Workbench


After you create the languageonly plan, you must run it through a series of
workbenches in order to load the language tables to the appropriate data
sources. The language installation process is the same for every database. The
following task highlights the critical stages in this operation.
To run installation workbench
1. Go to Running Installation Workbench."
2. Complete the procedures for Control Table Workbench and Specification
Table Merge Workbenches.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1285

Installation Guide

The control tables, data dictionary, and central objects will be loaded by
the Control Table Workbench and the Specification Table Merge
Workbench.

Verifying Enterprise Server Requirements


The following task highlights the critical stages in verifying server requirements
for language installation.
To verify enterprise server requirements
1. Verify that the enterprise server hardware and software meet requirements.
2. Verify that the enterprise server disk space meets requirements.
3. Go to Installing the Enterprise Server."
Verify the JDE.INI settings for local code set and code page values are set
for your preferred language. These values are found in the National
Language Support" tables in the chapter Language Process Overview."

Verifying Workstation Requirements


The following task highlights the critical stages in verifying workstation
requirements for language installation.
To verify workstation requirements
1. Verify that the workstation hardware and software meet requirements.
2. Go to Configuring and Installing a Workstation."
3. Install the appropriate language character set to a workstation.
4. Complete the step to verify the JDE.INI settings on the deployment server
for Interactive Runtime, Install, and Network Queues.
5. Complete the step to install OneWorld to a workstation.
6. Verify that the group and user profiles are set up properly.

1286

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Creating a Language-Only Installation Plan

Completing the Language Installation


Once you've verified that the enterprise server and workstation hardware and
software meet your language install requirements, you can complete the
installation.
See the Package Management Guide for more information about how to
transfer language specifications to the enterprise server.

Building and Deploying Alternate Language Packages


Once you've concluded the installation, it's time to build and deploy the
alternate language packages.
See Package Build" in the Package Management Guide for the details of
including a language or creating languageonly packages.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1287

Installation Guide

1288

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Installation Utilities
This section contains the following topics and tasks:
- Creating thirdparty ODBC data sources
- Revalidating software protection codes
- Uninstalling OneWorld
- Stopping OneWorld on the enterprise server
- Granting disk and registry access for Windows NT

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

131

Installation Guide

132

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Revalidating Software Protection Codes

When you revalidate OneWorld software protection codes, you must revalidate
both the deployment server and workstations. For example, you need to do this
if your deployment period or expiration date has expired or if you add modules
to OneWorld. The software notifies you seven days before your expiration date.
This chapter consists of the following tasks:
- Revalidating the deployment server
- Revalidating workstations

Revalidating the Deployment Server


You should revalidate the deployment server if:


The deployment period is about to expire or has expired

Modules have been added to OneWorld

Additional seats (licenses) to install have been purchased


To revalidate the deployment server

Labor Hours
Computer Hours
Personnel

0.25 (plus time to contact the J.D. Edwards Contracts


department)
0.25
Installer

Logon status

On the deployment server, in the planner environment as user


JDE with the database password for user JDE.

Prerequisites

OneWorld has been installed on the deployment server.

Concurrent Tasks

None

1. Log on to the deployment server in the planner environment as user JDE


with the database password for user JDE.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

133

Installation Guide

2. From the Advanced Operations menu (GH9611), choose JDEdwards


Licensing Security.
3. On Reset JDEdwards Security, click Reset Server Security.
On the JDEdwards Security Setup form, the information that appears may
be different from what is shown here.

4. For the authorization code you need to proceed, call J.D. Edwards at
3033344000, Monday through Friday 8:00 a.m. to 5:00 p.m. MST, and ask
for the Contracts Department. Be prepared to give the following
information:


Serial number

Number of client licenses

The serial number and authorization code change each time you install
OneWorld.
When you add more client licenses, type in the total number desired. For
example, if you currently have 1000 client licenses and you are adding 300
additional licenses, enter 1300.
5. To reset the deployment server, choose OK.

Revalidating Workstations
You might need to revalidate workstations for either of the following reasons:

134

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Revalidating Software Protection Codes

The expiration date has passed.

You added modules to OneWorld.


To revalidate workstations

Labor Hours
Computer Hours
Personnel

0.25
0.25 (plus time to contact the J.D. Edwards Contracts
department)
Installer

Logon status

On the workstation with the appropriate user ID and


password.

Prerequisites

OneWorld has been installed on the workstation.

Concurrent Tasks

None

1. Log on to the workstation with the appropriate user ID and password.


2. Choose any of the environments available to the workstation user.
3. From the Advanced Operations menu (GH9611), choose JDEdwards
Licensing Security.
4. On Reset JDEdwards Security, click Reset Client Security.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

135

Installation Guide

5. On JD Edwards Security Setup, from the Form menu, choose Get


Authorization.
The authorization code appears in the Authorization Code field.
6. To reset the workstation, click OK.

136

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Uninstalling OneWorld

You can remove previous OneWorld installations from workstations by running


the uninstallation program.
The uninstallation program performs the following:


Deletes the JDEdwardsOneWorld program group

Deletes jde*.* from the root directory

Removes the LOCAL data source

Deletes the path

Unregisters services

Removes the uninstall directory

Increments licenses on the deployment server

Deletes the installation directory tree

Deletes the registry entry

Troubleshooting
Ignore messages about security that appear during the uninstallation
procedure. If error messages say you cannot remove certain objects, make
sure that Read Only is not chosen on the object property sheet, and then
rerun the uninstallation program.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

137

Installation Guide

To uninstall OneWorld from the workstation

Labor Hours

.25

Computer Hours

.25

Personnel

Installer

Logon status

On the workstation

Prerequisites

None

Concurrent Tasks

None

1. On the Windows Start menu, open the Control Panel.


2. In the Control Panel, doubleclick Add/Remove Programs.
3. On Add/Remove Programs, choose JDEdwards OneWorld.
4. Click the Add/Remove button.
5. On JDEdwards OneWorld Client Maintenance Setup, choose Remove All
Components.
6. Click Finish.
A status bar shows progress as OneWorld is deleted. Repeat the process,
choosing JDEdwards OneWorld on the Add/Remove Programs list, to remove the
OneWorld program.

138

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Stopping OneWorld on the Enterprise Server

This chapter explains how to stop the OneWorld enterprise server if you need to
stop processes running on the server. For example, you might need to do this if
you are debugging the JDE.INI file. After saving the file, you have to stop and
then restart the enterprise server for the changes to take effect.

See Also


Starting the OneWorld AS/400 Enterprise Server" in the chapter Installing


OneWorld on the Enterprise Server" to restart the server
To stop the OneWorld AS/400 enterprise server

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

System administrator

Logon status

On the AS/400, logged on as ONEWORLD

Prerequisites

None

Concurrent Tasks

None

1. Log on to the AS/400 as ONEWORLD.


2. On the AS/400 command line, enter ENDNET.
This command ends JDENET from an AS/400 display, ends the JDENET
jobs, and cleans up JDENET runtime structures.
3. On the AS/400 command line, enter:
ENDSBS SBS(JDExxxxx) OPTION(*CNTRLD)
where xxxx is the release to which you are installing (for example,
B7333).
This command ends the JDExxxx subsystem.
4. On the AS/400 command line, enter:
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

139

Installation Guide

WRKACTJOB SBS(JDExxxxx)
where xxxxx is the release to which you are installing (for example,
B7333).
Wait until the JDExxxx subsystem ends before you continue.

1310

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Granting Disk and Registry Access for Windows NT

Users do not need full administrator access to install OneWorld on the Windows
NT workstation. However, they need disk and registry access for the installation.
This chapter explains how an administrator can grant nonprivileged users disk
and registry access.
Complete the following tasks:


Grant nonprivileged access to disk for Windows NT

Grant nonprivileged access to the Windows NT registry

See Also


Configuring and Installing Workstations."


To grant nonprivileged access to disk for Windows NT

This procedure can be used only by the administrator of the domain. The
procedure grants access to the jdeinst.log file and the OneWorld installation
directory.
Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

System administrator

Logon status

On the Windows NT workstation, logged on as administrator

Prerequisites

None

Concurrent Tasks

None

Use the following procedure to grant access to the jdeinst.log file:


1. Create an empty file in the c:\ root directory named jdeinst.log.
2. In Windows NT Explorer, rightclick the file and select Properties.
3. Click the Security tab.
OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1311

Installation Guide

4. Click Permissions.
5. Click Add.
6. On Add Users and Groups, doubleclick the user who is to be added.
7. Click the pulldown menu in the Type of Access field, and select Full
Control.
8. Click OK. Permission to access the jdeinst.log file is granted to the user.
Use the following procedure to grant access to the OneWorld installation
directory:
1. Create an empty directory named B7 on a drive. This directory will
become the installation directory for OneWorld.
2. In Windows NT Explorer, rightclick the directory and select Properties.
3. Click the Security tab.
4. Click Permissions.
5. Click Add.
6. On Add Users and Groups, doubleclick the user who is to be added.
7. Click the pulldown menu in the Type of Access field, and select Full
Control.
8. Check the Replace Permissions on Subdirectories box.
9. Click OK. Permission to access the OneWorld installation directory is
granted to the user, who can now install OneWorld to this directory.
To grant nonprivileged access to the Windows NT registry
This procedure can be used only by the administrator of the domain. The
procedure grants access to HKEY_LOCAL_MACHINE\Software\JDEdwards.

1312

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Granting Disk and Registry Access for Windows NT

Labor Hours

Less than 0.25

Computer Hours

Less than 0.25

Personnel

System administrator

Logon status

On the Windows NT workstation, logged on as administrator

Prerequisites

None

Concurrent Tasks

None

1. Run the regedt32 program: click the Windows NT Start button, click Run,
and in the Open field, type regedt32, and click OK.
2. Click the window titled HKEY_LOCAL_MACHINE on Local Machine.
3. Doubleclick the Software folder to open it.
4. On the Menu bar, click Edit and then Add Key.
5. In the Key Name field, type JDEdwards (capitalize as shown). Leave the
Class field blank.
6. Click OK.
7. On the Menu bar, click Security and then Permissions.
8. On the Registry Key Permissions box, click Add.
9. On the Add Users and Groups box, doubleclick the user who is to be
added.
10. Click the pulldown menu in the Type of Access field and select Full
Control.
11. Check the Replace Permissions on Existing Subkeys box.
12. Click OK. Permission to access the registry is now granted to the user.

OneWorld Xe UPDATE (8 February 2002)

Installation for AS/400 Systems

1313

Installation Guide

1314

Installation for AS/400 Systems

OneWorld Xe UPDATE (8 February 2002)

Index
A
Access, granting disk and registry access,
1311
Access codes
authorization code, 515
software protection codes, 133
Accounts receivable
chargeback records, 1119
Conversion Audit Envelope, 1118
Conversion Audit report, 1118
conversion from World to OneWorld,
1118
work file build programs, 1118
ActivEra (Solution Explorer). See Solution
Explorer
ActivEra Solution Explorer, definition, 25
Adding a printer to the enterprise server,
819
Additional languages. See Alternate
languages
Additional Servers
defining a deployment server, 1247
defining an enterprise server, 1249
defining machine / server types, define
a Java server, 1253
entering a plan description, 1243
entering a plan location, 1244
entering deployment server information,
1246
entering enterprise server information,
1248
Starting Installation Planner, 1242
verifying deployment server information,
1247
verifying enterprise server information,
1248
Additional servers, 1241
configuring, 1264
defining machine / server types, define
a Windows terminal server, 1254
final status, 1263
finalizing the installation plan, 1262

OneWorld Xe UPDATE (8 February 2002)

machine / server types


defining a Java server, 1253
defining a Windows terminal server,
1255
setting up environment data sources,
1257
Administrator, granting disk and registry
access, 1311
Alternate language, deployment server,
520
Alternate languages
building and deploying packages, 1020
creating a Language Only plan, 1279
disk space requirements, 434, 1280
installing on the deployment server,
1280
language preference codes, 321
language release CD, 1280
language text, 321
package build considerations, 832,
1020
package deployment considerations,
1021
standard packages, 320
supported languages, 321
transferring objects, 1021
workstation, 91
Architecture, language, 319
AS/400
Client Access with OneWorld, 86
coexistence
listing WorldSoftware modifications,
84
OneWorld, 35
reviewing setup issues, 84
configuration, 83
creating the job queue, 813
creating the output queue, 812
enterprise server
hardware and software requirements,
412, 414
verifying the installation, 814
libraries, 522
creation, 524

Installation Guide
output queue, default printer, 812
starting the OneWorld enterprise server,
817, 818
stopping the enterprise server, 139
TCP/IP protocol, 85, 86
verifying the installation, 814
AS/400 COMMON data source, setup,
1260
AS/400 Common data source, 67
setup, 661
verify, 645
ASUs (software updates), 14
Attended workbench, 78
Authorization code, 515
Autopilot, 1124

B
B73.3.3, whats new, 23
Base language
English, 320
language preference code, 321
Base Price System, 1121
Batch application, R4094A, 1121
BLOB support, disk space requirements,
432
Breaking News publication, 14
Build programs, accounts receivable,
1118
Building a language package, installer,
1020
Building and testing packages, 109
Building packages
deploying packages to workstations,
installer, 109
for language, 1020
System administrator, 109
translated objects, 1021
Building Word Search tables, 1122
Business Data, data source, coexistence,
67
Business data, prototype environment,
317
Business Data data source, setup, 658,
1235, 1261
BUSOBJ directories, 1014

C
CAPS.dll, 1011
Case sensitivity, conventions for this
guide, 19
Caution icon, conventions for this guide,
19
CD burner, 1018
Central Objects, data source, 66
Central objects, tables, 722
Central Objects data source, setup, 657,
1260
Character set, alternate language, 1286
Character sets. See Code pages
Chargeback records, accounts receivable
conversion, 1119
Checklist, Language Only plan, 1279
Choosing replication options, remote
installation, 1223
Classes, OneWorld, 12
Client Access, setup on the AS/400 for
OneWorld, 86
CLOG.dll, 1013
Cluster software, Installation Planner, 65
Code page and INI values, verify and
modify settings, 327
Code page setup, 327
Code pages
conversions, 324
database considerations, 324
fonts, 328
language preference codes, 324
settings, 325
single-byte and double-byte
considerations, 327
user display preferences, 329
verifying multinational settings, 325
Coexistence, 35
configuring data sources, 67
control table merges, 38, 63
data source configuration, System, 65
defining the AS/400 Common data
source, 661
expanding distribution flexible files,
1115
Ledger Type Master file (F0025), 1117
listing WorldSoftware modifications, 84
reviewing AS/400 setup issues, 84
user defined codes, 718

OneWorld Xe UPDATE (8 February 2002)

Index
WorldSoftware data library, 655
Completing the installation, 111
modifying OneWorld, 117
Completion tab, processing options, 1271
ComposerCBT, 119
Concluding the Remote Installation Plan
Setup, defining a remote installation plan,
1238
Configuring file transfer protocol (FTP),
56
Configuring OneWorld for use with Vertex
Quantum tax applications, 1133
configuring the database connections,
1134
mapping objects to the enterprise
server, 1137
testing the connection, 1138
Configuring OneWorld to run Autopilot,
1124
Configuring servers, 71
Configuring the AS/400, 83
Client Access used with OneWorld, 86
ICP/IP protocol, 85, 86
listing WorldSoftware modifications, 84
OneWorld user profiles, 84
reviewing coexistence setup issues, 84
Configuring the deployment server, 53
file transfer protocol (FTP), 55, 56
JDE user, 54
Configuring the OneWorld database
connections for Vertex Quantum tax
applications, 1134
Configuring the System - B73.3 data
source, 65
Configuring Windows NT, deployment
server, 53
Configuring your control tables, 720
installer, 721
Configuring your data sources, 716
installer, 716
Configuring your environments, 717
installer, 718
Configuring your locations, 715
Configuring your machines, 719
installer, 719
Configuring your packages, 723
installer, 723
Configuring your remote locations, 724
installer, 725

OneWorld Xe UPDATE (8 February 2002)

Considerations boxes, conventions for this


guide, 18
Control file, base English records, 320
Control Table Planner
Data Dictionary merge, 38
Menu merge, 38
User Defined Code merge, 38
User Overrides merge, 38
Control Table Workbench, 74, 721
configuring your control tables, 720
configuring your remote locations, 724
Control Tables, configuring, 720
Control tables
data source, 66
Installation Workbench, 74
merges, 38, 721
coexistence, 63
Control Tables data source, setup, 656,
1234, 1259
Conventions for this guide, 16
case sensitivity, 19
considerations boxes, 18
fonts, 19
icons, 19
tips and techniques boxes, 18
troubleshooting boxes, 18
Conversion Audit Envelope, 1118
chargeback records, 1119
Conversion Audit report, 1118
Conversion Audit report (P03961),
1118
OneWorld Build (P039601), 1118
WorldSoftware Build (P03960), 1118
Converting accounts receivable, 1118
Copying data dictionary files to the
enterprise server, 1111
recreating replicated files, 1112
transferring files, 1113
Creating a custom installation plan, 625
Creating a JDE user, 54
system administrator, 54
Creating a remote installation plan, 123,
124
Creating a typical installation plan, 611
Creating an output queue for the AS/400
default printer, 812
Creating database logins and users for
SQL Server 7.0, 544
editing the creation script, 544
running the creation script, 545

Installation Guide
Creating databases for SQL Server 7.0,
542
editing the creation script, 542
running the creation script, 543
Creating OneWorld user profiles, AS/400,
84
Creating the database users and owners
for Oracle, 537
Creating the job queue, 813
Creating the output queue, 812
Creating the tablespaces, 536
Creation script
database logins and users
editing the script, 544
running the script, 545
SQL Server database, 542, 543
CRP (prototype) environment, 317
Custom Installation
defining a deployment server, 631,
129
defining an enterprise server, 633
defining machine / server types, 637
define a data server, 638
define a Java server, 640
define a Windows Terminal server,
642
specifying machine / server types,
637
entering enterprise server data source
information, 635, 1215, 1251
entering enterprise server information,
633
entering location information, 629
entering plan description, 627
entering shared data source
information, 644
enterprise server information, specifying
(custom or default) data source
information, 635, 1215, 1251
finalizing the installation plan, 659
machine / server types
defining a data server, 639
defining a Java server, 641
defining a windows terminal server,
643
specifying machine / server types,
638
selecting an environment, 648
remote location, 1228

setting up environment data sources,


654
setting up environments, 648
starting Installation Planner, 626
verifying deployment server information,
631
verifying enterprise server information,
633
Custom installation
final status, 660
remote installation plan, 124
Custom installation plan, 625
Custom modifications
listing for WorldSoftware, 84
setup recommendations, 313
using environments, 316
Custom Plan, Language Only installation,
1281
Customer configuration (typical
configuration), 35
Customer preparation, 31
detail worksheet, 435
disk space requirements, 431
hardware and software requirements,
49
Language only installation, 1279
Customer Support, Telephone, fax, email
information, 15
Customer support, 14
authorization code, 515
premier maintenance, 15
software protection codes, 133
standard maintenance, 15

D
Data Dictionary, data source, 65
Data dictionary
copying files to the enterprise server,
1111
F9202 table, 321
installing on the AS/400, 522
language preference code, language
record, 321
library name, 647, 1227
merge, 38
recreating replicated files, 1112

OneWorld Xe UPDATE (8 February 2002)

Index
transferring files, enterprise server,
1113
Data Dictionary data source, setup, 646,
1227
Data servers, disk space requirements,
432
Data Source Workbench, 73, 716
configuring your data sources, 716
Data sources
adding to a plan, 65
AS/400 COMMON, setup, 1260
AS/400 Common, 67
setup, 661
verify, 645
Business Data, 66
coexistence, 67
setup, 658, 1235, 1261
Central Objects, 66
setup, 657, 1260
Control Tables, 66
setup, 656, 1234, 1259
Data Dictionary, 65
setup, 646, 1227
Do Not Translate (DNT), 67
Installation Workbench, 73, 716
Object Librarian, 65
setup, 647
ODBC, DNT data sources, 67
OWJRNL, setup, 646, 1258
Server Map, setup, 65, 636, 1216,
1252
setup, 37
System, 65
coexistence, 65
setup, 648, 1228
Versions, 67
setup, 657, 1262
Database, character sets and code pages,
324
Databases
DB2/400, loading central objects, 547
deployment databases, 529
doublebyte requirements, Chinese,
Japanese, 327
editing the creation script, 542
enterprise databases, 529
login and user creation script
editing the script, 544
running the script, 545
necessary onsite resources, 529

OneWorld Xe UPDATE (8 February 2002)

Oracle
central objects, 538
preparation, 533
users and owners, 537
planner environment, 315
preparing Oracle for OneWorld, 532
running the creation script, 543
SQL Server
creation, 542
loading central objects, 545
logins and users, 544
verifying code page settings, 530
DB2/400, loading central objects, 547
Default language record, 321
Default Mode tab, processing options,
1269
Defining a custom installation plan
installer, 626
remote installation, 124
Defining a Data Server
custom installation, machine / server
types, 639
remote installation, machine / server
types, 1218
Defining a default printer, 830
Defining a Deployment Server
custom installation, 631, 129
remote installation, 1210
typical installation, 616
Defining a Java Server
additional servers, machine / server
types, 1253
custom installation, machine / server
types, 641
remote installation, machine / server
types, 1220
Defining a remote installation plan, 125
Defining a typical installation plan, installer,
611
Defining a Windows Terminal Server
custom installation, machine / server
types, 643
remote installation, machine / server
types, 1222
Defining a Windows terminal server,
additional servers, machine / server types,
1255
Defining an Deployment Server, additional
servers, 1247

Installation Guide
Defining an Enterprise Server
additional servers, 1249
custom installation, 633
Defining AS/400 Common Data Sources,
661
Defining Machine / Server Types
additional servers, define a Java server,
1253
custom installation, 637
define a data server, 638
define a Java server, 640
define a Windows Terminal server,
642
specifying machine / server types,
637
remote installation, 1217
define a data server, 1218
define a Java server, 1220
define a Windows Terminal server,
1222
specifying machine / server types,
1217
Defining machine / server types, additional
servers, define a Windows terminal server,
1254
Deleting servers or machines from an
installation plan, 1277
Demonstration data, pristine environment,
317
Deploying packages
alternate languages, 1020
language considerations, 1021
Deploying workstation packages, 1020
Deployment environments, 316
custom modifications, 316
Deployment server, installing alternate
language, 1280
Deployment servers, 37
adding to a plan, 64
alternate language, 520
Client JDE.INI file, 93
configuration, 53
configuring FTP, 56
creating a JDE user, 54
disk space requirements, 431
installation, 37, 51, 53
installing FTP, 55
installing objects, 512
JDE.INI file, modifying the enterprise
server file, 88

language installation, 323


license setup, 514
OneWorld databases, 529
revalidation, 133
TCP/IP protocol for the enterprise
server, 526
wide area network (WAN), 39
Windows NT
configuration, 53
hardware and software requirements,
49
Windows NT security, 113
Detail worksheet, preparing for installation,
435
Development environments, 317
Directory Structure
Alternate languages, 1280
Language, 1280
Disk space, requirements
BLOB support, 432
data server, 432
deployment server, 431
enterprise server, 433
language installation, 434
multitier environments, 410
Disk space requirements, alternate
language, 1280
Distribution flexible files, expanding, 1115
Do Not Translate (DNT) data source, 67
Document updates, 13
Double-byte languages, code pages, 327

E
Editing the database creation script, 542
Editing the login and user creation script,
544
English, base language, 320
English deployment server, doublebyte
requirements, Chinese, Japanese, 320,
323
Entering a plan description
additional servers, 1243
defining a typical installation plan, 612
Entering a Plan Location, additional
servers, 1244
Entering Deployment Server Information,
additional servers, 1246

OneWorld Xe UPDATE (8 February 2002)

Index
Entering Enterprise Server Data Source
Information, custom installation, 635,
1215, 1251
Entering Enterprise Server Information
additional servers, 1248
custom installation, 633
defining a typical installation plan, 617
Entering Information Into Installation
Planner, remote installation, 126
Entering Location Information, custom
installation, 629
Entering Plan Description, 627
Entering Plan Location Information
defining a typical installation plan, 614
remote installation, 128
Entering Shared Data Source Information,
custom installation, 644
Entering Shared Datasource Setup
Information, remote installation plan,
1226
Enterprise Server Information, custom
installation, specifying (custom or default)
data source information, 635, 1215,
1251
Enterprise servers
adding to a plan, 65
AS/400
configuration, 83
hardware and software requirements,
412, 414
starting the server, 817, 818
stopping the server, 139
verifying the installation, 814
configuring, 1016
data dictionary
copying files, 1111
transferring files, 1113
disk space requirements, 433
Host Workbench, 73, 719
installation, 39
JDE.INI file, 88
JDE.INI file and code page setup, 327
job queue, 813
OneWorld
databases, 529
installation, 83, 87, 89
output queue, 812
default printer, 812
printer setup, 819
stopping OneWorld, 139

OneWorld Xe UPDATE (8 February 2002)

TCP/IP protocol, 526


updating language specifications, 832
wide area network (WAN), 39
Environment Checker. See Verification
Tool
Environment Workbench, 73, 717
configuring your environments, 717
Environments
deployment (DEP7333), 316
development (DV7333), 317
Installation Workbench, 73, 717
J.D. Edwards pristine (JD7333), 317
OCM mappings, 315
overview, 313
path codes, 315
planner (JDEPLAN), 315
production (PD7333), 317
prototype (PY7333), 317
setup, 38, 1228
remote installation, 1228
test (TS7333), 316
ESUs (software updates), 14
Expanding the distribution flexible files,
1115
Explaining the language installation
process, 1285

F
F9631 table, 1015
F9860 table, 1014
F98741 table records, 1017
F98743 records, 1014
Final status
additional servers, 1263
custom installation, 660
remote installation, 1239
typical installation, 620
Finalizing the Installation Plan
additional servers, 1262
defining a custom installation plan, 659
defining a remote installation plan,
1239
defining a typical installation plan, 620
Find It! (Solution Explorer), 1130
Finishing Installation Workbench, 726
installer, 726
Flexible files, expanding, 1115

Installation Guide
Fonts
code pages, 328
conventions for this guide, 19
forms, grids, and reports, 328
Form, Replication
Replication Load tab, 1225
Replication Setup tab, 1224
Forms
Advanced Parameters, 652
Control Table Workbench, 721
Custom Installation Plan
environment selection, 1283
Language Selection, 1284
Select environments, 1284
Data Load Parameters, 651
Data Server Revisions
custom installation, 639
remote installation, 1218
Data Source Revisions, 661
Autopilot, 1126
Data Source Setup, 636, 658, 1216,
1252
additional servers, 1257
remote installation, 1234
Data Source Workbench, 717
Deployment Server Revisions
additonal servers, 1247
custom installation, 631, 129
remote installation, 1210
typical installation, 616
Enterprise Server Revisions
additonal servers, 1249
custom installation, 633
Environment Workbench, 718
Installation Planner, remote installation,
127
J.D. Edwards Security Setup, 134,
136
JAS Server Revisions
custom installation, 641
remote installation, 1220
JAS server revisions, additional servers,
1253
Location Workbench, 714, 715
Machine Search & Select, Autopilot,
1125
Machine Search Select, 661
Machine/Server Types, 638, 1217
Processing Options, 1266

Reset J.D. Edwards Security, 134,


135
Select Environments, 659
additional servers, 1262
remote installation, 1236
Specification Table Merge Workbench,
722
Work With Data Sources, 661
Work with Data Sources, Autopilot,
1125
Work with Installation Plan, 712
Work with Installation Plans, 612, 627
additional servers, 1243
remote installation, 126
WTS Server Revisions
additional servers, 1255
custom installation, 643
remote installation, 1222
FTP
configuration, 56
installation, 55
FTPOUTPUT file, job log information, 811
Functions tab, processing options, 1274

G
Group profiles, 95

H
Hardware and software requirements, 49
AS/400, enterprise server, 412, 414
OneWorld Java client, 420
OneWorld Java development
workstation, 420
OneWorld Java Server, 422
Windows NT
deployment servers, 49
Terminal Server Edition (TSE), 425,
427
workstations, 416
Help You Install Web page, 13
Hexadecimal values, code page
conversions, 324
Home Page (Solution Explorer), setting
up, 1131
Host services checklist, 815

OneWorld Xe UPDATE (8 February 2002)

Index
Host Workbench, 73, 719
HTML documentation path (Solution
Explorer), 1129

I
Icons, conventions for this guide, 19
INF files, 1019
Installation
additional servers, 1241
configuring, 1264
entering a plan location, 1244
Entering deployment server
information, 1246
entering enterprise server
information, 1248
finalizing the installation plan, 1262
Starting Installation Planner, 1242
AS/400, 814
enterprise server, 814
completion, 111
conventions for this guide, 16
custom plan, 627
defining machine / server types, 637
entering enterprise server data
source information, 635, 1215,
1251
entering enterprise server
information, 633
entering location information, 629
entering shared datasource
information, 644
finalizing the installation plan, 659
setting up environment data sources,
654
setting up environments, 648
starting Installation Planner, 626
verifying deployment server
information, 631
verifying enterprise server
information, 633
defining a plan, remote installation,
125
deployment server, 51, 53
detail worksheet, 435
enterprise server, 83, 814
modifying OneWorld after completion,
117

OneWorld Xe UPDATE (8 February 2002)

packages, 101
pre-installation procedures, 41
preparation, 31
prerequisites, 12
process, 35
whats new, 21
process for language, 1285
remote installation plan, 124
entering shared datasource setup
information, 1226
remote plan, 125
concluding the remote installation
plan setup, 1238
defining machine / server types,
1217
entering information into Installation
Planner, 126
entering plan location information,
128
finalizing the installation plan, 1239
replicating data, 1223
setting up environments, 1228
specifying a deployment server, 129
specifying an enterprise server,
1212
verifying enterprise server
information, 1212
time estimates, 310
typical plan
entering a plan description, 612
entering enterprise server
information, 617
entering plan location information,
614
finalizing the installation plan, 620
remote locations, 620
running the planner validation report,
621, 660
starting Installation Planner, 611
verifying deployment server
information, 615
utilities
revalidating software protection
codes, 133
uninstalling OneWorld, 137
workstations, 91
interactive mode, 98
silent mode, 912
Installation overview, 35
deployment server, 37

Installation Guide
environments, 313
Installation Planner, 37
OneWorld Java Server, 13
process, 35
whats new, 21
Push installation, 12
web installation, 13
Windows NT Terminal Server Edition,
13
Installation Planner, 71
additional servers
configuring, 1264
entering a plan location, 1244
entering deployment server
information, 1246
entering enterprise server
information, 1248
finalizing the installation plan, 1262
setting up environment data sources,
1257
cluster software, 65
configuring servers, 71
control table merges, 63
custom installation
defining a remote plan, 125
defining AS/400 common data
sources, 661
defining machine / server types, 637
entering enterprise server data
source information, 635, 1215,
1251
entering enterprise server
information, 633
entering location information, 629
entering plan description, 627
entering shared datasource
information, 644
finalizing the installation plan, 659
selecting an environment, 648
setting up environment data sources,
654
setting up environments, 648
starting Installation Planner, 626
verifying deployment server
information, 631
verifying enterprise server
information, 633
custom plan, 625
remote installation, 123
data sources, 65

defining AS/400 common data sources,


661
defining the AS/400 Common data
source, 661
deleting servers or machines, 1277
deployment servers, 64
enterprise servers, 65
languages, 63
locations, 64
package setup and builds, 38
planning servers, 71
processing options, 1265
purpose, 37, 63
remote installation
concluding the remote installation
plan setup, 1238
defining machine / server types,
1217
entering information into Installation
Planner, 126
entering plan location information,
128
finalizing the installation plan, 1239
replicating data, 1223
selecting an environment, 1230
setting up environment data sources,
1233
setting up environment datasources,
1233
setting up environments, 1228
specifying a deployment server, 129
specifying an enterprise server,
1212
verifying enterprise server
information, 1212
remote installation plan, 124
entering shared datasource setup
information, 1226
remote locations, 659
typical installation
entering a plan description, 612
entering enterprise server
information, 617
entering plan location information,
614
finalizing the installation plan, 620
remote location, 620
running the planner validation report,
621, 660
starting Installation Planner, 611

OneWorld Xe UPDATE (8 February 2002)

Index
verifying deployment server
information, 615
typical plan, 611
Installation Planner Utilities, additional
servers, entering a plan description, 1243
Installation Workbench, 38, 71, 75
configuring your control tables, 720
configuring your data sources, 716
configuring your environments, 717
configuring your locations, 715
configuring your machines, 719
configuring your packages, 723
configuring your remote locations, 724
control tables, 74
data sources, 73, 716
environments, 73, 717
finishing the plan, 726
locations, 73, 715
merging your specification tables, 722
packages, 74, 723
servers, 73, 719
Specification Table Merge, 74
Installer
building a language package, 1020
building and deploying workstation
packages, 109
configuring your control tables, 721
configuring your data sources, 716
configuring your environments, 718
configuring your machines, 719
configuring your packages, 723
configuring your remote locations, 725
defining a custom installation plan, 626
defining a typical installation plan, 611
finishing Installation Workbench, 726
installing an alternate language on the
deployment server, 521
installing AS/400 libraries and the data
dictionary, 523
installing file transfer protocol (FTP),
55, 59
installing the objects, 512
merging your specification tables, 722
running the Installation Workbench,
713, 714, 715
setting up the TCP/IP protocol for the
enterprise server, 526
starting Installation Workbench, 712

OneWorld Xe UPDATE (8 February 2002)

Installing an alternate language on the


deployment server, 520
installer, 521
Installing AS/400 libraries and the data
dictionary, installer, 523
Installing file transfer protocol (FTP), 55
installer, 55, 59
Installing language release, Deployment
server, 1280
Installing OneWorld for SQL Server, 541
Installing OneWorld on a workstation
deployment server, Client JDE.INI file,
93
interactive mode, 94, 98
push installation, 94
silent mode, 94, 912
Installing OneWorld on the deployment
server, 53
alternate language, 520
configuration, 53
Data Dictionary, 522
objects, 512
TCP/IP protocol, enterprise server, 526
Windows NT security, 113
Installing OneWorld on the enterprise
server, 83, 87, 89
AS/400
configuration, 83
starting the server, 817
verifying the installation, 814
enterprise server JDE.INI file,
deployment server, 88
job queue, 813
output queue, 812
default printer, 812
setting up a printer, 819
Installing Oracle for Windows NT, 529
Installing the data dictionary, 522
Installing the objects, 512
installer, 512
Installing the OneWorld databases, 529
Installing the workstation, alternate
languages, 91
Interactive mode
installation on a client workstation, 98
installation on a workstation, 94
installing a workstation, 98
Internet Information Server, 54
Inventory Management (system 41),
1121

Installation Guide

J
J.D. Edwards OneWorld Scripting Tool.
See AutoPilot
J.D. Edwards Update Center, 14
JDE user, deployment server, 54
JDE.INI file, modifying for Home Page
(Solution Explorer), 1131
JDE.INI files
[INSTALL], deployment server, 96
[INTERACTIVE RUNTIME], deployment
server, 96
[JDENET], port number, 96
[NETWORK QUEUE SETTINGS],
deployment server, 96
[SECURITY], DefaultEnvironment
setting, 89
enterprise server and workstations,
327
language, 89
language support, setup, 96
modifying the enterprise server file on
the deployment server, 88
PORTTEST, troubleshooting, 816
setting, 1016
JDESET.BAT file, editing environment
variables, 539
Job log information, FTPOUTPUT file,
811
Job queue, 813
unused sequence number, 813

K
Knowledge Garden, Help You Install page,
13

L
Language
adding to a plan, 63
deployment server, 520
JDE.INI file, 89
JDE.INI settings, 91
preference codes, 93
process flowchart, 323

process overview, 1285


recreating replicated data dictionary
files, 1112
setting up the JDE.INI file, 96
Language architecture, 319
base language, 320
language preference codes, 321, 95
National Language Support, 326
Language CD, installing, 1280
Language character set, installing on
workstation, 1286
Language flag icon, conventions for this
guide, 19
Language Installation, process, 1285
Language installation
building and deploying packages, 1020
deployment server, 323
disk space requirements, 434
updating the enterprise server, 832
workstation, 324, 91
Language Only installation, customer
checklist, 1279
Language Only plan
checklist, 1279
creating, 1279
enterprise server INI settings, 1286
package build, 1287
user and group set up, 1286
workbenches, 1286
Language packages, deploying alternate
languages, 1020
Language preference codes
alternate languages, 321
base language, 321
default language record, 321
determining codes, 93
supported languages, 321
user profile, 321, 95
Language text, 321
Languages, supported, 327
Libraries, AS/400, 522
creation, 524
License, 514
Listing WorldSoftware modifications,
coexistence with AS/400, 84
Loading central objects for Oracle, 538
Loading central objects for SQL Server 6.5
and 7.0, 545
Loading central objects in DB2/400, 547
LocalCodeSet, code page settings, 325

OneWorld Xe UPDATE (8 February 2002)

Index
Location Workbench, 73, 715
configuring your locations, 715
Locations
Installation Planner, 64
Installation Workbench, 73, 715
Logging in to OneWorld, 54
Logins, SQL Server database, 544

M
Machine / Server Types
custom installation
defining a data server, 639
defining a Java server, 641
defining a windows terminal server,
643
specifying machine / server types,
638
remote installation
defining a data server, 1218
defining a java server, 1220
defining a windows terminal server,
1222
specifying machine / server types,
1217
Machine / server Types, additional servers,
defining a Java server, 1253
Machine / server types, additional servers,
defining a Windows terminal server, 1255
Machine Workbench, configuring your
machines, 719
Machines, deleting machines, installation
plan, 1277
Maintenance
premier, 15
standard, 15
Managing the OneWorld databases, 529
Mapping objects to the enterprise server,
Vertex Quantum tax applications, 1137
Media object queue (Solution Explorer),
1129
Media object queue, modifying, 117
Menus, merge, 38
Merges
control tables, 38
Data Dictionary, 38
Menu, 38
User Defined Codes (UDC), 38

OneWorld Xe UPDATE (8 February 2002)

User Overrides, 38
Merging your specification tables, 722
installer, 722
Microsoft
Internet Information Server, 3.0, 55,
59
Visual C++ Compiler, 93
Minimum technical requirements (MTRs),
14
Modes
interactive, installing a workstation, 98
silent, installing a workstation, 912
Modifying media object queues, 118
Modifying OneWorld
accounts receivable, 1118
Base Price System, 1121
distribution flexible files, 1115
Inventory Management (system 41),
1121
Ledger Type Master file (F0025), 1117
R4094A batch application, 1121
Sales Order Management (system 42),
1121
SQL Server options, 1110
Word Search, 1122
Modifying OneWorld after the installation,
117
data dictionary files, 1111
Modifying the Client JDE.INI file, on the
deployment server, 93
Modifying the enterprise server JDE.INI file
on deployment server, 88
MTRs (minimum technical requirements),
14
Multinational code pages
verifying settings, 325
workstations, 326
Multitier environments, disk space
requirements, 410
Multitier locations, 124

N
National Language Support, code page
setup, 327
National Language Support (NLS), 326
multilingual code page settings, 326
Note icon, conventions for this guide, 19

Installation Guide

O
Object Librarian, data source, 65
Object Librarian data source, setup, 647
Objects, installation, 512
OCM mappings
environments, 315
verifying for package builds, 1014
ODBC data sources, DNT data sources,
67
OneWorld
accounts receivable
chargeback records, 1119
OneWorld Build (P039601), 1118
AS/400
enterprise server installation, 814
starting the enterprise server, 817,
818
stopping the enterprise server, 139
Autopilot, 1124
Base Price System, 1121
classes, 12
coexistence, WorldSoftware, 35
completing the installation, 111
database considerations, 529
disk space requirements, 431
installation, packages, 101
installation for SQL Server, 541
installation on the enterprise server,
87, 89
installation process, whats new, 21
Inventory Management (system 41),
1121
Java client, hardware and software
requirements, 420
Java development workstation,
hardware and software requirements,
420
Java Server
hardware and software requirements,
422
installation, 13
license, 514
modification, 117
Sales Order Management (system 42),
1121
setting up a printer on the enterprise
server, 819
signon, 54

stopping OneWorld, enterprise server,


139
training, 12
uninstallation, 137
user profiles, AS/400, 84
Vertex Quantum tax applications, 1133
Word Search, 1122
workstations, installation, 98, 912
OneWorld Verification Tool. See
Verification Tool
Oracle
central objects, 538
database users and owners, 537
installing OneWorld on Windows NT,
529
preparing the database, 533
rollback segments, 535
system tablespaces, 534
tablespaces, creation, 536
Output queue, 812
default printer, 812
Overview
database character set and code page
considerations, 324
environments, 313
installing OneWorld, 35
language architecture, 319
OWJRNL data source, setup, 646, 1258

P
Package build
approving, 1018
completing the assemble and build
process, 1017
completing the package definition
screen, 1018
configuring the NT Enterprise server,
1016
copying INF files, 1019
delete CAPS.dll, 1011
deleting BUSOBJ directories, 1014
deleting F98741 table records, 1017
deleting F98743 records, 1014
deploying to a CD burner, 1018
mapping UBEs locally, 1014
modifying the F9860 table, 1014
updating, 1018

OneWorld Xe UPDATE (8 February 2002)

Index
verifing OCM mapping, 1014
verify the CLOG.dll setting, 1013
verifying the F9631 table, 1015
verifying the jde.ini settings, 1016
Package Workbench, 74, 723
configuring your packages, 723
Packages
alternate languages, 1020
build considerations, 832, 1020
building packages, 109
defining, 1018
deployment considerations, 1021
installation, 101
Installation Workbench, 74, 723
setup and builds, 38
testing packages, 109
updating, 1018
workstations, 1020
Packages tab, processing options, 1275
Path codes
environments, 315
planner environment, 315
Planner environments, 315
database, 315
path code, 315
Planning and configuring servers, 71
additional servers, 1242
Installation Workbench, 75
remote installation, 125
Planning the installation, 63
custom plan, 625
remote installation, 123
typical plan, 611
PortalLite directory (Solution Explorer),
1131
PORTTEST
AS/400, verifying the enterprise server
installation, 815
troubleshooting, 815
communication issues, 816
JDE.INI issues, 816
Pre-installation procedures, 41
Premier maintenance, 15
Preparing and installing DB2/400 for
OneWorld
Creating the processing option text file,
double-byte languages, 76
loading central objects, 547

OneWorld Xe UPDATE (8 February 2002)

Preparing and installing OneWorld for SQL


Server, 541
creating databases, 542
database logins and users, 544
loading central objects, 545
Preparing and installing Oracle for
Windows NT, 529
central objects, 538
database users and owners, 537
preparing the database, 532
verifying code page settings, 530
verifying the configuration, 532
Preparing the database for OneWorld,
533
Preparing the Oracle database for
OneWorld, 532
preparing the database, 533
rollback segments, 535
tablespaces, creation, 536
Preparing the rollback segments, 535
Prerequisites, installation, 12
Printers
enterprise server, 819
RMTPRTQ parameter, 812
Printing
adding a printer, 819
defining a default printer, 830
Pristine environments, 317
Process flow for installation, 310
Processing options, Installation Planner,
1265
Completion tab, 1271
Default Mode tab, 1269
Functions tab, 1274
Packages tab, 1275
Prompting tab, 1267, 1268
Replication tab, 1272
Status Change tab, 1270
Production environments, 317
custom modifications, 316
Profiles, 95
AS/400 users, 84
Programs and IDs
Conversion Audit report (P03961),
1118
P03960 (WorldSoftware Build), 1118
P039601 (OneWorld Build), 1118
P03961 (Conversion Audit report),
1118
P09940 (Update Ledger Type), 1117

Installation Guide
Prompting tab, processing options, 1267,
1268
Push installation, 12
workstation, 94

Q
QSERVER subsystem, Client Access on
the AS/400, 86
Query By Example, QBE, 327

R
RDBMS, 529
Recreating replicated data dictionary files,
1111
Refreshing the pristine environment, 317
Refreshing the prototype environment,
317
Relational database management systems
(RDBMS), 529
Remote Installation
concluding the remote installation plan
setup, 1238
defining a deployment server, 1210
defining machine / server types, 1217
define a data server, 1218
define a Java server, 1220
define a Windows Terminal server,
1222
specifying machine / server types,
1217
entering information into Installation
Planner, 126
entering plan location information, 128
final status, 1239
finalizing the installation plan, 1239
machine / server types
defining a data server, 1218
defining a java server, 1220
defining a windows terminal server,
1222
specifying machine / server types,
1217
replicating data, 1223
selecting an environment, 1230

setting up environment data sources,


1233
setting up environment datasources,
1233
setting up environments, 1228
specifying a deployment server, 129
specifying an enterprise server, 1212
verifying enterprise server information,
1212
Remote Installation Plan, entering shared
datasource setup information, 1226
Remote installation plan, 124
custom installation, 123
Remote location, custom installation,
selecting an environment, 1228
Remote Locations
configuring, 724
installation plan, 620
planning, 659
Remote Printer Queue (RMTPRTQ), 812
Removing previous OneWorld
installations, 137
Replicated local specification files,
enterprise server, 832
Replication, definition of, 317
Replication tab, processing options, 1272
Reporting process, accounts receivable
conversion, 1118
Reports
Conversion Audit, 1118
R91014, 1130
Specification Table Merge, 723
Requirements
disk space, 431
hardware and software, 49
Resetting SQL Server options, 1110
Retrofitting custom modifications, Visual
ER Compare tool, 103
Revalidating software protection codes,
133
deployment server, 133
workstations, 134
Revalidating the deployment server, 133
Revalidating workstations, 134
Reviewing AS/400 coexistence setup
issues, 84
Reviewing processing options for
Installation Planner, 1265
RMTPRTQ parameter, printers, 812

OneWorld Xe UPDATE (8 February 2002)

Index
Rollback segments, preparation for Oracle,
535
Running the accounts receivable
conversion process, 1118
chargeback records, 1119
Conversion Audit Envelope, 1118
reporting process, 1118
work file build programs, 1118
Running the database creation script,
543
Running the Installation Workbench, 75
installer, 713, 714, 715
Running the login and user creation script,
545
Running the Planner Validation Report,
defining a typical installation plan, 621,
660
Running the R4094A batch application,
1121

S
Sales Order Management (system 42),
1121
SARs (software action requests), 14
Scripting Tool. See AutoPilot
Security
OneWorld directories, 113
Windows NT, 113
Select environments, additional servers,
1257
Selecting an Environment
custom installation, 648
remote location, 1228
remote installation, 1230
Sequence number, job queue, 813
Server Map data source, setup, 65,
636, 1216, 1252
Server Workbench, 73, 719
Servers
additional servers, 1241
configuring servers, 71
deleting servers, installation plan, 1277
Installation Workbench, 73, 719
planning servers, 71
setup, 37
Setting up a printer on the OneWorld
enterprise server, 819

OneWorld Xe UPDATE (8 February 2002)

Setting up Client Access on the AS/400


server to use with OneWorld, 86
Setting up Environment Data Sources
AS/400 Common data sources, 661
choosing an environment setup option,
654
custom installation, 654
define Client Access ODBC data
sources, 663
remote installation, 1233
select another environment, 658
setup Business Data data source, 657
setup Central Objects data source,
657
verify AS/400 Common data source,
654
verify Control Tables data source, 655
verify the OWJRNL data source, 645
verify the Versions data source, 656
Setting up environment data sources,
additional servers, 1257
Setting up Environment Datasources,
remote installation, 1233
Setting up Environments
custom installation, 648
remote installation, 1228
select an environment, 650
select language environments, 653
specify environment data load
parameters, 651
verify advance parameters, 652
Setting up the ICP/IP protocol, 85, 86
Setting up the TCP/IP protocol for the
enterprise server, 526
installer, 526
system administrator, 526
Setting up the Windows NT deployment
server, 53
Setting up user profiles, 95
Setting up Windows NT security on
OneWorld directories, 113
Setup issues, AS/400 coexistence, 84
Setup recommendations, custom
modifications, 313
Signing on to OneWorld, 54
Silent mode
installation on a workstation, 94
installing a workstation, 912
Single-byte languages, code pages, 327
Software Action Requests (SARs), 14

Installation Guide
Software protection codes
deployment server, 133
revalidating codes, 133
workstations, 134
Software updates (ASUs, ESUs), 14
Solution Explorer
definition, 1129
Find It! program, 1130
Home Page, setting up, 1131
setting up the HTML documentation
path, 1129
Word Search Generation program,
1130
Specification Table Merge, Installation
Workbench, 74
Specification Table merge, reviewing the
merge report, 723
Specification Table Merge Workbench, 74
merging your specification tables, 722
Specification tables, merging your
specification tables, 722
Specifying (Custom or Default) Data
Source Information, enterprise server
information, custom installation, 635,
1215, 1251
Specifying a Deployment Server, remote
installation, 129
Specifying an Enterprise Server, remote
installation, 1212
Specifying machine / Server Types
custom installation, machine / server
types, 638
remote installation, machine / server
types, 1217
SQL Server
creating databases, 542
database creation script, 542, 543
database logins and users, 544
installing OneWorld, 541
loading central objects, 545
login and user creation script
editing the script, 544
running the script, 545
resetting options, 1110
Standard maintenance, 15
Standard packages, 320
multiple languages, 321
Standards, National Language Support,
326

Starting Installation Planner


custom installation, 626
defining a typical installation plan, 611
Starting Installation Workbench, installer,
712
Starting the OneWorld AS/400 enterprise
server, 817, 818
verifying the installation, 814
Status Change tab, processing options,
1270
Stopping OneWorld on the enterprise
server, AS/400, 139
Stopping the OneWorld AS/400 enterprise
server, 139
Supported languages, 321
System administrator
building and testing packages, 109
creating a JDE user, 54
setting up the TCP/IP protocol for the
enterprise server, 526
System data source, 65
configuring for coexistence, 65
setup, 648, 1228

T
Tables
central objects, 722
F0002, 438, 440, 442, 444, 446,
66, 67
F00021, 66, 67
F0004, 321, 66
F0004D, 321, 66
F0005, 66
F0005D, 66
F0025, 1117
F0082, 66
F00821, 66
F00825, 1122
F00826, 1122
F0083, 66
F0084, 66
F0092, 65
F00921, 65
F0093, 65, 73, 717
F0094, 65, 73, 717
F00941, 73, 717
F00942, 64, 73, 717

OneWorld Xe UPDATE (8 February 2002)

Index
F00945, 64
F03960, 1118
F0902, 815, 817
F4094, 1121
F42019, 1115
F42119, 1115
F42199, 1115
F43199, 1115
F9202, 321
F9650, 65, 73, 719
F9651, 65, 73, 719
F9654, 73, 715
F983051, 522, 67
F98306, 522, 67, 722
F98403, 73, 717
F986101, 73, 717, 816
F98611, 64, 73, 716, 816
F986115, 73, 716
F98750, 722
F98760, 722
F9885, 74, 723
F9886, 74, 723
F9887, 74, 723
Tablespaces, creation for Oracle, 536
Tablespaces for the Oracle system, 534
TAMFTP, transferring data dictionary files,
1113
Tax applications, Vertex Quantum tax
applications, 1133
TCP/IP
protocol setup, 526
SQL Server database, 542
TCP/IP protocol, setup, 85, 86
Terminal Server Edition (TSE), Windows
NT, 425, 427
Test environments, 316
training classes, 317
Testing packages, 109
Testing the Vertex Quantum connection
from OneWorld, 1138
Thirdparty products
Adobe Acrobat Reader, 94
installing, 910
Microsoft Internet Explorer, 94
Time estimates for installation, 310
Tips and techniques boxes, conventions
for this guide, 18
Training
OneWorld, 12
test environment, 317

OneWorld Xe UPDATE (8 February 2002)

Transferring data dictionary files to your


enterprise server, 1113
Troubleshooting
boxes, conventions for this guide, 18
PORTTEST, 815
TSE (Terminal Server Edition), Windows
NT, 425, 427
Typical customer configuration, 35
Typical Installation
defining a deployment server, 616
entering a plan description, 612
entering enterprise server information,
617
entering plan location information, 614
finalizing the installation plan, 620
running the planner validation report,
621, 660
starting Installation Planner, 611
verifying deployment server information,
615
Typical installation, final status, 620
Typical installation plan, 611
Typical Plan, Language Only installation,
1281
typical plan, remote locations, 659

U
UBEs, 1014
Unattended workbench, 78
Uninstalling OneWorld, 137
workstation, 138
Uninstalling OneWorld from the
workstation, 138
Updates, documentation, 13
Updating the enterprise server, language,
832
Updating the Ledger Type Master file
(F0025) P09940, 1117
Upgrade
hardware and software requirements,
49
running the plan, 75
Upgrade overview
Installation Workbench, 38
installations
enterprise server, 39
workstation, 310

Installation Guide
process flow, 310
User and group profile, Language Only
plan, 1286
User defined codes
coexistence, 718
F0004D table, 321
Ledger Type Master file (F0025), 1117
merge, 38
User display preferences, code pages,
329
User Overrides merge, 38
User profiles, 95
AS/400, 84
language preference code, 321, 95
workstations, 93
Users, creating for a deployment server,
54

V
Verification Tool, 43
with DB2 UDB database, 43
Verifying code page settings for Oracle,
530
Verifying Deployment Server Information
additional servers, 1247
custom installation, 631
defining a typical installation plan, 615
Verifying Enterprise Server Information
additional servers, 1248
custom installation, 633
remote installation, 1212
Verifying Oracle System tablespaces,
534
Verifying the AS/400 installation, 814
Verifying the OneWorld AS/400 enterprise
server installation, 814
PORTEST program, 815
Versions data source, 67
setup, 657, 1262
Vertex Quantum tax applications
configuring OneWorld, 1133
configuring the OneWorld database
connections, 1134
mapping objects to the enterprise
server, 1137
testing the connection from OneWorld,
1138

Visual C++ Compiler, 93


Visual ER Compare tool
AutoMerge, 107
interface, 104
launching, 103
reports, 106
Visual ER tool, 103

W
Web installation, 13
Web site (Knowledge Garden), 13
Whats new, installation process, 21
B73.3.3, 23
Wide area network (WAN), enterprise
server installation, 39
Windows NT
deployment servers
configuration, 53
hardware and software requirements,
49
installing objects, 512
installing OneWorld for Oracle, 529
preparing the Oracle database, 530,
532
security, 113
setting up the deployment server, 53
Terminal Server Edition (TSE), 425,
427
workstations, hardware and software
requirements, 416
Windows NT Terminal Server Edition,
installation, 13
Windows registry, 37
Word Search, 1122
Word Search Generation program
(Solution Explorer), 1130
Work file build programs, 1118
Worksheet, preparing for installation, 435
Workstation, uninstalling OneWorld, 138
Workstation installation, granting disk and
registry access, 1311
Workstations
building and deploying packages, 1020
code page settings, 326
installation, 91
installing OneWorld, 310
interactive mode, 98

OneWorld Xe UPDATE (8 February 2002)

Index
silent mode, 912
JDE.INI file and code page setup, 327
language installation, 324, 91
operating systems, 310
revalidation, 134
setting up user profiles, 93, 95
uninstalling OneWorld, 138
Windows NT, hardware and software
requirements, 416
WorldSoftware
accounts receivable
chargeback records, 1119
Conversion Audit Envelope, 1118
Conversion Audit report, 1118
conversion to OneWorld, 1118
WorldSoftware Build (P03960), 1118
coexistence
data library, 655
OneWorld, 35
defining the AS/400 COMMON data
source, 661
distribution flexible files, 1116
Ledger Type Master file (F0025), 1117
listing modifications, 84
merges for coexistence, 38
Worldwide Customer Support, 14

OneWorld Xe UPDATE (8 February 2002)

Installation Guide

OneWorld Xe UPDATE (8 February 2002)