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
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 redbook@us.ib 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
Loading...
+ 314 hidden pages