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.
International Technical Support Organization J.D. Edwards’ OneWorld B73.
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix 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 Server Edition, Network Station Manager 3.04, Citrix MetaFrame 1.0, Lotus Domino Go WebServer 4.6.2.2, Microsoft Visual C++ 5.0, Microsoft Internet Information Server 3.0, and Microsoft Access 7.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 1.1 The ITSO J.D.
5.7 Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.1 Netfinity Enterprise Server Guidelines . . . . . . . . . . . . . . . . . . . . . 5.7.2 Sizing Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Hardware and Software Requirements for Windows Terminal Server . . . . . . . . . 68 68 70 76 Chapter 6. Using ServerGuide for IBM Netfinity . . . . . . . . . . . . . . . . . 6.1 ServerGuide Overview. . . . . . . . . . . . .
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. . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . .
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 Server 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.
The Team That Wrote This Redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support 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 Technical Support Organization, Raleigh Center. He conducts residencies and writes redbooks about IBM Netfinity servers and network operating systems.
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.
x J.D. Edwards’ OneWorld B73.
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.
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.
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.
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 Station Client 5842\584205 Figure 2. The ITSO J.D.
Chapter 2. J.D. Edwards’ OneWorld B73.3 J.D. Edwards’ OneWorld 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.
• 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.
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.
• 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.
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 a single code base, to run across a TCP/IP network of multiple server platforms and SQL databases (Oracle, DB2, SQL Server).
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.
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.
12 J.D. Edwards’ OneWorld B73.
Chapter 3. Windows NT Server 4.0, Terminal Server Edition 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.
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 Independent Computing Architecture (ICA). Microsoft’s TSE runs on its own presentation protocol called Remote Desktop Protocol (RDP).
56K WAN Windows Terminal Server Citrix MetaFrame ICA clients Citrix MetaFrame ICA clients OneWorld Enterprise Server Backbone Laser printer Workstation Workstation Figure 3. Network Configuration of TSE and MetaFrame 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.
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.
Figure 6. The IBM Network Station 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.
Network Station Manager features and benefits: Table 1.
Chapter 4. IBM Netfinity 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, scalability, 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.
• Service - IBM’s renowned service and support are with you all the way. Listed are the worldwide available Web sites: Netfinity www.pc.ibm.com/us/netfinity/ - for latest products J.D. Edwards Alliance www.ibm.com/erp/jdedwards/ Server Solutions www.pc.ibm.com/us/solutions/netfinity/index.html ServerProven www.pc.ibm.com/us/compat/ SystemXtra www.pc.ibm.com/us/systemxtra/ TechConnect www.pc.ibm.com/techconnect/ Support www.pc.ibm.com/support/ Accessories www.pc.ibm.
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.
2. IBM Netfinity 5500 and 7000 servers will include a license of Domino Application Server Release 5 (Windows NT version) plus five client licenses. 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.
• 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.
330 Watt Power Supply Easy-to-Access Hard Drives - Up to 72.8GB of internal storage Handle for Easy Transport LED Information Display Multiple Bus Architecture 3 PCI and 3 ISA Slots 32X - 14X CD-ROM Wide Ultra SCSI Adapter Bays for Additional Options 1.44MB Diskette Drive Cooling Fan Up to 500MHz Pentium III Processors 3 DIMM Sockets for a Maximum of 768MB of 100MHz ECC SDRAM Memory Easy-to-Remove Side Panel Figure 7.
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 serviceability 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.
• 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 devices 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.
Standard 350 Watt (175W+175W) Redundant Power Supply, Additional 175 Watt Redundant Power Supply optional Front Bezel Release Lever Light Path Diagnostic Panel Rear Fan Open 5.25" Half-High Drive Bay 5 Slots Total (3xPCI, 2xPCI/ISA) Standard 1.
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 Pentium III processors with 100 Mhz operations to memory to be used in unior two-way processing applications.
• 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.
server’s well-being so that questionable components can be replaced during off hours. 4.4.2 Netfinity 5500 M20 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.
• 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.
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 complex and intensive business markets.
• 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 ports (16550A compatible), one parallel port, two USB ports, one SCSI port, a mouse port, and a keyboard por
• 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
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 server 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.
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.
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 to customers, IT managers and system administrators alike.
• 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.
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. WAN delay is carrier dependent.
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 data1 data5 data9 data2 data6 data10 data3 data7 data11 data4 data8 data12 5842\RAID0 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.
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.
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.
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 Summary 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.
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.
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.
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.
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 b
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.
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.
5.3 Software Considerations In the J.D. Edwards’ OneWorld B73.3.x Solution, the compulsory software choices for the deployment and enterprise servers 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.
• 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.
5.4.1 OneWorld Deployment Server Requirements 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.
Table 4. Database Hardware Requirements for Deployment Server Database Name Minimum Requirements IBM Recommendations 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.
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 Requirements - Deployment Server Description Size in GB Planner and other objects 1.6 GB Database Exports Oracle 1 GB Microsoft SQL Server 1.
5.4.2 OneWorld Enterprise Server Requirements In this section, we list the software and hardware requirements for the OneWorld enterprise server. Table 6. Software and Hardware Requirements for Enterprise Server Components Minimum Requirements IBM Recommendations 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 500 MB for Windows NT 4.0 2 GB for Windows NT 4.
Table 8 helps you calculate the disk space required for One World software on the enterprise server. This can also be found in Chapter 2 of the OneWorld Installation Guide (Windows NT-Based Systems), Release B73.3. Table 8. OneWorld Software Hard Disk Requirements - Enterprise Server Description System Directory 56 Size 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.
Depending on your database (Oracle or SQL Server), use the following tables to calculate the amount of disk space required for your enterprise server database. Base the total on the central objects data sources you require. Table 9.
Table 10. SQL Server Database Hardware Requirements for Enterprise Server Database Name JDEB733 Data Sources SQL Server 7.0 System - B733 Object Librarian - B733 Data Dictionary - B733 machinename - B733 Server Map 330 MB machinename (where machinename is the enterprise server) machinename - logic (where machinename is the enterprise server) JDE_CRPB733 Central Objects - CRPB733 2.
5.4.3 OneWorld Workstation Requirements 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.
Table 12. Database Hardware Requirements for OneWorld Workstation Database Name Minimum Requirements IBM Recommendations SQL Server 7.0 Client Not Available 40 MB RAM 150 MB - hard disk Not Available 150 MB + 16 MB RAM ODBC Driver: Use the versions in Mdac 2.1. Use of the incorrect version 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. 60 J.D. Edwards’ OneWorld B73.
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 OneWorld Installation Guide (Windows NT-Based Systems), Release B73.3 for further details on some of the following points. Review the following to gain an insight on items to consider prior to an installation: 1.
• Temp directories • Install paths • User IDs 5.
the installation plan you need to install OneWorld. 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.
Central Objects The data source for the Central Objects specification tables. 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). However, 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).
• 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 OneWorld 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.
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.
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 Online Now you can access the IBM Netfinity OneWorld sizing tool online via the following URL: http://www.ibm.com/erp/jdedwards/sizings/index.html Remember to answer the questions as carefully as possible so that the IBM Sizing Center may provide you with accurate sizing information.
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.
• 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.
For more information on the ServeRAID-3HB and -3L Ultra2 SCSI adapters, download this PDF from: ftp://ftp.pc.ibm.com/pub/pccbbs/pc_servers/ops6198f.pdf In addition, take a look a IBM Fibre-channel solutions. This information can be obtained at: ftp://ftp.pc.ibm.com/pub/pccbbs/pc_servers/sv6189f.pdf For a complete list of hardware and software requirements on the OneWorld enterprise server, refer to 5.4.2, “OneWorld Enterprise Server Requirements” on page 55. 5.7.
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.
Example of Page 3 Sizing Questionnaire OneWorld Company Name: Street Address: Street Address: City, State Zip: Country: Contact Person: Phone Number: Fax Number: Company description: (distribution, mfg, etc.) IBM Client Rep: Phone Number: IBM Product Specialist: Phone Number: IBM OMSYS Number: Business Partner Company Name: Contact Name: Phone Number: Fax Number: J.D.
Example of Page 4 Company Wide Users Application OneWorld Active Users World/World Vision Active Users* Total Logged On Users** Financial Distribution Manufacturing Total 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.
Example of Page 4 - Continued Conference Room Pilot and Development Requirements: Will the Conference Room Pilot machine become your production machine? Yes/No Peak active users on the CRP? World _________ OneWorld ________ Installation date for CRP? Will you require a separate development or test machine? If Yes, for how many users? Yes/No OneWorld ____World ____ Additional Information for Production Environment: Is coexistence with WorldSoftware a requirement? Yes/No What hardware do you have no
Example of Page 5 System Requirements for Production: Batch processing during online time (%) Disk Mirroring or RAID 5 required? Mirroring / RAID 5 High availability configuration required, such as: HACMP, MIMIX, OMS, or MSCS? HACMP / MIMIX / OMS MSCS If yes, percentage of total workload that needs to run in failover mode? Backup Media Required (4mm/8mm/3590/3570/DLT) Explanations of Some of the Above Questions: Conference Room Pilot Requirements: Customers often start with a conference room pilot fo
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 Terminal Server Edition Components Minimum Requirements IBM JDE Recommendations CPU Two-way Pentium Class Intel server Dual Intel Pentium III 400 MHz Note: For a TSE server supporting 15 or fewer workstations at least two processors.
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 you use Microsoft SQL Server. Please use your current ODBC drivers for the Terminal Server and use the workaround located in 9.11.1, “Instructions for MDAC2.1 and TSE” on page 317.
78 J.D. Edwards’ OneWorld B73.
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.
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.
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.
• 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.
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.
6.3.1 Installing Windows NT Server 4.0 Using the SoftwareGuide 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.
At this point, ensure that you have 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 by the ServerGuide. Click on the > button to continue with the installation. 8. Select FAT as the type of partition to be created.
6.4 SoftwareGuide CD-ROM with Windows Terminal Server Edition When using SoftwareGuide to install Windows NT Server 4.0, Terminal Server Edition, you must copy the necessary device drivers to diskettes and use these diskettes during the installation of Windows NT Server 4.0, Terminal Server Edition. Terminal Server 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.
Important During our installation of Windows NT Server 4.0, Terminal Server 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.
88 J.D. Edwards’ OneWorld B73.
Chapter 7. Implementing Oracle8 and J.D. Edwards’ OneWorld This chapter will discuss the necessary procedures for installing and configuring Oracle8 Enterprise Edition for Windows NT and J.D. Edwards’ OneWorld B73.3 applications on a Windows NT 4.0 platform. The server used in these processes are IBM’s Netfinity 5500 systems. Before installing Oracle and OneWorld, IBM’s ServerGuide (included with all new IBM Netfinity servers) was used to configure the Netfinity servers.
4. Select Maximize throughput for Network Applications. Do not reboot when prompted. 5. Return to Control Panel and select System. 6. Select the Performance tab. 7. Set the Application Performance Boost for Foreground Applications to 50% (slide set at halfway mark). 8. Click Change and modify initial paging file size to the recommended size. Click Set and OK. 9. The deployment server can now be shutdown and restarted. 4. Install Service Pack 4 or later for Windows NT Server 4.0. 5.
Figure 16. Oracle8 Installation Settings Screen 2. Complete the following fields: • Company Name = Input company name, for example, type IBM. • Name = DEFAULT_HOME • Location = The drive path where Oracle8 will be installed, for example, type d:\orant. • Language = English 3. Click OK to continue. 4. Select Oracle8 Client. 5. Select Database Administrator. This will install the database administration programs. Accept all default parameters. 6.
• Internet Service Manager • FTP Service • ODBC Driver and Administration 3. Click Close to go back to Windows NT desktop. 4. To configure FTP, select Start > Programs > Microsoft Internet Server > Internet Service Manager. 5. Right-click the FTP service with your computer name, and choose Service Properties. 6. Make sure Allow Anonymous Connections is not chosen. 7. Read the warning message that is displayed and click Yes. 8. On the FTP Service Properties, click the Directories tab, then Add. 9.
3. After Windows NT is installed, you need to change a few parameters for tuning purposes: 1. From your Windows NT desktop, select Start > Settings > Control Panel. 2. Double-click Network and select the Services tab. 3. Double-click the Server icon. 4. Select Maximize throughput for Network Applications. You will be prompted to reboot. Do not reboot at this time. 5. Return to Control Panel and select System. 6. Select the Performance tab. 7.
2. Place your Oracle8 Enterprise Edition for Windows NT in the CD-ROM drive. Oracle Install will launch automatically when the CD-ROM is inserted. If it does not, double-click the CD-ROM icon under My Computer. You will see a screen similar to Figure 17: Figure 17. Oracle8 Installation Screen 3. Select Begin Installation. You will see a screen similar to Figure 18: . Figure 18. Oracle8 Installation Settings Screen 4.
5. Click OK to continue. You will see a screen similar to Figure 19: Figure 19. Installation Options Screen 6. Select Oracle8 Enterprise Edition. You will see a screen similar to Figure 20: Figure 20. Cartridges and Options Selection Screen 7. Do not select any cartridges. Click OK to continue. You will see a screen similar to Figure 21: Figure 21. Starter Database Configuration Screen 8. At the Starter Database Configuration screen, select Custom Configuration and click OK to continue.
Figure 22. Legato Storage Manager Screen 9. In this example, the Legato Storage Manager was not used. Select No to continue. You will see a screen similar to Figure 23: . Figure 23. Oracle Documentation Screen 10.Select CD-ROM and click OK to view your documentation files from the CD-ROM. You will see a screen similar to Figure 24: Figure 24. Installation Completed Screen 11.After the components are installed, click No to continue. 12.You are now allowed to create and customize your database.
Figure 25. Oracle Database Assistant Screen 13.No cartridges were selected at this screen. Click Next to continue. You will see a screen similar to Figure 26: Figure 26. Oracle Database Assistant Screen Select Medium as the size for your database. Take a moment to view the character set for your database by clicking Change Character Set. Your character should match that of J.D. Edwards’ OneWorld language you selected Implementing Oracle8 and J.D.
(see Appendix K-1 of OneWorld Installation Guide (Windows NT-Based Systems), Release B73.3. For our example, using OneWorld B73.3 the character set required is WE_ISO88591 for U.S. English. Click Next to continue. You will see a screen similar to Figure 27 on page 98. Figure 27. Oracle Database Assistant Screen 14.In the fields, type the following: • Database Name = orc1 (this name was used for this example) • SID = orc1 • Initialization Filename = d:\orant\database\initorc1.
Table 15. OneWorld B73.3 Minimum System Tablespace Requirements for Oracle8 Tablespace Name Minimum Size (MB) SYSTEM 40 ROLLBACK_DATA 500 TEMPORARY_DATA 350 (MAX extents set to unlimited) USER_DATA 15 If you created the tablespaces with different names from those described above, you might need to modify some scripts described in the procedures that follow to reference the correct names. Figure 28. Oracle Database Assistant Screen 16.
Figure 29. Oracle Database Assistant Screen 17.At this screen, you will define the minimum system tablespace requirements for OneWorld B73.3. Under the SYSTEM tab, verify and modify the following fields: • Name = SYSTEM • Size (MB) = 40 18.Click the USER tab. You will see a screen similar to Figure 30 on page 101. Note: The tablespace requirements may be different for OneWorld versions, B73.3 and B73.3.1. Ensure that you’ve obtained the correct values for the version of OneWorld you are using. 100 J.D.
Figure 30. Oracle Database Assistant Screen 19.Under the USER tab in the Name field, type USER_DATA. Click the arrow buttons to reflect 15 in the Size (MB) field. Next, click the ROLLBACK tab. You will see a screen similar to Figure 31: Figure 31. Oracle Database Assistant Screen Implementing Oracle8 and J.D.
20.Under the ROLLBACK tab in the Name field, type ROLLBACK_DATA. Click the arrow buttons to reflect 500 in the Size (MB) field. Next, click the TEMPORARY tab. You will see a screen similar to Figure 32 on page 102. Figure 32. Oracle Database Assistant Screen 21.Under the TEMPORARY tab in the Name field, type TEMPORARY_DATA. Click the arrow buttons to reflect 350 in the Size (MB) field. Under Extents, check the Unlimited box. Click Next to continue. You will see a screen similar to Figure 33: Figure 33.
22.Accept the defaults for the Redo logs and click Next. You will see a screen similar to Figure 34 on page 103. Figure 34. Oracle Database Assistant Screen 23.Accept the defaults for archiving, unless you want to enable the archiving of the Redo logs. Click Next to continue. You will see a screen similar to Figure 35. Note: In a production environment, you will want to use archiving for recovery purposes, but for our example, we will leave it turned off. This can be changed later. Figure 35.
24.For OneWorld, your default database should have a block size of 4K to 8K depending upon your disk space. In the Block Size (Bytes) field, use the arrow buttons to select 4096. Click Next to continue. You will see a screen similar to Figure 36: Figure 36. Oracle Database Assistant Screen 25.Click Next to continue. You will see a screen similar to Figure 37: Figure 37. Oracle Database Assistant Screen 26.After modifying the parameters to customize your database, you are now ready to create it.
28.The name of the database will be orc1. The system identifier for the database will be orc1. Click OK to continue. 29.Click Yes to add the SID name (orc1) to your Listener.ora file. You will see a screen similar to Figure 38: Figure 38. Creating Database Progress Screen This process will take several minutes to complete. Once the process has completed you will see a screen similar to Figure 39: Figure 39. DBCreate Assistant Alert Screen 30.
7.2.2 Verify Setup of Listener.ora and Tnsnames.ora Files You need to check and make sure the Listener.ora and the Tnsnames.ora files are set up correctly on the enterprise server, where the database resides. This is done to ensure that the Oracle clients can communicate with the database. The Listener.ora file lists the names and addresses of all of the listener processes on the enterprise server and the instances it supports. The Tnsnames.ora contains a list of connect descriptors.
# D:\ORANT\NET80\ADMIN\TNSNAMES.ORA Configuration File:D:\orant\net80\admin\tnsnames.ora # Generated by Oracle Net8 Assistant ORC1.WORLD = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(Key = ORC1)) (CONNECT_DATA = (SID = ORC1)) ) # D:\ORANT\NET80\ADMIN\LISTENER.ORA Configuration File:D:\orant\net80\admin\listener.
communicate with the database named orc1 on the enterprise server. The host IP address is the IP address of the machine where the database actually resides. 1. From the deployment server, click Start > Programs > Oracle for Windows NT. 2. Select Oracle Net8 Assistant. 3. Highlight Service Name. 4. At the top of the menu click Edit and select Create. 5. Service Name = For this example, ORC1. Click Next. 6. Select TCP/IP (Internet Protocol) and click Next. 7. IPC Key Value = ORC1. Click Next. 8.
SID of the database shown in Figure 42) on the deployment server. You should get a response back saying that the attempt to contact the host was OK. 7.3 Installing and Configuring J.D. Edwards’ OneWorld B73.3 In this section, you will use the Installation Planner to create your plan and deploy OneWorld to the enterprise server(s) and the client workstations. During this installation we will install the OneWorld B73.3 Setup software on your deployment server. If necessary, refer to J.D.
• Authorization Code To continue with your installation, you will need to obtain an authorization code. You must call J.D. Edwards at 303-334-4000 (ask for Contracts). You will need to provide your J.D. Edwards’ Address Book number and the serial number that appears on the screen, the expiration data, and the number of licenses. Note: You may be instructed to leave a telephone number and someone from contracts will give you a call back.
Figure 45. OneWorld Congratulations Screen 10.Select Install Adobe Acrobat Reader 3.01 and click Close to continue. After the installation of the first setup CD-ROM has completed, you are not prompted to insert the second setup CD-ROM. Note: If you installed Adobe Acrobat Reader and Internet Explorer earlier during the installation process, do not select these programs for installation again. 11.After the first setup CD-ROM has completed loading its files, insert the second setup CD-ROM and run Setup.exe.
Figure 46. OneWorld Setup Options Screen On OneWorld Setup Options, choose the appropriate server database (either SQL Server or Oracle) to load its export files and scripts. For this example, select Oracle. In addition, click Change Directory to install the files on the d:\ drive. Click Next to continue. Note: The components you need for further building your database are copied into the subdirectory B733\DATABASE\EXPORTS. 12.
To prepare your rollback scripts, go to your enterprise server and complete the following steps: 1. From the enterprise server, map a network driver to the deployment server’s shared drive B733. For our example, our drive is x:\. 2. Make a backup copy of each of the scripts: • rbs_redo.nt • crtabsp.nt • crdbausr.nt • crusrs.nt These scripts reside on the deployment server in the \OneWorld\B733\Database subdirectory. 3. You will run the scripts from your Windows NT desktop using Oracle’s SQL Plus 8.0.
• From the command prompt, type svrmgr30 and press Enter. • Type connect internal and press Enter. • Type in the internal password you chose when installing Oracle (for our example, oneworld) and press Enter. • Type shutdown and press Enter. • Type startup and press Enter. • Log in to SQL Plus 8.0 again. 7. Before running crtabsp.nt, you must read the information in the label box and follow its instructions. To run crtabsp.nt, type and execute the following example: SQL> @x:\database\crtabsp.
appropriate user IDs, passwords, and other variables, then run the batch files to load the tables. The following steps must be performed on the deployment server: 1. Edit the batch files LOADDEVL.BAT, LOADPROD.BAT, LOADPRST.BAT, and LOADCRP.BAT in the \OneWorld\B733\Database\Exports\Oracle\NT directory to reflect your environment by completing steps 2 - 4. Note: For Oracle8, you must change the references from imp73 to imp80, and from plus33 to plus80. 2. In the JDESET.
In this section, you will provide information such as database type, enterprise server, operating system platform, install path, etc. For this example, the installation plan will be defined in the following procedures: 1. At your Windows NT desktop on the deployment server, launch OneWorld. Click Programs > OneWorld > OneWorld Explorer. You will see a screen similar to Figure 47: Figure 47. OneWorld Sign On Screen 2. Sign on to OneWorld as JDE (password, JDE) using the planner environment, JDEPLAN.
Figure 48. Work with Installation Plans Screen 4. On the Work with Installation Plans screen, click Add. You will see a screen similar to Figure 49: Figure 49. Custom Installation Plan - (Installation Planner) Screen 5. In Figure 49, complete the fields and selections of the following: • Name = Type the name of your installation plan (for example, B733INSTALL). • Description = Type the description of your installation plan. • Status = select 10. • Click Install. Implementing Oracle8 and J.D.
• Verify that the Coexistent with World Software box is not checked. 6. Click OK to continue. 7. You will be asked to define a location or select an existing location. Click OK to define a new plan. You will see a screen similar to Figure 50: Figure 50. Location Revisions Screen 8. Enter the following information for Location Revision: • Location = Enter the name or place that applies with this plan. For our example, we chose ITSO.
Figure 51. Deployment Server Revisions Screen 11.Complete the following information for the Deployment Server Revisions: • Machine Name = Name of your deployment server; for example, IBM5500DS. • Description = Enter a long description for the machine; for example, Primary Deployment Server. • Release = OneWorld release number you are installing, B733. • Primary Deployment Server = 1. • Server Shared Path= \B733. 12.If you are not adding another deployment server, click No to continue.
Figure 53. Enterprise Server Revisions Screen 14.On the Enterprise Server Revisions screen, complete the following fields: • Machine Name - The name of your primary enterprise server; for example, IBM5500ES. • Description - Enter a description of your machine name; for example, Enterprise Server. • Release = B733. • Host Type = Click the flashlight button and select code 50 (Intel NT). • Database Type = Click on the flashlight button and select O (ORACLE).
Figure 54. Data Source Setup Screen 17.From the action bar, click Form and select Advanced. You will see a screen similar to Figure 55 on page 121. Note: In the Connect String field, this is the same name as the database System Identifier (SID) used in the Tnsnames.ora file (example, orc1). Figure 55. Data Source Revisions for B733 Server Map Screen 18.Make the appropriate change in the DLL Name field. Implementing Oracle8 and J.D.
• Change JDBOCI73.DLL to JDBOCI80.DLL. • For B733 - Server Map, put a check mark in the OCM Data Source check box. 19.Click OK and then click Next if you are setting up another data source. 20.If you are finished setting up the data source, then click Cancel to continue. 21.OneWorld prompts if you want to add another enterprise server. For this example, click NO. You will see a screen similar to Figure 57 on page 123. Figure 56. Machine/Server Types Screen 22.
Figure 57. Data Source Setup for System - B733 Screen 23.Click Form > Advanced. You will see a screen similar to Figure 58 on page 123. Note: In the Connect String field, this is the same name as the database System Identifier (SID) used in the Tnsnames.ora file (example, orc1). Figure 58. Data Source Revisions for System - B733 Screen 24.Make the appropriate change in the DLL Name field. Implementing Oracle8 and J.D.
• Change JDBOCI73.DLL to JDBOCI80.DLL. • For System - B733, put a check mark in the OCM Data Source check box. 25.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 59. Figure 59. Data Source Setup for Object Librarian - B733 Screen 26.Review the fields to ensure the correct data is entered. From the action bar, click Form > Advanced. You will see a screen similar to Figure 60 on page 125. 124 J.D. Edwards’ OneWorld B73.
Figure 60. Data Source Revisions for Object Librarian - B733 Screen 27.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 28.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 61 on page 126. Implementing Oracle8 and J.D.
Figure 61. Data Source Setup for Data Dictionary - B733 Screen 29.From the action bar, click Form > Advanced. You will see a screen similar to Figure 62: Figure 62. Data Source Revisions for Data Dictionary - B733 Screen 126 J.D. Edwards’ OneWorld B73.
30.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 31.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 63: Figure 63. Environment Selection Screen 32.On the Environment Selection screen, both boxes are marked with a check as the default. For our example, we did not mark the check boxes so we could make our own selection of environments and the data to load. Click OK to continue.
Figure 64. Select Environments Screen 33.At this screen, you will need to select the environments that you want to define. In this example, PRD733 and CRP733 are chosen. However, you must choose and define each environment one at a time. Double-click PRD733. You will see a screen similar to Figure 65 on page 129. 128 J.D. Edwards’ OneWorld B73.
Figure 65. Data Load Parameters Screen 34.Select Load Production Data and then click OK. 35.OneWorld asks if you want to set up data sources for each environment or take the defaults that J.D. Edwards sets up. For our example, we chose to set up each data source. Click OK. You will see a screen similar to Figure 66 on page 130. Implementing Oracle8 and J.D.
. Figure 66. Data Source Setup for Control Tables - Prod (Production) Screen 36.Review the accuracy of the Control Tables data source. From the action bar, click Form > Advanced. Figure 67. Data Source Revisions for Control Tables - Prod (Production) Screen 130 J.D. Edwards’ OneWorld B73.
37.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 38.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 67: Figure 68. Data Source Setup for Central Objects - PRODB733 Screen 39.From the action bar, click Form > Advanced. You will see a screen similar to Figure 69 on page 132. Implementing Oracle8 and J.D.
Figure 69. Data Source Revisions for Central Objects - PRODB733 Screen 40.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 41.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 70 on page 133. 132 J.D. Edwards’ OneWorld B73.
Figure 70. Data Source Setup for Business Data - PROD Screen 42.Here you will set up the data source for your business data. From the action bar, click Form > Advanced. You will see a screen similar to Figure 71: Figure 71. Data Source Revisions for Business Data - PROD Screen Implementing Oracle8 and J.D.
43.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 44.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 72: Figure 72. Data Source Setup for Versions - PRODB733 Screen 45.From the action bar, click Form > Advanced. You will see a screen similar to Figure 73 on page 135. 134 J.D. Edwards’ OneWorld B73.
Figure 73. Data Source Revisions for Versions - PRODB733 Screen 46.Make the appropriate change in the DLL Name field. Change JDBOCI73.DLL to JDBOCI80.DLL. 47.Click OK and then click Next to set up the next data source. You will see a screen similar to Figure 74 on page 136. Implementing Oracle8 and J.D.
Figure 74. Select Environments Screen 48.Repeat the same steps for CRP733 as you did for PRD733. Double-click CRP733. Remember to change the DLLs from 73 to 80. When you reach this screen again and CRP733 is selected as shown in Figure 74, click Close to continue. 49.OneWorld prompts you if you want to set up another location. For our example, click No. You will see a screen similar to Figure 75 on page 137. 136 J.D. Edwards’ OneWorld B73.
Figure 75. Congratulations Screen 50.Click OK to continue. 7.3.3 Validate the Plan In this section, you will run the plan validation report to ensure that the plan is correct and ready for installation. 1. Run the plan validation report. From your OneWorld Explorer interface, type GH961 in the Fast Path field and press Enter to go to the System Installation Tools menu. 2. Double-click Plan Validation. You will see a screen similar to Figure 76 on page 138. Implementing Oracle8 and J.D.
Figure 76. Work With Batch Versions - Available Versions Screen 3. Highlight the grid record for Version XJDE0001, then click Select. You will see a screen similar to Figure 77: Figure 77. Version Prompting Screen 138 J.D. Edwards’ OneWorld B73.
4. Choose the Data Selection box, then click Submit. You will see a screen similar to Figure 78: . Figure 78. Data Selection Screen 5. At this screen, you will set criteria design information. In the column, Right operand, double-click "Plan Name" and select Literary. Type in your plan name, for example, B733INSTALL and click OK. You will see a screen similar to Figure 79: Figure 79. Processing Options Screen 6. On the Extra Info tab on Processing Options, accept the defaults and click OK. 7.
Figure 80. Report Output Destination Screen 8. Choose On Screen to view your validation report at your display. Click OK. Adobe’s Acrobat Reader launches the Installation Planner Validation Report PDF. 9. Review the report and ensure your information is correct. Exit the Acrobat Reader and select Close to exit Validation. Figure 81. Custom Installation Plan (Work with Installation Plans) Screen 10.On Work with Installation Plans, click Expand to review the entire plan you created.
Note: If the Data Source administrator appears, requesting that you create a data source, click Cancel to continue. You should have created all of your data sources earlier during the installation planner process. Figure 82. Work with Installation Plans Screen 2. A message appears to let you know that the Release Master has completed. Click OK and then click Close. 7.3.5 Running Installation Workbench The Installation Workbench runs the plan you created.
Figure 83. Work with Installation Plan Screen 4. At the Work with Installation Plan screen, double-click the Plan Name, B733INSTALL record. You will see a screen similar to Figure 84: Figure 84. Location Workbench Screen 142 J.D. Edwards’ OneWorld B73.
5. Verify that this form lists all the necessary locations for your plan. From the action bar click Form > Configure (the Workbench updates your Detail Status to 60 and changes the Status Description from Validated to Installed). 6. Click Next to continue. You will see a screen similar to Figure 85: Figure 85. Data Source Workbench Screen 7. At the Data Source Workbench screen, scroll down the list of items and verify that the information presented lists all the necessary data sources for our plan. 8.
Figure 86. Environment Workbench Screen 10.On the Environment Workbench screen, verify the environment you selected and each environment’s associated parameters for correct values. OneWorld includes the deployment server environment in this list. Note: The environment configuration phrase takes approximately two hours or more per environment to run. You can let Environment Workbench run overnight, but do not lock the workstation or Environment Workbench stops after loading the first environment. 11.
Figure 87. Machine Workbench Screen 13.Review the Machine Workbench for the correct parameters. At the action bar, click Form > Configure (this will update your Detail Status to 60 and changes the Status Description from Validated to Installed). 14.Click Next to configure your packages. You will see a screen similar to Figure 88 on page 146. Implementing Oracle8 and J.D.
Figure 88. Package Workbench Screen 15.On the Package Workbench screen, review the Conference Room Pilot (CRP) and Production (PROD) packages. From the action bar, click Form > Configure. 16.Click Next to finish the plan. From the action bar, click Form > Finish. 7.3.6 Setting Up and Verifying the Hosts File If no Domain Naming Service is defined on your network, you must set up the hosts file for each machine.
7.4 Installing OneWorld on the Enterprise Server In this section, you will use the CD-ROM software OneWorld Release B73.3 Windows NT Intel, 1 of 1 to install OneWorld on the enterprise server. This installation process copies the OneWorld system and the path code files directly from the CD-ROM to the enterprise server. Complete the following steps to install the enterprise server software: 1. Log on to the enterprise server with system administrator privileges. 2.
Figure 89. OneWorld B733 NT Enterprise Server Setup Screen 8. Click Next to continue. You will see a screen similar to Figure 90: Figure 90. Deployment Path Dialog Screen 9. At the Deployment Path Dialog screen, type the path on the deployment server where the base OneWorld installation exists. In this example, we typed x:\OneWorld\B733. Click Next to continue. You will see a screen similar to Figure 91 on page 149. 148 J.D. Edwards’ OneWorld B73.
Figure 91. Enterprise Server Setup Type Screen 10.Select Custom for your setup type. In the Target Folder field of the Setup Type screen, type the directory where you want the files to be installed on your enterprise server. For this example, we typed D:\oneWorld\ddp\b733. Click Next to continue. You will see a screen similar to Figure 92 on page 150. Note: Under Space Available the software package does not recognize the correct amount of space that is available. Do not be alarmed.
Figure 92. Enterprise Server Setup Component Selection Screen 11.At the Component Selection screen, you may want to select all the components that apply to your OneWorld setup. In this example, prodb733, crpb733 and system were selected. Click Finish. 12.When the enterprise server setup completes copying its files, the OneWorld B733 NT Enterprise Server Setup screen will notify you that the installation was successful. 13.Click OK to continue. 7.4.
The porttest program initializes a user and an environment (assuming that OneWorld is installed and configured correctly). The program should display messages indicating the selection of records out of a OneWorld table. If it does not, review the jde.log_### that was specified in the JDE.INI file on the enterprise server. If porttest fails to run, see the Host Services Checklist in the reference section of the J.D. Edwards’ OneWorld Installation Guide (Windows NT-Based Systems), Release B73.3. 3.
7.4.1.3 Start the OneWorld Enterprise Server To start the OneWorld enterprise server, perform the following steps: 1. From the Windows NT interface, click Start > Settings > Control Panel. Select the Services icon. 2. Choose the JDE B733 Network services and click Start. 3. Next, choose the JDE B733 Queue services and click Start. Note: You must always start Network, then Queue services.
Figure 94. Work With Paper Types (Paper Type Revisions) Screen 3. In the B73.3 release of OneWorld, the only valid paper types are the ones that are pre-defined User Defined Codes (UDCs): LETTER, LEGAL, and A4. In this section, adding a paper type will not be necessary, however, the basic steps are shown below. For Paper Type Revisions, enter the following fields: • Paper Type = Select the paper type that you are going to use. • Paper Height = Specify the height of the paper for this paper type.
Figure 95. Work With Physical Printers (Physical Printer Revisions) Screen 3. Complete the required fields: • Physical Printer = Name of printer that exists on you network: In Windows NT, the format is \\enterprise server name\printer name. For our example, we used \\IBM5500ES\IBM40375. • Capability Type = Select the type of capability that are required for OneWorld to print properly. For this example, H (host) is chosen first.
7.5.4 Adding a Logical Printer 1. On the Printers (GH9013), choose Work with Logical Printers (P98616). 2. On Work with Logical Printers, click Add. You will see a screen similar to Figure 96: Figure 96. Work With Logical Printers (Logical Printer Revisions) Screen 3. Complete the following fields for Logical Printer Revisions: • Logical Printer = Name of printer where you will send your print job. • Description = Long description of your printer. • Physical Printer = Location of your printer.
Figure 97. Work With Default Printers (Default Logical Printer Revisions) Screen 3. Complete the required fields: • User ID = *PUBLIC • Environment Name = *ALL • Host = enterprise server name • Printer Name = Name of your printer • Object Status = AV (Active) 4. Once completed, Click OK to continue. 7.6 Setting User and Group Profiles J.D. Edwards recommends you set up one or two users to perform the installation process.
assignments available to all of the individual users belonging to that group. In our example, we will create a user and assign that user to a group. However, the user we create will have packages and environments assigned directly to its profile. Profiles define certain setup and display features, such as language, date format, and country code. Although we can set up numerous users (clients) for OneWorld, our example demonstrates a basic overview of setting a group.
Figure 99. User Profiles (User Profile Revisions) Screen 5. To create a group profile: • In the User ID field, type a group name, such as ACCOUNTING.. • In the User Class/Group field, type *GROUP. 6. Click OK. 7. Click Add to create a new user. You will see a screen similar to Figure 100 on page 159. 158 J.D. Edwards’ OneWorld B73.
Figure 100. User Profiles (User Profile Revisions) Screen 8. Complete the following fields: • In the User ID field, type the individual’s user ID. For our example, we used LEIUSER1. • In the User Class/Group field, type the name of the group to which the user belongs, such as ACCOUNTING or use the flashlight button to search for this group. Leave this field blank if the user does not belong to a group. Note: The flashlight button appears in the field that is selected. • Enter an address book number. 9.
. Figure 101. User Profile (Work With User Profiles) Screen 3. Choose an existing user ID. For our example, we chose LEIUSER1. This can be an individual or group profile. (See Figure 101.) 4. From the action bar, select Row > Deployment. 5. On the User Deployment Preferences screen, complete the following fields: • Deployment Location = (We left this field blank for this example). Note: You can have the workstation installation pull packages from a machine other than your deployment server.
7.6.3 Assigning Environments to a Profile When starting OneWorld, you can assign more than one environment to each user or group from which any user or group can choose. If users do not have environments of their own, they can choose from the ones assigned to their group. To assign environments, perform the following steps: 1. From your OneWorld work space access the Advanced Operations menu (GH9011), choose User Profiles. 2. On Work With User Profiles, click Find. 3. Choose a profile.
7.7 Installing Oracle8 Client Before you begin with the installation of OneWorld client on the workstation, you must install Oracle8 Client: 1. Insert the Oracle8 CD-ROM and select Begin Installation. You will see a screen similar to Figure 103 on page 162. Figure 103. Oracle8 Client Installation Settings Screen 2.
Figure 105. Oracle8 Client Configuration Screen 5. Select Application User and click OK. 6. You are now asked if you want to leave the Oracle documentation on the CD-ROM, or install it to disk (approximately 80 MB required). You will also have to have an HTML viewer installed to access the documentation. For this example, we chose to leave it on the CD-ROM for now. 7. Setup now begins installing the software and creating the icons. 7.
Note: You can resynchronize replicated data by changing the ForcedSync value in the [REPLICATION] section from 0 to 1. When client workstations are installed, this value is set to 0, meaning you do not want to resynchronize data. 7.8.2 Modify the Setup.inf File on the Deployment Server In this section, Setup.inf will be modified to specify the default environment. Note: You do not need to perform this task if you want the default environment to be Production (PRD733).
Figure 106. OneWorld Client Install Screen 3. Read the licensing terms and click Continue. You will see a screen similar to Figure 107. The OneWorld installation process verifies that several of the system .DLLs are current. If they are not current, you receive a message to reboot your system. When you reboot, the system updates the .DLLs in your Windows directories. To install OneWorld, you must begin again with the first step in this task. Figure 107. OneWorld Sign-On (Installation) Screen 4.
Click the option to Install Development Objects if you are a OneWorld developer. This option appears only if you have a compiler loaded on your workstation. You can also change the drive where OneWorld is installed, but the directory path is always b7. 6. To initialize the package, click Next. Note: This could run for several minutes. The client installation displays two status bars. The first shows the status of the installation.
Chapter 8. Implementing Microsoft SQL Server 7.0 and OneWorld In this chapter, we will set up the deployment server for OneWorld. This will allow us to create and maintain installation plans, and deploy OneWorld code to the enterprise server and client workstations. Our configuration includes Microsoft SQL Server 7.0 for Windows NT 4.0 and J.D. Edwards’ OneWorld B73.3. The servers used in this process were IBM’s Netfinity 5500 systems.
3. Double-click the Server process. 4. Select Maximize throughput for Network Applications. Do not reboot when prompted. 5. Return to Control Panel and select System. 6. Select the Performance Tab. 7. Set the Application Performance Boost for Foreground Applications to 50% (slide set at halfway mark). 8. Click Change and modify initial paging file size to the recommended size. Click Set and OK. 9. The deployment server can now be shut down and restarted. 4.
2. Select Install SQL Server 7.0 Prerequisites (shown in Figure 108 on page 168). Next, select Windows NT 4.0. You will see a screen similar to Figure 109: Figure 109. SQL Server 7.0 Prerequisites Screen 3. Select Launch Setup Wizard. This will install Internet Explorer 4.01 SP 1. 4. Click Next. Choose Standard Installation and accept the defaults. When the process is finished you must restart the computer and run the Microsoft SQL Server 7.0 CD-ROM again. Implementing Microsoft SQL Server 7.
Figure 110. SQL Server 7.0 Selection Screen 5. This time, select Install SQL Server 7.0 Components. You will see a screen similar to Figure 111: Figure 111. SQL Server 7.0 Components Selection Screen 170 J.D. Edwards’ OneWorld B73.
6. Select Database Server - Standard Edition. You will see a screen similar to Figure 112: Figure 112. Select Install Method Screen 7. Select Local Install - Install to the Local Machine. Click Next twice. 8. At the Software License Agreement screen, select Yes. 9. At the User Information screen, enter the appropriate information for User and Company. For our example, we entered IBM in both fields. Click Next and you will see a screen similar to Figure 113: Figure 113. Setup Type Screen 10.
Note: In this step, we changed the drive letter for the SQL Client 7.0 installation to match that of the SQL Server 7.0 software installation on the enterprise server. For the SQL Server 7.0 software installation on the enterprise server, you must ensure you have plenty of disk space available when OneWorld script files are run to create databases, create database logins and users, and load central objects for SQL Server 7.0.
Figure 115. SQL Server Client Network Utility Screen 15.Click Add and you will see a screen similar to Figure 116: Figure 116. Add Network Utility Configuration Screen 16.In the Network libraries select TCP/IP protocol. In the Server alias field, enter the name of your enterprise server (for example, IBM5500ES). 17.Click OK to continue and you will see a screen similar to Figure 117 on page 174. Implementing Microsoft SQL Server 7.
Figure 117. Server Client Network Utility Screen 18.Click OK. 8. From the Windows NT desktop, access the User Manager for Domains under Administrative Tools (Common) to create user ID JDE and assign it the password JDE. Give this user administrative rights. 9. Log off and log on with the JDE ID. Note: After logging back on, you may be required to complete the installation of the Service Processor DLL file and device driver. Press Enter twice. 10.
9. Configure the Directory Properties tab by adding the drive where you will install OneWorld by filling out the following fields: 1. Directory - Type the drive where OneWorld will be installed (example, d:). 2. Alias Field - Type the drive location preceded by a slash (for example, /d:). 3. Under Access, select read and write options. 4. Click OK. 5. Under Directory Listing Style select MS-DOS and click OK. 11.
7. Set the Application Performance Boost for Foreground Applications to 50% (slide set at halfway mark). 8. Click Change and modify initial paging file size to the recommended size. Click Set and OK. 9. At this point, check that your screen resolution is set to at least 256 colors or higher. 10.The enterprise server can now be shut down and restarted. 4. Install Microsoft Visual C++ 5.0. Choose Professional Edition. The path used for this installation is: C:\Msdev\DevStudio\VC.
Figure 118. SQL Server 7.0 Selection Screen 3. Select Install SQL Server 7.0 Prerequisites and you will see a screen similar to Figure 119. Figure 119. SQL Server 7.0 Prerequisites Screen Implementing Microsoft SQL Server 7.
4. Select Launch Setup Wizard. This will install Internet Explorer 4.01 SP 1. When the process is finished you must restart the computer. 5. Again, you must run the installation program from the SQL Server 7.0 CD-ROM. Figure 120. SQL Server Selection Screen 6. Select Install SQL Server 7.0 Components. You will see a screen similar to Figure 121. 178 J.D. Edwards’ OneWorld B73.
Figure 121. SQL Server 7.0 Components Selection Screen 7. Select Database Server - Standard Edition. You will see a screen similar to Figure 122: Figure 122. Select Install Method Screen 8. Select Local Install - Install to the Local Machine. Click Next twice and continue. 9. Accept the licensing agreement. Click Yes. 10.At the User Information screen, enter the appropriate information for user and company name. Implementing Microsoft SQL Server 7.
Figure 123. Setup Type Screen 11.Select Custom configuration and click Next to continue. You will see a screen similar to Figure 124 on page 180. Note: In this step, we changed the drive letter to reflect where we intend to install the SQL Server 7.0 software on the enterprise server. You must ensure you have plenty of disk space available when OneWorld script files are run to create databases, create database logins and users, and load central objects for SQL Server 7.0. Ensure SQL Server 7.
Figure 125. Character Set/Sort Order/Unicode Collation Screen 13.Accept all default parameters. Click Next to continue. You will see a screen similar to Figure 126. Figure 126. Network Libraries Screen 14.Select TCP/IP Sockets; the port number is 1433. Click Next to continue. You will see a screen similar to Figure 127 on page 182. Implementing Microsoft SQL Server 7.
Figure 127. Services Accounts Screen 15.In the following fields, choose: • Use the same account for each service. Auto start SQL Server Service. • Use a Domain User account and press Enter • Username: JDE • Password: JDE • Domain: The name of your domain. For this example, ONEWORLD. 16.Click Next to continue. 17.Choose your licensing mode and click Continue to complete loading the software. Figure 128. Setup Complete Screen 18.When Setup is completed, click Finish and click Exit to continue. 182 J.D.
19.Restart the enterprise server and continue. 20.You must configure your SQL Client. To configure Client Network Utility, select Start > Programs > Microsoft SQL Server 7.0 > Client Network Utility. You will see a screen similar to Figure 129: Figure 129. SQL Server Client Network Utility Screen 21.Click Add. You will see a screen similar to Figure 130. Figure 130. Add Network Library Configuration Screen 22.
Figure 131. SQL Server Client Network Utility Screen 23.Click OK. 24.Go to your Windows NT desktop. 25.After completing the client setup, you can now enter the SQL Server Management utility. 184 J.D. Edwards’ OneWorld B73.
8.3 Installing and Configuring J.D. Edwards’ OneWorld B73.3 In this section, you will use the Installation Planner to create your install plan and deploy OneWorld to the enterprise server(s) and client workstations. During this installation, we install the OneWorld B73.3 setup software on your deployment server. If necessary refer to the OneWorld Installation Guide (Windows NT-Based Systems), release B73.3 as a reference.
contracts). You will need to provide your J.D. Edwards’ Address Book number and the serial number that appears on the screen, the expiration data and the number of licenses. Note: You may be instructed to leave a telephone number and someone from contracts will give you a call back. It is important that you have a telephone near the deployment server you’re about to set up. 5.
Figure 134. OneWorld Congratulations Screen 8. Select Install Adobe Acrobat Reader 3.01 and click Close to continue. After the installation of the first setup CD-ROM has completed, you are not prompted to insert the second setup CD-ROM. Note: If you installed Acrobat Reader and Internet Explorer earlier during the installation process, do not select these programs for installation again. 9. After the first setup CD-ROM has completed loading its files, insert the second setup CD-ROM and run Setup.exe.
10.On OneWorld Setup Options, choose the appropriate server database (either SQL Server or Oracle) to load its export files and scripts. For this example, select SQL Server. In addition, click Change Directory to install the files on the d:\ drive. Click Next to continue. Note: The components you need for further building your database are copied into the subdirectory B733\DATABASE\EXPORTS. 11.When copying of the export files and scripts has completed successfully, click Close. 12.
8.3.1 Creating Databases for SQL Server 7.0 In this section, we begin the creation of the SQL Server 7.0 databases for OneWorld B73.3. The OneWorld tables are divided among multiple databases. These databases and their owners are created using scripts that are delivered with OneWorld. In Table 16, you will notice the specific OneWorld data sources and their respective database location: Table 16.
3. The database creation script is in the \Oneworld\B733\Database folder. The name of the script is DB_SQLSRVR70.SQL (shown in Figure 136 on page 190). 4. Review the script and edit the paths (default path is z:\mssql) and verify that the directory you are specifying exists in the enterprise server. For our example, we changed z:\mssql to d:\mssql7 (d:\mssql7 is where SQL Server 7.0 exists on the enterprise server). 5.
6. After you have finished editing the script, save this under a new name (for example, DB_SQLSRVR70OK). 7. On the deployment server, click Start > Programs > SQL Server 7.0 > Query Analyzer. Establish a connection to your SQL Server using a database administrator ID and password (for example, user sa and no password or Windows NT Administrator, JDE). 8. Click File > Open. You will see a screen similar to Figure 137: Figure 137. Open Query File Screen 9.
10.From the action bar, click Query > Execute. This process will take several minutes to complete. You can verify your results by looking at the final results in the lower half of the form. 8.3.2 Creating Database Logins and Users for SQL Server 7.0 In this section, we begin the creation of SQL Server 7.0 database logins and user IDs for OneWorld B73.3. These logins and users are created using script provided with OneWorld.
8.3.3 Loading Central Objects for SQL Server 7.0 In this section, we will complete the final step to prepare Microsoft SQL Server 7.0 for OneWorld B73.3 by loading the central objects data sources. To begin, complete the following steps: 1. Edit the JDESET.BAT script located in the d:\OneWorld\B733\Database\Exports\Sqlsrvr\NT subdirectory. Check the machine name (identified by machinename).
The Installation Planner will guide you in a step-by-step process toward defining your installation plan. In the example below, we define and set up the enterprise server, deployment server, data sources, CRP and Production package builds and environments. After completing your plan, you will load OneWorld on the enterprise server. In this section, you will provide information such as database type, enterprise server, operating system platform, install path, etc.
Figure 141. Work with Installation Plans Screen 4. On Work with Installation Plans screen, click Add. You will see a screen similar to Figure 142: Figure 142. Custom Installation Plan (Installation Planner) Screen 5. In Figure 142, complete the fields and selections of the following: • Name = Type the name of your installation plan (for example, B733INSTALL). • Description = Type the description of your installation plan. • Status = Select 10. • Click Install. Implementing Microsoft SQL Server 7.
• Verify that the Coexistent with World Software box is not checked. 6. Click OK to continue. 7. You will be asked to define a location or select an existing location. Click OK to define a new plan. You will see a screen similar to Figure 143: Figure 143. Location Revisions Screen 8. Enter the following information for Location Revision: • Location = Enter the name or place that applies to this plan. For our example, we chose ITSO.
Figure 144. Deployment Server Revisions Screen 11.Complete the following information for the Deployment Server Revisions: • Machine Name = Name of your deployment server; for example, IBM5500DS. • Description = Enter a long description of the machine; for example, Primary Deployment Server. • Release = OneWorld release number that you are installing, B733. • Primary Deployment Server = 1. • Server Share Path= \B733. 12.If you are not adding another deployment server, click No to continue. 13.
Figure 145. Enterprise Server Revisions Screen 14.On the Enterprise Server Revisions screen, complete the following fields: • Machine Name - The name of your primary enterprise server; for example, IBM5500ES. • Description - Enter a description of your machine name; for example, ENTERPRISE SERVER. • Release = B733. • Host Type = Click the flashlight button and select code 50 (Intel NT). Note: The flashlight button is shown when you place the cursor in the field.
Figure 146. Data Source Setup Screen 17.From the action bar, click Form and select Advanced. You will see a screen similar to Figure 147 on page 200. Implementing Microsoft SQL Server 7.
Figure 147. Data Source Revisions Screen 18.At this screen, put a check mark in the OCM Data Source check box. Note: The DLL Name must be JDBODBC.DLL for SQL Server. The OCM check box is checked for only the IBM5500ES - B733 Server Map and System - B733 data sources. 19.Click OK to create a new data source. You will see a screen similar to Figure 148 on page 201. 200 J.D. Edwards’ OneWorld B73.
Figure 148. Create New Data Source Screen 20.Choose System Data Source and Click Next to continue. You will see a screen similar to Figure 149: 21.Note: When creating ODBC data sources you can elect to not use the Login ID and Password to configure data sources. However, we use the procedure recommended by J.D. Edwards’. Figure 149. Create New Data Source Screen 22.Select SQL Server driver and click Next to continue. 23.Click Finish to create a new data source.
Figure 150. Create a New Data Source to SQL Server Screen 24.Complete the following fields: • Name (of Data Source) = IBM5500ES - B733 Server Map • Description = IBM5500ES - B733 Server Map • Server (SQL Server) = The name of your enterprise server, IBM5500ES 25.Click Next to continue. You will see a screen similar to Figure 151: Figure 151. Create a New Data Source to SQL Server Screen 26.Select With SQL Server authentication using a login ID and password entered by the user.
Figure 152. Create a New Data Source to SQL Server Screen 27.Mark the check box for Change the default database to: and select JDEB733 from the pull-down menu. Click Next to continue. You will see a screen similar to Figure 153. Note: The check box Create temporary stored procedures for prepared SQL statements and drop the stored procedures should not be checked. Our version of the ODBC administrator was shaded and we were unable to modify per J.D. Edwards’ recommended procedure. Figure 153.
Figure 154. ODBC Microsoft SQL Server Setup Screen 29.Review your setup and click OK to continue. 30.Again, click OK to continue. 31.If you are not adding another enterprise server, click No to continue. You will see a screen similar to Figure 155: Figure 155. Machine/Server Types Screen 32.Check the appropriate box for other Machine/Server Types. If none of the servers is selected, then turn off these options. In our example, none of the 204 J.D. Edwards’ OneWorld B73.
items was selected. Click OK. If any of the above are chosen, then refer to J.D. Edwards’ OneWorld Installation Guide (Windows NT - Based Systems), Release B73.3 guide. Note: For instructions on WTS (Windows Terminal Server), refer to Chapter 9, “Implementing Windows NT Terminal Server Edition” on page 251. 33.Next, OneWorld prompts you for the data source information for the shared data sources. Click OK and use Table 18 in the next several screens. Table 18.
Figure 157. Data Source Revisions for System - B733 Screen 35.Accept the defaults and place a check mark in the OCM Data Source check box. The OCM check box is checked only for the IBM5500ES - B733 Server Map and System - B733 data sources. Click OK to create a new data source. Note: You must repeat the same steps used during the creation of a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 18 on page 205 to identify the name of the associated database. 206 J.D.
Figure 158. Data Source Setup for Object Librarian - B733 Screen 36.In the Server Name field, ensure the name of your enterprise server is shown (for example, IBM5500ES). The owner is OBJB733. Click Form > Advanced. You will see a screen similar to Figure 159 on page 208. Implementing Microsoft SQL Server 7.
. Figure 159. Data Source Revisions for Object Librarian - B733 Screen 37.Accept the defaults. Click OK to create a new Data Source. Note: You must repeat the same steps used during the creation of a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 18 on page 205 to identify the name of the associated database. 208 J.D. Edwards’ OneWorld B73.
Figure 160. Data Source Setup for Data Dictionary B733 Screen 38.In the Server Name field, ensure the name of your enterprise server is shown (for example, IBM5500ES). The owner is DDB733. Click Form > Advanced. You will see a screen similar to Figure 161 on page 210. Implementing Microsoft SQL Server 7.
Figure 161. Data Source Revisions for Data Dictionary - B733 39.Accept the defaults. Click OK to create a new data source. Note: You must repeat the same steps used during the creation of a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 18 on page 205 to identify the name of the associated database. 210 J.D. Edwards’ OneWorld B73.
Figure 162. Environment Selection Screen 40.On the Environment Selection screen, check the appropriate box if you want to accept defaults. Uncheck these options if you want to choose your own environment information. For our example, none of the environments was chosen. Click OK to continue. You will see a screen similar to Figure 163 on page 212. Implementing Microsoft SQL Server 7.
Figure 163. Select Environments Screen 41.At this screen, you will select the environments you want to define. In our example, we chose PRDB733 and CRP733. Double-click PRDB733 and you will see a screen similar to Figure 164 on page 213. Note: You must choose and define each environment one at a time. 212 J.D. Edwards’ OneWorld B73.
Figure 164. Data Load Parameters Screen 42.Select Load Production Data and then click OK. 43.OneWorld asks if you want to set up data sources for each environment or take the defaults that OneWorld sets up. For our example, we clicked OK and used Table 19 to create ODBC data sources: Table 19.
. Figure 165. Data Source Setup for Control Tables - Prod Screen 44.Review the accuracy of the Control Tables - Prod data source. From the action bar, click Form and select Advanced. You will see a screen similar to Figure 166 on page 215. 214 J.D. Edwards’ OneWorld B73.
Figure 166. Data Source Revisions for Control Tables - Prod Screen 45.Accept the defaults. Click OK to create a new Data Source. Note: You must repeat the same steps when you create a data source for IBM5500ES - B733 Server Map beginning with Step 19 on page 200. Use Table 19 on page 213 to identify the name of the database. Implementing Microsoft SQL Server 7.
Figure 167. Data Source Setup for Business Data - Prod Screen 46.From the action bar, click Form and select Advanced. You will see a screen similar to Figure 168 on page 217. 216 J.D. Edwards’ OneWorld B73.
. Figure 168. Data Source Revisions for Business Data - Prod Screen 47.Accept the defaults. Click OK to create a new data source. Note: You must repeat the same steps when you create a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 19 on page 213 to identify the name of the database. Implementing Microsoft SQL Server 7.
. Figure 169. Data Source Setup for Central Objects - PRODB733 Screen 48.From the action bar, click Form and select Advanced. You will see a screen similar to Figure 170. Figure 170. Data Source Revisions for Central Objects - PRODB733 Screen 218 J.D. Edwards’ OneWorld B73.
49.Accept the defaults. Click OK to create a new data source. Note: You must repeat the same steps when you created a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 19 on page 213 to identify the name of the database. Figure 171. Data Source Setup for Versions - PRODB733 Screen 50.From the action bar, click Form and select Advanced. You will see a screen similar to Figure 172 on page 220. Implementing Microsoft SQL Server 7.
Figure 172. Data Source Revisions for Versions - PRODB733 Screen 51.Accept the defaults. Click OK to create a new data source. Note: You must repeat the same steps when you created a data source for IBM5500ES - B733 Server Map beginning with step 19 on page 200. Use Table 19 on page 213 to identify the name of the database. 220 J.D. Edwards’ OneWorld B73.
Figure 173. Select Environments Screen 52.Repeat the same steps for CRP733 as for PRD733. Double-click CRP733. When you reach this screen again and CRP733 is complete, click Close to continue. 53.Click No if you do not want to add another location. You will see a screen similar to Figure 174 on page 222. Implementing Microsoft SQL Server 7.
Figure 174. Work with Installation Plans Screen 54.Click OK to continue. 8.3.5 Validate the Plan In this section, you will run the plan validation report to ensure that the plan is correct and ready for installation. 1. Run the plan validation report. If you are not at the System Installation Tools menu, type GH961 in the Fast Path field and press Enter. 2. Double-click Plan Validation. You will see a screen similar to Figure 175 on page 223. 222 J.D. Edwards’ OneWorld B73.
Figure 175. Work With Batch Versions - Available Versions Screen 3. Highlight the grid record for Version XJDE0001, then click Select. You will see a screen similar to Figure 176: Figure 176. Version Prompting Screen Implementing Microsoft SQL Server 7.
4. Select the Data Selection box, then click Submit. You will see a screen similar to Figure 177: . Figure 177. Data Selection Screen 5. At this screen, you will set criteria design information. In the column, Right operand, double-click Plan Name and select Literary. • Type in the plan name; for our example, we typed B733INSTALL • Click OK. You will see a screen similar to Figure 178: Figure 178. Processing Options Screen 6. On the Extra Info tab on Processing Options, accept the defaults and click OK.
Figure 179. Report Output Destination Screen 8. Choose On Screen to view your validation report at your display. Click OK. Adobe’s Acrobat Reader launches the Installation Planner Validation Report PDF. 9. Review the report and ensure your information is correct. Exit the Acrobat Reader and select Close to exit Validation. Figure 180. Work with Installation Plans Screen 10.On the Work with Installation Plans screen, click Expand to review the plan you’ve created. Go to the next section and continue. 8.
Note: If the Data Source administrator appears, requesting that you create a data source, click Cancel to continue. You should have created all of your data sources earlier during the installation planner process. Figure 181. Work with Installation Plans Screen 2. A message appears to let you know that Release Master has completed. Click OK and then click Close. 8.3.7 Running Installation Workbench The Installation Workbench runs the plan you created.
Figure 182. Work with Installation Plan Screen 4. At the Work with Installation Plan screen, double-click the Plan Name, B733INSTALL record. You will see a screen similar to Figure 183: Figure 183. Location Workbench Screen Implementing Microsoft SQL Server 7.
5. Verify that this form lists all the necessary locations for your plan. From the action bar click Form > Configure (the Workbench updates your Detail Status to 60 and changes the Status Description from Validated to Installed). 6. Click Next to continue. You will see a screen similar to Figure 184: Figure 184. Data Source Workbench Screen 7. At the Data Source Workbench screen, we scrolled down the list of items and verify that the information presented lists all the necessary data sources for our plan.
Figure 185. Environment Workbench Screen 10.On the Environment Workbench screen, verify the environment you selected and each environment’s associated parameters for correct values. OneWorld includes the deployment server environment in this list. Note: The environment configuration phrase takes approximately two hours or more per environment to run. You can let Environment Workbench run overnight, but do not lock the workstation or Environment Workbench stops after loading the first environment. 11.
Figure 186. Machine Workbench Screen 13.Review the Machine Workbench for the correct parameters. At the action bar, click Form > Configure (this will update your Detail Status to 60 and changes the Status Description from Validated to Installed). 14.Click Next to configure your packages. You will see a screen similar to Figure 187. 230 J.D. Edwards’ OneWorld B73.
Figure 187. Package Workbench Screen 15.On the Package Workbench screen, review the Conference Room Pilot (CRP) and Production packages. From the action bar, click Form > Configure. 16.Click Next to finish the plan. From the action bar, click Form > Finish. 8.3.8 Setting Up and Verifying the Hosts File If no Domain Naming Service is defined on your network, you must set up the hosts file for each machine.
8.4 Installing OneWorld on the Enterprise Server In this section, you will use the CD-ROM software OneWorld Release B73.3 NT Intel, 1 of 1 to install OneWorld on the enterprise server. This installation process copies OneWorld system and path code files directly from the CD-ROM to the enterprise server. Complete the following steps to install the enterprise server software: 1. Log on to the enterprise server with system administrator privileges. 2.
Figure 188. OneWorld B733 NT Enterprise Server Setup Screen 8. Click Next to continue. You will see a screen similar to Figure 189: Figure 189. Deployment Path Dialog Screen 9. At the Deployment Path Dialog screen, type the path on the deployment server where the base OneWorld installation exists. In this example, we typed x:\OneWorld\B733. Click Next to continue. You will see a screen similar to Figure 190 on page 234. Implementing Microsoft SQL Server 7.
Figure 190. Enterprise Server Setup Type Screen 10.Click Custom for your setup type. 11.In the Target Folder field of the Setup Type screen, type the directory where you want the files installed on your enterprise server. In our example, we typed D:\OneWorld\ddp\B733. Click Next to continue. You will see a screen similar to Figure 191 on page 235. Note: Under Space Available the software package does not recognize the correct amount of space that is available. Do not be alarmed.
Figure 191. Enterprise Server Setup Component Selection Screen 12.At the Component Selection screen, you may want to select all the components that apply to your OneWorld setup. In this example, prodb733, crpb733, and system were selected. Click Finish to continue. 13.When the enterprise server setup completes copying its files, the OneWorld B733 NT Enterprise Server Setup screen will notify you that the installation was successful. 14.Click OK to continue. 8.4.
Table 20. OneWorld Data Sources and Database Names for SQL Server 7.0 Data Sources Database Name System - B733 Object Librarian - B733 Data Dictionary - B733 machinename - B733 Server Map machinename (where machinename is the enterprise server). machinename - logic (where machinename is the enterprise server).
8.4.1.1 Installing OneWorld Network and Queue Services In this section, you will install JDESQUE and JDESNET. To complete the installation of JDESQUE and JDESNET, perform the following steps: 1. Open a DOS command prompt, and type the following commands: cd\OneWorld\ddp\B733\System\Bin32 jdesque -I jdesnet -I exit 2. From the Windows NT interface, click Start > Settings > Control Panel. Select the Services icon. You will see a screen similar to Figure 192: Figure 192. Windows NT Services Screen 3.
OneWorld Enterprise Server Processes" in the J.D. Edwards’ OneWorld Installation Guide (Windows NT Based-Systems), Release B73.3. 8.5 Setting Up a Printer on the OneWorld Enterprise Server In this section, these procedures are performed to set up a printer for our OneWorld enterprise server. However, depending on the customer or clients, these steps may be different. The following tasks will be done on the deployment server in the deployment environment (DEPB733): • Adding a paper type.
however the basic steps are shown below. For Paper Type Revisions, enter the following fields: • Paper Type = Select the paper type that you are going to use. • Paper Heights = Specify the height of the paper for this paper type. • Paper Width = Specify the width of the paper for this paper type. • Unit of Measure = Indicate the unit of measure in which the paper height and width are entered. 4. Click OK and then Cancel to continue. 8.5.
Note: The capability type H (Host) and P (Paper) are required to set up a physical printer. However, T (Type) and W (Where) are for informational purposes only and may be optional. • Capability = This step is determined by the capability type. For example: Paper represents LETTER, A4, and LEGAL, while Host represents the name of the machine that process the job. 4. Click OK. 5. Repeat the same procedure above for P (Paper) and if necessary, for T (Type) and W (Where). 6.
• Logical Printer = Name of printer where you will send your print job. • Description = Long description of your printer. • Physical Printer = Location of your printer. • Conversion Program = Choose your correct conversion program. • Paper Type = Choose your appropriate pre-defined paper type. 4. Click OK to save the record for your printer definition. 8.5.5 Adding a Default Logical Printer In this section, we will add a default printer. Complete the following steps: 1.
8.6 Setting User and Group Profiles J.D. Edwards recommends you set up one or two users to perform the installation process. Once this is done, you can then set up the rest of your users and groups when you have time to consider how you want groups to be organized and what preferences you want each group to have. In this section, we will perform the following: • Create a user and group profile. • Assign our packages to our profiles. • Assign our environments to our profiles. 8.6.
Figure 197. User Profiles (Work With User Profiles) Screen 4. Click Add to create a new profile. You will see a screen similar to Figure 198 on page 244. Implementing Microsoft SQL Server 7.
Figure 198. User Profiles (User Profile Revisions) Screen 5. To create a group profile: • In the User ID field, type a group name, such as ACCOUNTING.. • In the User Class/Group field, type *GROUP. 6. Click OK. 7. Click Add to create a new user. You will see a screen similar to Figure 199 on page 245. 244 J.D. Edwards’ OneWorld B73.
Figure 199. User Profiles (User Profile Revisions) Screen 8. Complete the following fields: • In the User ID field, type the individual’s user ID. For our example, we used LEIUSER1. • In the User Class/Group field, type the name of the group to which the user belongs, such as ACCOUNTING, or use the flashlight button to search for this group. Leave this field blank if the user does not belong to a group. • Enter an address book number. 9.
. Figure 200. User Profile (Work With User Profiles) Screen 3. Choose an existing user ID. For our example, we chose LEIUSER1. (This can be an individual or group profile.) 4. From the action bar, select Row > Deployment. 5. On the User Deployment Preferences screen, complete the following fields: • Deployment Location = We left this field blank for this example. Note: You can have the workstation installation pull packages from a machine other than your deployment server.
8.6.3 Assigning Environments to a Profile When starting OneWorld, you can assign more than one environments to each user or group from which any user or group can choose. If users do not have environments of their own, they can choose from the ones assigned to their group. To assign environments, perform the following steps: 1. From your OneWorld work space access the Advanced Operations menu (GH9011), and choose User Profiles. 2. On Work With User Profiles, click Find. 3. Choose a profile.
8.7 Installing OneWorld Client The workstation installation copies all necessary components of OneWorld to a client workstation. To prepare for the OneWorld client installation, we will perform the following steps: • Modify the JDE.INI file on the deployment server. • Modify the Setup.inf file on the deployment server. 8.7.1 Modify the JDE.INI File on the Deployment Server You must modify the JDE.INI file on the deployment server prior to installing OneWorld on your workstations.
4. Save the file, then close it. 8.7.3 Installing OneWorld Client (Interactive Mode) Install the OneWorld Client software on the designated workstation using Interactive Mode. Ensure that all the required software for the workstation has been installed, such as the SQL Server client software. No other services or open programs should be active during the OneWorld client installation. For instructions on how to install the SQL Server 7.
Figure 203. OneWorld Sign-On (Welcome) Screen 4. Type the login ID. (For this example, LEIUSER1.) Note: This list of packages comes from your user and group profiles for deployment preferences. 5. Check the box to the left of each package to install on the client workstation. Click the option to Install Development Objects if you are a OneWorld developer. This option appears only if you have a compiler loaded on your workstation.
Chapter 9. Implementing Windows NT Terminal Server Edition This chapter provides information and instructions to install and configure Windows NT Terminal Server Edition, Citrix MetaFrame, Netscape Navigator, Go Lotus Domino Go Webserver, eNetwork OnDemand Server, NC Navigator, Network Station Manager and Network Station, and the OneWorld B73.3 Client. Once these tasks have been completed, Windows NT Terminal Server Edition will be able to support multiple IBM Network Stations accessing the OneWorld B73.
• IBM DHCP services may be installed using your IBM Network Station Manager CD-ROM. • Microsoft DHCP services or another version of DHCP. • Or you can elect to run no DHCP services at all. In our example, we elected not to use DHCP in our lab environment. 9.2 Hardware and Software Requirements The table below is a summary of the amount of disk space required by the components we installed in the plain vanilla sample installation we describe below, using the General Availability version of NSM Release 3.
• NC Navigator Network Station Browser • Adobe Acrobat Reader If you wish to use Microsoft’s Internet Explorer and Internet Information Server (IIS) instead of the Netscape Navigator browser and Lotus Go Webserver, you can download the Internet Explorer from Microsoft’s Web site and obtain the IIS code from the Windows NT Server 4.0, Terminal Server Edition CD-ROM. The URL for Microsoft’s Web site is: http://www.microsoft.com 9.
Figure 205. Error Message When Installing on a FAT Drive 2. A Web browser, either Netscape Navigator 4.04 or Microsoft Internet Explorer 4.0.4. The IBM Network Station Manager has not been tested using later browser products. 3. A Web server, either Lotus Domino Go Webserver 4.6.1 or Microsoft’s Internet Information Server 4.0. In our installation, we installed the Domino Go Webserver. 9.4 Installation of Windows NT Server 4.0, Terminal Server Edition The installation of Windows NT Server 4.
represent a choice of the language that the product should use once installed, except in the case of the additional products. Figure 206. First Install (Language) Screen 2. The second screen shown in Figure 207 allows you to view the readme file (we highly recommend you read this before proceeding), install the IBM Network Station Manager, install additional products, and explore the contents of the CD-ROM. The additional products are: • Netscape Navigator 4.0 • Lotus Domino Go Webserver 4.6.
Select Install Additional Products first since we need the Web browser and Web server prerequisite products. You will see a screen similar to Figure 208. 9.5.1 Installation of Netscape Navigator 4.0 In this section, we begin the installation of Netscape Navigator. 1. On the Install Additional Products screen, select Netscape Navigator 4.0. Figure 208. The Install Additional Products Screen 2. The installation process is very straightforward as there are few decisions to be made.
4. Start the browser and follow the instructions. You will click through several screens before reaching the New Profile Setup (shown in Figure 210): Figure 210. New Profile Setup Screen 5. This setup creates a profile and allows you to choose Netscape Navigator as your default browser.
Figure 211. Lotus Domino Go Webserver - Select Components Screen 2. On the Select Components screen, the first three entries are already pre-selected. Check the Java Servlet check box to add and click Next to continue. 3. You are prompted for an installation directory. In our example, we chose to leave at the default, C:\. Click Next. The next two screens (Figure 212 and Figure 213 on page 259) show the different directories to be created, giving you the option to change their location if desired.
Figure 213. Lotus Domino Go Webserver - Choose Component Directories Screen Figure 214. Lotus Domino Go Webserver - Choose Configuration Parameters Screen 4. This panel allows you to change some of the basic configuration data. Accept the defaults and enter our administrator ID (JDE) and password (JDE). Click Next. Note: The use of JDE as the admin ID and admin password is not a requirement. This can be whatever you select. 5.
Figure 215. Lotus Domino Go Webserver - Completion Warning Screen Notice, as indicated in the message above, the Lotus Domino Go Webserver can be started using the Services activity in the Control Panel. In other words, there is not an icon in a folder somewhere that you can click to start the Web server; you can only start it by starting the corresponding Windows NT service. 6. It is not necessary to start the Web server at this time. Select No, I will restart my computer later and click OK. 7.
Figure 217. Language Selection for Network Station Manager Screen This screen asks for a language selection. This language selection is only for the language used during the installation process dialogs and not to select the language that the application will use once installed. The language that the application uses after installation is automatically determined by the value of the default system locale in the Windows NT Regional Settings. 3. Select U.S. English and click OK. 4.
Figure 219. Choose Destination Location Screen 7. This screen allows you to choose the target folder for the IBM Network Station Manager. We accepted the default. Click Next to continue. You will see a screen similar to Figure 220. Figure 220. Select Program Folder Screen 8. Accept the default for the program folder; click Next to continue. You will see a screen similar to Figure 221 on page 263. 262 J.D. Edwards’ OneWorld B73.
Figure 221. Migration Screen This screen is used only if you are migrating from a previous version and you need to indicate the location of the user preference files to be migrated. For example, you might specify x:\nstation where x: is a drive mapped to the server on which the old release is installed. 9. In our example, we are not migrating so we leave this blank. Click Next to continue. You will see a screen similar to Figure 222: Figure 222.
and DDNS servers, the TFTP server, the TIMED server, the network station login (NSLD) server, the NFS server, and the RPC Portmapper server. Note: These components can be installed individually as well by using the specific setup.exe file for the eNetwork On-Demand Server. See the readme.txt file in the \ntnsm\en\products\enod\tcpip directory on the CD-ROM for more details. 10.Click Next to continue. You will see a screen similar to Figure 223: Figure 223.
Figure 224. Summary of Products to Be Installed Screen 12.Click Next to continue. The program files are copied to your system and later will see a screen similar to Figure 225. Figure 225. Desktop Shortcut Creation Question 13.You are asked if you want the installation to create a shortcut for you on the desktop, which allows you to start the IBM Network Station Manager directly from the desktop on the server. Click Yes to continue. The program starts setting the Go Webserver permissions.
Figure 227. Completion Screen 9.5.4 Verify the Network Station Manager and Components Installation If you need a quick visual confirmation that your installation was done properly and that you have all the required components, the following screens are provided to help verify your installation of products. In addition, these screens might be useful in cases where problems are encountered during or after installation. 1.
Figure 228. Add/Remove Programs Properties Screen (Installation Verification) The Add/Remove Program list should at least have the following installed products: • IBM eNetwork On-Demand Server • IBM Network Station Manager • Lotus Domino Go Webserver • NC Navigator • Netscape Navigator • Windows NT Terminal Server 4.0 Service Pack 4 Although the Windows NT Terminal Server 4.0 Service Pack 4 is listed here, you should consider installing it toward the end of your setup. 2.
Figure 229. Installed Services Screen The fact that all of these services have a status of Started is probably the best indication that the installation was successful. If there was a problem with the installation, it is probable that one or more of these services would not be able to start correctly. The IBM DDNS and IBM DHCP Server services may not appear in this list if you chose not to use the Microsoft DHCP Server or the IBM DHCP Server.
For example, assume we have users User1 and JDE defined on the ONEWORLD PDC as members of a global group called NSMACCT. We want to give these users the ability to log on to the IBM5000WTS server. When these users were defined on the PDC, they were made part of a global group called NSMACCT on the PDC, as illustrated in the next figure, which displays the Global Group Properties on the ONEWORLD domain PDC: 1. Select the Start > Programs >Administrative Tool > User Manager for Domains. 2.
Figure 232. Add Users and Groups Screen Notice that we have selected in the List Names From field, ONEWORLD. The list of names that gets displayed is from the ONEWORLD Primary Domain Controller. We select the NSMACCT group from the list and click Add so that the \\ONEWORLD\NSMACCT entry appears in the bottom portion of the window, indicating that we are adding the NSMACCT global group from the ONEWORLD domain to our local group NSMUser on the IBM5000WTS server.
IBM5000WTS attached to ONEWORLD NSM R3 ONEWORLD PDC V 1 ser U y erif SAM SAM NSMACCT User1 JDE NSMUser \\ONEWORLD\NSMACCT Is User1 member of NSMUser? NS Login Server Network Station Logon User1 NS Login Client Figure 233. NSMUser Group on Local Server 9.5.6 Lotus Domino Go Webserver Service Startup If you examine the startup information for the Lotus Domino Go Webserver Windows NT service, it should appear as automatic startup, which means that it should be automatically started after a reboot.
Figure 234. Service Startup Screen 3. Under System Account, select Allow Service to Interact with Desktop, to display this service on your desktop, and click OK. The next time you boot your system, this service will start automatically and display a Go Webserver status screen. To start displaying this screen immediately, continue to the next step. 4. From the Windows NT Services screen, highlight Lotus Domino Go Webserver and click Stop. Click Start to execute Go Webserver.
This status panel displays activity and log information. Notice the bottom left-hand corner of the screen displays Server Ready, indicating that the Web server is indeed operational. Note: When you install the Lotus Domino Go Webserver on Windows NT Server 4.0, Terminal Server Edition, the status panel shown in Figure 235 on page 272 will not be displayed on remote clients. It is only displayed if you are logged on at the desktop of the TSE server. 9.6 MetaFrame from Citrix Systems Inc.
Figure 236. MetaFrame Installation Autorun Panel 3. At this screen, click MetaFrame Setup to start the install process on your IBM5000WTS. 4. Click I Agree to accept the terms of the MetaFrame License Agreement and continue. 5. Enter the serial number of the license. The serial number should be printed on the documentation that ships with the MetaFrame product. Click OK. The install program begins to copy files to your system. 6.
Figure 237. Lotus SmartSuite 97 Screen (Exit and Reboot) Screen 7. Here, you are given the option to load Lotus SmartSuite. For our example, we chose to Exit and Reboot. Click OK. Remove the Citrix MetaFrame CD-ROM from the CD-ROM drive. 9.7 Activate MetaFrame Licensing on Windows NT Terminal Server Edition After your system has been restarted, we will activate the Citrix MetaFrame license. This section describes the process of installing the ICA client on Windows NT Terminal Server Edition.
browser to access the Citrix Web site, http://www.citrix.com/activate, to activate Metaframe. You will see a screen similar to Figure 239: Figure 239. Citrix Product Activation URL Screen 3. Click Citrix MetaFrame and then click Activate License (Citrix Activation System). 4. Take a moment to read the information regarding the 30-day grace period. Click Continue. 5. Complete the Registrant Information form and click Continue. 6. Complete the Application/Usage Information form and click Continue.
Figure 240. Activation Detail Form Screen 7. Complete the Activation Detail form and click Continue. You will be presented with your activation code. Write this code down or print the screen. Click OK. 8. You will be presented with a summary of your license activation. Click Exit. 9. Return to your Citrix Licensing screen (shown in Figure 238 on page 275).
Figure 241. MetaFrame Installation Autorun Panel 2. Select Setup ICA Client and click Next to continue. You will see a screen similar to Figure 242: Figure 242. Destination Location Screen 3. Choose the Destination folder for the ICA Client. Click the Browse button (for example, D:\Program Files\Citrix\ICA Client). 4. Choose Next to continue. 5. Choose the default for Program Folder and Existing file and click Next and continue. 278 J.D. Edwards’ OneWorld B73.
Figure 243. ICA Client Setup Screen 6. Type in a unique name that you will call the workstation client and click Next to continue (for example, we used IBM5000WTS). You will see a screen similar to Figure 244. Note: At this point, the Client icons will be created. Figure 244. ICA Client Complete Screen 7. Choose OK, and close. 9.8.1 Network Station Client Configuration for OneWorld In this section we discuss the procedures for setting up an icon or button on the Network Station (client).
Figure 245. IBM Network Station Manager Main Screen 4. From the Setup Tasks, on the left side of the screen, click Startup and select Menus. You will see a screen similar to Figure 246: Figure 246. Menu Content Defaults Screen 280 J.D. Edwards’ OneWorld B73.
5. Select the default that you are using. For this example, select System defaults. Note: Depending on your preferences, you may choose to set up a group or a specific user. 6. At the bottom of the screen, click Next to continue. You will see a screen similar to Figure 247: Figure 247. Local Program Menu Items Screen 7. Select a type of menu. For this example, scroll down to Local Program Menu Items. • Menu item label = Enter the name of the OneWorld application (for example, ONEWORLD).
other applications. However, we chose to add the creating of an ICA client for the PC desktop. Complete the following steps: 1. From your Windows NT desktop, click Start > Programs > MetaFrame Tools > ICA Client Creator. You will see a screen similar to Figure 248: Figure 248. Make Installation Disk Set Screen Note: This process takes two diskettes. It also formats and loads its data. 2. Insert the first diskette and then click OK to continue.
Figure 250. Client Destination Location Screen 7. Click Next to install the client to the default destination folder. You will see a screen similar to Figure 251: Figure 251. Client Program Folder Screen 8. Click Next to add the icons to the Citrix ICA Client folder. You will see a screen similar to Figure 252 on page 284.
Figure 252. ICA Client Name Screen 9. Type in your client name and click Next to continue. (For our example, we used OWNTWKSTN.) 10.In the Citrix ICA Client Icon Group, select Remote Application Manager to set up the application that you will be using to log in to the Windows Terminal Server. You will see a screen similar to Figure 253: Figure 253. Remote Application Manager Dialog Box 11.Click Yes to continue. You will see a screen similar to Figure 254: Figure 254. Remote Application Screen 284 J.D.
12.Select the connection type that you will be using. (For example, we used Network). Click Next and continue. You will see a screen similar to Figure 255: Figure 255. Add a new Remote Application Screen Complete the following fields: • Description = Type in a description for your remote application. (For example, we used OW_B733.) • Network Protocol = Select the type of Network Protocol. (For example, we used TCP/IP.
Figure 257. Add a new Remote Application Screen 15.Complete the following fields: • Username = The user name to connect to the application server (for example, JDE). • Password = The password for the user. • Domain = Enter the domain name (for example, ONEWORLD). 16.Click Next and continue. You will see a screen similar to Figure 258: Figure 258. Add a new Remote Application Screen 17.Click Next and continue. You will see a screen similar to Figure 259 on page 287.
Figure 259. Add a new Remote Application Screen 18.Leave the following fields blank: • Application = (Leave blank) • Working Directory = (Leave blank) 19.Click Next and continue. You will see a screen similar to Figure 260: Figure 260. Add a new Remote Application Screen 20.Click Next and continue. You will see a screen similar to Figure 261 on page 288.
Figure 261. Add a new Remote Application Screen 21.Click Finish. You will receive the message below confirming that setup has successfully completed. Setup is complete. (Note: At this time, you may log on to the Windows Terminal Server by double-clicking the OW_B733 or whatever application that you create. 9.8.
9.9 Configure Installation Planner for Windows NT Terminal Server This section provides the necessary steps to create an installation plan to install Microsoft Windows NT Server 4.0, Terminal Server Edition. In Chapter 7, “Implementing Oracle8 and J.D. Edwards’ OneWorld” on page 89 and Chapter 8, “Implementing Microsoft SQL Server 7.0 and OneWorld” on page 167, we created an installation plan for OneWorld B73.3 using Oracle8 Enterprise Edition for Windows NT and Microsoft SQL Server 7.0.
Figure 264. Custom Installation Planner Screen 5. On Installation Planner, enter the base plan information by completing the following fields: • Name = The name of your installation plan (for example, B733WTS). • Description = The description of your plan with as much detail as possible. • Status = 10. • Click Install. • Verify that the Coexistent with World Software box is not checked. 6. Click OK. On Location Search, choose the location, and click Select. You will see a screen similar to Figure 265.
Figure 265. Custom Installation Plan (Location Revisions) Screen 7. Click OK to continue. 8. On the Enter Deployment Server Information screen, click Skip. Figure 266. Enterprise Server Dialog Box 9. On the Enter Enterprise Server Information screen, click Select. Note: Our Enterprise server exist from an earlier setup, therefore, we click Select. If we were adding a new enterprise server, we would click OK and continue with the data source setup. Follow the steps: 10.
Figure 267. Custom Installation Plan (Enterprise Server Revisions) Screen 11.Click OK. You will see a screen similar to Figure 268: Figure 268. Data Source Setup Screen 12.Click OK. (Select the highlighted section.) 292 J.D. Edwards’ OneWorld B73.
13.Click OK to continue. Figure 269. Enterprise Server Dialog Box 14.Click No if you are not adding another enterprise server. Next, you will see a screen similar to Figure 270: Figure 270. Custom Installation Plan (Machine/Server Types) Screen 15.Check WTS Server and then click OK. You will see a screen similar to Figure 271 on page 294.
Figure 271. Windows Terminal Server Dialog Box 16.Click OK to continue. You will see a screen similar to Figure 272: Figure 272. Custom Installation Plan (Windows Terminal Server Revisions) Screen 17.Complete the following fields for the WTS Server Revisions: • Machine Name = The name of your Windows Terminal Server. (For example, IBM5000WTS.) • Description = A description of your installation plan. • Release = The release number of OneWorld that you are installing. 294 J.D. Edwards’ OneWorld B73.
• Installation Path = The installation directory path to which you are installing OneWorld on your server. Make sure that it is specific to the version of the release, for example, we used d:\b7. 18.Click OK. OneWorld asks if you want to add another Windows Terminal Server: If you do not want to add another Windows Terminal Server, click No. 19.Oneworld now prompts you for the data source information for the shared data sources for the Windows Terminal Server that was added. Click OK.
Figure 274. Custom Installation Plan (Data Source Setup) Screen 21.Verify the accuracy of the Object Librarian data source and then click OK. You will see a screen similar to Figure 275. 296 J.D. Edwards’ OneWorld B73.
Figure 275. Custom Installation Plan (Data Source Setup) Screen 22.Verify the accuracy of the Data Dictionary data source and then click OK. You will see a screen similar to Figure 276 on page 298.
Figure 276. Custom Installation Plan (Environment Selection) Screen 23.In the Environment Selection, make sure Default Environments and Default Data Load are not checked and then click OK to continue. You will see a screen similar to Figure 277 on page 299. 298 J.D. Edwards’ OneWorld B73.
Figure 277. Custom Installation Plan (Select Environments) Screen The Wxxx733 environments will appear since we selected to add a Windows Terminal Server to our plan. Note: Refer to the reference section "Default Environment OCM Mappings" of the install manual to review and understand the Object Configuration mappings for each of the environments. 24.To set up your environments, the following step must be completed. 25.On Select Environments, double-click the environment that you choose to define.
Figure 278. Custom Installation Plan (Data Load Parameters) Screen 26.Choose Do Not Load Data and then click OK. Note: You would only load data if you had not previously installed that environment. Figure 279. Custom Installation Plan (Data Source Screen) 27.Click OK to set up the data sources. 300 J.D. Edwards’ OneWorld B73.
Figure 280. Custom Installation Plan (Data Source Setup) Screen 28.Verify the accuracy of the Control Tables data source and then click OK. You will see a screen similar to Figure 281 on page 302.
Figure 281. Custom Installation Plan (Data Source Setup) Screen 29.Verify the accuracy of the Central Object data source and then click OK. You will see a screen similar to Figure 282 on page 303. 302 J.D. Edwards’ OneWorld B73.
Figure 282. Custom Installation Plan (Data Source Setup) Screen 30.Verify the accuracy of the Business data source and then click OK. You will see a screen similar to Figure 283 on page 304.
Figure 283. Custom Installation Plan (Data Source Setup) Screen 31.Verify the accuracy of the Version data source and then click OK. 32.The system now displays Select Environments (see Figure 284 on page 305) so that another environment can be defined (if necessary). 304 J.D. Edwards’ OneWorld B73.
C Figure 284. Custom Installation Plan (Select Environments) Screen 33.On Select Environments, choose the next environment that you want to define. 34.Repeat all of the previous steps that were done above to configure the data sources and environment. 35.After defining all of your environments, click Close. 36.OneWorld will now ask if you would like to add another location, click No. A message will appear stating that the plan has been finalized. Note: When the plan is finalized, the status is set to 20.
Figure 285. Custom Installation Plan (Work With Batch Versions) Screen 38.Complete the following steps to run the Planner Validation Report. Highlight XJDE0001, Planner Validation Report, and click Select. You will see a screen similar to Figure 286: Figure 286. Version Prompting Screen 39.At the Version Prompting screen, check the box for Data Selection and then click Submit icon. You will see a screen similar to Figure 287 on page 307. 306 J.D. Edwards’ OneWorld B73.
Figure 287. Custom Installation Plan (Data Selection) Screen 40.At this screen, you will set criteria design information. In the column, Right operand, double-click "Plan Name" and select Literary. Type in the plan name, for this example, B733WTS. 41.Click OK and continue. You will see a screen similar to Figure 288: Figure 288. Processing Options Screen 42.On the Extra Info tab on Processing Options, verify the fields and click OK. You will see a screen similar to Figure 289 on page 308.
Figure 289. Report Output Destination Screen 43.Choose On Screen to view your validation report at your display. Click OK. Adobe’s Acrobat Reader launches the Installation Planner Validation Report PDF. 44.Review the report and ensure your information is correct. Exit the Acrobat Reader and select Close to exit Validation. You will see a screen similar to Figure 292 on page 310. Figure 290.
46.From the action bar, click Form > Release. You will see a screen similar to Figure 291. Note: If the data sources have been previously created in the Installation Planner, click Cancel to continue. (In our example, we clicked Cancel since we had previously created our data sources.) Figure 291. Custom Installation Plan (Release Master Completion) Screen 47.The system will now inform you that the process has completed. Click OK and Close to continue. 9.9.
Figure 292. Installation Workbench (Work with Installation Plan) Screen 3. Again, verify that a printer is set up for your deployment server. 4. On Work with Installation Plan, double-click your plan. For our example, B733WTS. You will see a screen similar to Figure 293 on page 311. 310 J.D. Edwards’ OneWorld B73.
Figure 293. Installation Workbench (Location Workbench) Screen 5. Verify that this form lists all the necessary locations for your plan. From the action bar, click Form > Configure (this will update your Detail Status to 60 and changes the Status Description from Validated to Installed). 6. Click Next and continue. You will see a screen similar to Figure 294 on page 312.
Figure 294. Installation Workbench (Data Source Workbench) Screen 7. At the Data Source Workbench screen, scroll down the list of items and verify that the information presented listed all the necessary data for your plan. Note: If you are using non-Oracle data sources, you must create ODBC data sources defined in the plan that you did not create earlier when setting up the plan during Running Installation Planner, or it will automatically prompt for any that are not set up. For SQL Server 7.
Figure 295. Installation Workbench (Environment Workbench) Screen 11.On the Environment Workbench screen, review each environment and each environment’s associated parameters for correct values. Note: The environment configuration phase takes approximately two hours or more per environment to run. You can let Environment Workbench run overnight, but do not lock the workstation or Environment Workbench stops after loading the first environment. 12.
Figure 296. Installation Workbench (Machine Workbench) Screen 14.Review the Machine Workbench for the correct parameters. 15.From the action bar, click Form > Configure (this will update your Detail Status to 60 and changes the Status Description from Validated to Installed). 16.Click Next to configure your packages. You will see a screen similar toFigure 297 on page 315. 314 J.D. Edwards’ OneWorld B73.
Figure 297. Installation Workbench (Package Workbench) Screen 17.On the Package Workbench screen, we review the Conference Room Pilot and Production packages. 18.From the action bar, click Form > Configure. 19.Click Next to finish the plan. 20.On the Congratulations screen, from the action bar click Form > Finish. From the Work with Installation Plans, click Close. 9.10 Installing and Configuring the OneWorld Client on WTS This section assumes that the users already exist within OneWorld.
2. From your OneWorld work space access the Advanced Operations menu (GH9011), and choose User Profiles. 3. On Work With User Profiles, click Find. 4. Choose a profile. In our example, we highlighted JDE (see Figure 298): Figure 298. User Profile Screen 5. From the action bar, click Row > Deployment to select a package name. Highlight CRPB733PA and click Select. Note: Install a full package of OneWorld. You need to install a full package because OneWorld on the terminal server is multiuser.
Figure 299. User Profiles (User Environment Revisions) Screen 7. For User Environment Revisions, select the environments you want this user to have: • Display Sequence (Display Seq.) = This is an optional field. Leave blank to arrange environment names alphabetically or enter numbers to create your own order. • Environment = We selected WCRP733 (CRP733, PRD733, and DEPB733 already existed and had been selected earlier). 8. Click OK.
to performing a client install on the Windows Terminal Server, complete the following steps: 1. On the deployment server, go to the \Oneworld\b733\client directory. 2. Create a new directory called \olddlls off of the \client directory. 3. Move the following .dlls from the \client directory to the \client\olddlls directory: Odbc32.dll, Odbccp32.dll, Odbccr32.dll, and Odbcint.dll. 4. Continue performing the steps in the next section to prepare the client install on the Windows Terminal Server.
3. In the [DB SYSTEM SETTING] section, set the Default PathCode parameter to the valid path code you want to be the default (this should match the environment). 4. For the parameter Last User =, remove JDE from this parameter and leave it blank. 5. Save the file, then close it. 9.11.4 Installing OneWorld Client (Interactive Mode) Install the OneWorld Client software on the designated workstation using Interactive Mode. Ensure no other services or open programs are active.
Figure 301. OneWorld Sign-On (Installation) Screen 4. Type the login ID. (For this example, JDE.) Note: This list of packages comes from your user and group profiles for deployment preferences. 5. Check the box to the left of each package to install on the client workstation. You can change the drive where OneWorld is installed, but the directory path is always b7. 6. To initialize the package, click Next to continue. Note: This could run for several minutes.
Appendix A. Modify Setup.inf and ODBCDataSource.inf for SQL Server When you prepare to install the OneWorld client on your workstations, you must change two files prior to running Setup.exe. Those files are Setup.inf and ODBCDataSource.inf. We learned during the implementation process of SQL Server 7.0 that unless you modify these files to leave the parameter LastUser= blank, you will have problems loading your client. The Setup.inf and ODBCDataSource.
322 J.D. Edwards’ OneWorld B73.
Appendix B. Special Notices This publication is intended to help IS professionals perform server selection and implementation for J.D. Edwards’ OneWorld B73.3, Microsoft Windows NT Server 4.0, Terminal Server Edition, Oracle8 Enterprise Edition for Windows NT, and Microsoft SQL Server 7.0 on IBM Netfinity. The information in this publication is not intended as the specification of any programming interfaces that are provided by J.D. Edwards’ OneWorld B73.3, Microsoft Windows NT Server 4.
Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments may vary significantly. Users of this document should verify the applicable data for their specific environment. Reference to PTF numbers that have not been released through the normal distribution process does not imply general availability.
Appendix C. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. C.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 329. • Netfinity Server Management, SG24-5208 • IBM Network Station Manager Release 3 Guide for Windows NT, SG24-5221 • Implementing Lotus Domino Connector and J.D.
• http://www.pc.ibm.com/us/server/sguide/ • http://www.pc.ibm.com/us/netfinity/ • http://www.pc.ibm.com/us/networkstation/ • http://www.redbooks.ibm.com/ • http://www.pcco.ibm.com/us/techlink/wtpapers/hotplug.html • http://www.ibm.com/Services/ • http://www.pc.ibm.com/us/infobrf/updconn.html • http://www.pc.ibm.com/us/netfinity/index.html. • http://www.ibm.com/erp/jdedwards/sizings/index.html • http://service.boulder.ibm.com/nc • http://www.microsoft.com • http://www.microsoft.
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided. • Redbooks Web Site http://www.redbooks.ibm.com/ Search for, view, download or order hardcopy/CD-ROM redbooks from the redbooks web site. Also read redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks site.
IBM Redbook Fax Order Form Please send me the following: Title Order Number First name Last name Company Address City Postal code Country Telephone number Telefax number VAT number Card issued to Signature Invoice to customer number Credit card number Credit card expiration date We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment. 330 J.D. Edwards’ OneWorld B73.
Index NC Navigator 264 Netscape Navigator 256 installation of J.D. Edwards’ OneWorld 109, 185 Installation Package Package Workbench 231, 315 Installation Planner defining the for WTS 289 defining the plan 193 Installation Workbench 226, 309 Data Source Workbench 228, 312 Environment Workbench 229, 313 Integrated Solutions 2 ITSO lab environment 4 Numerics 128-bit version - NC Navigator 264 A additional products autorun.
NCD 255 Netscape Navigator installation 256 Network Station 251 Network-Centric Computing 2 NSMAdmin 268 NSMUser 268 O Oracle8 for Windows NT 19 P porttest 236 prerequisites 253 R RAID support 39 Remote Desktop Protocol 14 S Size of Installed Directories 252 W Windows NT Server 4.0, Terminal Server Edition 13, 14, 251 advantages 13 backup domain controller 251 installation 254 primary domain controller 251 software components 251 stand-alone server 251 332 J.D. Edwards’ OneWorld B73.
ITSO Redbook Evaluation J.D. Edwards’ OneWorld B73.3 and Windows Terminal Server for IBM Netfinity SG24-5842-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: • Use the online evaluation form found at http://www.redbooks.ibm.com • Fax this form to: USA International Access Code + 1 914 432 8264 • Send your comments in an Internet note to redbook@us.ibm.
Printed in the U.S.A. J.D. Edwards’ OneWorld B73.
