IBM B73.3 User Manual

J.D. Edwards’ OneWorld B73.3 and
Windows Terminal Server for IBM Netfinity

Rufus Credle, Bryan Nguyen, Craig Parks, Miguel Angel Rubio

International Technical Support Organization

www.redbooks.ibm.com

SG24-5842-00

International Technical Support Organization

J.D. Edwards’ OneWorld B73.3 and
Windows Terminal Server for IBM Netfinity

July 1999

SG24-5842-00

Take Note!

Before using this information and the prod uct it supports, be sure to read t he ge neral informatio n in Appe ndix B,
“Special Notices” on page 323.

First Edition (July 1999)

This edition applies to J.D. Edwards’ OneWorld B73.3, Oracle8 for NT 8.0.5, Microsoft SQL Server 7.0, Windows NT
Server 4.0 Terminal Ser ver Edition, Networ k Sta tion Manager 3.0 4, Citrix MetaFrame 1.0, Lotus Domino Go
WebServer 4.6.2.2, Microsoft Visual C++ 5.0, Microso ft Internet Information Server 3.0, and Microsoft Access 7 .0
running on IBM Netfinity.

Comments may be addressed to:
IBM Corporation, Inter national Technical Support Organization
Dept. HZ8 Building 678
P.O. Box 12195
Research Triangle Park, NC 27709-2195

When you send information to IBM, you grant IBM a non-e xclusive right to use or distribute the information in any way
it believes appropriate without incurring a ny obligation to you.

© Copyright International Business Machines Corporation 1999. All rights reserved.

Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

1.1 The ITSO J.D. Edwards’ OneWorld and IBM Netfinity Lab Environment . . .4

Chapter 2. J.D. Edwards’ OneWorld B73.3. . . . . . . . . . . . . . . . . . . . . . . . . . .5

2.1 Configurable Network Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.2 The Advantages of Configurable Network Computing . . . . . . . . . . . . . . . . .9

2.3 Recommendations for Configurable Network Computing. . . . . . . . . . . . . .10

Chapter 3. Windows NT Server 4.0, Terminal Server Edition . . . . . . . . . . .13

3.1 IBM Network Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.1.1 IBM Network Station Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Chapter 4. IBM N etfin ity Family of Ser vers . . . . . . . . . . . . . . . . . . . . . . . . .19

4.1 About IBM Netfinity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

4.1.1 The Foundation for J.D. Edwards and Domino Applications . . . . . . .20

4.2 IBM Netfinity 3000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

4.3 IBM Netfinity 5000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

4.4 IBM Netfinity 5500 and 5500 M20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

4.4.1 IBM Netfinity 5500. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

4.4.2 Netfinity 5500 M20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

4.5 IBM Netfinity 7000 M10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Chapter 5. Sizing, Considerations, and Recommendations. . . . . . . . . . . .35

5.1 Hardware and Software Considerations and Requirements. . . . . . . . . . . .36

5.2 Hardware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

5.2.1 CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

5.2.2 Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

5.2.3 Hard Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

5.2.4 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

5.2.5 RAID Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

5.2.6 Fault Tolerance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

5.2.7 Backup and Recovery Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

5.2.8 Maintenance and Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

5.2.9 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

5.2.10 Networking Performance Hints for J.D. Edwards’ OneWorld . . . . . .49

5.3 Software Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

5.4 Hardware and Software Requirements for J.D. Edwards’ OneWorld . . . . .51

5.4.1 OneWorld Deployment Server Requirements . . . . . . . . . . . . . . . . . .52

5.4.2 OneWorld Enterprise Server Requirements . . . . . . . . . . . . . . . . . . . .55

5.4.3 OneWorld Workstation Requirements . . . . . . . . . . . . . . . . . . . . . . . .59

5.5 Preparing for OneWorld Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

5.5.1 OneWorld Installation Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

5.5.2 OneWorld Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . .64

5.5.3 Setting Up OneWorld Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

5.6 Requests for Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

5.6.1 The Sizing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

5.6.2 Sizing Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

© Copyright IBM Corp. 1999 iii

5.7 Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.7.1 Netfinity Enterprise Server Guidelines . . . . . . . . . . . . . . . . . . . . . . . 68

5.7.2 Sizing Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.8 Hardware and Software Requirements for Windows Terminal Server . . . 76

Chapter 6. Using ServerGuide for IBM Netfinity . . . . . . . . . . . . . . . . . . . . 79

6.1 ServerGuide Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.2 HardwareGuide and Windows NT Server 4.0. . . . . . . . . . . . . . . . . . . . . . 81

6.3 SoftwareGuide and Windows NT Server 4.0 . . . . . . . . . . . . . . . . . . . . . . 82

6.3.1 Installing Windows NT Server 4.0 Using the SoftwareGuide CD . . . 84

6.3.2 Operating System FixPaks CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . 85

6.4 SoftwareGuide CD-ROM with Windows Terminal Server Edition . . . . . . . 86

Chapter 7. Implementing Oracle8 and J.D. Edwards’ OneWorld. . . . . . . . 89

7.1 Deployment Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

7.2 Enterprise Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.2.1 Installing Oracle8 Enterprise Edition for Windows NT . . . . . . . . . . . 93

7.2.2 Verify Setup of Listener.ora and Tnsnames.ora Files. . . . . . . . . . . 106

7.3 Installing and Configuring J.D. Edwards’ OneWorld B73.3. . . . . . . . . . . 109

7.3.1 Preparing Rollback Segments, Tablespaces, and Cursors. . . . . . . 112

7.3.2 Installation Planner - Defining the Installation Plan . . . . . . . . . . . . 115

7.3.3 Validate the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

7.3.4 Running Release Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

7.3.5 Running Installation Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . 141

7.3.6 Setting Up and Verifying the Hosts File . . . . . . . . . . . . . . . . . . . . . 146

7.4 Installing OneWorld on the Enterprise Server . . . . . . . . . . . . . . . . . . . . 147

7.4.1 Starting the OneWorld Windows NT Enterprise Server . . . . . . . . . 150

7.5 Setting Up a Printer on the OneWorld Enterprise Server . . . . . . . . . . . . 152

7.5.1 Adding a Paper Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

7.5.2 Adding a Physical Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

7.5.3 Defining a Conversion Program. . . . . . . . . . . . . . . . . . . . . . . . . . . 154

7.5.4 Adding a Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

7.5.5 Adding a Default Logical Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . 155

7.6 Setting User and Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

7.6.1 Creating a User and Group Profile. . . . . . . . . . . . . . . . . . . . . . . . . 156

7.6.2 Assigning Packages to a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

7.6.3 Assigning Environments to a Profile. . . . . . . . . . . . . . . . . . . . . . . . 161

7.7 Installing Oracle8 Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

7.8 Installing OneWorld Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

7.8.1 Modify the JDE.INI File on the Deployment Server. . . . . . . . . . . . . 163

7.8.2 Modify the Setup.inf File on the Deployment Server. . . . . . . . . . . . 164

7.8.3 Installing OneWorld Client (Interactive Mode) . . . . . . . . . . . . . . . . 164

Chapter 8. Implementing Microsoft SQL Server 7.0 and OneWorld . . . . 167

8.1 Deployment Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

8.2 Enterprise Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

8.2.1 Installing Enterprise SQL Server for Windows NT . . . . . . . . . . . . . 176

8.3 Installing and Configuring J.D. Edwards’ OneWorld B73.3 . . . . . . . . . . . 185

8.3.1 Creating Databases for SQL Server 7.0. . . . . . . . . . . . . . . . . . . . . 189

8.3.2 Creating Database Logins and Users for SQL Server 7.0 . . . . . . . 192

8.3.3 Loading Central Objects for SQL Server 7.0 . . . . . . . . . . . . . . . . . 193

8.3.4 Installation Planner - Defining the Installation Plan . . . . . . . . . . . . 193

8.3.5 Validate the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

8.3.6 Running Release Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

iv J.D. Edwards’ OneWorld B7 3.3 a nd Wi ndows Terminal Server

8.3.7 Running Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . .226

8.3.8 Setting Up and Verifying the Hosts File. . . . . . . . . . . . . . . . . . . . . .231

8.4 Installing OneWorld on the Enterprise Server . . . . . . . . . . . . . . . . . . . . .232

8.4.1 Starting the OneWorld Windows NT Enterprise Server . . . . . . . . . .235

8.5 Setting Up a Printer on the OneWorld Enterprise Server. . . . . . . . . . . . .238

8.5.1 Adding a Paper Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

8.5.2 Adding a Physical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

8.5.3 Defining a Conversion Program. . . . . . . . . . . . . . . . . . . . . . . . . . . .240

8.5.4 Adding a Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

8.5.5 Adding a Default Logical Printer . . . . . . . . . . . . . . . . . . . . . . . . . . .241

8.6 Setting User and Group Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

8.6.1 Create a User and Group Profile. . . . . . . . . . . . . . . . . . . . . . . . . . .242

8.6.2 Assign Packages to a Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

8.6.3 Assigning Environments to a Profile . . . . . . . . . . . . . . . . . . . . . . . .247

8.7 Installing OneWorld Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

8.7.1 Modify the JDE.INI File on the Deployment Server . . . . . . . . . . . . .248

8.7.2 Modify the Setup.inf File on the Deployment Server . . . . . . . . . . . .248

8.7.3 Installing OneWorld Client (Interactive Mode) . . . . . . . . . . . . . . . . .249

Chapter 9. Implementing Windows NT Terminal Server Ed ition . . . . . . .251

9.1 Types of Windows NT Server Installs for IBM Network Station Manager.251

9.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .252

9.3 Prerequisites Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253

9.4 Installation of Windows NT Server 4.0, Terminal Server Edition . . . . . . .254

9.5 Installation of IBM Network Station Manager and Additional Products . . . 254

9.5.1 Installation of Netscape Navigator 4.0. . . . . . . . . . . . . . . . . . . . . . .256

9.5.2 Installation of Lotus Domino Go Webserver. . . . . . . . . . . . . . . . . . .257

9.5.3 Installation of IBM Network Station Manager. . . . . . . . . . . . . . . . . .260

9.5.4 Verify the Network Station Manager and Components Installation. .266

9.5.5 Create NSMAdmin and NSMUser Groups. . . . . . . . . . . . . . . . . . . .268

9.5.6 Lotus Domino Go Webserver Service Startup . . . . . . . . . . . . . . . . .271

9.6 MetaFrame from Citrix Systems Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

9.6.1 MetaFrame Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

9.7 Activate MetaFrame Licensing on Windows NT Terminal Server Edition.275

9.8 ICA Client Setup on Windows Terminal Server . . . . . . . . . . . . . . . . . . . .277

9.8.1 Network Station Client Configuration for OneWorld. . . . . . . . . . . . .279

9.8.2 Workstation Client Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281

9.8.3 MetaFrame Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288

9.9 Configure Installation Planner for Windows NT Terminal Server . . . . . . . 289

9.9.1 Run Installation Workbench for the Windows Terminal Server Plan. 309

9.10 Installing and Configuring the OneWorld Client on WTS . . . . . . . . . . . .315

9.10.1 Assigning Environments to Profile. . . . . . . . . . . . . . . . . . . . . . . . .315

9.11 Installing OneWorld Client on Windows NT Terminal Server . . . . . . . . .317

9.11.1 Instructions for MDAC2.1 and TSE . . . . . . . . . . . . . . . . . . . . . . . .317

9.11.2 Modify the JDE.INI File on the Deployment Server . . . . . . . . . . . .318

9.11.3 Modify the Setup.inf File on the Deployment Server . . . . . . . . . . .318

9.11.4 Installing OneWorld Client (Interactive Mode) . . . . . . . . . . . . . . . .319

Appendix A. Modify Setup.inf and ODBCDataSource.inf for SQL Server 321

Appendix B. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Appendix C. Rela te d Public at ions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

C.1 International Technical Support Organization Publications. . . . . . . . . . . . . . 327

v

C.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327

C.3 Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327

C.4 Referenced Web Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327

How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

IBM Redbook Fax Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

vi J.D. Edwards’ OneWorld B7 3.3 a nd Wi ndows Terminal Server

Preface

This redbook describes how to implement the Enterprise Resource Planning
(ERP) and thin client solutions, J.D. Edwards’ OneWorld B73.3, and Microsoft
Windows NT Server 4.0, Terminal Ser ver Edition on IBM Netfinity servers. In
particular, it covers the planning and installation of OneWorld B73.3 using
Oracle8 Enterprise Edition for Windows NT and Microsoft SQL Server 7.0. In
addition, it covers the planning and installation of Microsoft Windows NT Server

4.0, Terminal Ser ver Edition using Citrix MetaFrame to connect to multiple IBM
Network Stations, and the latest IBM Nefinity family of servers that includes the
new Pentium III Xeon technology and other IBM features.

This redbook is designed to provide you with an easy understanding of the
implementation process, the installation, and the environments of OneWorld
optimized for the IBM Netfinity system. We’ve included an introduction to J.D.
Edwards’ OneWorld, its architecture and business solutions; the roles and
advantages of the Windows NT Terminal Server and IBM Network Stations, the
Netfinity sizing and implementation process for optimizing and configuring
OneWorld for Windows NT and hardware and software considerations
information to help in your decision making.

Also shared in this redbook are instructions on the use of IBM’s latest
ServerGuide that is used to set up the Netfinity hardware and prepare your
system for Windows NT Server, and the Netfinity Manager, a systems
management solution to monitor and manage the Deployment and Enterprise
server and OneWorld workstation clients.

In our example of the sizing and implementation process, we provide a scenario
on how you would prepare and configure the IBM Netfinity server for OneWorld’s
Pristine, Production, Development, and Conference Room Pilot environment
using Oracle8 for NT and Microsoft SQL Server 7.0 relational databases.

This redbook is not designed to replace the J.D. Edwards’

Guide (Windows NT-Based Systems), Release B73.3

help you quickly set up and run the OneWorld solution in an organization or
corporate environment.

It is assumed that the reader of this redbook has had some education and work
experience in using Oracle8 Enterprise Edition for NT, Microsoft SQL Server 7.0,
Microsoft Windows NT Server 4.0, and J.D. Edwards’ OneWorld.

OneWorld Installation

. This book is designed to

© Copyright IBM Corp. 1999 vii

The Team That Wrote This Redbook

This redbook was produced by a team of specialists from around the world
working at the International Tec hnical Suppor t Organization, Raleigh Center.

Figure 1. The Team (left to right), Credle, Parks, Rubio, Nguyen

Rufus Credle is an Advisory Software Engineer and certified Professional Server
Specialist at the International Tec hnical Suppor t Organization, Raleigh Center.
He conducts residencies and writes redbooks about IBM Netfinity servers and

network operating systems. Rufus’s various positions during his IBM career have
included assignments in administration and asset management, system
engineering, marketing and services. He holds a BS degree in Business
Management from Saint Augustine’s College. Rufus has been employed at IBM
for 19 years.

Craig Parks is a consultant with the IBM Global Service’s ERP Practice
specializing in J.D. Edwards’ OneWorld architecture. He has over 10 years of
experience with systems, networking hardware and software installations, and
management software on various platforms. He is a Certified Microsoft
Professional and Certified NetWare Engineer . He holds a BS degree in Computer
Science from the University of West Georgia.

Bryan Nguyen is an ERP Consultant for IBM Global Service, IT Infrastructure of
North America. He is a qualified engineer who specializes in the architecture of
J.D. Edwards’ OneWorld application. His strong knowledge of both software and
hardware is backed by nine years of industry experience of various platforms
such as Windows NT, UNIX, and Novell. He holds a Bachelor of Science in
Aerospace Engineering.

viii J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Miguel Angel Rubio is an ERP Specialist Consultant for IBM Global Services in

Spain, specializing in J.D. Edwards’ WorldSoftware and OneWorld solutions. He
has 11 years of experience with IBM software and hardware products such as
AS/400 and Netfinity. He has over three years’ experience in the installation and
configuration of J.D. Edwards’ WorldSoftware and OneWorld applications. He
holds a degree in Business Management from Carlos III University in Spain.

Thanks to the following people for their invaluable contributions to this project:
David Watts, Jackie Kozel, Linda Robinson

International Tec hnical Support Organization, Raleigh Center
Diane Nissen, Pre-Sales Sizing Specialist, IBM ERP Pre-Sales Center

IBM Philadelphia
Pat Moore, Don Gaines, Boyd Fenton - Manager, IBM JDE International

Competency Center
IBM Denver

Claude Bechard, Senior Technical Marketing Suppor t Representative - ITSO
IBM Raleigh

Lee Pisarek, Server Implementation Specialist, IBM Netfinity Technology Center
IBM Raleigh

Al Hardy, IBM JDE EMEA Pre-Sales Solution Architect for Netfinity
IBM United Kingdom

Al Kalafian, Senior I/T Architect, IBM ERP Competency Center
IBM Philadelphia

Mark Owens, Manager Technical Consulting
World Technology Services, Seattle WA

Comments Welcome

Your comments are important to us!

We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:

• Fax the evaluation form found in “ITSO Redbook Evaluation” on page 333 to

• Use the online evaluation form found at

• Send your comments in an Internet note to [e-mail] m.com

the fax number shown on the form.

http://www.redbooks .ibm.com/

ix

x J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Chapter 1. Introduction

When a company talks about Enterprise Resource Planning (ERP), it’s talking
about a top-to-bottom transformation of the way it operates, does business and
faces the future. Changes are set in motion regarding how the company is
managed, how it serves customers, and how it reacts to the marketplace. Such a
transformation will ultimately affect the fundamental ingredients of success that
are directly involved: greater customer satisfaction, reduced cycle time,
increased productivity.

In this wide perspective, a new information technology infrastructure is part of a
large moving picture that can involve reengineering business processes,
overhauling the roles, responsibilities and daily routines of personnel and
implementing application software. However, this does not happen overnight and
as companies are realizing all over the world, help is needed. From the time that
an ERP requirement is identified through implementation and beyond to
operations, IBM and J.D. Edwards will help you enhance your business
processes.

A company’s decision to implement the enterprise software and modules of J.D.
Edwards’ SCOREx (supply chain optimization and real-time extended execution)
is predicated on the desire to reduce the incremental cost of adding new business
and provide its customers with superior service and extended business
processes throughout the supply chain. When it comes to running J.D. Edwards’
applications, IBM has the leading technology and the depth and breadth of
experience to provide your customer with a total solution. The customer’s
business needs may dictate a stand-alone configuration or a mix and match of
AS/400 models, Netfinity servers, RS/6000 servers and IBM Network Stations.
When it comes to quality and choice, IBM is the only alliance partner for J.D.
Edwards that can fulfill UNIX, Windows NT, and OS/400 platforms.

ERP solutions from J.D. Edwards have helped thousands of businesses across
the world translate good ideas into good business practices. Today, a great idea
is J.D. Edwards’ OneWorld and IBM Netfinity systems. Both offer you the fully
integrated, rich business functionality J.D. Edwards is known for, matched with
the scalability, the power, and performance of IBM Netfinity running Windows NT
Server.

It’s been two decades since IBM and J.D. Edwards teamed up to deliver flexible
ERP solutions that dramatically improve the management of factories,
inventories, people, and equipment. With J.D. Edwards’ OneWorld and IBM
Netfinity systems, you will leverage the mutual strengths of two industry leaders
to streamline the flow of information among your employees, customers,
suppliers, and partners. IBM and J.D. Edwards have managed operation
offerings, and IBM’s service organization installs J.D. Edwards’ software.

© Copyright IBM Corp. 1999 1

The reasons why more and more organizations continue to acquire the J.D.
Edwards solution are based upon the flexibility, the simplicity , and the adaptability

of the company’s products unmatched by any of its competitors. The solutions
listed below provide direct benefits to the customer:

• Integrated Solutions
J.D. Edwards’ software helps streamline customers’ businesses by providing

the capability to implement and view real-time information updates across the
organization. This allows customers to access and utilize consistent and
current information, and keep up with the speed of change.

• Network-Centric Computing
When change in an organization’s operation is necessary, J.D. Edwards’

network-centric architecture allows customers to write the change once and
safely deploy the change across their entire organization. With this kind of
flexibility and adaptability, customers can maximize performance.

• Tools
With tools such as ActivEra, you remain in control of your business and your

system remains the solution. With the ability to modify your system on the fly,
both during and after implementation, your organization can respond to
market changes and put ideas into action with the greatest of ease.

ActivEra's tools and technologies extend the capabilities of all J.D. Edwards’
software. Business activators allow your business professionals to put new
ideas into practice without programmer involvement. And technology
activators enable your technical professionals to streamline management of
your system's infrastructure. With ActivEra, everyone in your organization can
turn ideas into action.

• J.D. Edwards’ JDExpert and OnTrack
To help simplify and expedite your implementation process, J.D. Edwards

offers JDExpert, a service and implementation partner program suppor ted by
OnTrack, its new implementation approach and toolset. Providing a vast array
of professional expertise, the JDExpert program has grown to include more
than 5,750 certified consultants facilitating rapid implementations and services
for more than half of J.D. Edwards’ new customers.

JDExpert currently compri ses mor e than 200 business partners, including Big
Six firms, channel partners, and over 100 service partners, who are positioned
to successfully implement J.D. Edwards solutions while maintaining their
established high customer satisfaction levels. Their relationships with such a
broad range of partners allow you to leverage the latest technology and follow
the industry-practice models appropriate for your business.

Backing JDExpert is OnTrack, a set of configuration tools and methods
designed to simplify and accelerate your implementation. This new six-step
approach includes accelerated tools to provide the framework, custom-built
documentation to offer the b lueprint, and classroom tr aining to enab le ongoing
mentoring. Within OnTrack is an interactive business process configuration
tool (Composer is the configuration tool; OnTrack, the methodology) called
Composer, which gives you two options for configuring your solution by
process or application. Both configuration options integrate with your current
J.D. Edwards applications and provide a graphical display of business
choices.

2 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

OnTrack is so flexible that it even lets you modify your software after the
implementation is complete to incorporate subsequent changes in your
operations. With JDExpert and OnTrack guiding your enterprise software

implementation, life doesn’t have to be so complicated after all.

• J.D. Edwards’ SCOREx
Supply chain operation is a huge market focus. J.D. Edwards’ SCOREx

(supply chain optimization and real-time extended execution) is designed to
integrate and extend a company’s business life cycle and execute tailored
supply chain for individual customers. SCOREx offers an integrated solution
with functionality that ranges from advanced planning and scheduling, order
management, and warehouse management to transportation management
and cost management. SCOREx provides a dynamic, comprehensive
information backbone for managing processes and enterprise data between
supplier’s suppliers and customers’ customers.

• J.D. Edwards/IBM Alliance
By marrying IBM platforms with J.D. Edwards solutions, customers benefit

from an industry-leading partnership. And when they’re ready to expand to
Windows NT or UNIX for full utilization of supply chain, IBM’s solutions
complement J.D. Edwards’ flexibility.

Recently added to the J.D. Edwards’ OneWorld and IBM Netfinity solution is the
IBM Network Station. Windows NT Server 4.0, Terminal Ser ver Edition provides
an excellent solution for OneWorld in a LAN/WAN environment and is
complemented by the services of the IBM Network Station. More information on
the IBM Network Station is in 3.1, “IBM Network Stations” on page 15.

Introduction 3

1.1 The ITSO J.D. Edwards’ OneWorld and IBM Netfinity Lab Environment

To help you envision our lab environment as you prepare to explore the planning
and installation procedures in this redbook, the following has been provided:

Deployment Server

NT - Intel Only

IBM Netfinity 5500

Enterprise Server

LAN

NT - Intel

IBM Netfinity 5500

TSE OneWorld Client

IBM NSM

IBM Netfinity 5000

LAN

Standard

OneWorld

Client

IBM Network

Stati o n

Client

Figure 2. The IT SO J.D. Edwards’ OneWorld and IBM Ne tfinity Lab Environme nt

4 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

5842\584205

Chapter 2. J.D. Edwards’ OneWorld B73.3

J.D. Edwards’ O neWorld is a network-centric, object-oriented, multinational ERP
software package that provides customers with the flexibility to quickly adapt
business processes to meet market demands, and the ability to capitalize on the
latest functionality and lower costs offered by emerging technologies. As
databases and operating systems began to change more quickly, companies
required an open architecture that provided progressive platform flexibility.

J.D. Edwards responded by delivering OneWorld, an integrated suite of
client-server applications based on the company’s Configurable Network
Computing (CNC) architecture.

OneWorld offers a complete, integrated suite of ERP applications for today’s
commercial organizations. From traditional ERP modules to industry-specific
functionality, OneWorld addresses the critical business requirements of the
fast-moving, resourceful ventures that compete and succeed in today’s global
economy.

• Financial Applications
General accounting, accounts payable, accounts receivable, financial

modeling and budgeting, financial reporting, fixed assets, cash-basis
accounting. Full concurrent-use inter national c apabilities includi ng roughl y 23
languages (including double-byte Janji,) and numerous currencies along with
specialized taxation, tariff accounting and regulatory management modules to
accommodate local requirements in each location. OneWorld is also designed
to accommodate and comply with new and changing currencies as they
evolve. For example, OneWorld is well-positioned to respond to the proposed
single European currency requirements; existing functionality enables
multicurrency processing, including pricing, dual currency general ledger
restatement and flexible fixed asset rules.

• Manufacturing Capabilities
Shop floor management, product data management, forecasting, scheduling,

capacity planning, change management, work order management, facilities
planning, procurement, maintenance management, configuration
management, environmental management. Single Pass planning capabilities
centralize multiple locations and mixed-mode production processes under one
worldwide Requirements Planning umbrella. Specialized manufacturing
capabilities include process, discrete, mixed mode and repetitive modes of
manufacturing.

• Distribution/Logistics
Inventory management, stock valuation and management, warehouse

management, transportation management, load and delivery management,
labor management, and electronic commerce.

• Human Resources
Payroll, time accounting, benefits administration, Human Resources

budgeting, position control, turnover analysis, organizational development,
recruiting management, multiskill search, job posting, salary and wage
administration, and ad hoc reporting.

© Copyright IBM Corp. 1999 5

• Vertical Solutions
Architecture, engineering, construction, mining, real estate, energy/chemical,

utilities, and public services.

OneWorld, introduced in 1996, provides a true distributed object architecture and
an advanced business rules engine that transcend traditional client/server
technology.

Its unique network-centric architecture separates business functionality from the
underlying operating systems, communications, and database technologies,
enabling organizations to embrace new technologies without rethinking or
reengineering existing information flow. OneWorld’s architectural foundation,
advanced graphical user interface, integrated toolset, and platform neutrality
deliver the stability and flexibility necessary to deal with ever-changing business
needs.

OneWorld combines mission-critical enterprise applications with extensive
offerings specific to the rapidly changing needs of business today. OneWorld is
an evolution of the J.D. Edwards’ popular WorldSoftware and WorldVision
products and provides a bridge between traditional enterprise resource planning
(ERP) functions and customer interaction programs such as customer support,
direct marketing and sales force automation, creating dynamic, customer-centric
supply chains.

OneWorld is designed from the ground up to interface with legacy business
management applications, PC-based functions, best-of-breed niche solutions,
reporting tools and other functions used by an organization. J.D. Edwards utilizes
advanced application programming interfaces (APIs) to provide OneWorld with
the flexibility to integrate with applications using a wide variety of databases,
communication protocols, programming languages, standards and operating
systems offering you a wide degree of freedom and flexibility to tailor the IT
function and infrastructure to best suit your customer needs.

To maintain a competitive edge, your organization faces both business and
technology challenges. J.D. Edwards addresses these challenges with
multinational, multicurrency, global business solutions on an application
architecture that masks complexity, leverages technology, and paves the way to
the future.

Today, J.D. Edwards’ OneWorld and IBM Netfinity systems offer you the fully
integrated, rich business functionality J.D. Edwards is known for, matched with
the scalability, power, and performance of IBM Netfinity running Windows NT.

OneWorld’s Configurable Network Computer (CNC) is a type of software
architecture that allows you to distribute application components to run on a
variety of platforms without the need of a specific platform on which the database
is run. This also allows the user to change technologies without rewriting
applications. The OneWorld physical configuration include:

The Deployment Server - is the central point of the OneWorld installation
process from which the Deployment Server distributes the OneWorld software
to one or more enterprise servers and client workstations. Also, this allows the
Deployment Server to define new types of servers. With this release of
OneWorld B73.3, it is possible to set up Java application servers (JAS), a

6 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Windows Terminal Server (TSE), and data servers. During the installation
process you can add other Deployment Servers (multitier deployment).

The Enterprise Server - is one or more servers that operates as the data
storage and can run the centralized logic. OneWorld Enterprise Server is
currently supporting the following database management systems:

• IBM DB2 on AS/400 hardware platform

• Oracle Database Management System on both UNIX and Windows NT
platforms

• MS SQL server DBMS on Windows NT platforms.

The IBM hardware platforms currently supporting OneWorld Enterprise Server
are:

• IBM - AS/400 using the OS/400 operating system

• IBM - RS/6000 using the UNIX operating system

• IBM - Netfinity using Microsoft NT operating system

Workstations - are PCs that have OneWorld client software installed and
provide the interface between the user and data. The Workstation works two
ways:

Direct Connect Processing - allows a user to distribute data and logic while
connected to the Enterprise Server by TCP/IP protocol.

Store and Forward Processing - allows a user to work on a workstation that is
disconnected from a server.

These components can exist within a single computer or across several different
computers. The single computer environment is recommended only for training
and demonstrations (Demo Junior).

The actual install process consists of six general steps:

1. Installing the basic software requirements for the Deployment Server and the
Enterprise Ser ver, such as Windows NT Server 4 and Service Packs,
Microsoft Internet Services, Microsoft Access, Visual C++, SQL Server or
Oracle for Windows NT. For specific versions see 5.4, “Hardware and
Software Requirements for J.D. Edwards’ OneWorld” on page 51.

2. Installing the basic software requirements for the workstations, such as
Windows 95, Windows 98 or Windows NT Workstation, Microsoft Access,
Visual C++ (only required for programming), SQL Server Client or Oracle
Client.

3. Installing OneWorld on the deployment server from the CD-ROM:

• CD1 - copies the path codes for the environment you want to install

• CD2 - copies the component you need for building your database

4. Setting up the installation plans for the enterprise server by running the
Installation Planner. OneWorld Installation Planner provides different
environments for different purposes:

• PRT733 - Pristine Environment

Contains pristine objects that cannot be modified but are used for
comparison with other environment. This is used for disaster recovery and
response line problem solving.

J.D. Edwards’ OneWorld B73.3 7

• CRP733 - Conference Room Pilot Environment
This environment is used in an initial phase of implementation. During this

phase the CRP is used for converting non-JDE tables and creating UDCs
and menus. This is used to load data into the different system tables
(general accounting, accounts payable, accounts receivable, etc). It’s used
too for future upgrades.

• TST733 - Test Environment
This environment is used to run test modifications before the PRD733

environment is run.

• DEV733 - Development Environment
It’s used for custom development and shares test data with TST733.

• PRD733 - Production Environment
After the completion of CRP, the contents of CRP733 are copied here. This

is an environment for production end users.

These environments can be defined as a Typical Installation Plan or a Custom
Installation Plan. These concepts are discussed in detail in Chapter 7,
“Implementing Oracle8 and J.D. Edwards’ OneW orld” on page 89 and Chapter
8, “Implementing Microsoft SQL Server 7.0 and OneWorld” on page 167.

5. Installing OneWorld software on the Enterprise server by running Installation
Workbench.

6. Installing OneWorld software on the client workstations.

The OneWorld network-centric software architecture comprises the following
components:

• Design Tools

• Applications

• OneWorld Foundation Code

• OneWorld Middleware

These above components are discussed in detail in 2.1, “Configurable Network
Computing” on page 9.

Customers using OneWorld are not required to reengineer their organizations.
Users can initially leverage the competitive benefits of OneWorld to support
current operations without changing existing processes. At any time, customers

are free to evolve business processes at their own pace using J.D. Edwards’
"Best Business Practice" templates or the product’s extensive, easy-to-use
customization options.

8 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

2.1 Configurable Network Computing

OneWorld is built on a distributed-object, network-centric architecture called
Configurable Network Computing (CNC). J.D. Edwards describes Configurable
Network Computing as "an application architecture that allows interactive and
batch applications, composed of
network of multiple server platforms and SQL databases (Oracle, DB2, SQL
Server). The applications consist of reusable business functions and associated
data that can be configured across the network dynamically. The o verall objective
for businesses is to provide a future-proof environment that enables them to
change organizational structures, business processes, and technologies
independently of each other."

The CNC architecture provides greater flexibility, scalability, and systems
management ease by focusing on networks, rather than individual machines.
With it, you’ll be able to change your network configuration at
changing processes, organizational structures, and technology choices.

OneWorld comprises the following components:

• Design Tools
OneWorld provides a unified set of tools to create all interactive applications,

batch applications, and reports.

• Applications

a single code base

, to run across a TCP/IP

run time

to support

OneWorld provides the interactive and batch applications that perform your
business needs. F or example, Purchase Order Entry and General Ledger P ost
are applications.

• OneWorld Foundation Code
OneWorld provides underlying core processing that both interactive and batch

applications depend on to run. The Configurable Processing Engine
processes batch applications in OneWorld.

• OneWorld Middleware
OneWorld provides middleware that insulates your applications from the

underlying database, operating system, hardware, messaging systems, and
telecommunications protocols. This insulates your business solution from the
platform technology.

2.2 The Advantages of Configurable Network Computing

The advantages of CNC include:

• Network-centric software
Network-centric software provides immediate availability of enhancements to

business objects, business rules, modes of processing, hardware, and
databases to all supported applications.

OneWorld's middleware is comprised of a common set of APIs that integrate
multivendor, multiprotocol differences to insulate developers from the need to
program to a specific platform.

• Flexible, leveraged technology

J.D. Edwards’ OneWorld B73.3 9

OneWorld tools conceal the code to allow you to create applications without
having to master a programming language. Developers can reuse objects
between applications or different purposes to provide consistency throughout
all OneWorld applications. OneWorld also provides a common interface
between applications, so when you move from form to form, you see the same
general setup.

• Supports worldwide business requirements
OneWorld provides support for mixed currency and languages. It also

provides the ability to run OneWorld on platforms from servers to laptops. This
allows trav eling consultants to enter records in OneWorld on their laptop, then
send these updated records over the Internet to keep records as updated as
possible.

• Custom solutions without consequences
You can make custom solutions to business applications with little or no

consequences when you upgrade to a new release of OneWorld. This allows
you to maintain consistency, retain flexibility, and minimize the time required to
implement upgrades.

2.3 Recommendations for Configurable Network Computing

J.D. Edwards provides the following recommendations for Configurable Network
Computing:

• Fewer is better
More computers mean more administration. It might be necessary at times to

add computers to your network, but try to use as few as possible.

• Homogeneity
Tr y to have one type of server hardware, one operating system, and one

workstation operating system if possible. OneWorld supports a heterogeneous
network, but avoid this unless it is absolutely necessary.

• Batch processing has advantages
Batch processing is more efficient than interactive or real-time processing.

Electronic commerce or electronic data interchange (EDI) is an excellent way
to process transactions. Store and forward processing is another f orm of batch
processing that allows the advantages of real-time editing and quick response
time at workstations.

• Data warehousing
Offloading most report writing to a secondary computer or computers not only

relieves the processor load from the main server, it also increases the
response time of the interactive users. Fifty to seventy percent of computer
processing cycles are used for reporting and data analysis. Offloading this
processing to a separate data warehouse provides a substantial opportunity to
ensure satisfactory performance for both the interactive and batch users. It
also allows you to use analysis tools such as OLAP to analyze the data.

• Processing mode
The type of processing mode you are using should depend on the volume of

data entry. Real-time processing can be used for low-volume data entry, while
store and forward processing should be used for high-volume data entry. You

10 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

can use the batch of one concept as a compromise between real-time and
store and forward processing.

• Multitiered networks
The database management systems consume a great deal of computer

resources. Separating the J.D. Edwards’ applications from the database
management systems allows optimum computing power for both needs. This
creates a three-tiered network that consists of PC’s that connect to application
servers, that connect to database servers. A fourth tier would be created if
data warehousing was bought into play. Multitiered networks complic ate
matters, but also improve performance and scalability.

• Multiple servers by vertical
OneWorld can work with mixed databases concurrently across multiple

machines. Objects and data can be accessed from several mixed databases
including Microsoft Access, Oracle, SQL Server, and AS/400. You can also
have separate servers for different applications. For example, you can have a
separate server for accounts receivable, and a separate server for
manufacturing. You do not need a single, central server. This concept of
multiple servers working together is central to the concept of CNC.

• Data replication
Several facilities for data replication are provided by J.D. Edwards, including

OneWorld application for data replication that allows for just-in-time
replication, pull replication, push replication, and non-mode replication; and
the table conversion utility that is a batch replication process. OneWorld can
also utilize several open system tools that support the replication of data.

• Departmental and application work groups
To keep data replication simple, it is often preferable to replicate data to an

application server in a single group that performs the same business
functions. In a departmental work group, workstations would have no
replicated data. Only business objects would be replicated and maintained on
the department's application server. This setup decreases the amount of data
replication by minimizing the data transfer between the workstations and the
application servers.

J.D. Edwards’ OneWorld B73.3 11

12 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Chapter 3. Windows NT Se rver 4.0, Terminal Server Edit ion

Windows NT Server 4.0, Terminal Server Edition (TSE or WTS) is a multiuser
extension of the Microsoft Windows NT family of operating families. The TSE
environment is considered a thin-client architecture where all application
processing occurs centrally on the server. Because TSE clients will be available
for many different desktop platforms, TSE provides access to 32-bit
Windows-based applications from virtually any desktop and provides the
technology for organizations seeking to move into a pure 32-bit desktop
environment.

In the early 1990s, client/server technology emerged combining the flexibility of
the PC (client) with the power of mini and midrange computers known as servers.
The early incarnations of client/ser ver involved "fat clients" in which application
logic and user interface run on each workstation (client). Data management
functions execute on the server. This scenario is effective when client and server
reside on the same LAN (local area network), but the generated network traffic
can lead to performance issues when considering WAN (wide area network)
connections between the client and the server. Although client/server still proves
to be a compelling computing architecture for many enterprises, a growing
number of businesses are now looking for "thin clients" alternatives that provide
for better WAN or dial-up connection performance.

The Microsoft solution to this challenge is the introduction of Windows TSE. TSE
extends the reach of corporate networks by providing for LAN-like performance
over WAN and dial connections. TSE allows multiple users to run an application
located on a terminal server as if that application were running locally on the

user’s machine. The terminal server is located on the same LAN as the enterprise
server, while the end-user workstations can be connected to the terminal server
over a WAN or dial-up connection. By sending only the information necessary to
paint the screen and convey mouse and keyboard events, performance over
WAN and dial-up connections rivals that of normal client/server applications over
a LAN. Administering a single copy of an application on the terminal server
greatly reduces the total cost of ownership for that application.

There are three advantages of Windows Ter minal Ser ver:

• WAN Traffic Reduction

• Central Administration

• Desktop Administration

WAN traffic is greatly reduced using TSE because the architecture is built for
efficient usage of bandwidth-intensive programs. All of the processing of an
application takes place on the server, while only the mouse, video, and keyboard
traffic are being passed across the network. Also, the administration portion of all
the desktops are done from one central location and that is on the server. All
updates are done on the server saving administration time. The administrator no
longer has to visit each client to make any changes greatly reducing
administration costs. Remote users also gain from this; they no longer have to
worry about having the latest updates.

© Copyright IBM Corp. 1999 13

Citrix and Its Relationship to TSE

Microsoft and Citrix agreed to provide Windows-based terminal support for the
Windows NT environment. Since Windows NT 3.51, Citrix has developed a
multiuser technology called Winframe. Winframe is a technology based on a
presentation protocol called

Microsoft’s TSE runs on its own presentation protocol called

Protocol

Citrix now provides ICA support for Terminal Ser ver Edition through a product
they named
expands the client platform options. Where TSE client software supports Win16
and Win32 machines and some RDP-equipped Windows terminals, MetaFrame
supports client software using DOS, Win16, Win32, X-Ter m, Macintosh, Solar is,
Windows CE, and also ICA equipped network computers. Citrix Metaframe is an
add-on software for Terminal Server Edition.

Advantages of Utilizing Citrix with TSE are:

(RDP).

MetaFrame.

• Performance - with the MetaFrame’s ICA protocol, there is 20% less
bandwidth than with TSE’s RDP.

• Functionality enhancements - multiple network topologies are now
supported with Citrix. It not only supports TCP/IP but also IPX/SPX, PPP,
and NetBIOS. TSE only supports TCP/IP. However, keep in mind that
OneWorld only supports TCP/IP.

Independent Computing Architecture

MetaFrame replaces the older Winframe. MetaFrame

(ICA).

Remote Desktop

• CCPDD - MetaFrame allows the functions of cut/copy/drag/drop between
the session windows. TSE does not.

• Device mapping - MetaFrame allows the mapping of devices local to a
remote client such as hard drives, fax modems, and printers from the
Ter minal Ser ver - TSE only allows with printing which can only be done
through a workaround.

• Session shadowing - with MetaFrame loaded, TSE supports an
administration tool called session shadowing. This is useful for
administrators who want to audit remote sessions. It can also be used with
video conferences and support desk roles.

ICA and RDP are presentation services protocols that separate an application’s
logic from its user interface (UI), processing the logic portion of an application on
the server and displaying the UI on the client.

A disadvantage of Citrix MetaFrame is additional cost.
Figure 3 on page 15 is a network configuration utilizing Terminal Ser ver Edition

with Citrix MetaFrame laptops dialing in as clients.

14 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Windows Terminal Server

56K

WAN

Citrix MetaFrame

ICA clients

OneWorld Enterprise Server

Backbone

Laser printer

Workstation

Figure 3. Networ k C onfig uratio n of TS E and Met aFrame

3.1 IBM Network Stations

The IBM Network Station is an industry-leading family of versatile thin clients that
is simple, reliable, affordable and easy to manage. The Network Station enables
users to access applications on virtually any server, from PC-based Windows NT
servers to IBM S/390 mainframes, all at the same time.

The basic IBM Network Station includes:

Citrix MetaFrame

ICA clients

Workstation

• A PowerPC RISC-based microprocessor, of varying speed dependent on the
model

• RAM memory, up to 64 MB

• Network interface supports 10Base-T Ethernet or 4/16 Mbps token-ring

• 8-bit audio speaker

• Standard PC type ports for:

• Keyboard

• Mouse

• VGA or SVGA monitor

• Parallel port supports system printer connection

• Serial port for modem or peripheral device support

• Type 2 PCMCIA flash memory car d for local storage (except for later models
of the Series 1000)

Windows NT Server 4.0, Terminal Server Edition 15

IBM Network Station benefits are:

• Provides simultaneous access to applications throughout the enterprise and
on the Internet, intranets, and extranets.

• Enables fast deployment of applications on the server.

• Simplifies the management and administration of desktops.

• Reduces total cost of ownership.

• Leverages widely accepted Internet standards and technologies.

• Reduces hardware failures, down time and lost productivity. Improves data
security.

• Extends the life of desktop computing investments.

• Positions the enterprise for the future.

Below is a graphical representation of the IBM Network Station Series and how
they are viewed at the desktop level:

Figure 4. The IB M Network Station Ser ies 100

The IBM Network Station Series 100 (Figure 4) is the access network computer.
It’s the most economical thin client for organizations that want to move beyond
limited-function terminals and access graphical applications, the Internet, and
Java applets alongside traditional, character-based applications. Like all
members of the Network Station family, the Series 100 helps speed application
deployment and lower your total cost of computing.

Figure 5. The IB M Network Station Ser ies 300

The IBM Network Station Series 300 (Figure 5) is the Internet network computer.
It’s the thin client of choice for organizations that need access to browser-based
applications and data residing on the Internet or corporate intranets, along with
graphical Windows and character-based applications. The IBM Network Station
Series 300 is available in versions that support Ethernet, Token-Ring and Twin
axial (AS/400) cable connections. Like all members of the Network Station family,
the Series 300 helps speed application deployment and lowers you total cost of
computing.

16 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Figure 6. The IB M Networ k S tatio n Series 1000

The IBM Network Station Series 1000 (Figure 6) is the Java-focused network
computer. It delivers powerful support for running Java applications while
simultaneously accessing familiar graphical Windows and character-based
applications. It’s the thin client choice for organizations that are implementing
Java- and Internet-oriented application architectures and it comes with the
Java-based Lotus eSuite software.

3.1.1 IBM Network Station Manager

The Network Station ships with Network Station Manager, paired client and
server software that includes a user interface, emulators, a browser, Java Virtual
Machine, and other features.

The IBM Network Station Manager software provides for management,
administration, and authentication of the IBM Network Station. It provides a
customized environment with discrete or simultaneous access to:

• Windows (ICA), UNIX, 5250, 3270, and ASCII terminal-based applications

• Internet and intranet applications and data

• JVM 1.1.6

• IBM Netfinity servers, AS/400, RS/6000, S/390 and other PC server types.
Network Station Manager Version 1, Release 3 is the industry-standard for

managing first-generation IBM Network Station thin clients. Network Station
Manager Version 1, Release 3 (NSM V1R3) is IBM’s industry-leading thin client
management and administration software that enables centralized, server-based
set up and configuration for all Network Station Series 100s, 300s, and 1000s in
an enterprise. An administrator can access Network Station Manager from any
location on the network to create and manage user-specific desktop
environments and access privileges, and to control all Network Station
applications and access to server resources such as disk files and printers.

More information regarding the IBM Network Station and the IBM Network Station
Manager can be obtained from the following Web site:

http://www.pc.ibm. com/us/networkst ation/

For deploying the IBM Network Station, we highly recommend that you obtained
the IBM redbook,

, SG24-5221. This redbook can be obtained from the following Web site in

NT

IBM Network Station Manager Release 3 Guide for Windows

PDF format:

http://www.redbook s.ibm.com/

Windows NT Server 4.0, Terminal Server Edition 17

Network Station Manager features and benefits:

Table 1. The IBM Network Station M anage r Features and Be ne fits

Feature Benefit

Centralized, se rver-b as ed
management and
administration

Browser interface For Administrators:

For Administrators:

- Fast, easy application deployment

- Efficient use of IT resources

- Enhanced security, data backup, and recovery

For Users:

- Less time spent on system maintenance

- Access to desktop environment from any
Network S tation in the enter prise, allowing
users to roam

- Access to current applications enables
customization of desktop characteristics

- Enables access from any Network Station
accessible to the network

For Users:

- Provides an easy-to-use graphical interface
with built-in online help that can reduce
training and support costs

- Offers access to the Internet or corporate
intranet, along with Java applet/application
support

Multiple configuration
default levels

- IBM-supplied defaults help you get started
quickly using common settings that can later
be overriden

- System defaults permit mass changes
affecting all users

- User and workstation defaults enable highly
granular desktop custom ization

In addition, the Network Station Manager provides:

• Built-in support for multiple serial ports and touch screen displays

• Flash Memory Card support

• Extensive National Language Support

• Support for ICA load balancing, virtual print, vir tual communications, text
cut/paste

• Support for Lotus eSuite WorkPlace 1.5 (English only)

• Supports local boot from flash card

• Year 2000 and Euro-ready

18 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Chapter 4. IBM Netfin ity Family of Servers

The IBM and J.D. Edwards solution for your business starts with a choice of
Intel-based servers that can provide exeptional network support. With the IBM
server models, you will gain outstanding power, sc alability, control, and service,

for today’s enterprise-to-small network environments. Your decision to choose the
IBM and J.D. Edwards solution will allow you to deploy business-critical
applications with confidence. J.D. Edwards and IBM are very concerned about
the aspects of their customers’ businesses, such as the high availability of
network services to access and manage mission-critical information, and provide
a reliable and secure platform.

This chapter introduces a new line of IBM Netfinity 7000 M10, 5500 M20, 5500,
5000, and 3000 servers, the first in a new family of enterprise servers. The IBM
Netfinity servers leverage IBM's server heritage, combining high-performance
application computing based on industry-standard, Intel processor-based
technology. The IBM Netfinity servers have been designed to enable customer s to
run demanding e-business applications, including Web server and on-line
transaction processing (OLTP), and data-intensive operations.

The IBM server solution provides a very reliable platform for running the world's
most popular network operating system, Microsoft NT Server 4.0, the network
operating system required for J.D. Edwards’ OneWorld Deployment server. This
chapter describes the IBM server product line and its features. This information
should be used to select the right server platform for your ERP business solution.

4.1 About IBM Netfinity

From the ground up, IBM Netfinity is designed and built to deliver midrange-level
performance in critical areas such as enterprise res ource planning (ERP) and
e-business. The IBM Netfinity server provides the power and scalability to
distribute the most demanding 24x7x365 applications and data including your
ERP and e-business applications. The IBM Netfinity server includes the following
controls for easier management of all your system’s resources and the total
service that business-critical systems demand:

• Processing Power - IBM Netfinity uses the latest Intel Pentium III Xeon
processors, power integrated into a server system balanced and tuned for
high-speed distribution of applications and data throughout your enterprise.

• Scalability - IBM Netfinity servers handle the most resource-hungry data and
applications with ease. These applications include J.D. Edwards’ OneWorld,
Lotus Domino, Microsoft SQL Server and Oracle8 for Windows NT. The
ingenious design of the IBM Netfinity server allows it to be configured as a
tower or a rack system, so it's easy to grow your server with your business.
Key options and components can be quickly replaced, upgraded, or removed ­without powering down the server.

• Control - IBM Netf inity Manager softw are and the Netfinity Adv anced Systems
Management Adapter put you in complete control of your server and all your
systems’ resources graphically, from a single point of control. So you can see
all your systems at a glance, from virtually anywhere in the world, anytime of
the day or night. You'll also be in the position to proactively manage your
systems for peak efficiency and output.

© Copyright IBM Corp. 1999 19

• Service - IBM’s renowned service and support are with you all the way. Listed
are the worldwide available Web sites:

Netfinity
J.D. Edwards Alliance
Server Solutions

www.pc.ibm.com/us /netfinity/ - for latest products

www.ibm.com/erp/jd edwards/
www.pc.ibm.com/us/ solutions/netfin ity/index.html

ServerProven www.pc.ibm.com/us/ compat/
SystemXtra www.pc.ibm.com/us/ systemxtra/
TechConnect www.pc.ibm.com/tec hconnect/
Support www.pc.ibm.com/sup port/
Accessories www.pc.ibm.com/us/ accessories/
Services www.ibm.com/servic es/
Year2000 www.pc.ibm.com/yea r2000/
TCdigest www-1.ibm.com/supp ort/tcp/
iSource www.ibm.com/isourc e

Today, you can configure and order your Netfinity server directly from the Internet
at a very competitive price. To do so, go to the following Web site:

BuyIBM

www6.pc.ibm.com/bu yibm

If you need assistance to help you in your buying decision, use the Sales
Assistant located at the BuyIBM Web site.

4.1.1 The Foundation for J.D. Edwards and Domino Applications

J.D. Edwards’ OneWorld on Windows NT gives you an ERP solution designed to
meet your needs today and well into the future. The pow erful, scalab le foundation
for OneWorld is IBM Netfinity.

The IBM Netfinity is ready to provide you with the following features:

1. The latest Pentium Xeon III Technology
Up to four-way Pentium III Xeon symmetrical multiprocessing in both tower

and rack-mountable IBM Netfinity 7000 M10 models.

2. Ultra Fast Throughput

High-speed intelligent disk subsystems with Wide Ultra SCSI controllers,
Serial Storage Architecture (SSA), and Fibre-channel adapters and drives,
deliver excellent Windows NT application performance.

3. Storage Flexibility

Expand disk arrays while the server is still running using IBM Logical Drive
Migration technology with IBM ServeRAID Adapters.

4. Netfinity Advanced Systems Management PCI Adapter

The Netfinity Advanced Systems Management Adapter allows you to
communicate with your Netfinity server using Netfinity Manager. It can be
used to configure and monitor many of your system's features. With the
Netfinity Advanced Systems Management service of Netfinity Manager, you
can configure events such as POST, loader, and O/S timeouts, critical
temperature, voltage and tamper alerts, and redundant power supply failures.

20 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

This service also enables you to dialout and directly access and control a
remote system’s NASM adapter or Netfinity Advanced Remote Management
processor.

5. Complete Manageability Software Suite
Includes IBM Netfinity Manager software for proactive server management

and control, IBM Capacity Management tool for upgrade planning, and
integrated UPS management for safe application shutdown. All of these are
provided as standard to help you reduce your total cost of ownership.

6. Extensive Hardware Management Integration
Disk Drive alerting with S.M.A.R.T. and Predictive Failure Analysis (PFA)

provides pre-failure notification for disk drives. Enable full 'lights out’ remote
management including key component status and remote power and restart
with an IBM system management processor that is standard on some models
and optional on all IBM Netfinity systems.

7. High Availability

Minimizes system down time with ECC memory, RAID subsystems with
hot-swappable disk drives, redundant power supply units, and cooling fans.
Certified for Microsoft Cluster Server to provide a highly availab le f ault-toler ant
platform for Windows NT applications to protect against server or application
failure.

8. Rack Mountable

IBM Netfinity Rack provides an industry-standard 19" enclosure to support
IBM Netfinity 7000 M10 and 5500 rack mountable servers and other options to
save valuable floor space and ease maintenance operations.

9. Compatibility and Performance

Dedicated IBM engineering teams conduct ongoing compatibility testing,
certification testing, performance measurement, and optimization to help
ensure that IBM Netfinity systems, Windows NT Server, and J.D. Edwards’
OneWorld run seamlessly together.

10.IBM Start Up Support and IBM Warranty

IBM Start Up Support provides, at no additional charge, telephone assistance
for IBM and selected third-party hardware, and Windows NT Server, for the
first 90 days of ownership. Our servers are also covered by IBM’s three-year
limited on-site warranty.

11.TechConnect

A comprehensive program designed exclusively for networking professionals
provides unique solution-based technical information, training and certification
opportunities, and more.

12.Lotus Domino R5 Included

Data can be transferred from J.D. Edwards’ OneWorld application to Lotus
Domino and other Lotus products, allowing users to use their familiar
applications for data analysis and manipulation.

The new Domino R5 offerings at no additional charge will be package with the
Netfinity server as follows:

1. IBM Netfinity 3000 and 5000 servers will include a license of Domino Mail

Server Release 5 (Windows NT version) plus five client licenses.

IBM Netfinity Family of Servers 21

2. IBM Netfinity 5500 and 7000 servers will include a license of Domino

4.2 IBM Netfinity 3000

The Netfinity 3000 delivers solid performance and excellent functionality to the
entry server marketplace. Your small business applications can run faster or be
upgraded to handle today’s more complex business requirements by installing
them on the affordable Netfinity 3000 containing the latest Intel Pentium II
processor technology. These stylish, uni-processor ser vers feature a powerful
500/100(1) MHz Pentium III processor with 512 KB ECC L2 cache, a full-duplex
10/100 Mbps Ethernet controller, a PCI Fast/Wide Ultra SCSI Adapter, and
integrated sensors to monitor system well-being.

The Netfinity 3000 expands the entry Netfinity product line by offering the latest
Intel processor with the right level of network server function to produce an

affordable mini-tower package perfect for many of today’s business networking
applications. They are ideal in small business environments for handling basic to
moderately complex business application suites or as a file server. For
large-to-medium-sized businesses, they are designed to run similar business
applications in departmental or branch office environments.

Potential customers acquiring an IBM Netfinity 3000 server may have the
following requirements:

Application Server Release 5 (Windows NT version) plus five client
licenses.

• An affordable server that practically installs itself with the IBM ServerGuide
CD-ROM. The IBM ServerGuide is shipped with all Netfinity servers.

• A server packed with power and scalability features that support the
operations of a J.D. Edwards’ OneWorld Deployment server , and other roles of
file-and-print serving, workgroup productivity applications, such as the Lotus
Domino Mail Server R5 (shipped with Netfinity at no additional cost), and
shared Internet access.

• 500/100 MHz Pentium III processor with dedicated 512 KB ECC L2 cache.

• 64 MB 100 MHz SDRAM Error Checking and Correcting (ECC) DIMM
standard, expandable to 768 MB.

• Five available full-length expansion slots - two PCI slots and three ISA slots.

• Six total drive bays supporting up to 72.8 GB of internal hard disk storage.

• Bootable 32X/14X IDE CD-ROM, 9.1 GB Wide Ultra SCSI hard disk drive
(model dependent), and 1.44 MB diskette drive.

• A 330-watt, voltage-sensing power supply with a fan and two additional
cooling fans - power and cooling for robust configurations.

• An IBM PCI Fast/Wide Ultra SCSI Adapter using the Adaptec AHA-2940UW
PCI adapter supporting up to four internal SCSI devices through the 16-bit
internal connector or 15 external SCSI devices through the 16-bit external
connector.

• Two USB por ts, two high-speed, NS16550A software-compatible serial ports,
and one high-speed parallel port supporting devices using SSP/EPP/ECP
protocols adhering to the IEEE 1284 standard.

22 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

• Integrated Accelerated Graphics Port (AGP) video controller with 4 MB of 100
MHz synchronous graphics RAM (SGRAM0 providing optimum setup and
systems management capability).

• Integrated systems management features - Vital Product Data (VPD) plus
thermal, voltage, and fan sensors - alerts generated through Netfinity
Manager.

• Netfinity Manager software (at no cost), which allows you to apply proactive
Systems Management functions across your entire networked business
systems. In addition, Netfinity Manager can integrate with key workgroup and
enterprise management platforms using industry- standard protocols, such as
SNMP, MIB, and MIF, and allowing proprietary systems management software
to integrate, by using critical file monitoring.

• A reliable foundation to confidently build your networked entry-enterpris e
business system.

The IBM Netfinity 3000 is shown in Figure 7 on page 24.

IBM Netfinity Family of Servers 23

330 Watt Power Supply

Multiple Bus Architecture
3 PCI and 3 ISA Slots

Wide Ultra SCSI Adapter

Hard Drives - Up to 72.8GB

Easy-to-Access

of internal storage

Handle for

Easy Transport

LED Information

Display

32X - 14X

CD-ROM

Bays for

Additional Options

1.44MB

Diskette Drive

Cooling Fan

Easy-to-Remove

Side Panel

Figure 7. Explo ded View of t he IBM Net finity 3000 Tower Server

Even at entry level, this platform combines leading-edge, industry-standard
technologies, good internal data storage capacity, ease of installation and system
management, and solid performance through a 500/100 MHz Pentium III
processor. These uni-processor servers provide a cost-effective,
high-performance platform to support networking applications where moderate

24 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Up to 500MHz

Pentium III Processors

3 DIMM Sockets

for a Maximum of 768MB

of 100MHz ECC SDRAM Memory

amounts of adapter expansion and internal disk storage is required or anticipated
in the future.

4.3 IBM Netfinity 5000

The IBM Netfinity 5000 delivers the perfect blend of power, manageability,
expandability, and serv iceability to satisfy the requirements of
small-to-large-sized businesses looking for an affordable general purpose
network server. These servers fit right into business environments where rack or
tower configurations are desired.

For e-business applications, the y are an e xcellent choice as Lotus Domino Server

R5 or Domino Intranet servers. For your J.D. Edwards’ OneWorld solution, the
Netfinity 5000 is the recommended entry server to support OneWorld deployment
services. In addition, they offer 500 MHz Pentium III power with synchronized 100
MHz operations to memory so that the distribution, updates and upgrades of
OneWorld software ov er the network are quick and efficient. To keep a OneWorld
deployment site running, the Netfinity 5000 has various cost-effective,
high-availability features such as hot-swap hard disk drives, Predictive Failure
Analysis (PFA), and redundant power supplies. Each value-priced Netfinity 5000
is backed by the same world-class service and suppor t found with our larger
systems.

Using the integrated Netfinity Advanced Systems Management processor in
conjunction with IBM award-winning Netfinity Manager and award-winning
Lightpath diagnostics, it is the total solution for proactive control of your
networked business systems, seamlessly integrating with key workgroup and
enterprise management platforms.

The Netfinity 5000 is for customers interested in greater processing subsystem
performance, disk capacity, rack-drawer capability, and high-availability functions
than that of the Netfinity 3000. Customers requiring a higher level of availability
and greater disk storage capacity will still want the Netfinity 5500. The Netfinity
5000 is for customers who want a very affordable general-purpose server that
has excellent performance capability, manageability, serviceability, and moderate
amounts of high-availability features.

The Netfinity 5000 is a completely new mechanical package engineered for the
compactness of a 5 U rack drawer. Potential users of the IBM Netfinity 5000
server may have the following requirements:

• 500/100 MHz Pentium III processors with 512 KB ECC L2 cache.

• Ready for two-way symmetrical multiprocessing (SMP) applications with
optional second processo.r

• Innovative 350-watt power supply - standard redundant capability.

• 128 MB high-speed system memory - 2 GB maximum.

• Integrated Netfinity Advanced Systems Management processor.

• Five full-length adapter card slots - three PCI and two PCI/ISA slots.

• Eight drive bays -

• Five 3.5-inch slim-high, hot-swap drive bays, two 5.25/3.5-inch half-high

device bays, and one 3.5-inch slim-high drive bay.

IBM Netfinity Family of Servers 25

• Internal support for high-performance 4.51 GB and 9.1 GB 10K Wide Ultra
SCSI HDDs and a high-capacity tape backup device.

• Options By IBM (OBI) provides an excellent selection of de vices tested and
supported on the Netfinity 5000 (such as the 20/40 GB 8 mm Internal SCSI
Tape Drive and the 12/24 GB DDS/3 4 mm Internal Tape Drive.

• Up to 91 GB of internal data storage - five 18.2 GB Ultra SCSI SL
Hot-Swap HDDs.

• A 32X/14X IDE CD-ROM and 1.44 MB diskette drive.

• Tower and industry-standard 5 U rack-drawer models.

• Integrated 10/100 Mbps Ethernet, dual-channel Ultra SCSI, and an SVGA
controller with 1 MB of video memory.

• Two serial por ts (two 16550A compatible), one parallel port, two USB por ts,
system management port, mouse por t, and keyboard port.

The IBM Netfinity 5000 is shown in Figure 8.

26 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Standard 350 Watt (175W+175W)
Redundant Power Supply, Additional 175 Watt
Redundant Power Supply optional

Rear Fan

5 Slots Total (3xPCI,
2xPCI/ISA)

Front Bezel Release Lever

Light Path Diagnostic Panel

Open 5.25" Half-High

Standard IDE CD-ROM Drive

Drive Bay

Standard 1.44MB

Diskette Drive

Up to 2-way
Pentium III
processors
and 512KB
Level 2 cache

Maximum 2GB Memory,
4 DIMM Slots Total,

Hard Disk Drive Bay Fan

PCI/ISA Card Support Bracket

Side Cover Release Lever

Power Switch

Room for up

to 5 slim-high

Internal hot-plug

Wide Ultra

SCSI Hard

Disk Drives

Figure 8. Exploded View of the IBM Netfinity 5000

4.4 IBM Netfinity 5500 and 5500 M20

The IBM Netfinity 5500 and 5500 M20 servers have the power, scalability and
manageability for the many demands of your networked systems. Furthermore,
with the IBM Netfinity 5500 models, you can maximize your investment through
IBM’s unrivaled, world-class service and support programs.

4.4.1 IBM Netfinity 5500

New rack and to w er models of the popular, award- winning Netfinity 5500 giv e y ou
the latest Pentium III processor power to run your business. These functionally
rich servers not only boost performance but offer the scalability, control, and
serviceability you need to confidently run your business-critical applications.

The Netfinity 5500 servers are positioned between the Netfinity 5000 and the
Netfinity 5500 M20. They are affordable, two-way SMP capable Pentium III

Reset Switch

IBM Netfinity Family of Servers 27

processor-based platforms designed with high-availability features required to run
business-critical applications.

The Netfinity 5500 is for customers who need the power and affordability of the
new P ent ium III processors with 100 Mhz operat ions to memory to be used in uni­or two-way processing applications. But it is as important for those customers
who must have advanced levels of high-availability and fault-tolerant features for
business critical applications found in their corporate data center, branch office,
or medium-sized business. Potential users of the IBM Netfinity 5500 who need
high-performance, high-availability, two-way SMP capable ERP, database,
application server, or e-business solution may have the following requirements:

• 500/100 MHz Pentium III processors with 512 KB ECC L2 cache

• 128 MB or 256 MB system memory - 1 GB maximum

• Upgradeable to two-way or four-way Intel Pentium Xeon(R) processors

• Standard 400-watt hot-swap po w er supply, optional hot-swap redundant power
supply, and standard hot-swap redundant fans

• Integrated Netfinity Advanced Systems Management Processor

• Seven full-length adapter card slots - four hot-swap PCI slots, two
conventional PCI slots, and one dedicated ISA slot

• Ten total drive bays -

• Six 3.5-inch slim-high, hot swap drive bays, three 5.25/3.5-inch half- high

device bays, and one 3.5-inch slim-high drive bay - all allowing access to
removable media

• One conventional fan and two high-capacity blow ers reducing temperatures

for full configurations of adapters and 10K rpm HDDs

• Internal support for high-performance 4.51 GB and 9.1 GB 10K Wide Ultra

SCSI hard disk drives and high-capacity tape backup devices

• Options By IBM (OBI) provide an excellent selection of devices tested and

supported on the Netfinity 5500; devices included are:

• 35/70 GB Internal DLT Tape Drive

• 20/40 GB 8-mm Internal SCSI Tape Drive

• 12/24 GB DDS/3 4-mm Internal Tape Drive

• Up to 109.2 GB of internal data storage - six 18.2 GB Ultra SCSI SL

Hot-Swap Hard Disk Drives

• Up to 1.2 terab ytes of h ot-swap storage when combined wit h thr ee Netfinity

EXP15 storage units in two additional Netfinity NetBAY3 enclosures

• An 32X/14X IDE CD-ROM and 1.44 MB diskette drive

• Industry standard 8 U, 19-inch, rack-drawer model

• Tower models with innovative Netfinity NetBAY3 enclosure

• Integrated dual-channel ServeRAID II Wide Ultra SCSI controller with 4 MB
cache, providing up to 132 MB/sec throughput for high-performance RAID 0,
1, or 5 internal or external data storage with logical drive migration and
updated drivers to support:

• Background data scrubbing - corrects disk media errors before they cause

a problem.

28 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Processor Shuttle,
System Board with Integrated Dual

Channel Wide Ultra SCSI ServeRAIDII
Controller, Integrated Advanced System
Management Processor and 10/100
Ethernet Controller

2 PCI Slots (1/2 PCI Slot on 5500 M20)

4 Hot-Plug PCI Slots with
Indicator Lights

One ISA Slot

• One step array initialization and synchronization - reduces the time to
prepare a new RAID 5 array to accept data

• 10/100 Mbps Ethernet, and SVGA video controllers

• An SVGA controller with 1 MB of video memory

• Three serial ports (two 16550A compatible), one parallel port

• USB ports, a mouse port, and a keyboard port
The IBM Netfinity 5500 is shown in Figure 9.

Netfinity 5500

Netfinity 5500: Up to

2-way SMP Pentium III

Processors with 512KB

Integrated Level 2 Cache and

support for 1GB ECC SDRAM

Netfinity 5500 M10

Netfinity 5500 M10: Up to

2-way SMP Pentium II

Xeon Processors with up to 1MB

Level 2 Cache and support

for up to 2GB ECC SDRAM

PFA Enabled, Redundant
(Optional) Hot-Pluggable
Power Supplies

System Board Protection Shield
Sliding Internal Shuttle for

Easy Maintenance
IBM Netfinity 5500 Family:

8U Rackable Server
Server Operations Display Panel

Power-on Button

1.44MB Diskette Drive

32X - 14X CD ROM for Automated
Installation of Operating
Systems with ServerGuide

2 Open Half-High Bays for
Optional 5.25" Drives
(Supports Internal DLT)

IBM Netfinity NetBAY3: 3U stackable enclosure.
Housing industry standard rack components
like the IBM EXP15, ARC UPS, etc.
(One NetBay3 is Standard on the Tower Model)

Figure 9. Explo ded View of t he I BM Ne tfinity 5500 an d 55 00 M2 0 Rack Serv er

Customers in medium-to-large-sized accounts should be informed that the
Netfinity 5500 is not only a powerful SMP capable server with e xcellent scalability
features, but also has all the other ingredients necessary to run business-critical
applications and minimize down time. Fault tolerance and high-availability
features of this server are designed to make adapter card, power supply, or hard
disk drive failures transparent to clients on the LAN. In addition, there are
predictive failure analysis features for the processor, VRM, memory, and HDDs,
error-logging of events, and status LEDs provide a constant snapshot of the

PFA-Enabled Redunant

Hot-Pluggable Cooling Fans

Light-path Diagnostic Panel

Room for up to 6 Slim-High

(3 Half-High) Internal

Hot-Pluggable Wide Ultra

SCSI Hard Disk Drives

IBM Netfinity EXP15 (Optional)

Storage Enclosure

Netfinity 5500 M20

Hard Disk Drives up to 36.4 GB

for a Maximum Storage

Capacity of 364GB

Netfinity 5500 M20: Up to

4-way SMP Pentium III Xeon

Processors with up to 1MB
Level 2 Cache and support
for up to 4GB ECC SDRAM

IBM Netfinity Family of Servers 29

server’s well-being so that questionable components can be replaced during off
hours.

4.4.2 Netfinity 5500 M 20

The IBM Netfinity 5500 M20 servers advance the popular Netfinity 5500 line by
introducing affordable, four-way SMP processing power and scalability to
mainstream network computing. Using the latest high-performance Intel 500 MHz
Pentium III Xeon processors, these servers deliver blazing performance while
giving you the advanced high-availability and remote system management
features you need to handle your business-critical applications. Valuable IBM
programs top off the offering by bringing mainframe-like support, installation
tools, and e-business solution capability without additional charge.

The Netfinity 5500 M20 (also shown in Figure 9 on page 29) excels in network
server applications by using powerful Pentium III Xeon processors with either 512
KB ECC or 1 MB full-speed caches that run external operations to memory and
I/O buses at 100 MHz. These four-wa y capab le processors coupled to high-speed
100 MHz memory, two primary PCI buses, high-performance integrated Ethernet
and RAID controllers, and optional 10K rpm hard disk drives (HDDs) jump
mainstream server performance to new heights.

The Netfinity 5500 M20 server is positioned just under the Netfinity 7000 M10.
For those who require the additional expansion of memory and I/O adapters or
the performance of 64-bit PCI bandwidth and four-way SMP Pentium II Xeon
processors, the Netfinity 7000 M10 is an excellent solution. The Netfinity 5500
M20 is for customers who need 500 MHz Pentium III Xeon processors with
four-way SMP capability and support for large amounts of memory for
compute-intensive applications. They are the perfect solution when advanced
levels of high-availability and serviceability features are necessary for
business-critical applications found in corporate data centers, branch offices, or
medium-sized businesses.

Potential customers who need an advanced mainstream server for the J.D.

Edwards’ OneWorld ERP system, a database server, an application server, or
e-business solutions may have the following requirements:

• Advanced 500 MHz/512 KB or 500 MHz/1 MB Pentium III Xeon processors
with 100 MHz operations to memory and I/O subsystems

• 500 watts hot-swap power supply, hot-swap redundant fans, and optional
hot-swap redundant power supply

• Netfinity Four-Way Processor Upgrade for Netfinity 5500 and 5500 M10

• 256 MB ECC system memory - 4 GB maximum

• Integrated Netfinity Advanced Systems Management Processor

• Six adapter card slots -

• Four hot-swap, full-length PCI slots, one conventional, half-length PCI slot,

and one dedicated full-length ISA slot

• Ten drive bays -

• Six 3.5-inch slim-high, hot-swap drive bays, three 5.25/3.5-inch half-high

device bays, and one 3.5-inch slim-high drive bay - all allowing access to
removable media

30 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

• Two hot-swap fans and two hot-swap, high-capacity blowers reducing
temperatures for full configurations of adapters and 10K rpm HDDs

• Internal support for:

• 18.2 GB slim-line and 36.4 GB half-high Wide Ultra SCSI hot-swap

HDDs (7,200 rpm)

• High-performance 9.1 GB and 18.2 GB 10K Wide Ultra SCSI hot-swap

HDDs (10,000 rpm)

• High-capacity tape backup devices

• Options By IBM (OBI) provides an excellent selection of devices tested and
supported on the Netfinity 5500 M20; devices include:

• 35/70 GB Internal DLT Tape Drive

• 20/40 GB 8mm Internal SCSI Tape Drive

• 12/24 GB DDS/3 4mm Internal Tape Drive

• A 32X/14X IDE CD-ROM and 1.44 MB diskette drive

• Up to 109.2 GB of internal data storage - six 18.2 GB Wide Ultra SCSI
SCA-2 SL HDDs

• Over 1.2 terabytes of hot-swap storage when combined with three Netfinity
EXP storage units in two additional Netfinity NetBAY3 enclosures

• Industry-standard 8 U, 19-inch, rack-drawer models

• Tower models with innovative Netfinity NetBAY3 enclosure

• 10/100 Mbps Ethernet

• Three serial ports (two 16550A compatible), one parallel port, two USB ports,
a mouse port, and a keyboard port

• Integrated dual-channel ServeRAID II Wide Ultra SCSI controller with 4 MB
cache, providing up to 132 MB/sec throughput for high-performance RAID 0,
1, or 5 internal or external data storage with logical drive migration and
updated drivers to support:

• Background data scrubbing - corrects disk media errors before they cause

a problem.

• One step array initialization and synchronization - reduces the time to

prepare a new RAID 5 array to accept data

• An SVGA controller with 1 MB of video memory

The configuration flexibility of Netfinity 5500 M20 is a key benefit in supporting
today’s dynamic business environments.

4.5 IBM Netfinity 7000 M10

The IBM Netfinity 7000 M10 server is a reliable enterprise server available in
either rack or tower models. This server is able to deliver exceptional power,
functionality, and value to handle complex, business-critical database or
application server needs among growing messaging and intranet applications.
The Netfinity 7000 M10 system is intended for enterprise customers whose
networks depend on a reliable, high-performance platform with excellent
scalability for future growth. The Netfinity 7000 M10 can also function as a

IBM Netfinity Family of Servers 31

OneWorld Enterprise server in LAN environments where a significant number of
users require a large amount of server resources.

With the addition of the Netfinity 7000 M10 models to the Netfinity family, even
greater intensive CPU requirements and larger databases can be
accommodated, meeting the processing power and robustness of even the most
demanding and complex business-critical environments in today’ s highly comple x
and intensive business markets.

The Netfinity 7000 M10 advances Intel-based network computing to new levels of
performance with an architecture that consists of a 64-bit, 100 MHz CPU
backplane that supports four 500 MHz Pentium III Xeon processors, a 100 MHz
memory controller, and two 16-bit, 100 MHz F-16 buses. The four-way SMP
capable Netfinity 7000 M10 delivers impressive TPC-D, SpecWeb on Windows
NT, and J.D. Edwards benchmarks that are prove it can handle the e-business or
advanced application server environments in your enterprise.

Potential customers seeking a reliable foundation to confidently run your

networked mission-critical J.D. Edwards’ enterprise applications may have the
following requirements:

• High-performing 500 MHz Pentium III Xeon processors optimized for server
applications with:

• 512 KB ECC L2 cache

• 1 MB ECC L2 cache

• 2 MB ECC L2 cache

• High-speed (50 ns) interleaved, ECC memory - up to 8 GB capacity

• Dual, high-speed system buses supporting high-speed Ethernet, ATM, and
FDDI topologies and ServeRAID 3H/3L, SSA, or Fibre Channel disk
subsystems

• Five 64-bit and seven 32-bit PCI adapter slots

• Integrated Netfinity Advanced Systems Management PCI Adapter with
Ethernet port providing a dedicated processor to perform advanced remote
management and monitoring functions

• Twelve full-length PCI slots supporting multiple adapters and allowing for
adapter redundancy

• Horizontal orientation fits the rack drawer or can be converted to tower
installations with device bays remaining in a convenient horizontal position

• Six total drive bays - all allowing access to removable media

• Four 3.5-inch slim-high or two half-high, hot-swap drive bays

• One 5.25/3.5-inch half-high device bay with 32X/14X CD-ROM

• One 3.5-inch slim-high drive bay with 1.44 MB diskette drive

• Internal support for high-performance 4.51 GB, 9.1 GB, and 18.2 GB, 10K
Wide Ultra SCSI HDDs, or 7200 rpm drives up to 36.4 GB each

• Terabytes of data storage capacity through attachment of external Netfinity
EXP storage units using 36.4 GB HDDs

• An excellent selection of devices tested and supported with the Netfinity 7000
M10 such as the 35/70 GB External DLT Tape Drive or Magstar Tape Libraries

32 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

• Two Integrated Adaptec AIC-7895 SCSI controllers providing up to 132
MB/sec throughput for high-performance internal or external data storage, or
external tape backup

• Industry-standard 11 U, 19-inch rack-drawer models

• Conversion to tower configurations and optional Netfinity NetBAY3 enclosures

• Supports Fibre Channel and Oracle Parallel Server through the Netfinity
Cluster Enabler

• Two serial por ts (16550A compatible), one parallel port, two USB por ts, one
SCSI port, a mouse port, and a keyboard port

• An S3 Trio64V2/GX video controller with 1 MB of video memor y

The Netfinity 7000 M10 is shown in Figure 10.

Figure 10. Explode d View of the IB M Netf inity 70 00 M 10 S erver

The Netfinity 7000 M10 contains advanced availability, manageability, and
serviceability features to help diagnose problems quickly, even from remote
locations:

IBM Netfinity Family of Servers 33

• Hot-swap PCI card slots, drive bays, fans, power supplies, and optional
redundant power supplies enabling redundancy and replacement of
components without powering down the server

• Predictive failure analysis (PFA) on key components warning of impending
problems so corrective action can be taken before system outage

• An integrated Netfinity Advanced Systems Management PCI Adapter in a
dedicated PCI slot supporting:

• Remote access through a serial or LAN connection

• Management from a Netfinity Manager console, an ANSI terminal emulator,

or Web browser

• Monitoring and logging of system events

• Alerts generated if critical system thresholds are approached

• Restarting the server if the operating system is not responding

• Light-Path Diagnostics displayed on the control panel quickly point to a failing
component.

• Mechanical design points allow top, front, and rear access to make critical
components more easily accessible so servicing and upgrading new options is
quick and easy.

34 J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server

Chapter 5. Sizing, Considerations, and Recommendations

Currently the IBM sizing service for J.D. Edwards is able to provide pre-sales
support for two-tier implementation only. In a two-tier implementation the
enterprise ser ver functions as the central database server, supporting clients
running OneWorld business logic.

Configuration can be changed very rapidly in the field, instantly, as the
requirements of business dictate. Additional servers can be added on an
application basis, such as Web, File, Print, without having to rewrite applications
and without need of application programmers for the new systems.

The approach to sizing J.D. Edwards’ OneWorld on the IBM Netfinity platform is

the same as sizing any hardware with an application, that is, to simply identify
individual components, such as:

• Network operating system

• Systems management software

• Networking software

• Applications

• Hardware platform components
When individual components have been identified, determine the individual

requirements of each, then total them up to define the overall requirements. This
is a very simple overview of a sizing process. There are many other aspects to
this, which are too many to consider discussing here and best left to a separate
book on the subject of sizing methodology.

This simple approach does lead to a methodology of sizing that will allow
flexibility within individual components, which is very important in today’s rapidly
and ever changing IT and business environments.

Before submitting a sizing request to IBM, it is strongly suggested that you read
and understand the sizing process of J.D. Edwards’ OneWorld as it discusses
points that you may have not considered.

Note: This chapter covers the sizing requirements of J.D. Edwards’ OneWorld
versions B73.3 and B73.3.1 only.

It is recommended that you carefully read 5.2, “Hardware Considerations” on
page 36 and 5.3, “Software Considerations” on page 50.

While considering your customer’s requirements, you should take notes as you
read. This overall approach will ensure that you have made careful deliberation of
both hardware and software. Once you have reviewed the hardware
considerations and software considerations, review 5.6, “Requests for Sizing” on
page 66.

© Copyright IBM Corp. 1999 35

5.1 Hardware and Software Considerations and Requirements

To simplify the sizing overview, we discuss the IBM Netfinity hardware that

currently supports J.D. Edwards’ OneWorld software.
The basic hardware topics covered in this chapter are:

• CPU requirements

• Memory requirements

• Hard disk requirements

• Networking requirements

In addition, we discuss other options and functionality you should consider for the
overall stability, availability and reliability of your customer’s business. These
items are:

• RAID support and IBM ServeRAID Adapters

• Fault tolerance

• Backup and recovery process

• Maintenance and service

• Performance

• Physical configuration of the overall system

These topics are discussed in detail in 5.2, “Hardware Considerations” .

5.2 Hardware Considerations

This section takes a close look at hardware items you should consider when
selecting a server for reliability and performance. The implementation should be
based on sound business needs versus cost/performance.

5.2.1 CPU

Within the bounds of Intel technology today, there are no realistic fault tolerance
capabilities available for CPUs. All IBM Netfinity Servers support at least two
processors with the higher end models supporting four processors. If a processor
should fail, then there is currently no way to avoid rebooting the system, which
means down time to the users. However, to reduce the down time, IBM Netfinity
servers with more than one processor will automatically upon a failure and
reboot, reconfigure the system with the faulty processor disabled.

5.2.2 Memory

All memory in the IBM Netfinity Server range is Error Checking and Correcting
(ECC). Using the latest technology available in the marketplace, memory such as
ECC EDO DIMM and ECC SDRAM provide speed, reliability and flexibility in
critical environments that demand very high standards.

As the need for speed and reliability of systems increases, the reliability and
flexibility of memory becomes of paramount importance.

36 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

5.2.3 Hard Disks

In today’s environment, hard disks are becoming more and more reliable, with an
average life expectancy around 100,000 hours. Your selection of hard disks
should provide you with the confidence and assurance of data integrity.

Unexpected data errors are a very serious issue in today’s business and disk
failures are annoying t o customers, I T managers and system administrators alik e.
So what if the disk could tell you it was having problems before it failed or before
that piece of data is unreadable? With today’s hard disk technology, businesses
run critical applications and store critical data while maintaining a 24x7x365
operation. IBM hard disks, have Self-Monitoring Analysis and Reporting
Technology (SMART) built in to them as standard to alert you of any potential
problems.

Predictive Failure Analysis (PFA) within the SMART specification provides early
warning of some hard-disk drive failures. This allows critical data to be protected.
SMART is the industry-standard reliability prediction indicator for hard disk
drives. IBM paved the way for SMART by marketing the industry’s first
failure-prediction capability for SCSI hard disk drives.

Regular backups, combined with SMART-capable hard-disk drives, help
safeguard against loss of data. There are two kinds of hard-disk drive failures:
unpredictable and predictable. As you might expect, unpredictable failures
happen quickly, without advance warning. These failures can be caused by static
electricity, handling damage or thermal-related solder problems. Predictable
failures, on the other hand, are the types of failures that SMART attempts to
detect. These failures result from the gradual degradation of the drive’s
performance.

SMART-capable drives use a variety of techniques to monitor data availability.
These techniques vary from one manufacturer to another. F or e xample , a SMART
drive might monitor the fly height of the head above the magnetic media. If the
head starts to fly too high or too low, there’s a good chance the drive could fail.
Other drives might monitor different conditions, such as ECC circuitry on the
hard-drive card or soft-error rates. Depending on the circumstances, some drives
might monitor all or none of these conditions.

Internal hard drives also support the SCSI Accessed Fault Tolerant Enclosure
(SAF-TE) standard to protect hard drive data if failures occur. If one of IBM’s
SMART-capable drives predicts it is going to fail while it’s s till under warranty,
IBM will repair or replace it at no additional cost to you. PFA keeps track of key
parameters of the drive over time. If any of these key parameters should exceed
its predetermined threshold, drive logic will alert the system of this event, so that
necessary remedial action can be taken before any physical failure occurs. The
alert can be sent to the systems management’s software, such as IBM Netfinity
Manager, where predetermined actions are addressed.

Predictive Failure Analysis will monitor parameters, such as:

• Spindle motor problems (torque and speed)

• Hardware problems (electronic and logic)

• Channel problems (noise, asymmetry, pre-comp, DC offset)

• Fly height change problems

Sizing, Considerations, and Recommendations 37

5.2.4 Networking

• ECC on the fly (ECC and cache)

• Media problems:

• Soft error count for read/write operations

• Hard error count for read/write operations

• Auto rewrite counts

• Auto reallocation count and more

When choosing disks, there are several factors to consider that will ultimately
affect performance and I/O capabilities of the overall system not just the disk
subsystem, so ensure that you choose the right size and speed of disks to meet
your needs.

Other points you should consider for your server are hot-swap hard disks,
hot-swap disk controllers, the flexibility for growth, and other issues, such as:

• Will this server support the future hard disks when they are available?

• Can I use Fibre Channel disks on the system when they are available?

• If I buy these disks today and need to upgrade six months from now, will I still
be able to buy the same disks?

The networking design and network infrastructure is a very important par t of any
Intel-based server solution. This is particularly important with J.D Edwards’
OneWorld version B73.2.1 and above, as these versions of software are event
driven. Event driven means that as the operator k e ys data into individual fields on
the screen, then moves to another field, the input to a previous field is sent over
the network. This allows for an evenly distributed flow of data across the network,
rather than large packets of data, which can create network congestion.

Another major networking influence within J.D. Edwards’ OneWorld software is
how the workstations are to be used:

• Thin client - All OneWorld environments and objects run on the enterprise
server

• Thick client - Runs most of the OneWorld application locally

Again, the style of client used will be dependent upon the best option for the
customer’s implementation. Also refer to 5.2.9, “Performance” on page 48
regarding networking performance hints within J.D. Edwards’ OneWorld.

Failure of any network adapter where loss of service to endusers is created is a
disaster in today’s business-critical environments. To overcome this, there are
various solutions available from IBM. Refer to 5.2.6.6, “PCI and ISA Adapter
Cards” on page 46 for further details of options available.

5.2.4.1 Ethernet Network Hints and Tips

In this section is a list of tips to consider for an Ethernet network:

1. The network infrastructure wiring plant should be 10Base-T Category 5 based.
By using a 10base2 "thinwire/coaxial" daisy-chained system, you will have
throughput problems along with a higher number of collisions.

38 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

5.2.5 RAID Suppor t

2. Never put two servers on the same hub if it can be avoided. This will keep
backplane congestion low while allowing for high momentary throughput.

3. Utilize good IP addressing control for all clients. Maintain sub-domain
addressing to parallel link ID with sub-network domain ID.

4. Maintain good segment layering and keep the segment propagation delay to
IEEE specifications. Maximum LAN delay should be 52ms for every 330 feet
of wire. W A N delay is carrier dependent. Solid measurements at this stage are
critical.

5. WAN to LAN insertion is unique for each company so to ensure proper system
response remember to do a bandwidth usage analysis with the J.D. Edwards
application.

6. Optimize all programming to ensure that the WAN is the last network resource
used in any one particular OneWorld operation.

7. Workgroup servers must be on the same segment as the operational clients
the workgroup server supports.

8. Maintain remote to small non-collocated groups. Also, remote access should
be through the Internet as much as possible.

When you have det ermined the amount of hard disk storage y ou r equire , you may
need to look at the possibility of using one or more versions of hardware RAID on
the IBM Netfinity server. A major influence on performance, reliability and
availability and data integrity is the correct choice of RAID controller and RAID
levels to use.

Why consider RAID? Given the most mechanical part in any computer today is
the hard disk drive and that the hard disk is the most commonly used component.
Adding RAID to the server configuration will instantly afford an increase in both
availability and fault tolerance of the system. The IBM Netfinity server product
range supports RAID 0, RAID 1, Enhanced RAID 1, and RAID 5 with the IBM
ServeRAID Adapter.

What is RAID? RAID stands for Redundant Array of Independent Disks, by that
we mean:

• Several disks can be linked to appear as one larger disk to the system.

• A single disk can be mirrored to another disk at a hardware level.

• RAID allows a single disk, within an array to fail, without system impact.

• RAID increases performance of the sy stem.

• RAID allows you to have databases and files larger than single disk size.

• RAID increases data integrity of the system.

To discuss RAID in depth is not within the bounds of this book. However, if you
wish to know more about RAID there are many books on the subject. RAID is also
discussed within the IBM Netfinity server user’s guide and installation manuals.

For the purposes of this book we will cover RAID very briefly.

Sizing, Considerations, and Recommendations 39

5.2.5.1 RAID Zero (RAID 0)

RAID 0 is the striping of data across a number of disks (as shown in Figure 11):

RAID-0

Non-Fault Tolerant

Figure 11. Example of RAID 0

When the data is striped in this manner the main benefit is performance. In
simple terms if you have four disks in a single RAID 0 array, then data access is
four times faster than retrieving the same amount of data from a single disk.

However , there is an e xpense for an increase in performance. If a disk should fail,
all data is lost on the array. The only way to recover this data is from a previous
backup. This is an expensive cost, in time, backup procedures, data recovery,
and also data loss. Any data entered after the last backup is lost, and has to be
reentered. A complete system reboot and data recovery must be done to bring
the system back online at the time the failure occurs.

data1
data5
data9

data2
data6

data10

data3
data7

data11

data4
data8

data12

5842\RAID0

5.2.5.2 RAID O ne (RAID 1)

RAID 1 is the mirroring of single disks on a single disk controller (as shown in
Figure 12):

RAID-1

Fault Tolerant

Figure 12. Example of RAID 1

When data is written to one disk, it is also written to a second disk, thereby
creating a mirror of the data. Where RAID 0 improves performance, RAID 1
degrades performance. This is because a single write of data requires two writes
(one write to each disk in the mirror).

However , the gain is in reliability and availability of data. If a single disk fails, then
there is a complete copy of this data on the second disk. Recovery in this
circumstance is to simply switch to the other disk (this may require a reboot of the
system). Once back online you replace the failed disk, and reinitiate the mirror to
bring things back to normal.

data1
data2

data1
data2

5842\RAID1A

40 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Disk duplexing

is similar to RAID 1 except the two disks are attached to different
disk controllers. The advantage here is a further gain of fault tolerance. The
system or data can now withstand the loss of a disk controller and a disk. In some
circumstances a reboot of the system is required, to switch to the other disk
controller and to bring the system back online.

5.2.5.3 Enhanced RAID 1

Enhanced RAID 1 is a combination of RAID 0 and RAID 1. To put it simply, it is
the "mirroring" of a RAID 0 array, within a single array (shown in Figure 13):

RAID-1
Enhanced

Fault To lerant

Figure 13. Example of Enhanced RAID 1

data1
data4

data2
data1

data3
data2

data4
data3

5842\RAID1

This combination of RAID 0 and RAID 1 has advantages of increased
performance when reading data but has an overhead of writing data twice on all
writes. However, this can be used to an advantage, by placing the Enhanced
RAID 1 in a mostly read environment.

Loss of a single disk (as in RAID 1) does not create data loss. In most
circumstances this will provide very good data protection, while providing
enhanced performance.

5.2.5.4 RAID Five (RAID 5)

RAID 5 is the striping of data and parity (or checksum) across all disks (shown in
Figure 14):

RAID-5

Fault Tolerant

CS=6

data4
data7

data10

data1

CS=19

data8

data11

data2

data5

CS=32

data12

data3
data6
data9

CS=42

Based upon the

single unknown

For example, data1 + data2
+ data3 = checksum

Figure 14. Examp le of R AID 5

single equation

technique.

5842\RAID5

Data is striped with a parity or checksum on each write of data. The total amount
of data that can be stored in a RAID 5 array is N-1, where N is the number of
disks within the single array. For example, 5 x 9.1 GB in an array will give 4 x 9.1
GB of data storage capacity. If a disk should fail, the system will keep providing
data to end users, creating read data by using the checksum as required. There

Sizing, Considerations, and Recommendations 41

is performance degradation when one disk fails. However the disk can be
replaced, the missing data restored and performance returned, automatically
when a hot-spare disk is a part of your configuration or manually when a failed
disk has to be physically replaced.

The major advantage of RAID 5, is its ability to keep the system up and running in
the event of a disk failure, no down time, no loss of data with a single disk failure.
However , where as in RAID 0, RAID 1, and Enhanced RAID 1, the loss of a single
disk may require a reboot of the system; in RAID 5 it does not. This is a major
advantage when there is a need to keep the data available to endusers and
customers for long periods.

5.2.5.5 IBM S erveRAID Adapters

Today’s business critical data grows at an alarming rate. A few years ago a
database of around 20 GB would have been considered large, even beyond the
scope and capacity of all but the largest of mainframes.

Today, databases of around 20 GB are very normal, and nothing out of the
ordinary. It is databases of 1 or 2 terabytes that are seen as incredibly large.

So what growth rate can you expect from your customer’s database?
The answer is unpredictable, but one point is certain, and that is, grow it most

certainly will. If you have a system that will handle up to 100 GB of hard disk
today, but you require only 60 GB, your customer will buy 60 GB of hard disk.
Sometime in the future, your customer will want to expand, or concentrate some
of his data, into smaller more manageable sizes. The challenge is to achieve this
data without losing availability to endusers.

So how can this be achieved? Until recently, we had to:

1. Back up all the data.

2. Redefine the disk arrays, or install larger disks and redefine the arrays.

3. Restore the data.
This is an expensive way of growing a database. In today’s environment this

would be unacceptable within a 24x7x365 operation.
The IBM ServeRAID adapter has the answer to this. To grow the database as

mentioned above from 60 GB to 100 GB, you would simply insert more hard
disks, and migrate or "grow instantly" the disk space available to the operating
system, by increasing the size of the array that is already in use, without any loss
of service to endusers.

With IBM ServeRAID adapters, you can migrate the data in a variety of ways. The
options are:

• From RAID 0 to RAID 5

• From RAID 5 to RAID 0

• From RAID 1 to RAID 5

• From RAID 5 to RAID 5 (array expansion)
This functionality of the IBM ServeRAID adapter is known as Logical Drive

Migration (LDM) and is available as standard with all current IBM ServeRAID

42 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

adapters. Also available for the IBM ServeRAID adapters are a range of battery

backed cache options to provide even greater stability to your customer’s data.

5.2.5.6 RAID S ummary

RAID should always be considered when availability and file size of business
critical data is an issue. Individual requirements will dictate the final RAID
solution for the customer.

In all cases there are advantages and disadvantages of each RAID solution in
practical terms. These should be considered when selecting your hard disk
configuration for the IBM Netfinity and J.D. Edwards’ OneWorld implementation.

Refer to Table 2 for an overview of advantages and disadvantages of RAID
solutions. You should review 5.2.6, “Fault Tolerance” for further details regarding
overall fault tolerance of the system.

Table 2. IBM Netfinity Hardware Cons iderations

Considerations Advantages Disadvantages

RAID 0 Very high read and write

performance

RAID 1 Data integrity - high Degrades performance

Disk Duplexing Data integrity - very high

Performance is greater than RAID 1
Higher fault tolerance than RAID 1
Second disk controller

Enhanced RAID 1 Data integrity - very high

High fault tolerance
No reboot on single disk failure

RAID 5 Data integrity - very high

High fault tolerance
No reboot on single disk failure

Failure must be dealt with
immediately with loss of access to
users
Data integrity - low

(two writes for each data write)
Expensive, size of single disk is
limitation

Single disk is size limitation
Expensive - 2x disk capacity for data

Performance impact
Performance - parity/checksum
overhead

Performance impact
Performance - parity/checksum
overhead

5.2.6 Fault Tolerance

As discussed in 5.2.5, “RAID Support” on page 39 there are limits to availability,
and fault tolerance capabilities that various RAIDs can offer within the system by
themselves. This section will look at other ways of offering fault tolerant solutions
to get closer to the ultimate goal of 100% availability.

If we look at the most likely failures, given the history of IT technology, then we
can start to look at the gain on reliability and availability versus cost of
implementing the relevant solution. The most likely failures are discussed here in
some order of "likely to fail", as this order can vary from country to country
dependent upon many local factors.

Sizing, Considerations, and Recommendations 43

Note: This is not the complete set of IBM Netfinity solutions, but only the
solutions that are supported within the current set of IBM Netfinity and J.D.

Edwards’ OneWorld offerings.

5.2.6.1 Main Power

With the increase in manufacturing technology in recent years, it is a reflection of
that advancement, that in today’s IT environment, the main supply is one of the
most likely components of the system to fail.

To avoid losing data when the main supply fails, there is only one real solution,
that is, to use an uninterruptible power supply (UPS). A UPS will not only provide
main power in the event of a main power failure, but also reduce or eliminate
surges, spikes, and noise on the main supply, during normal use, providing a
much smoother level of main voltage. This aids in protecting system data from
corruption by these unpredictable characteristics of the main supply.

The UPS will provide main voltage for a limited time after the main supply has
been removed. This enables system management software or hardw are to initiate
an automatic unattended shutdown of the server.

Refer to Chapter 4, “IBM Netfinity Family of Ser vers” on page 19 for further
details on the IBM systems management capabilities and offerings.

Another option is to use the software supplied with the UPS system to monitor the
main power and have it initiate a shutdown of the system automatically, in such
an event.

When buying a UPS from IBM all software and hardware are tested and certified
to be solution assured, within the IBM ServerProven Program with not only the
IBM hardware but also any of the operating systems supported on that same
model of IBM Netfinity server.

5.2.6.2 Disk a nd RAID Cont rollers

A commonly overlooked, critical component is the hard disk controller, it is the
heart of any system as much as the CPU or memory. It is also very influential in
terms of performance and reliability.

So why do we take it for granted? The reasons are historical. It was not until
recently that hard disk controllers had some fault tolerance, either as standard or
as an option. There were one or two "niche market" adapters around, that
provided some fault tolerance but these were expensive and not
industry-standard by any means. With the advent of RAID, the hard disk
controller has started to gain recognition and respect. Many industry standard
hard disk adapters are now available with features that provide fault tolerance. In
almost all cases these are RAID controllers.

So what are the fault tolerant features of RAID controllers? The most obvious is
the RAID array itself, as discussed in 5.2.5, “RAID Support” on page 39. The
various levels of RAID offer fault tolerance for the data on the disks.

The IBM ServeRAID controllers can also have battery-backed cache. In the event
of a complete main power failure, the battery will store the cached data, which
has not been written to disk for up to 14 days. Another function is that the
battery-backed cache modules are removable from the adapter and can be

44 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

placed on the replacement adapter, thereby removing the "human factor" in
reconfiguring the arrays.

IBM ServeRAID adapter also supports fail-over and hot-swap technology. This
means that in the event of RAID controller failure, then a second or standby
ServeRAID controller can replace the existing adapter automatically. The failed
adapter can be replaced at a convenient time. There is no need to power down
the server to replace the failed adapter, as it can be hot-swapped, keeping the
system available to users.

5.2.6.3 Memo ry

Memory is of the utmost importance in deter mining the reliability and
performance of any system. Installing memory to capacity is an obvious choice to
achieve high performance. However, this will only achieve high performance for
the memory of the system, and is an expensive way of ensuring you have
optimum memory performance.

To address this issue, look at the memory requirements of the whole system, then
round this up to the nearest size of memory available for the system.

So how do you determine the amount of memory required?
List the software that will be running on the system, then add up each of the

individual network operating system and application requirements. This basic
approach will help you to determine the desired amount of memory. This figure
should be used as a guide since there are many factors that will influence the
amount of actual memory required within a system.

Another consideration for business-critical servers is the flexibility of the memory
being used. For example, what happens if a memory DIMM should fail? Will the
server stop working or will it keep going?

In high-end servers today, the failure of a single DIMM should not stop the
system. The memory controller should be intelligent enough to switch off a single
DIMM, or switch off a bank of DIMMs if using memory interleaving to enable the
server to keep functioning. Where a single DIMM or a bank of DIMMs are
switched off, there will be some performance degradation. How much
performance degradation will depend upon the way in which the memory and the
whole server has been configured. Under some operating systems there may be
the requirement of a reboot of the system to switch off the memory. If you want to

take advantage of this type of feature, be sure to check if it’s supported on the
hardware.

5.2.6.4 Fans

Fans in today’s Intel-based servers are of critical impor tance. In tests, an
eight-degree rise in temperature can reduce the system life by around 10 to 15%,
while creating intermittent errors throughout the system.

The IBM Netfinity range of servers incorporate a fan monitoring system and a
temperature or environmental monitoring system. Sensors constantly monitor the
fans rotation and temperature, reporting back to the system management
hardware or software of any variation, outside of tolerance.

Some models of IBM Netfinity servers incorporate a "spare fan" design, such that
the loss of a single fan will not raise the temperature above the design

Sizing, Considerations, and Recommendations 45

specifications. System management hardware or software will report the failure of
a fan, which can be changed at a convenient time, without the worry of the
system overheating. No need to power down the system to replace the fan, as
most models incorporate hot-swap fans. If you wish to take advantage of these
features, check to see if they are available for your preferred model, by referring
to the technical descriptions within Chapter 4, “IBM Netfinity Family of Servers”

on page 19.

5.2.6.5 System Power Supply

Power supplies have historically been a "single point of failure". Models of IBM
Netfinity incorporate redundant power supply options, effectively providing a
spare power supply. Should a power supply fail, the system will continue to run
with the remaining operational power supply or supplies. The failing power supply
can be replaced at a convenient time, without the need to power down the
system, as most IBM Netfinity power supplies are hot-swap.

All redundant power supplies include Predictive Failure Analysis (PFA). Refer to

5.2.3, “Hard Disks” on page 37 for further details on PFA.

5.2.6.6 PCI an d ISA Adapt er Cards

Adapter cards are at the very heart of client server and network computing. In
today’s highly intensive network-oriented solutions, there is no room for failure of
a network adapter. One possib le solution to this issue is to install multiple network
adapters in a single system attached to different segments or rings. So that
should an adapter fail, then only a portion of users will be offline, while the
adapter is waiting to be replaced.

A solution available from IBM is to use a combination of:

• Hot-swap network cards

• Active-passive fail-over redundancy of network cards

• Active-active use of network failover adapters (Ethernet only at time of writing)
Note: Hot-swap and failover is only available for PCI adapters. Currently, this is a

new technology and only a few adapters currently support this feature. For a
current list of adapters refer to:

http://www.pcco.ib m.com/us/techlin k/wtpapers/hotpl ug.html

In both cases, you will be able to hot-sw ap the netw ork adapters if installed within
a hot-swap model of an IBM Netfinity server upon failure, without any need to
reboot the system and loss of service to the network users.

It is recommended to avoid using ISA adapters in a high-end server. The I/O
capacity of ISA adapters is very limited and will not provide the I/O capacity
required for highly intensive network computing.

5.2.7 Backup and Recover y Process

In all good solutions is a well-planned backup and recovery process. The basis of
a good backup solution is planning and attention to detail within your customer’s
business data processes. It is not enough to assume that simply backing up the
data once a day/week/month is good enough for your customer’s business. You
must understand the business requirements of the data and the impact that loss
of data will have on your customer’s business.

46 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

The main points to consider in providing a good solution are:

• Time taken to back up and restore data

• Impact to system, if doing online backup

• Ability to recover individual files or databases as required

• Cost of recovering files and databases

• Tape device to use

• Network infrastructure - if backing up across a network

• Size of databases and growth rate

• Tape backup software to use

• Storage of backup media

• Testing of recovery procedures

• Scheduling of full backups

• Scheduling of incremental backups - if used

• Disaster recovery plans

• Documentation of all the above
As you can see from the list above, this is not a simple task. Great care must be

taken to ensure the right backup and recovery procedures are used, and
documented which meet the individual circumstances of the customer’s
requirements.

It is sufficient that you have a basic understanding of what is required to fulfill the
needs of an IBM and J.D. Edwards’ OneWorld solution. For particular customer
needs, it is recommended that you consult a qualified person to specify the
backup and recovery solution required.

Contact IBM Global Services, within your country, for a list of offerings at:

http://www.ibm.com /Services/

5.2.8 Maintenance a nd Service

IBM offers the best server support in the industry. For decades, IBM has been a
leader in large and midrange system service and support. Now with that same
expertise and focus on Netfinity products, IBM offers you an integrated system
that provides you with high-availability service and support, designed and
optimized to meet your business needs. IBM is uniquely qualified to deliver a
caliber of service and suppor t that allows businesses to concentrate on doing
their business.

IBM continues to improve service and support for Netfinity servers. IBM’s focus
includes increasing the availability of maintenance parts; providing support
specialists at the local, regional, and country levels; and assigning customer
service representatives and technical support managers to your business.

5.2.8.1 Remote Connect Su ppor t

IBM’s Remote Connect is a major enhancement to service and support for
Netfinity servers. Using the latest technology advances delivered by select
models of the Netfinity product line, IBM offers a "Call Home" remote support

Sizing, Considerations, and Recommendations 47

feature in an Intel processor-based server. If your server experiences a problem,
it will dial IBM and set in motion the right level of support to keep your system up
and running. And, you can select options to have IBM contact you or your
approved warranty service provider.

Using the multiple technologies in IBM’s newest Netfinity servers, Netfinity
Manager software and the IBM Netfinity Advanced Systems Management PCI
Adapter, our support capability allows us to remotely deliver hardware problem
determination, launch on-site resources if needed, and invoke any level of
support, including product engineering, within minutes. Included in this offering is
a comprehensive problem-management system that provides tracking,
management, escalation, and transfer of problem ownership to the appropriate
skills required to resolve an issue.

5.2.8.2 Update Connector

IBM’s electronic-support Web site provides an automated service for updating
your Netfinity and PC Server BIOS and driver files called Update Connector.
Update Connector is a quick and convenient way to access the latest available
BIOS and driver code. Connecting and executing through the Web, Update
Connector searches your system’s configuration, determines the levels of BIOS
and drivers currently installed, and notifies you of the latest levels. At your
discretion, Update Connector can send you the latest versions for your system
and prepare them for installation at your convenience.

5.2.9 Performance

For more information visit:

http://pc.ibm.com/ us/infobrf/updco nn.html

5.2.8.3 MoST Connect

Leveraging the latest technology advancements in Netfinity and PC Server
systems and Netfinity Manager, IBM increases its on-site support by enhancing
the Mobile Solution Ter minal (MoST), carried by our ser ver field-service
representatives. MoST Connect provides a direct communication link between
the IBM field service specialist at your location and the experts at the IBM
HelpCenter. Continuing to improve on-site support, IBM delivers remote-console
capability with both voice and data communications through a Netfinity or PC
Server system’s serial port.

MoST Connect allows the HelpCenter support specialist to perform remote
problem determination and launch additional resources, including product
engineering if required, to solve a server problem.

MoST Connect enables the HelpCenter to assemble a pool of skills and be
virtually on-site to address the most complex problems without delay.

The overall performance of any system is based upon creating a balanced and
capable system that can handle not only the day-to-day running of the business,
but also the peaks that will occur during a 12-month period of any business.
Another factor within performance is the growth rate of the b usiness requirements
and capacity of the system design. Designing a well-balanced system to meet all
of these requirements is the work of a network and system design consultant who
understands the performance characteristics of IBM Netfinity hardware, Microsoft
Windows NT 4.0, Oracle or SQL Server and J.D. Edwards’ OneWorld software.

48 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Contact a consultant for further advice and guidance on designing, planning, and
implementing a well balanced solution.

5.2.10 Networking Performance Hints for J.D. Edwards’ OneWorld

To prevent network congestion, and to improve overall network access and server
performance, the following guidelines are recommended:

• One to 50 concurrent users, one network card

• 51 to 150 concurrent users, two network cards

• 151 to 300 concurrent users, three network cards

• 301 to 500 concurrent users, four network cards

• 500+ concurrent users, four Network cards plus one additional card for every
250 concurrent users.

The above guidelines will help provide the required bandwidth within mixed J.D.
Edwards’ OneWorld environments. However, if most of your concurrent users
(75% or more) are operating in either a financial or distribution environment, note
that these particular environments are more event driven than others. You may
want to consider the following adjustments to the previous guidelines:

• For a financial environment, reduce the above concurrent users figures by
15%.

• For a distribution environment, reduce the above concurrent users figures by
10%.

Again, these are recommended guidelines, but they will provide you with a good
basis from which to start sizing your network.

Another helpful note might be the following that was found during our test runs:

With 10/100 Base-T NIC car ds, in a switched port environment, it was found th at
a 100 Mb server up-l inks to 10 Mb segments is not nec essarily faster due to the
protocol conversio n latency betwee n the 10 Mb and 100 Mb within th e segments.
Testing showed as much as 17% incr ease in performa nce by replacing 100 Mb
up-links with 10 M b. However, if y ou are moving la rge amounts of d ata beyond
the 10 Mb link cap acity, you may f ind different re sults from this depending

upon your customer’s partic ular networking environmen t.

Sizing, Considerations, and Recommendations 49

5.3 Software Considerations

In the J.D. Edwards’ OneWorld B73.3.x Solution, the compulsory software
choices for the deployment and enterprise ser vers are:

• Microsoft Windows NT 4.0 with Service Pack 4

• Microsoft Access 7.0 or Microsoft Access 97

• Microsoft Visual C++ 5.0

• Microsoft Visual C++ 6.0 (For B73.3.1 only)
The software listed above will not require any in-depth consideration other than

their hardware requirements. Refer to 5.4.1, “OneWorld Deployment Server
Requirements” on page 52 and 5.4.2, “OneWorld Enterprise Server
Requirements” on page 55 for further details on these products.

Therefore, the main software considerations for your customer should be aimed
at the database software to be used with the J.D. Edwards’ OneWorld
implementation. The choices are:

• Microsoft SQL Server 7.0 and client software

• Oracle 8.0.5.x or higher and client software
Your customer may choose to use a combination of the above, although this is

not recommended. There may be compatibility issues and difficulties associated
with upgrading either database software in the future, which in turn m ay create
database issues which will be very difficult to diagnose and resolve. It is for these
reasons and simplicity that you and your customer should consider only one of
the database packages listed.

Factors that may influence the decision of which database software to use could
be:

• Performance

• Database size

• Cost of skill levels available

• Ease of data transfer or data conversion from current system

• Network infrastructure

• Number of users

• Database growth rate

• Compatibility with existing software
These are just some of the items to consider; your customer may consider

several more. The underlying point to make here is that this decision should only
be made by a competent and qualified person, such as a database administrator.

Other software considerations you may want to review are those additional
services or requirements your customer may have, such as:

• File server

• Print server

• Web or Internet server

50 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

• Mail server

• Intranet server

• Extranet server

• Application server

These functions or applications may not be part of the J.D. Edwards’ OneWorld
solution, but they are certainly part of any company’s requirements in today’s IT
environment. These requirements should be considered separate from the IBM
Netfinity and J.D. Edwards’ OneWorld solution unless it’s an integrated solution
of OneWorld, for example, Lotus’ Domino Connector for OneWorld or IBM’s
Net.Commerce. Stay abreast of any network performance implications that these
functions may have on the overall performance of your solution.

5.4 Hardware and Software Requirements for J.D. Edwards’ OneWorld

In this section we discuss and list the minimum hardware and software

requirements for implementing J.D. Edwards’ OneWorld. These requirements
are:

• CPU requirements

• Memory requirements

• Hard disk requirements

• Networking requirements

• Software requirements

• Hardware requirements to run the relevant software

If you have not already done so, it is advisable to read 5.2, “Hardware
Considerations” on page 36 and 5.3, “Software Considerations” on page 50
before reviewing the guidelines in this section.

Review each component to determine your customer’s requirement for OneWorld
implementation. It is recommended that you take notes as you read through this
section, with your customer’s configuration in mind.

From these notes you will gain an insight into the overall basic hardware and
software requirements for your customer’s implementation.

Note: In the following server requirements, it is assumed that only the operating
system (Microsoft Windows NT 4.0 with Service Pack 4) along with the
requirements of the J.D Edwards’ OneWorld applications and environments are
being installed on IBM Netfinity servers.

Listed among the minimum hardware requirements for OneWorld are IBM
hardware recommendations. These recommendations were based on the realistic
performance of J.D. Edwards’ OneWorld software running within a live
environment. These recommendations should be used as a guide to achieve a
higher performance level and meet the needs of your customer’s environment. It
is our intent to provide you with a reasonable balance of performance for your
deployment server and enterprise server to achieve a high level of satisfaction.

Sizing, Considerations, and Recommendations 51

5.4.1 OneWorld Deployment Server Requ irements

In this section, we list the software and hardware requirements for the OneWorld
deployment server. To guarantee the pristine quality of the software, and to
protect the performance of operational systems during the installation process,
this server is dedicated only to deploying and operating OneWorld software.

Table 3. Software and Hardware Requ iremen ts for Deployment S er ver

Components Minimum Requirements IBM Recommendations

CPU Intel Pentium II 266 MHz Intel Pentium II 400 MHz
RAM 128 MB 256 MB
Virtual Memory 300 MB initial, no less than 600 MB

as the maximum

Hard Disk
Microsoft Windows NT Server 4.0 with
Service Pack 4

Screen Resolution 800 x 600 pixels 800 x 600 pixels with 256 colors
CD ROM Required 16x speed or higher
OneWorld B73.3 14 GB - Depending on the numbers

Microsoft Access 97 or 7.0 Not Available 30 MB
Microsoft Visual C++ 5.0

Microsoft Visual C++ 6.0
(For B73.3.1 Only)

Internet Explorer 4.01 or above Not Available 30 MB
Tape Backup Not Available
Token Ring or Ethernet Connection

Note: Y ou must conn ect the client and
server using one of these methods

1.00 GB 2 GB for NT 4.0
Includes networking, systems
management software,
documentation and Oracle tools

23 GB (Oracle) and 45 GB (SQL) or

of path codes being used

Not Available 140 MB

more depending on the numbers of
path codes being used

52 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Table 4. Database Hardware Requirem ent s for Deployment Ser ver

Database Name Minimum Requirements IBM Recommen dat ions

SQL Server 7.0 Client (1) Not Available 130 MB with DBA

Note:

ODBC Administrator: 3.510.3513.0
and later
SQL Server driver: 3.70.06.23 and
later
Access32 driver: 4.00.3513.00 and
later

Use of the incorrect version may
cause data corruption. All of these
versions are available on the Mdac

2.1 stack. It must be obtained from
Microsoft.

Oracle 8.0.5 or later Client CD(1) Not Available 150 MB with DBA

Required: Oracle SQL Plus 8.0.5 or
later

Note: The CD must match your
specific release.

Note:

(1) Choose one version of Oracle or SQL Server for the main database.
All other software is required.

The OneWorld installation program provides you with several environments that
represent the typical customer configuration. On the deployment server, these
environments are preset in the installation process to provide you with an easy
solution for installation setup.

In the installation process, the OneWorld installation program includes the
planner environment to define the main components of a OneWorld configuration,
and the deployment environment that administers system data source
information, such as profiles, packages, and environments. The deployment
environment uses the planner path code from the planner environment to run the
OneWorld on the deployment server.

In Table 5 on page 54, the required diskspace for the objects and path codes
included in the planner and deployment environments are listed.

Sizing, Considerations, and Recommendations 53

The following table helps you calculate the disk space required for OneWorld
software on the deployment server. This can also be found in Chapter 1 of the

OneWorld Installation Guide (Windows NT-Based Systems), Release B73.3

Table 5. OneWorld Software Hard Disk Re quirem ents - De ployment Se r ver

Description Size in GB

Planner and other objects 1.6 GB
Database Exports Oracle 1 GB

Microsoft SQL Server 1.05 GB
CRP Path Code 3 GB (1)
Development Path Code 3 GB (1)
Pristine Path Code 3 GB (1)
Production Path Code 3 GB (1)
Additional Path Codes 3 GB (1)
Note:

(1) Each path code size includes space for two sets of full and partial packages.
A full package re quires appro ximately 1.2 GB and a partial package re quires appro ximately
164 MB.

.

54 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

5.4.2 OneWorld Enterprise Server R equirements

In this section, we list the software and hardware requirements for the OneWorld
enterprise server.

Table 6. Software and Hardware Req uirem en ts for Enter p ris e Server

Components Minimum Requirements IBM Recommendat ions

CPU Intel Pentium II 266 MHz Dual Intel Pentium III 400 MHz
RAM 96 MB 512 MB includes 32 database users
Hard Disk

Microsoft Windows NT Server 4.0
with Service Pack 3 or 4

Screen Resolution 800 x 600 pixels 800 x 600 pixels
CD-ROM Required 16x speed or higher
OneWorld B73.3 and Database See OneWorld disk space

Microsoft Access 97 or 7.0 Not Available 30 MB
Microsoft Visual C++ 5.0

Microsoft Visual C++ 6.0
(For B73.3.1 Only)

Internet Explorer 4.01 or above Not Available 30 MB
T ape Backup Not Available Refer to req uirements of tape back up

Table 7. Database Hardware Requir emen ts for Ente r pr ise Se r ver

Database Name Minimum Requirements IBM Recommendat ions

500 MB for Windows NT 4.0 2 GB for Windows NT 4.0

Includes networking, systems
management software,
documentation and Oracle tools

See OneWorld disk space
requirements for the enterprise
server shown in Table 7, Table 8,
Table 9, and Table 10.

Not Available 140 MB

requirements for the enterprise

server shown in Table 7, Table 8,

Table 9, and Table 10.

software used

SQL Server 7.0 (1) Not Available 150 MB or above

Oracle 8.0.5 (1) Not Available 250 MB

Note:

(1) Choose one version of Oracle or SQL Server for the main database.
All other software is required.

Sizing, Considerations, and Recommendations 55

Table 8 helps you calculate the disk space required for One World software on
the enterprise ser ver. This can also be found in Chapter 2 of the

Installation Guide (Windows NT-Based Systems), Release B73.3

Table 8. OneWorld Software Har d Disk Re quirem ent s - E nterprise Se r ver

Description Size

System Directory 55 MB
Pristine Path Code Directory 1.15 GB
CRP Path Code Directory 1.15 GB
Development Path Code Directory 1.15 GB
Production Path Code Directory 1.15 GB
Additional Path Code Directory 1.15 GB

OneWorld

.

56 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Depending on your database (Oracle or SQL Server), use the following tables to
calculate the amount of disk space required for your enterprise ser ver database.
Base the total on the central objects data sources you require.

Table 9. Oracle Database Hardware Re quire men ts for Ente r pr ise S er ver

Description (Data Source) Oracle (MB)

System Tables (System - B733) 20
Server Map Tables (

Map)
Object Librarian Tables (Object Librarian - B733) 70
Data Dictionary Tables (Data Dictionary - B733) 125
Production Data (Business Data - PROD) 400
Pristine Data (Business Data - JDE) 400
CRP Data (Business Data - CRP) 400
Test Data (Business Data - TEST) 400
Production Control Tables (Control Tables - PROD) 50
CRP Control Tables (Control Tables - CRP) 50
Test Control Tables (Control Tables - Test) 50
Central objects for pristine path code (Central

Objects - PRISTB733)
Central objects for production path code (Central

Objects - PRODB733)
Central objects for CRP path code (Ce ntral Obje cts

- CRPB733)

enterpriseserver

- B733 Server

20

1650

1650

1650

Central objects f or de v elop ment path code (Ce ntra l
Objects - DEVB733)

Central objects for any additional path codes 1650

1650

Sizing, Considerations, and Recommendations 57

Table 10. SQL Server Database H ardwa re Req uirem ent s for Enterprise Ser ver

Database Name Data Sources SQL Server 7.0

JDEB733 System - B733

Object Librarian - B733
Data Dictionary - B733

machinename
machinename

machinename

server)

machinename
machinename

server)

JDE_CRPB733 Central Objects - CRPB733

Versions - CRPB733

JDE_CRP Control Tables - CRP

Business Data - CRP

JDE_PRISTB733 Central Objects - PRISTB733

Versions - PRISTB733
JDE_PRISTINE Business Data - JDE 550 MB
JDE_PRODB733 Central Objects - PRODB733

- B733 Server Map
(where

is the enterprise

- logic (where
is the enterprise

330 MB

2.2 GB

550 MB

6 GB

2.2 GB

Versions - PRODB733

JDE_PRODUCTION Control Tables - Prod

Business Data - PROD
JDE_DEVB733 Central Objects - DEVB733

Versions - DEVB733

JDE_DEVELOPMENT Control Tables - Test

Business Data - TEST

Note:

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 to the
correct SQL Server databa se. Re view th e Third-P arty ODBC Data Sources in th e refere nce
section of the

B73.3

.

OneWorld Installation Guide (Windows NT-Based Systems), Release

400

2.2 GB

550 MB

58 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

5.4.3 OneWorld Workstation Requiremen ts

In this section, we list the software and hardware requirements for the OneWorld
workstation:

Table 11. Software and Hardware Requirements for Workstations

Components Minimum Requirements IBM Recommendations

CPU Intel Pentium 200 MHz Intel Pentium II 400 MHz
RAM 32 MB 96 MB
Hard Disk Space 320 MB - 1.49 GB Free Space

320 MB - Partial without
Development Objects

992 MB - Partial with Development
Objects

1.49 GB - Full without Development
Objects

1.8 GB - Full with Development

Objects
Screen Resolution 800 x 600 pixels 800 x 600 pixels
Windows NT 4.0 Workstation with

SvcPa ck 4 (1)
or Windows 95 (2)
or Window 98 (2)

Internet Explorer 4.01 or above Not Available 30 MB
Acrobat Reader 3.01 or above Not Available 5 MB
Microsoft Access 7.0

or Access 97 (optional)
Microsoft Visual C++ 5.0(3)

Microsoft Visual C++ 6.0(5)
OneWorld HELP Files 22 MB (4) 25 MB
Printer Postscript, line, PCL Network printer able to handle

Notes:

(1) Must use Windows NT 4.0 Workstation with Service Pack 4, if being used as a development workstation.
(2) Although it is possible to do development on Windows 98 and Windows 95, it is not recommended.
(3) Microsoft C++ 5.0 is only required if the workstation is to be used for programming.
(4) Normally, the OneWorld HELP files are serviced from the deployment server. However, if you wish, they can be
installed on workstations.
(5) Microsoft C++ 6.0 is only required if the workstation is to be used for programming. C++ 6.0 is only supported on
OneWorld B73.3.1.

Not Available 500 MB - Windows NT Workstation

350 MB - Windows 95
400 MB - Windows 98

Not Availab le 30 MB - Only require d if user is to edit

tables

Not Available 140 MB

requirements

Sizing, Considerations, and Recommendations 59

Table 12. Database Hardware Requ ireme nts for OneWorld Workst ation

Database Name Minimum Requirements IBM Recommen dat ions

SQL Server 7.0 Client
ODBC Driver: Use the versions in

Mdac 2.1. Use o f the inco rrect v ersion
may result in data corruption

Oracle 8.0.5 Client
Note: This must match your specific

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

Not Available 40 MB RAM

150 MB - hard disk

Not Available 150 MB + 16 MB RAM

60 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

5.5 Preparing for OneWorld Installation

This section presents an overview of the information required and should be
discussed between the OneWorld consultant and the customer to prepare for the
OneWorld installation.

Please refer to Chapter 3 "Installation Worksheet" of the

Guide (Windows NT-Based Systems), Release B73.3

of the following points.
Review the following to gain an insight on items to consider prior to an

installation:

1. General Information Required

• OneWorld security code

• Software license expiration date

• Authorized modules

• Installation plan information

2. Deployment Server General Information Required

• Name of server

• Multitier (YES/NO)

• Data source type

• Platform type

• Hardware configuration including CPU, MEM, RAID arrays

• TCP/IP configuration details (IP address, subnet mask)

• LAN connections and network information

OneWorld Installation

for further details on some

• Coexistence (YES/NO)

• Applications and versions number details

• Database software to be used

• HELP files to be deployed (YES/NO)

3. Enterprise Ser ver General Information Required

• Name of server

• Hardware configuration including CPU, MEM, RAID arrays

• TCP/IP configuration details (IP address, subnet mask)

• LAN connections and network information

• Platform type

• Coexistence (YES/NO)

• Applications and versions number details

• Database software to be used

4. Enterprise Ser ver Environments Information
This requires input with regard to the OneWorld environments that are used.

Information will include items, such as:

• Home directories

Sizing, Considerations, and Recommendations 61

• Temp directories

• Install paths

• User IDs

5. OneWorld Data Source Names
Data sources will be created for each of the shared environments, they are:

• Syste m

• Object Librarian

• Data Dictionary

•Server Map

• Distributed Processing (enterprise ser ver)

• Replicated Local Data
In addition, there will be input requirements for each of the recommended

environments that are to be installed:

• Deployment - DEPB733

• Planner - JDEPLAN

• Production - PRD733

• Tes t - TST733

• CRP - CR P733

• Pristine - PRT733

• Development - DEV733
For each environment to be installed, data source names, object mappings

and packages information will be required. Data source names required for
each environment will be:

• Business Data

• Central Objects Data

• Control Tables (not required for Pristine Environment)

• Version Tables

6. Workstation General Information Required

• Multitier (YES/NO)

• Data source type

• Hardware configuration including CPU, MEM, RAID arrays

• TCP/IP configuration details (IP address, Subnet mask)

• LAN connections and network information

• Applications and versions number details

• Database software to be used

• HELP files to be deployed (YES/NO)

5.5.1 OneWorld Installation Planner

Installation Planner is a OneWorld application that runs on the deployment server
as a system administration tool. Installation Planner guides you through defining

62 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

the installation plan you need to install OneW orld. The information you provide on
the Installation Planner form, such as database type and enterprise server type,
determines the information you will see on the screens as you go through the
setup of the Installation Planner.

Installation Planner guides you through setting up:

• Enterprise ser ver information

• Deployment server information

• Data sources

• Environments

Enterprise Server Information

To set up the plan for the enterprise ser ver, you must provide the OneWorld
installation program with the name of the enterprise server, its platform type, and
the database that runs on it. The program populates the enterprise server tables
(F00053, F000531, and F000532) and defines the data sources f or the e nterprise
server. In addition, it provides information for the Object Librarian, Central
Objects, Versions, System, Data Dictionary, Business Data, Control Table, and
Server Map data sources.

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 type of database
you use. This information populates the Release Master (F00945), Path Code
(F00942), and Data Source Master (F98611) tables appropriately.

Data Source Information

When you run Installation Planner, you set up the following data sources once
because they are shared across all of your environments:

System The data source for the System tables. It is identified by the

OneWorld release level (for example, System - B733).

Object Librarian The data source for the Object Librarian tables. It is identified

by the OneWorld release level (for example, Data Dictionary ­B733).

Data Dictionary The data source for the OneWorld Data Dictionary tables. It is

identified by the OneWorld release level (for example, Data
Dictionary - B733).

Server Map The data source for the replicated system tables for

distributed processing on your enterprise server (for example,
enterprise ser ver - Server Map). It is specific to each
enterprise ser ver.

You will also set up the following data sources for each environment:
Business Data The data source for the Business Data tables. You can have

multiple sets of Business Data sources (for example,
Business Data - CRP, Business Data - PROD, Business Data

- TEST, and Business Data - JDE).

Sizing, Considerations, and Recommendations 63

Central Objects The data source for the Central Objects specification tabl es. It

is identified by the type and version number of OneWorld. In
addition, you can have multiple sets of central objects
specifications (for example, Central Objects - PRODB733,
Central Objects - PRISTB733, Central Objects - DEVB733,
and Central Objects - CRPB733). Howe v er, you can have only
one Central Objects data source for each path code.

Versions The data source for the OneWorld Versions tables (F983051

and F98306). You can have multiple sets of versions tables
(for example, Versions - PRODB733, Versions - PRISTB733,
Versions - DEVB733, and Versions - CRPB733). However,
you can have only one Versions data source for each path
code.

Control Tables The data source for the Control Tables.You can have multiples

(for example, Control Tables - Production, Control Tables ­Test, and Control Tables - CRP).

J.D. Edwards configures your OneWorld data sources as completely as possi ble.
However, when you run Installation Planner, you might need to modify some data
source information to reflect your system-specific configuration. For example, if
you use Oracle 8.0, you must specify JDBOCI80.DLL in the .DLL Name field for
all Oracle data sources.

5.5.2 OneWorld Installation Workbench

After you plan the OneWorld installation, run Installation Workbench to allocate
and configure software and resources. Depending on your plan, you might not
run all the workbench programs during Installation Workbench. For example, if
you are not a J.D. Edwards WorldSoftware customer, you will not run the control
table merges, so those workbench programs are not displayed. Installation
Workbench follows the plan you created.

Running the installation plan updates various tables during each of the
workbench processes you chose to perform during the planning stage.

The following actions could occur:

• Data Source Workbench - Copies all data sources that are defined in the plan
from the F98611 Data Source Master and F986115 Table and Data Source
Sizing files in your Planner data source to your System - B733 data source. It
also updates the F98401 Data Source Plan detail record to reflect completion.

• Environment Workbench - Copies the F0093, F0094, F00941, and F00942
environment information tables and the F986101 Object Configuration
Manager table from your Planner data source to your System - B733 data
source. It then updates the F98403 Environment Plan detail record to reflect
completion. Depending on the plan settings, it also runs batch applications
that create the tables and indexes for environments defined in the plan.

• Host Workbench - Copies the host configuration files (F00053, F000531, and
F000532) from the Planner data source to the System - B733 data source. It
then updates the F98402 Host Plan detail record to reflect completion and
uses the environment information to populate the F986101, F98611, and
F986115 tables in the Server Map data source. (Only valid en vironments , data
sources, and server map tables are created.)

64 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

• Package Workbench - Transfers the F9885, F9886, and F9887 package
information tables from the Planner data source to the System - B733 data
source. It then updates the F98404 Package Plan detail record to reflect
completion.

5.5.3 Setting Up One World Users

Setting up users and groups can be time consuming, but you can do it easily
during the conference room pilot phase of the installation process. J.D. Edwards
recommends you set up one or two users to perform the installation process, then
set up the rest of your users and groups later when you have the time to consider
how you want groups to be organized and what preferences you want each group
to have.

The user profile defines a specific user or group to OneWorld. This description
includes:

• The group the user is with (such as accounting) and display preferences (such
as language). Groups are an important aspect of OneWorld. By assigning
users to groups, system administrators can define user preferences and
securities based on groups rather than the individual user.

• The packages from which the user can choose when installing OneWorld to
the client workstation.

• The environments from which the user can choose when starting a OneWorld
session.

About Group Preference Capability
Group preference capability eliminates the need to assign packages to each

individual user profile. By assigning individual users to a group, you can perform
package assignment once for the group and have those assignments available to
all of the individual users belonging to that group. If necessary, you can specify a
different package assignment for each user. In this case, the individual user
assignments override the group assignments.

Deployment and environment information is read first from the user’s individual
profile, and then, if no information exists, from the group’s information.

The following example clarifies this:

Table 13. Reading User’s Individual Profile

User Information Group Information

User ID: John
Packages Assigned:
None

User ID: Jane
Package Assigned: PROD

Group ID: Group1
Packages Assigned: CRP, TEST

Group ID: Group 2
Packages Assigned: CRP, DEVL, TEST

The results of the different user and group profiles are as follows:

• John has no assigned packages in his user profile. As a member of Group 1,
he has the CRP and TEST packages available.

• Jane has the assigned package PROD. Although a member of Group 2, the
assignments in her user profile override the group assignments.

Sizing, Considerations, and Recommendations 65

You can specify different packages by users when necessary while taking
advantage of the reduced setup effort offered by group preferences.

This section describes the different ways to use the User Profile applications.
When setting up profiles perform the following:

• Create all group profiles for the enterprise.

• Create a user profile for every user, and (optional) assign a group profile and
display preference to each user.

• Assign to each group or user the following preferences:

• Packages available to each group or user

• Environments available to each group or user

Note: During User Deployment, sign on to the deployment environment
(DEPB732) on your deployment server.

5.6 Requests for Sizing

The purpose of this section is to describe the current approach for doing
pre-sales sizing for the J.D. Edwards’ OneWorld application suite running on IBM
server platforms. We will start by discussing the performance characterization
testing that has been done to date, describe how this data is being used to do
pre-sales sizing, and then discuss configuration issues for the IBM Netfinity
Platform.

We will then discuss how a sizing request is created and then discuss a typical
sizing response from IBM.

This information is taken from the

Edwards OneWorld Software on IBM Platforms - Version 5.3.

developed by the IBM-JDE Competency Center.

5.6.1 The Sizing Process

In the event you or your customer need assistance in sizing an IBM Netfinity
server for J.D. Edwards’ OneWorld, the IBM/ERP Presales group is available to
provide worldwide sales and sizing support. The IBM/ERP Presales group only
size systems (for example, Netfinity, RS/6000, and AS/400) to run OneWorld or
OneWorld coexistence with WorldSoftware. The IBM/ERP Presales group can be
contacted at 1-800-IBM-0222 or via e-mail: [e-mail].

How Do I Request a System Sizing?

To request a system sizing, an IBM ERP consultant or business partner will
perform the following:

1. Obtain a copy of the IBM/J.D. Edwards Sizing and Planning Questionnaire
from the IBM FAX server at 1-800-IBM-4FAX (or 408-256-5422, if outside of
the U.S. and Canada) and request document ID 8651.

2. Fill out the questionnaire in its entirety.

Sizing and Configuration Guidelines for J.D.

This document was

3. Fax the completed questionnaire to the IBM/ERP Pre-Sales Sizing Center in
Philadelphia, PA at [phone].

66 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

4. A professional sizing response package will be returned to the IBM ERP
consultant or business partner within five business days.

Netfinity OneWorld Sizing Tool On line

Now you can access the IBM Netfinity OneWorld sizing tool online via the
following URL:

http://www.ibm.com /erp/jdedwards/s izings/index.htm l

Remember to answer the questions as carefully as possible so that the IBM
Sizing Center may provide you with accurate sizing information.

Request Document ID 8651

Once completed in its entirety, the questionnaire is then faxed to the IBM/ERP
Pre-Sales Sizing Center. Professionals in the sizing center will analyze the input
and provide an estimate of server sizing based on the performance data we have
to date. For unusual sizing requests the sizing center may engage the IBM/J.D.
Edwards International Competency Center or J.D. Edwards performance experts.

Once the analysis is complete a comprehensive document summarizing the
output of a sizing analysis is delivered to the requester.

The Sizing Tool

The IBM/J.D. Edwards International Competency Center is comprised of a group
of experienced professionals dedicated to providing high quality sales support for
IBM platforms running J.D. Edwards software. In addition to a Competency
Center Manager, the team includes server platform technical specialists, a sizing
specialist, a network specialist, and a marketing specialist. The tool used for
sizing the OneWorld and IBM Netfinity solution was developed by the
Competency Center team. This tool is based on an analysis of the performance
characterization data collected during the performance benchmark test runs for
the IBM Netfinity servers.

The current tool is a user-based sizing tool and is designed to take user counts
as collected by the sizing questionnaire then creating a reasonable estimate of
resource needed for each server platform. Certain minimum requirements are

built in to the tool. These are discussed in 5.6.2, “Sizing Guidelines” .

5.6.2 Sizing Guidelines

We must keep in mind that w hile pre-sales sizing is a v ery important phase of any
OneWorld sale, the actual amount of mone y spent on server hardw are in a typical
implementation may be a relatively small portion of the entire package. We
believe that for every dollar spent on OneWorld software a customer might expect
to spend a dollar on server hardware, a dollar on PC upgrades, a dollar on
network upgrades, and from three to four dollars on services. These numbers will
vary by customer, but they demonstrate the fact that the cost of the server may
comprise from 10% to 30% of the entire project cost.

In many situations we have seen the issue of pre-sales sizing take on a role m uch
more important than the amount of money spent on this portion of the package
can justify.

Sizing, Considerations, and Recommendations 67

Another important consideration when evaluating a pre-sales sizing is that the
test workloads created for benchmark testing may vary significantly from the
actual workload of any given customer for the same application module.

For example, consider the manufacturer whose typical customer may place an
order for an average of three items per sales order. A manufacturer in another
industry may average hundreds of items per sales order. Yet when asked to do a
pre-sales sizing for each of these potential customers we would be sizing based
on a sales order entry script that entered ten items per sales order. This may yield
acceptable results for the first prospect but may grossly understate the
requirements of the second prospect.

To address this issue J.D. Edwards and IBM recommend that each customer
revisit server sizing a number of times during the implementation process when
more details about how they will actually be using the OneWorld applications are
known.

The current J.D. Edwards implementation methodology proposed to every
potential customer suggests that sizing be revisited as part of the Conference
Room Pilot phase, and revisited again after the environment has been tuned and
prior to going live. This ensures that the final sizing estimates are based on the
exact application environment that the customer will be using, not on the
environment created for the benchmark testing.

Another important issue to understand is that the limited benchmark testing to
date has focused only on a very simple two-tier implementation of OneWorld. The
benchmark tests were run with relatively "fat" clients, that is, the client PC was
executing the OneWorld business logic and the server machines were acting as
database servers only. This is only one possible configuration for a product
whose greatest strength is the flexibility it offers customers in implementing
multitier configurations. It is hoped that in the near future we will have the
capability to test multitier configurations.

5.7 Configuration Guidelines

The purpose of this section is to document the configuration requirements for the
various elements of a OneWorld implementation. Guidelines for the deployment
server, client PCs, and the Netfinity database (or enterprise server) server are

reviewed in detailed in 5.4.1, “OneWorld Deployment Server Requirements” on
page 52, 5.4.2, “OneWorld Enterprise Server Requirements” on page 55 and

5.4.3, “OneWorld Workstation Requirements” on page 59.

5.7.1 Netfinity Enterpr ise Server Guid elines

Every OneWorld implementation must include an enterprise server. The
enterprise ser ver acts as the central repository of data for all OneWorld users.
The enterprise server contains all the tables and data, to which users will be
reading and writing to. So in this instance you can understand how critical the
enterprise ser ver is to a customer’s business. Not only does it have to be a
powerful machine, it also has to be very reliable, very available, and very
responsive to enable it to meet the demands of the customer’s business.

The following comments apply to Netfinity configurations with either the Oracle or
SQL Server database:

68 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

• Sizings are done at a target server CPU utilization of 40% to 60%.

• Main memory is sized at 8 MB per active user and never to be less than 512
MB.

• Disk space is sized at 250 MB per user and either 23 GB (Oracle) or 45 GB
(SQL Server) for OneWorld objects, plus an additional 30% for free space and
then multiplied by 2 for RAID 1.

• For SQL Server a factor of 1.4 is applied to a given database size. Our
experience has shown that SQL Server needs that much more space to hold
the same database as in an Oracle or DB2/400 environment.

• We recommend a RAID 1 implementation in a Netfinity environment to ensure
adequate disk performance.

Comments regarding network performance impact and multiple database servers
also apply to the Netfinity server. With Netfinity we do not have available any
standard interactive performance tests (like CPW for AS/400 or OLTP for
RS/6000) so we cannot effectively scale our measured performance results into
the other members of the Netfinity product line. Therefore we can only size for
each individual member of the Netfinity line after we have been able to
performance test it.

To date we have completed testing for a Netfinity 7000-M10 server (4-way mode)
running the Oracle database. These tests were done with the 400 MHz processor
cards with 1 MB level 2 cache. We then use a rule of thumb to project the
performance of the 512 KB level 2 cache CPU cards.

We have also tested the Netfinity 5500-M10 server with both 350 MHz and 400
MHz processors with the Oracle database. Testing with the Netfinity server was
performed using the ServeRAID II adapter and 4.51 GB 10,000 rpm disk drives.
This high performance disk configuration proved to be critical to achieving good
OneWorld response times.

Recently announced IBM Netfinity servers will provide even greater performance.
We are presently engaged in providing new performance test information using
these new systems. To view the Netfinity systems, see Chapter 4, “IBM Netfinity
Family of Servers” on page 19 of visit the IBM Netfinity Web site at:

http://www.pc.ibm. com/us/netfinity /index.html.

All Netfinity servers for use with OneWorld should be configured for RAID 1 using
the latest ServeRAID-3HB and 3L Ultra2 SCSI adapters.

The ServeRAID-3HB and 3L Ultra2 SCSI adapters. The ServeRAID-3HB Ultra2
has three SCSI channels whereas all can be externally accessible from a single
PCI slot and 32MB of mirrored write cache included as standard for high
availability and true enterprise storage. Using an advanced RISC I/O processor
on the ServeRAID-3L Ultra2, the Ultra2 SCSI technology with twice the date rate
of Wide Ultra SCSI, and an advanced 64-bit, high performance (up to 264Mbps)
PCI interface, you can support data-intensive applications. The ServeRAID-3L
provides one SCSI channel and 4MB cache. The Ultra2 SCSI channels are
capable of supporting up to 15 devices each at up to 80 MBps data throughput.
Select Netfinity models support up to eight adapters for up to 8.7 TB of external
storage using the Netfinity EXP15.

Sizing, Considerations, and Recommendations 69

For more information on the ServeRAID-3HB and -3L Ultra2 SCSI adapters,
download this PDF from:

ftp://ftp.pc.ibm.c om/pub/pccbbs/pc _servers/ops6198 f.pdf

In addition, take a look a IBM Fibre-channel solutions. This information can be
obtained at:

ftp://ftp.pc.ibm.c om/pub/pccbbs/pc_se rvers/sv6189f.pdf

For a complete list of hardware and software requirements on the OneWorld

enterprise ser ver, refer to 5.4.2, “OneWorld Enterprise Server Requirements” on
page 55.

5.7.2 Sizing Questionnaire

An example of the Sizing and Planning Questionnaire for OneWorld on the IBM
Netfinity server platform is included for reference:

Note: This is an example only and should not be used for a sizing request.

Example of Page 1 (Fax Header Sheet)

In order to obtain a questionnaire for use with a customer please call the IBM
automated fax service at 1-800-IBM-4FAX from the USA or Canada or (408)
256-5422 from anywhere else.

Request document ID 8651

Using the fax service will ensure that the latest version of the Sizing and
Planning Questionnaire is obtained.

Important: Please request a copy of this questionnaire every few months from
the IBM FAX server to ensure that you have the latest version. Call
1-800-IBM-4FAX or 1-408-256-5422, select option 2, and request document ID

8651.

70 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Example of Page 2

Sizing Questionnaire

OneWorld
Introduction:
Thank you for allowing IBM the opportunity to provide you a sizing estimate for

OneWorld software from J.D. Edwards running on an IBM server platform. We
will be requesting the following information in order to arrive at a system
recommendation and architecture based on your requirements and business
environment.

This information will allow us to provide you with an estimation of the processor
class, memory, and disk space requirements.

The sizing process initiated by the completion of this Sizing and Planning
Questionnaire is called a pre-sales sizing estimate. A pre-sales sizing is based
on minimal input and is intended to be a very rough estimate of server resource
required to support a given OneWorld workload. The accuracy of the sizing
estimate is dependent upon many variables such as the accuracy of the
information provided by you, the customer , (we recognize that it ma y be difficult
to provide exact numbers on your environment) and the actual usage of the
system in a real-time environment. Sizing is an iterative process and the sizing
issue should be revisited a number of times during the implementation process.
Perf ormance data gathered during the pilot phase of an implementation project
should be used to generate a much more accurate estimate of server
resources required for a given OneWorld workload.

In this pre-sales sizing estimate we will provide to you an estimate of disk
space required to support the OneWorld database for the number of users
defined in your workload estimate. This will be a very rough estimate as the
disk space required does not always correlate with the number of active users.
J.D. Edwards has a disk sizer tool that can be used to obtain a much more
accurate estimate of the disk space required.This more accurate estimate can
be obtained by contacting your J.D. Edwards marketing representative.

Currently we are able to provide pre-sales sizing estimates for two-tier
implementations of OneWorld only. In a two-tier implementation the server
functions as the central database server supporting client PCs running
OneWorld business logic. Certain customers may find it appropriate to explore

multitier implementations of OneWorld exploiting the flexibility of OneWorld’s
Configurable Network Computing (CNC) environment.

Currently sizing for multitier implementations is beyond the scope of this
document.

Sizing, Considerations, and Recommendations 71

Example of Page 3

Company Name:
Street Address:
Street Address:
City, State Zip:
Country:
Contact Person:
Phone Number:
Fax Number:
Company description:

(distribution, mfg, etc.)

IBM Client Rep:

Sizing Questionnaire

OneWorld

Phone Number:
IBM Product Specialist:
Phone Number:
IBM OMSYS Number:

Business Partner ­Company Name:

Contact Name:
Phone Number:
Fax Number:
J.D. E dw a rds R ep :
Phone Number:

Platform preferred (check one): ______AS /400
_____ Netfinity (NT) with Oracle
_____ Netfinity (NT) with SQL Server
_____ RS/6000

72 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Example of Page 4

Company Wide Users

Application OneW orld

Active Users

Financial
Distribution
Manufacturing
Total

World/World
Vision
Active Users*

Total Logged
On Users**

Users

Please complete this information as accurately as possible. Be sure not to
double count users. Classify users where they spend a majority of their time
each day. We are trying to size for a peak hour of a day when the most
concurrently active users are online.

*Fill in the World/World Vision Active User column ONLY if coexistence with
OneWorld is required on the same machine. Use same definition for active
user as above.

TOTAL LOGGED ON USERS: Indicates the maximum number of connected
users or logged on users who may or may not be actively interacting with the
system.

**If unable to provide active user counts, we will assume 65% of the logged on
users as being active users

Sizing, Considerations, and Recommendations 73

Example of Page 4 - Continued

Conference Room Pilot and Development Requirements:

Will the Conference Room Pilot machine become
your production machine?

Peak active users on the CRP? World _________

Installation date for CRP?
Will you require a separate development or test

machine?
If Yes, for how many users?

Yes/No

OneWorld ________

Yes/No
OneWorld ____World ____

Additional Information for Production Environment:

Is coexistence with WorldSoftware a requirement? Yes/No
What hardware do you have now?

If AS/400, give model number
Do you want a phased approach to sizing, and if

Yes, give active user number and dates for each
phase

Date for start of produc tio n

Phase 1
Phase 2
Phase 3

Growth projected one year after start of production
(%)?

74 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Example of Page 5

System Requirements for Production:

Batch processing during online time (%)
Disk Mirroring or RAID 5 r equ ir ed? Mirroring / RAID 5

High availability configuration requir ed, such as :
HACMP, MIMIX, OMS, or MSC S?

If yes, percentage of total workload that n eeds to
run in failover mode?

Backup Media Required (4mm/8mm/3590/3570/DL T)

HACMP / MIMIX / OMS
MSCS

Explanations of Some of the Above Questions:
Conference Room Pilot Requirements:

Customers often start with a conference room pilot for functional testing.
Sometimes this system becomes the production system but not always.

Additional Information: We would like to know your plans for the start of
production since future hardware enhancements may be recommended if
appropriate.

System Characteristics

• Batch jobs such as reports, MRP runs, general ledger updates, EDI, need to

be considered if run during peak online time.

• Disk mirroring typically provides high availability on the disk in a UNIX or

Windows NT environment. This should be considered for the production
environment.

• High availability on the CPU can be attained by using IBM’s HACMP

product on the UNIX platform, MIMIX (from Lakeview Corp.) or OMS (from
Vision Solutions) on the AS/400, or MSCS on the Netfinity. In all cases, a
second system is required for implementation.

Sizing, Considerations, and Recommendations 75

5.8 Hardware and Software Requirements for Windows Terminal Server

In this section, we list the OneWorld B73.3 software and hardware requirements
for the Microsoft Windows NT Server 4.0, Terminal Server Edition.

Table 14. Software and Hardware Requirements for Windows Ter minal Server Edition

Components Minimum Requirements IBM JDE

Recommendations

CPU Two-way Pentium Class

Intel server

Operating System Windows Terminal Server
RAM 30 MB per user 512 MB plus 30 MB per user
Screen Resolution
Hard Disk (1)

for Microsoft Terminal
Server Edition

Hard Disk (2)
For OneWorld and
additional applications

Dual Intel Pentium III 400
MHz

Note: For a TSE server
supporting 15 or fewer
workstations at least two
processors. For more than
15 users, four 400 MHz or
higher processors.

4 GB, set at RAID 0 for the
TSE root drive.

A minimum of three 4 GB
hard drives, set at RAID 5.
Swap space should be
configured to use the striped
disk set and configured to
be at least one to two times
the available physical
memory.

Network Card Required Note: The netw ork interface

Citrix MetaFrame Required Load on striped disk set
Domino Go Web Server Required Load on striped disk set
Network Station Manager Required Load on striped disk set
OneWorld B73.3 Client Required Load on striped disk set
SQL Client Connectivity Required Load on striped disk set

76 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

card (NIC) used to
communicate with the
enterprise server should
utilize a switched 100 Mbps,
full duplex connection as a
minimum.

Components Minimum Requirements IBM JDE

Recommendations

Important:

(1) Mdac 2.1 (which contains the versions of ODBC drivers) is not supported for Windows
Terminal Server Edition. However, Mdac 2.1 is now required for all other servers and
workstations if y ou u se Micros oft SQL Server. Please use your current ODBC driv ers f or the

Ter minal Server and use the workaround located in 9.11.1, “Instructions for MDAC2.1 and
TSE” on page 317.

(2) For performance reasons, swap space should be configured to use the striped disk set
and configured to be at least one to two times the size of available physical memory.
OneWorld sho uld be ins talled on a striped dis k se t. Th e N TF S fil e s yst em i s re co mm en ded
throughout the hard drive configuration.

Sizing, Considerations, and Recommendations 77

78 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Chapter 6. Using ServerGuide for IBM Netfinity

The HardwareGuide CD helped us to perform a simplified server installation that

was specific to our system based on the hardware detected. HardwareGuide’s
easy-to-use wizard interface gave us complete control of the setup and
configuration process, with a choice of an express or custom configuration path.
After we completed the hardware configuration, we were ready to install our
network operating system. The SoftwareGuide CD was used to install our
Windows NT 4.0 Server network operating system. SoftwareGuide helped us by
installing the device drivers needed for our IBM Netfinity 5500 systems and are
utilized by Windows NT 4.0 Server. This was all that was needed to get our
servers up and running. Afterward, we downloaded Microsoft’ s Service Pack 4 for
Windows NT 4.0 Server to update our network operating systems to the latest
level.

World Wide Web

For the latest device drivers, software patches, product information, general
ServerGuide notes or specific information about your s erver model and y our
operating system, visit the ServerGuide home page at:

http://www.pc.ibm. com/us/server/sg uide/ and click Support.

Information and BIOS updates for your server can also be obtained from the
Netfinity Web site:

http://www.pc.ibm. com/us/netfinity/ and click Support.

6.1 ServerGuide Overview

Installing and configuring a server can be a complex, time-consuming task. In
addition to installing hardware, installing the operating system, device drivers and
applications makes the task more complex. Because of this , some of your highest
cost can be the initial installation and configuration of a server. When several
servers are being installed, the costs can rise significantly.

The solution for IBM Netfinity servers is IBM ServerGuide. ServerGuide is
designed to simplify and shorten setup, configuration, and network operating
system (NOS) installation. ServerGuide simplifies deployment, helping you
reduce your total cost of ownership, and also reduces the complexity that
administrators and technical personnel face.

ServerGuide is shipped with every IBM Netfinity server. ServerGuide’s built-in
intelligence recognizes machine types and models of servers and software
versions and other hardware criteria. As a result, ServerGuide offers installation
and configuration choices designed for your system and its respective custom
configuration.

ServerGuide is packaged in an easy-to-use binder format that contains the
ServerGuide CDs and the IBM Netfinity system reference manual. ServerGuide
aids the installation of all major operating systems. You need your own copy of
the operating system you plan to install.

© Copyright IBM Corp. 1999 79

ServerGuide includes the following CDs:

• ServerGuide SoftwareGuide

• ServerGuide HardwareGuide

• CoPilot Application Guide

• Book Factory

• Diskette Factory

• Operating System FixPaks
FixPaks are provided for Microsoft Windows NT, Novell IntraNetWare and

OS/2 Warp

ServerGuide supports the following operating systems:

• IBM OS/2 Warp Server, Advanced and SMP

• Microsoft BackOffice Small Business Server 4.0

• Microsoft Windows NT Server 4.0

• Microsoft Windows NT Server Enterprise Edition 4.0

• Microsoft Windows NT Workstation 4.0

• Novell IntraNetWare

• Novell NetWare 5

• SCO Open Server Release 5.0.4 and 5.0.5

• SCO UnixWare 7

In addition, ServerGuide provides the following products and installation tools at
no additional charge:

• Lotus Domino Application/Mail Server 5.0 (specific product is dependent on
Netfinity server purchased)

• IBM Netfinity Configurator

• APC PowerChute plus

• Replicated Installation Path for Multiple Windows NT Server 4.0

• Book Factory

• Diskette Factory

• System Information Tool

• RAID Manager

• IBM Netfinity Manager

• IBM Update Connector

• IBM Network Station Manager

• IBM Cluster Systems Management

• IBM ServeRAID Adapter Administration and Monitor Utility

• Adaptec EZ-SCSI Utility

• Norton AntiVirus for Windows NT Server Edition

80 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

6.2 HardwareGuide and Windows NT Server 4.0

The HardwareGuide CD helps you perform a simplified server installation that is
specific to your system based on the hardware detected. HardwareGuide’s
easy-to-use wizard interface puts you in complete control of the setup and
configuration process, with your choice of an express or custom configuration
path; no setup diskettes are needed on Netfinity servers. You can run system
configuration utilities, set up your RAID configuration, and install flash BIOS
updates directly from the HardwareGuide CD. HardwareGuide also installs and
uses a 50 MB system partition on your hard drive. The system partition, if
availab le , can be used in the fut ure b y other IBM pr oducts . After you complete the
hardware configuration you are ready to install your network operating system.

Begin using the HardwareGuide CD by completing the following steps:

1. Insert the HardwareGuide CD, and turn on or reboot your Netfinity system.

2. At the Make a selection screen, select (Start here) Run HardwareGuid e for
all servers and press Enter.

3. At the ServerGuide language screen, click English.

4. In the region and keyboard panels, the default selection is United States. Click
Next.

5. Read the Welcome Screen and click Next.

6. Select Express as your configuration method.

7. Select Microsoft Windows NT Server as the operating system you will install
and click Next.

8. The Express Configuration detects the hardware configuration and states
which utility programs are required. For example:

• Date and time

• ServeRAID configuration

• System partition configuration
Click Next.

9. At the date and time screen, ensure that the correct date and time are
indicated (if not, modify to correct). Click Next.

10.The ServeRAID Configuration screen appears. Take a moment to read the
information. Click Next.

11.If the controller card (controller 1) is not configured, click the right mouse
button and select Configure the ServeRAID Controller. You will have two
configuration paths from which to select:

• Express Configuration for Controller 1

• Custom Configuration for Controller 1

12.In our example, we had six 9 GB drives installed in our IBM Netfinity 5500 (the
deployment server). Select Express Configuration for Controller 1. The
controller card is set to one array, one logical drive and six physical drives.

• New Array A: 43.3 MB capacity

• New Logical Drive 1: RAID level-5, 34.7 MB

• Physical Drives: 5 - 8.6 MB used capacity on each drive

Using ServerGuide for IBM Netfinity 81

• Hot Spare Drives: ID 5 on SCSI Channel 2 is 8.6 MB

13.Click Apply to continue.

14.At the confirm dialog screen, click Yes. Then click File and Exit.

15.Click OK to restart the system.

16.Leave the HardwareGuide CD in the system. After the system reboots the
system partition screen appears. Read the information and click Next.

17.Click Done. The ServerGuide presents the status report for each utility
program as completed. Click Next.

18.Select Exit HardwareGuide and continue with SoftwareGuide. Click Next
and then click OK. After shutdown, insert the SoftwareGuide CD and restart
the system.

19.Continue by following the instructions in 6.3.1, “Installing Windows NT Server

4.0 Using the SoftwareGuide CD” on page 84. To understand more about
SoftwareGuide, you should begin reading 6.3, “SoftwareGuide and Windows
NT Server 4.0” .

6.3 SoftwareGuide and Windows NT Server 4.0

Use the SoftwareGuide CD to install your network operating system easily.
SoftwareGuide helps you install the device drivers needed for your IBM server.
Hints and tips are available in the online README. Supported operating systems
include:

• Microsoft Windows NT Server

• Microsoft BackOffice Small Business Server

• OS/2 Warp Entry, Advanced and SMP Server

• SCO OpenServer and Novell IntraNetWare and NetWare

Each operating system has its own installation method, giving a range of
flexibility during installation. The methods are tailored to the operating system.
For example, Microsoft Windows NT Server supports diskette-less installation. A
Microsoft Windows NT installation provides a replicated path, saving time when
installing multiple servers. This is all that’s needed to get your server up and
running.

If you choose to update your operating system to the latest level, ServerGuide
also includes the CD with current operating system FixPaks.

For the purposes of this redbook, this section concentrates on the aspects of
ServerGuide 4.1 as it pertains to the installation of Windows NT Server 4.0.

For the installation of Windows NT Server 4.0, ServerGuide provides assistance
in building driver diskettes for the various IBM products and the installation
diskettes for Windows NT Server 4.0. However, you will have to make sure that
the drivers that you create from the ServerGuide CD-ROM are newer than those
provided with the product. You can do this by checking their time and date
stamps.

82 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

World Wide Web

For the latest device drivers, software patches, product information, general
ServerGuide notes or specific information about your server model and your
operating system, visit the ServerGuide home page at:

http://www.pc.ibm. com.us/server/sg uide

Using ServerGuide for IBM Netfinity 83

6.3.1 Installing Windows NT S erver 4.0 Us ing the SoftwareG uide CD

Start the SoftwareGuide bootable CD-ROM by placing it in the CD-ROM drive of
your server and reboot the system. After the POST test runs, SoftwareGuide
boots and the ServerGuide language selection screen appears. Complete the
following instructions for a successful installation:

1. Select the language that you want to use during the software installation
process. There are five options:

• English

• French

•German

• Spanish

• Ital i a n
For this installation process, we selected English.

2. The country and keyboard selection screen is displayed. A left arrow, right
arrow and question mark now appear at the bottom of the screen. Selecting
the question mark gives you help information on the displayed screen. The left
arrow will take you to the previous screen and the right arrow will take you to
the next screen. These buttons perform the same functions on many of the
following screens on which they appear.

3. Select the appropriate country and keyboard for your software. For this
installation process, select United States as the country and United States
for the keyboard. Select > to continue.

4. At the Main Menu, there are six options:

• README Hints and Tips

•Overview

• Product Registration

• Diskette Factory

• Operating System Installation

• Introduction to CoPilot Application Guide
Select Operating System Installation.

5. The ServerGuide Operating System selection screen appears and it has four
options:

• Novell IntranetWare

• Microsoft Windows NT Server

• IBM OS/2

• SCO OpenServer
Select Microsoft Windows NT Server.

6. The Selecting a Windows NT Server 4.0 Version and Installation Method
screen appears. Ensure that the following are selected for Version and
Method for Windows NT Server CD Installation:

• Windows NT Server Release 4.0

• Customized Installation

84 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

At this point, ensure that you hav e the retail version of Windows NT Server 4.0
available. Click on the > button to proceed with the installation.

7. The Installed Adapters screen is displayed. This screen shows the server
type, the hard disk adapters and controllers, and the network adapters and
controllers installed in the server, as detected b y the ServerGuide. Clic k on the
> button to continue with the installation.

8. Select FAT as the type of partition to be created. Make your Windows NT
Server partition size 2 GB. Click the > button to proceed with the installation.

9. Select 5 concurrent connections (or whatever the correct number of
connections should be entered). Click the > button twice to proceed with the
installation.

10.Remove the SoftwareGuide CD from the CD-ROM drive and insert the
Windows NT Server 4.0 CD. Click OK to continue with the installation of
Windows NT Server 4.0.

11.After the files are copied to your server, you will see a dialog box indicating to
remove the Windows NT Server 4.0 CD from the drive. Click OK to continue.
Your system will begin to restar t.

Notes

Use the following notes for a successful installation of your Deployment server
and Enterprise ser ver.

1. Refer to your Windows NT Server documentation for setup and
configuration instructions.

2. When your server reboots, if you see a Virus Warning Screen, ensure the
highlighted line states Change is expected and press Enter.

3. Although the setup Microsoft Internet Information Server is a requirement
for the Deployment server, do not select it during the Windows NT Server

4.0 installation.

4. During our installation, we selected TCP/IP and NetBIOS as our protocols.

5. A MSDOS window will appear running setup.exe, press Enter twice to
continue.

6. Create your repair disk.

7. Once your Windows NT Server 4.0 is up and running, remember to partition,
format and assign drive letters for the remaining hard drive(s).

6.3.2 Operating Sys tem FixPaks CD-ROM

This CD-ROM contains the vendors’ FixPaks for their operating systems. FixPaks
are provided for Microsoft Windows NT, Novell IntranetWare, and OS/2 Warp.
Use this CD-ROM to load the Microsoft Windows NT Server 4.0 Service Pack 4.
Remember to check your Microsoft Web site for r ecent releases of service packs.
The Web site is

http://www.microso ft.com/.

Using ServerGuide for IBM Netfinity 85

6.4 SoftwareGuide CD-ROM with Windows Terminal Server Edition

When using SoftwareGuide to install Windows NT Server 4.0, Terminal Ser ver
Edition, you must copy the necessary device drivers to diskettes and use these
diskettes during the installation of Windows NT Server 4.0, Terminal Ser ver
Edition. Ter minal Ser ver Edition is installed via its diskettes and CD-ROM (you
must use the shrink-wrap version).

Note: At the time of writing, ServerGuide does not support Windows NT Server

4.0, Terminal Ser ver Edition.
After using HardwareGuide, you should use SoftwareGuide to prepare your

system for the Terminal Ser ver Edition installation. Complete the following steps
to create the necessary diskettes:

1. Place the SoftwareGuide CD-ROM into the server and reboot.

2. At the main menu, click Diskette Factory.

3. Under Select a Category, you should see Your Server selected as the default.
Click > to continue.

4. Check the packages that appear on the screen. In our example, we used an
IBM Netfinity 5000 as our Windows Terminal Ser ver and selected:

• IBM Netfinity 5000 System Diskettes

• IBM ServeRAID Adapter
Click > to continue.

5. In our example, the diskettes we selected to create from the packages were:

• 7800 Family Manager Set Disk 1 of 2

• IBM ServeRAID Device Driver Diskette

• IBM Netfinity S3 Trio V2/GX Device Driver for NT

• IBM Netfinity, PC Sr vr Ethernet Ctr lr and IBM Netfinity 10/100 Fault

Tolerant Dev Drvr.

6. Click > to begin creating your diskettes. After all the diskettes have been
completed, click < four times to return to the ServerGuide exit dialog box and
click OK.

7. Remove the CD-ROM and then click OK.

8. Continue with the installation of Windows NT Server 4.0, Terminal Server
Edition using the diskettes and CD-ROM shipped with the product.

86 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server

Important

During our installation of Windows NT Server 4.0, Terminal Ser ver Edition, at
the Mass Storage Device screen you must install the Adaptec driver for
Windows NT from the 7800 Family Manager Set Disk 1 of 2 and the IBM
ServeRAID Adapter from the IBM ServeRAID Device Driver diskette.

After you complete installing Windows NT Server 4.0, Terminal Server Edition,
you must install Windows NT Server 4.0, Terminal Server Edition Service Pack

4. During the installation of the Service Pack, a dialog box will appear
indicating that a file was detected that was installed by your computer
manufacturer and you will be asked if you would like to overwrite this driver
with a file from the Service Pack.

Do not overwrite this file

. This file is the

Adaptec driver for Windows NT and your IBM system.
The Windows NT Server 4.0, Terminal Ser ver Edition Service Pack 4 can be

downloaded from the Microsoft Web site:

http://www.microso ft.com

Note: The IBM Netfinity S3 Trio V2/GX Device Driver for NT and the IBM Netfinity
PC Srvr Ethernet Ctrlr and IBM Netfinity 10/100 Fault Tolerant Dev Drvr diskettes
were not used during our installation because Windows NT Server 4.0, Terminal
Server Edition automatically detected the video device and network adapter and
installed the correct drivers.

Using ServerGuide for IBM Netfinity 87

88 J.D. Edwards’ OneWorld B73.3 and W indows Terminal Server