Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT Bill Sadek, Herman Kummler, Akash Saxena, Sandro Thierbach International Technical Support Organization http://www.redbooks.ibm.
International Technical Support Organization Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT November 1998 SG24-5219-00
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix E, “Special Notices” on page 151. First Edition (November 1998) This edition applies to SAP R/3, Release Number 3.1H and 3.1I of SAP R/3 for Windows NT, for use with the Microsoft Windows NT Server 4.0. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 678 P.O.
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 0.1 Comments Welcome . . . . . . . .
2.10 BIOS and Firmware Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10.1 Netfinity 7000 System BIOS Update . . . . . . . . . . . . . . . . . . . . . . . 2.10.2 ServeRAID BIOS and Firmware Update . . . . . . . . . . . . . . . . . . . . . 2.10.3 Hard Disk Drive Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.11 Configurating the Advanced System Management Adapter . . . . . . . . . . 2.12 IBM Netfinity 7000 System Configuration Utility . . . . . . . .
4.3.12 eNetwork Communications Suite . . . . . . . . . . . . . . . . . . . . . . . . . .108 4.3.13 eNetwork Host On-Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 4.3.14 DataJoiner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 4.3.15 IBM Flowmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 4.4 SAP R/3 Data Solutions using IBM ADSM. . . . . . . . . . . . . . . . . . . . . . . .109 4.
List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. © Copyright IBM Corp. 1998 Bidirectional SSA Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 SAP R/3 Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Layered Architecture of the R/3 System . . . . . . . . . . .
51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. viii Assign Home Directory to ADM . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Change Permissions for Everyone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 User Rights Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. © Copyright IBM Corp. 1998 Netfinity 7000 Bios and Driver Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 On-Battery Run Time in Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 On-Battery Run Time for Selected Server Models . . . . . . . . . . . . . . . . . . . . . . 21 Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Preface Netfinity servers have grown in processor power and storage capabilities at an exponential rate. This fact, coupled with high availability and clustering techniques, has led to increased sales in this market segment. Mission-critical applications such as SAP are increasingly being installed on this platform. Half of all new SAP licenses are on Windows NT. This redbook will help you install, tailor and configure SAP R/3 on a Netfinity server.
Thanks to the following people for their invaluable contributions to this project: David Laubscher, Netfinity Server Technical Support Services Phil Horwitz Martha Centeno Mchael Riley Marc Shelley 0.1 Comments Welcome Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other Redbook in one of the following ways: • Fax the evaluation form found in “ITSO Redbook Evaluation” on page 165 to the fax number shown on the form.
Chapter 1. Introduction This chapter covers in detail why you should proceed with IBM Netfinity Servers and discusses the Netfinity technology advantage and High Availability features. The chapter also discusses SAP, its architecture and various SAP releases. 1.1 Why Netfinity Servers? The IBM Netfinity Server family is a new generation of enterprise systems that offers you power, scalability, control and service.
1.1.1.1 Disk Space for SAP R/3 The SAP R/3 system is a data-intensive application with huge databases and demands unusually large amounts of disk storage. It transfers massive blocks of information so you will need a technology that is robust, reliable and scalable. You have a huge choice of internal and external hard disk subsystems for best performance and data reliability.
Note For your SAP R/3 environment, we recommend you use only the RAID adapters to implement RAID technology with high-performance and data availability. The common SCSI adapters are very useful for connecting backup devices or for smaller test-and-development environments to build software RAID systems. The supported maximum number of PC ServeRAID II SCSI Adapters you can use in any one server is five.
Figure 1. Bidirectional SSA Loop SSA connectivity is extremely adaptable and it requires only thin copper cables to connect devices together. As SSA is a serial communication protocol it only needs two twisted-pair copper cables for a full-duplex data transfer between two devices. Because you can use thin copper cables, the quality and the protection of the cables is much better than with SCSI.
Up to three SSA RAID Adapters can be installed in the Netfinity 7000. This means that up to 288 disks can be connected to one server. With 9.1 GB disks, this equates to 2.6 terabytes of online storage. Note: In your RAID configuration planning, remember that Windows NT restricts the number of usable data and system partitions throughout the amount of available drive letters. At the moment you can connect only hard disk drives to an SSA adapter.
1.1.2.1 Netfinity Manager The Netfinity Manager Software is included in every delivered IBM PC Server and Netfinity Server. Netfinity Manager is a powerful system management tool that runs on IBM and non-IBM machines. You can manage your workstations and servers locally or remotely over your network, a serial link or even the World Wide Web. It always gives you current information about the status of your machines. 1.1.2.
• A new major enhancement of service and support for Netfinity servers is the Call Home remote support, using the latest technology advances delivered by the IBM Netfinity 7000. Once available only in typical mainframe environments, it is now available for an Intel processor-based server. If your server experiences a problem, it will dial IBM to set in motion the right level of support to keep your system up and running.
Figure 2. SAP R/3 Modules The applications in R/3 are modules designed to tap the company’s performance potential. They link operational steps to forge automated workflow chains, control the flow of information from one department to another, and connect the company with its customers and suppliers. 1.3 Why R/3 Applications Excel • R/3 brings together people who work on shared tasks within the same company, in a network of companies, or in their dealings with customers and business partners.
• Include enhancements to R/3 applications, such as systems for production optimization and transportation planning. • Open up new business opportunities with electronic commerce (seamless integration of R/3 with Internet). • Use Java Technology to make R/3 available to your users with a familiar GUI on the Internet. • Include fax, electronic mail, optical archiving systems, and multimedia tools in the R/3 System's business applications.
middleware, or basis layer, is that portion of an R/3 system that is ported to specific environments as written in C and C++. The ABAP/4 Development Workbench is the SAP programming environment used to develop client/server applications. The programming is done using SAP 4GL ABAP/4 language. 1.6 Client/Server R/3 Architecture In this section we discuss briefly the fundamental architecture of the R/3 system.
assigned a primary role by the dispatcher that will control, to a certain degree, what type of work will be performed by that work process. The number of work processes and the types that can exist for an instance are controlled by the instance profile. The duration of a work process is the time between screen input and screen output from the presentation server. The work process starts a commit before the output is displayed to the screen.
of new functions that improve your value-chain management and time to market. In addition to these features, SAP will ship two industry-specific solutions as components of the standard system: R/3 Retail for the retail sector and R/3 Public Sector for public institutions. 1.8 High Availability SAP R/3 is a business-critical network application and users are usually sensitive about unplanned system idle time resulting from server breakdowns.
• Auto recovery features if the operating system hangs IBM ServeRAID II Adapter • • • • • RAID-0, RAID-1, Advanced RAID-1 and RAID-5 capabilities Hot-Spare and Automatic rebuild capabilities RAID array spanning over three SCSI channels MSCS enabled Optional 8 MB battery backup cache 1.8.2 High Availability on the Operating System Windows NT implements some fault tolerance and high availability features as well.
1.8.4 Clustering For an additional level of high availability, clustering solutions for your Netfinity Servers are obtainable. IBM offers a diversity of high-availability clustering choices: • Microsoft Cluster Server (MSCS) for a shared-disk configuration • Vinca High Availability offerings for a shared-disk configuration • Vinca StandbyServer for a mirrored-disk configuration A clustering solution will prevent the R/3 System from being unavailable for the customer if a hardware or software failure occurs.
failing server comes back online and takes over its applications, then this process is known as fail back. The second phase of Microsoft Cluster Server will implement failover with more than two servers and the third phase will incorporate workload balancing and cluster management solutions for NT servers. IBM has certified three fundamental hardware configurations for Microsoft Cluster Server. They are listed on the Microsoft Hardware Compatibility List (HCL).
16 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Chapter 2. Configuring the Hardware and Installing Windows NT This chapter and Chapter 3, “Installing the SAP R/3 Base System” on page 89 describe an easy way to set up SAP R/3 on your system. The chapters guide you through the several steps required to assure a reliable SAP R/3 system. The installation steps focus on the following hardware and software installations.
Type the product name, such as Netfinity 7000 or ServeRAID, in the search field and you will get a list of all needed drivers and diskettes.The following table provide an overview of the diskettes needed during this installation and show the latest versions at the time of publication. Table 1. Netfinity 7000 Bios and Driver Diskettes Category Diskette Packages Netfinity 7000 BIOS/Flash Update System Configuration ServeRAID Adapter BIOS/Firmware Configuration Administration Supplemental Programs 4.
A short-term increase in voltage, typically lasting at least one hundredth of a second. Surges are caused by the stopping of nearby high-powered electrical motors such as elevators. Computers are designed to receive power within a certain voltage range. Anything outside of this range will stress delicate components and cause premature failure. • Noise: Noise is a phenomenon where another type of wave form is superimposed on the normal sine wave of power.
• APC Smart-UPS 3000 SU3000RMB, 3000 volt ampere/2250 watt,rack-model, part #94G6676 (120 VAC) • APC Smart-UPS 3000 SU3000RMiB, 3000 volt ampere/2250 watt, rack-model, part #94G6677 (220-240 VAC) 2.2.2 UPS Sizing UPS sizing calculates the sort of UPS you will need for your specifications. You have to determine two factors to size your UPS: 1. The total load protected by the UPS in volt-amps 2. The needed on-battery run time Use the following checklist to determine the total load: 1.
VA LOAD SU700NET SU1000NET SU1400 NET SU1400RMB SU3000RMB 800 - 9 15 11 33 900 - 7 12 9 29 1000 - 6 11 8 26 1200 - - 8 6 20 1400 - - 7 5 16 1600 - - - - 13 2000 - - - - 9 2200 - - - - 8 2500 - - - - 6 3000 - - - - 4 Note: Your needed on-battery run time depends on the time for your shutdown procedure. Another approach might be to choose a more powerful UPS, which will guarantee a few hours of battery power.
PowerChute plus software in the Back-UPS mode on the servers which are connected to this basic ports. The computer interface port on the UPS is an advanced port with advanced notification and management features.
Shutdown Modes: 1. Confirmed Shutdown Mode The Interface Expander shuts down the UPS after all servers that are connected to the three ports have reported that they are shut down. 2. Until Low Battery Shutdown Mode A similar mode to the UPS standard operation. The Interface Expander shuts down the UPS after the low-battery time interval. 3. Time Shutdown Mode In this mode the UPS operates on battery for a user-specified length of time before the Interface Expander shuts down. This is done by DIP switches.
External Disk Subsystems If possible always connect external disk subsystems to the same UPS system as the server where their data cables are connected to.
Which Modules Should Be Installed? • For the servers connected to a UPS serial port that you want to be monitored, install the monitoring service (UPS Monitoring Module). • For UPS monitoring and configuration on this server, select the graphical user interface program (User Interface Module). • You don't have to install the user interface on the monitored server. You can remotely monitor and configure a server over the network from another machine. This machine need not be connected to a UPS port.
The SAP R/3 system on-line documentation can be installed on a stand-alone Windows 95 or Windows NT workstation from the SAP installation package without the R/3 system running. To find the related information select in the on-line documentation the following: Basis Components > System Administration > Computer Center Management System > R/3 System Administration > Starting and Stopping the R/3 System > Start and Shutdown Processing under Windows NT.
U:\usr\sap\RDU\SYS\profile>dir Volume in drive U is sapnt Volume Serial Number is 98E6-6C0B Directory of U:\usr\sap\RDU\SYS\profile 04/24/98 04/24/98 04/09/98 04/15/98 04/15/98 04/15/98 04/14/98 04/21/98 04/21/98 04/15/98 04/15/98 04/13/98 09:10a
. 09:10a .. 03:25p 1,134 DEFAULT.BAK 02:54p 1,349 default.pfl 03:57p 7,396 RDU_D00_itsosap2 03:57p 4,069 RDU_D00_itsosap2.BAK 09:31a 7,159 RDU_DVEBMGS00-itsosap1.ng 01:09p 7,134 RDU_DVEBMGS00_itsosap1 01:09p 7,006 RDU_DVEBMGS00_itsosap1.• Shut down remotely all R/3 application instances on application servers that are connected to another UPS and then stop remotely their R/3 application instance services. • Shut down remotely the R/3 central instance if it connected to a different UPS system and then stop remotely its R/3 central instance service. • Shut down the database. • Shut down the operating system. 3. On a database server with central instance • Notify all R/3 users aboutan impending system shutdown.
Information about installing and using PowerXtend with Netfinity Manager is found in Netfinity Server Management, SG24-5208. PowerChute and PowerXtend must be installed on both the Netfinity Manager and any machine whose UPS information you want to manage via Netfinity Manager. PowerChute plus must be installed before installing PowerXtend. You can also use the PowerXtend module and the Netfinity Manager with the Alert Manager to execute a batch file and shut down your system if the utility power fails.
Remember One advantage of the Pentium Pro processor in SMP environments is that every processor has its own integrated second level cache. As the second level cache is integrated on the processor it works with the same clock speed as the processor itself. In older Pentium SMP environments the second level cache and shared memory were integrated on the system board. 2.3.2 Installing the Processor Upgrade The Netfinity 7000 comes standard with 256 MB main memory and one processor installed.
Figure 6. System Board Netfinity 7000 Every processor card contains two Zero Insertion Force (ZIF) sockets. Figure shows the locations of the ZIF sockets on the processor cards. The lower socket is Socket #1 and upper socket is Socket #2. The ZIF sockets are compatible with Intel’s Socket 8 specification. Each board may contain one or two processors, for a configurable range from one up to a total of four processors.
Figure 7. Processor Card Netfinity 7000 The population order is defined by the number of processors you want to install on the processor cards. Table 5 shows the different supported population order for 1, 2, 3 or 4 processors. As example for a two-way processor system, one Pentium Pro processor must be installed on the socket #1 on the primary processor card and one on the socket #1 on the secondary processor card. Other processor configurations are not supported. Table 5.
Note Normally you do not need to change any jumper settings on the processor cards for the processor upgrade. But if you upgrade a Netfinity 7000 Pentium Pro 200 MHz 512 KB second level cache model to a Pentium Pro 200 MHz 1 MB second level cache model then check and change the cache size jumper settings on the jumper block J1C1 for both settings on the processor cards. Figure 8.
• The memory board contains four banks, arranged in 16 DIMM connectors and supports four-way memory interleaving. See Figure 9 for the location of the memory module banks and connectors on the memory board. – Bank 0 connectors J2, J3, J4 and J5 – Bank 1 connectors J6, J7, J8 and J9 – Bank 2 connectors J10, J11, J12 and J13 – Bank 3 connectors J1, J15, J16 and J17 • Each bank contains connectors for four memory modules. Three memory-module kits are available: 256 MB, 512 MB and 1024 MB.
Figure 9. Memory Card Netfinity 7000 Table 6 gives examples of possible memory configurations. Table 6. Some Acceptable Memory Configurations 2.5 Installing Adapter Cards in the IBM Netfinity 7000 The Netfinity 7000 system board has six Peripheral Component Interconnect (PCI) bus slots for add-in boards. The PCI subsystem consists of two input/output (I/O) bus segments: a first PCI bus (PCI bus #0) and a second PCI bus (PCI bus #1). Both are independent PCI bus systems.
Architecture (EISA) bus slots for add-in boards. EISA is fully backward-compatible with Industry Standard Architecture (ISA). You can install old or new ISA and EISA add-in boards in your server, which may save your older hardware investments. Figure 10 shows you a block diagram of the Netfinity 7000 system architecture. . Figure 10. Netfinity 7000 System Architecture 2.5.
Figure 11 shows the location of the PCI buses on the Netfinity 7000 system board. The PCI slots 4 to 6 are the expansion slots of the second PCI Bus. Figure 11. PCI Slots on the Netfinity 7000 System Board But if you use multiple RAID or network adapters, then distribute every adapter over both PCI buses.
That is also true for hard disk drives. If a hard disk drive connects to the on-board adapter and a hard disk drive connects to an additional hard disk controller in a PCI slot, and the priority of the on-board adapter is higher, then the system will always try to boot from the on-board adapter if an operating system is installed or not, unless you disable the boot capability of the on-board adapter (Disable BIOS). Then the status bootable device is removed from the device connected to the on-board adapter.
The system will then disable the Basic Input Output System (BIOS) and release its system resources for every installed ServeRAID adapter except the BIOS of the ServeRAID adapter with the highest boot order priority. That is especially true in the case of the ServeRAID adapter and the Netfinity 7000 this one plugged in the PCI Slot with the lowest number. This is also the adapter where your operating system is booted. For the highest boot order priority, see 2.5.2, “Boot Order Netfinity 7000” on page 37.
2.5.5 Redundant Network Interface Cards A high-end server system such as the Netfinity 7000 with all its high-availability features is useless if a single NIC fails. The server is running but not on the network and the users cannot work with it. Implementing multiple NICs in your SAP R/3 and database servers helps you to provide a higher level of availability and eliminate the NIC as a potential single point of failure. All IBM Netfinity models can operate with multiple network interface cards installed. 2.
2.6 Installing Internal Hard Drives in the IBM Netfinity 7000 You can install 12 hot-swap hard drives in a Netfinity 7000. The hot-swap capability is realized through two hot-swap backplanes in the Netfinity 7000. Each of the two backplanes connects six hot-swap slimline hard drives. These backplanes use the industry standard 80 pin Single Connector Attach (SCA) to connect the Ultra/Wide SCSI II hard drives. Every SCSI device on a SCSI bus needs a unique SCSI ID.
Table 7 and Table 8 show the settings for the backplane jumper block J10. Table 7. Backplane Option Jumper Block (J10) Table 8. SCSI ID Settings on Jumper Block (J10) Refer to IBM PC Server Technology and Selection Reference, SG24-4760 for additional information. 2.7 Installing External Hard Drives in the EXP10 You can install ten half-high or slimline hard drives in an EXP10 storage expansion unit. The EXP10 has four SCSI ports and can be divided in two SCSI buses.
Figure 13. EXP10 Bay SCSI ID Assignments The EXP10 already integrates a SCSI signal repeater to support Wide Ultra SCSI mode with external cable lengths up to 2 meters. Figure 14 shows the rear of the EXP10. To configure a Netfinity EXP10 as a single 10 drive SCSI channel, one external SCSI cable is attached from the SCSI adapter to the SCSI bus 1 IN connector in the unit. The 0.
Figure 14. Rear of the IBM Netfinity EXP10 Storage Expansion Unit We would prefer the configuration with two SCSI buses when the EXP10 is connected to the database server. You can distribute ten hard disk drives over two SCSI channels. The ServeRAID adapter supports RAID arrays over several channels and already has two external ports. You can also use the third ServeRAID channel for external SCSI expansion units. This is provided by the option: IBM Third Channel Cable, part #76H5400.
Limitations of the new 9.1 GB 10K rpm drives The Netfinity EXP10, will only support a total of 8 x 9.1 GB 10K rpm HDDs (specifically, part number 01K7968). IBM will support mixed configurations of these drives. A flyer will be included with this drive option that specifically recommends to the customer that the middle two slots be populated with the dummy trays. The middle two slots run hottest and so should be left with the dummy trays only. Whatever the mixed configuration is, when even a single 9.
Manufacturer Part Number DRAM Type Size Fujitsu MB814260-7-PJRD OR -60 256KBx16 512KB Toshiba TC514260BJ-70 OR -60 256KBx16 512KB Micron MT4C16257DJ-7TR OR -6 256KBx16 512KB Oki MSM514260A-70JSTR 256KBx16 512KB Hyundai HY514260BJC-70 TAPE/REEL 256KBx16 512KB Siemens HYB514171BJ-70 256KBx16 512KB Siemens HYB514171BJ-70 TAPE/REEL 256KBx16 512KB Samsung KM416C256BJ-7T OR -6 256KBx16 512KB Samsung KM416C256AJ-7T OR -6 256KBx16 512KB 256KBx16 512KB 256KBx16 512KB Note:
2.9 IBM Netfinity 7000 Power and Cooling The IBM Netfinity 7000 Server chassis is divided in two parts. The upper part contains the system board and its components. Three hot-swap cooling fans provide cooling redundancy, which means that the server can continue to operate even if a fan fails. Nevertheless, the failing hot plug fan should be replaced as soon as possible to regain the cooling efficiency and maximum reliability.
Note: Please read the README file on the Netfinity 7000 BIOS flash update diskette. 1. Unpack the downloaded Netfinity 7000 BIOS flash update diskette image file to a diskette. 2. Make sure you have recorded any setup or SCU changes you may have made before you do the BIOS update. 3. Insert the diskette in your floppy diskette drive and ensure that the diskette is not write protected. 4. Reboot the server from the floppy drive. 5.
A:>ADDVPD /B:sssssssss /M:8651fff In the above command put the 7-digit serial number where the s’s are and the 3-digit feature number where the f’s are (along with the 8651 model number). This information is located on the serial number label on the front cover. 17.At the next boot the POST will display the VPD banner with the information you enter. 2.10.2 ServeRAID BIOS and Firmware Update Two updates are available for the ServeRAID adapter: a BIOS and a firmware update.
1. Unpack the downloaded IBM ServeRAID and ServeRAID II BIOS/Firmware flash update diskette image file to a diskette. 2. Insert the diskette in your floppy diskette drive and reboot the server. 3. The following menu appears: IBM DOS 6.1 Startup Menu ======================== 1. 2. 3. 4. 5. ServeRAID ServeRAID ServeRAID ServeRAID ServeRAID II, II, II, II, II, BIOS and FIRMWARE update BIOS update only FIRMWARE update only upgrade/add BIOS - all adapters upgrade/add BIOS to first adapter Enter a choice: 4.
1. 2. 3. 4. 5. 6. Update drives attached to the PCI Adaptec SCSI Controllers Update drives attached to a single ServeRAID or ServeRAID II Adapter Update drives when there are 2 ServeRAID II Adapters installed Update drives attached to the IBM F/W PCI-Bus RAID Adapter Update drives attached to the IBM F/W Streaming RAID (Micro Channel) Check drives attached to the 704 Mylex PL Raid Adapter Enter a choice: 5. Select choice 2.
Figure 16. Main Menu ASMA Configuration Utility 4. Select 1. Configure Service Processor. 5. Select port address 200h and interrupt 5. 6. Check your settings by selecting 2. View Service Processor Configuration. 7. Select the port 200h again. 8. The adapter should respond with the configured interrupt and port address. Figure 17. View Service Processor Configuration 9. Select 3. Update Service Processor to update the Service Processor Firmware.
3. Remove the battery from the adapter and set it aside. 4. Carefully short the battery contacts together with a small paper clip or a small metal screwdriver for 5-10 seconds. This resets the adapter and clears the configuration. 5. Reinstall the battery on the adapter. 6. Reinstall the adapter. After you reset the adapter and clear the configuration, or replace the battery, you must reconfigure the adapter as described above.
Figure 18. System Configuration Utility CD Boot Menu a. Choose 1. Run System Configuration Utility a. Reply to the next two questions with N. 3. If you boot from the SCU Diskette then select 1. Execute AMISCU in the following menu. Figure 19. System Configuration Utility Disk Boot Menu 4. The SCU will start and show you the SCU main menu. Figure 20.
2.12.1 SCU Settings for the ASMA Card The Netfinity 7000 server requires a configuration file to configure ISA or EISA adapters. The configuration file for the ASMA card is located on the System CD-ROM and the System Configuration Diskette. The file is automatically recognized through the SCU. The following steps depend on whether your adapter was already entered in the SCU program or not. 1. At the SCU program main menu screen, select Add and Remove Boards. 2.
Figure 22. ASMA EISA Config File a. Then select the EISA slot where the adapter is installed. a. Press Esc to go back to the system configuration program main menu. 7. You do not have to change the Configuration Settings. The ASMA card is automatically set to port 200h and interrupt 5 in the SCU. 2.12.2 SCU Settings for the NT Installation Please check the following settings before you install Windows NT on the Netfinity 7000. 1. At the SCU program main menu screen, select Change Configuration Settings.
Figure 24. APIC Settings 5. Scroll the list down to BOOT SUBSYSTEM GROUP and set the First Boot Device to Boot IDE CD-ROM Hard Drive Image, the Second Boot Device to Boot Floppy and the Third Boot Device to Boot Hard Disk. You can also set the entry Perform Memory Test on Warm Boot to Disable. This saves a lot of time as you have to reboot the server often during the system and Windows NT intallation. Figure 25. BOOT Options 6.
2.12.3 Configuration ServeRAID Adapter The next steps cover the RAID configuration for the Windows NT installation with the ServeRAID offline tool from the IBM ServeRAID and ServeRAID II configuration diskette. The Windows NT installation for SAP R/3 is usually made on the 4.5 GB hardware mirrored hard disk drives.
To load the program insert the IBM ServeRAID and ServeRAID II configuration diskette in the floppy drive. Then reboot the server from the floppy drive. The RAID configuration utility is automatically loaded. Figure 27. ServeRAID Configuration Utility Main Menu 2.12.3.1 ServeRAID Adapter Settings and Array Configuration For this configuration, it is assumed that all drives you want to use are recognized by the ServeRAID adapter and in ready state (RDY).
Figure 28. Initialize Configuration 3. To initialize the configuration select 2. Initialize Configuration. 4. Read the warning and press any key to confirm. Note: This procedure will delete all older RAID configurations and reset all setup values of the ServeRAID adapter to the defaults, such as stripe size, write policy, SCSI transfer mode and so on. 5. Confirm the initialization by answering Yes. 6. Press Esc twice to go back to the configuration main menu.
Figure 29. Set SCSI Transfer Rate 5. Press F10 and confirm with Yes to save your changes. 6. Press any key. 7. Press Esc twice to go back to the configuration main menu. Check Extended BIOS Mapping The range of older IBM RAID adapters supports only BIOS mappings of 2 GB. The BIOS Compatibility Mapping setting in the ServeRAID adapter is to support RAID Arrays created by the older RAID adapters. You have to set this parameter to Extended BIOS Mapping (8 GB) if you want to boot partitions greater than 2 GB.
Figure 30. Set BIOS Compatibility Mapping 5. Press Esc twice to go in the configuration main menu. Changing the RAID Parameters There are two RAID parametersthat allow you to fine tune the RAID subsystem: s the Stripe Unit Size and the read ahead option. Each of these options affects all arrays and all logical drives configured on the adapter. The Stripe Unit Size is the amount of data written to a given disk before writing to the next disk in the array.
system I/O request size, and no read ahead to the end of the stripe unit size is performed. Data Will Not Be Lost The read ahead setting can be modified without destroying data in a logical unit. To obtain optimum values is nearly impossible in a multitasking environment with many different applications, or when using SAP R/3, which has many different modules and varying and often changing user requirements.You may test your special environment for a long time and still hardly see a difference.
Creating Array and Logical Drive To create your logical drive for the Windows NT installation do the following: 1. To create a RAID array select 4. Create/Delete/Copy Log Drive in the ServeRAID adapter configuration main menu. 2. Select 3. Create Disk Array. 3. Choose drives for the array and press Enter on every drive you wish to place in the array. 4. Press Esc to create the array. 5. To create a logical drive select 4. Define Logical Drive. 6.
16. Confirm the warning about saving configuration to a diskette by answering Yes to quit the program. The configuration can be saved after you finished all steps of the installation. 17. Go on to the Windows NT installation. Note: Please remember only one logical drive should be created for the Windows NT installation process. If any other drives are defined and you are trying to install to a partition greater than 1 GB, this will cause problems.
6. Press Enter to toggle between Write-Through (WT) and Write-Back (WB) mode. For write caching set it to WB. Figure 33. Changing the Write Policy of the Logical Drives 7. Press Esc twice to go back to the main menu and leave the program. 2.12.3.3 Backing Up the ServeRAID Configuration After you finish installing Windows NT, creating all other logical drives, and changing all RAID parameters, you should save your ServeRAID configuration to a diskette.
Figure 34. Back Up the ServeRAID Configuration You can use your ServeRAID configuration diskette to save the file on it. 5. Press ESC twice to leave the ServeRAID configuration program. 2.12.4 Protecting the Netfinity 7000 The following security features help you to protect your Netfinity 7000 server. The settings are done in the BIOS Setup program or in the SCU.
administrative and user passwords are enabled, either can be used to boot the system or enable the keyboard and/or mouse, but only the administrative password will allow Setup and the SCU to be changed. To disable a password, change it to a null string. • User password controls access to the system. To control access to using the system, set a user password and enable it through Setup or the SCU. To disable a password, change it to a null string.
2.13.1 Windows NT Installation 1. Insert the IBM PC ServeRAID Device Driver Diskette in the floppy diskette drive and the Windows NT boot CD-ROM in the CD ROM drive and then reboot the server. 2. Press F6 at the Windows NT setup message: Setup is inspecting your computer’s hardware configuration... . 3. At the next screen, select S to specify additional devices. 4. Select other from the list of SCSI adapters. 5.
Note: The partition size should range from 300 MB to no greater than 2000 MB for FAT partitions, and from 300 MB to no greater than 4000 MB for NTFS partitions. We recommend a partition size of 4000 MB for the SAP installation. 16.When prompted for the partition, select the less than 4 GB partition that was created previously. 17.Select FAT file system or NTFS file system and press Enter to format the installation partition. 18.Specify an installation directory and press Enter (the default is C:\WINNT). 19.
Server Type The only way to change the server type is to reinstall, so choose carefully. Server types include: • Primary Domain Controller (PDC): This server tracks changes made to accounts of all computers on the network. Only one is necessary per domain. • Backup Domain Controller (BDC): This server acts as a backup to the PDC. Multiple BDCs are allowed per domain. • Stand-Alone Server: This serves as neither a PDC or BDC. The server can be a member of a domain or a workgroup.
37.If your adapter is supported but not detected by Setup then do the following: • Click Select From List..., then Have Disk.... • Specify the path to the driver and press Enter. • Click OK to choose the driver and OK again to return to Setup. 38.When you are finished selecting network adapters, press Enter from the Windows NT Server Setup screen. 39.Select Network Protocols to install and press Enter when finished. Note You have to install TCP/IP protocol for SAP R/3.
2.13.2 Install Windows NT 4.0 Service Pack 3 Note: You will need about 75 MB of free disk space to unpack the Service Pack. Disconnecting Your UPS Microsoft recommends that you disconnect any UPS before upgrading your Windows NT release. This precaution applies to APC UPSs. During upgrades, Windows NT sends character strings to the serial ports.
Figure 35. Logical Drive for the Second Window NT Installation Note Create the logical drive for the second Windows NT before you create, format and partition additional logical drives for data space and the SAP R/3 installation. The order in which you create the logical drives is the scan order in which the Windows NT installation program will recognize logical drives and any created partitions. Repeat the steps for Windows NT and Service Pack installation.
Figure 36. Example boot.ini File for Two Windows NT Installations The disk value determines the adapter number, the rdisk value the logical drive and the partition value the partition number. 2.13.4 Creating an Emergency Boot Disk With the emergency boot disk you can boot your two Windows NT installation from a floppy disk.
You will find further information about the ServeRAID Administration and Monitoring utility and logical drive migration in the redbook Implementing PC ServeRAID SCSI and SSA RAID Disk Subsystems, SG24-2098. 2.13.5.1 Installing the Administration and Monitoring Utility 1. It is assumed Windows NT is running. 2. Insert the IBM ServeRAID and ServeRAID II administration and monitoring diskette in the floppy disk drive. 3. Open the Windows NT start menu and click on Run.... 4. Type A:\setup and press Enter. 5.
Figure 38. Create a New Array and Logical Drive 1. Select the ready drives (RDY) you wish as part of the new array and click OK. Figure 39. Selecting Hard Drives for the New Array 2. Select a RAID level and click OK to create the logical drive.
Figure 40. Selecting RAID Level and Size of the New Logical Drive 3. Repeat these steps to create additional disk space. 4. Don’t forget to Initialize the new created logical drives. The synchronization for RAID level 5 logical drives starts automatically with the ServeRAID II adapter and is running in the background. 5. Click on a button for a logical drive in the administration and monitoring utility main view to initialize this drive.
Figure 41. Initialize Logical Drive 6. Select the Initialize button to initialize this logical drive. 7. You can now go to the following steps and create operating system partitions on the new logical drives and format these with a file system. 2.13.6 Preparing the Disk Space for the SAP R/3 installation You can now create partitions with the Windows NT graphical interface Disk Administrator to use the disk space on the new logical drives.
Figure 42. Windows NT 4.0 Disk Administrator • Click with the right mouse button on a disk where you want to create a partition to open a local pop-up menu. • Select Create... to create a primary or click on Create Extend... to create an extended partition. • Select the size of your partition and create the partition. If you selected Create Extended... in the step before, you first have to select Create... in the local pop-up menu on your new partition to create a partition in your extended partition.
• It is a direction of SAP to format each new partition for your SAP R/3 installation with the NTFS file system and a cluster size of 4096 bytes. • Set the parameters for the file system and cluster size and press OK to format the partition. • Repeat the steps for every new partition. Note: We recommend that you save the new disk configuration with the Repair Disk Utility as described in 2.13.10, “Repair Disk Utility” on page 87. We recommend you to repeat the procedure after the R/3 installation. 2.13.
Figure 44. Forground Session Priority There are three settings for the boost indicator that determine the priority of foreground applications. • Maximum For the best response time for the foreground programs. • Middle Gives background programs a better response time but still gives more processor time to the foreground programs. • None Gives all programs equal amounts of processor time.
• Click on the Change button. You will see the following dialog box. Figure 45. Page File Size and Distribution You can set the Initial Size and the Maximum Size of the paging file for a specific drive. SAP recommends a page file size at least three times as much as your main memory. This is valid for all R/3 application and database servers. If you install an R/3 central server (database + application at one machine) calculate an additional 500 MB for the page file size.
Minimums and Maximums When specifying a page file size, increase the minimum value to equal the maximum value. When the page file needs to grow past the minimum value, it will slow down your server in the process. By setting both values equal, you will waste some disk space but the system does not need to spend time sizing the page file.
Figure 47. Server Service Tuning You can specify how much memory is reserved for the operating system indirectly by specifying how much memory (relatively) to give to server processes. You have four choices: 1. Minimize Memory Used: this choice will minimize the memory used for disk cache and maximize the memory available for the operating system. However, on file servers, the resulting performance would not be desirable. Therefore, only use this choice for Windows NT workstations. 2.
C:\>a: A:\>\nt\setup.exe To continue the installation of the Service Processor DLL file and device driver, press Enter. Press any other key to quit. SMAddress = 300 SMInterrupt = 5 Copying \nt\IBMSPW.DLL to C:\WINNT\System32\IBMSPW.DLL Copying \nt\IBMSPW.SYS to C:\WINNT\System32\drivers\IBMSPW.SYS The Service Processor DLL file and device driver are installed and started. Press any key to exit. • If you do not first change to the diskette root directory you will get an error message that the SM.
To install the utilities on Windows NT you only need to create a directory on your server and copy the files from the IBM ServeRAID and ServeRAID II supplemental diskette to this directory. The files for Windows NT are located in the \NT directory on the diskette. 2.13.10 Repair Disk Utility After you finish your all SAP R/3 installations we recommend that you update your emergency repair disks created during the Windows NT installation with the repair disk utility on every installed server.
88 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Chapter 3. Installing the SAP R/3 Base System This chapter describes the installation of SAP R/3 Release 3.1G with Oracle on Windows NT. SAP strongly recommends that R/3 only be installed by certified R/3 installers. Please refer to SAP installation documentation for further details.
• Oracle and SAP executables and non-data files on two mirrored 4.5 GB disks • Database files on six 4.5 GB disks in a RAID 5 configuration The application servers were configured with a minimum configuration of a single 4.5GB drive for Windows NT, paging and SAP files. 3.2 Customizing Windows NT Before installing SAP R/3 some changes to Windows NT are required. Please refer to Chapter 2, “Configuring the Hardware and Installing Windows NT” on page 17 before proceeding.
5. Click on Groups. 6. Add the Administrators group to the groups the user belongs to as shown in Figure 50. 7. Click OK. Figure 50. Add User to Group Administrators 8. You must create a home directory only for the ADM user (RDUADM in our example). This is where the installation tools and logs will be kept. At least 20MB is required. The recommended directory is c:\users\ADM. Do the following: • Click the Profile button on the new user screen. • Go to the Local Path field (see Figure 51).
2. Right mouse click on c:\users\ADM. 3. Select Properties. 4. Click on the Security tab. 5. Click on Permissions. 6. Click on Everyone. 7. Change Type of Access to Full Control (see Figure 52). Figure 52. Change Permissions for Everyone 8. Click OK on the Directory Permissions screen. 9. Click OK on the Properties screen. 3.2.3 Add Right to Log on As a Service Two SAP programs will be installed as a Windows NT service by the SAP install program R3INST. R3INST is covered in detail later.
Figure 53. User Rights Policy 7. Click Add on the User Rights Policy screen. 8. Click Show Users. 9. Select SAPService and click Add. See Figure 54. Figure 54. Add Log on As a Service Right to Sapservice 10. Click OK, then OK again. 11. Exit User Manager. 3.3 Installing Oracle This section describes the installation of Oracle Release 7.3.2 for SAP R/3 Release 3.1G. Oracle must be installed before SAP R/3.
2. Start Windows NT Explorer. 3. Find the directory \Nt\Nt_x86\7322\Instal.l 4. Double-click on install.exe. 5. Click OK on the Language screen. You must take the default English_SAP as shown in Figure 55. Figure 55. Oracle Installation Language 6. Enter your company name and the Oracle home directory as shown in Figure 56. and click OK. Figure 56. Oracle Installation Settings 7. Click OK on the Configuration screen (Figure 57). Oracle will be added to your path. Figure 57. PATH Change for Oracle 8.
Figure 58. Select Oracle Products to Install • If you are installing the database instance, click Install to install all selected products. • If you are installing a dialog instance or central instance without database, select only: 1. Required Support Files 7.3.2.2.0 2. SQL*Net Client 2.3.2.1.4 3. SQL*Net Protocol Adapters 9. Click OK on the Information screen about release notes. 10. Click Exit when you return to the Software Asset Manager screen (Figure 59). Figure 59. End of Oracle Install 11.
1. Start Windows Explorer. 2. On the same Oracle CD find the directory \Nt\Nt_x86\Pat_7323\Install. 3. Double-click on orainst.exe. 4. Click OK on all screens. 3.4 Installing SAP R/3 3.4.1 Installing a Central Instance The central instance must be installed first. 1. Log on as ADM. 2. Insert the SAP Kernel CD. 3. Start Windows NT Explorer. 4. Go to the directory \Nt\I386. 5. Double-click on R3inst.exe. 6. Click Continue. 7. Enter the you chose and click OK on the SID selection screen.
Figure 61. Choose Type of SAP Server 15. Select Create a new central instance and click OK (Figure 62). Figure 62. Creating Central Instance 16. On the Central Instance screen, leave the instance ID 0 and the memory equal to all the memory installed on your system. You should not have to change the hostname if you are planning to install the database on this central instance. See Figure 63. Figure 63. Central Instance Parameters 17. Enter \SAPService in the Domain\Account field.
Figure 64. SAP Service Account 18. Assign disk drive letters to the SAP directories on the Required disk space screen. This is done by clicking on a line and typing the drive letter. Assign drive letters to all directories. (Planning for the allocation of SAP files is discussed in Appendix D, “SAP R/3 Sizing and Installation Planning” on page 141). See Figure 65. Figure 65. Assign Disk Drive Letters 19. Click Install/Do i. 20. After install is complete, exit R3INST. 3.
3.5.1 Changing Defaults The default tablespace sizes are contained in the file sapfs.inf in the install directory, c:\users\\install. If you wish to increase the size of any tablespace or if you wish to use hardware mirroring, you must change this file with the SAP utility program SAPPAD. SAPPAD is like Notepad. Proceed as follows: 1. Start a command prompt. 2. Type cd \users\\install. 3. Type sappad sapfs.inf. 4.
Figure 67. Local Drives 6. Select Database-Server, then click OK. 7. Select Standard installation from the installation window (see Figure 68). Figure 68. Database Installation Window 8. All the server options should be checked (see Figure 69). Figure 69. Database Install Options 9. Assign disk drive letters to the Database server directories and the Oracle tablespace sets on the Required disk space screen. This is done by clicking on a line and typing the drive letter.
Figure 70. Assign Disk Drive Letters 10. Click Install/Do it. 11. Locate the file label.asc on the CD and click Open. 12. When prompted "Do you wish to copy the contents of the 1st Export CD to hard disk", click Yes (see Figure 71). Figure 71. Copy Export CD 1 To Disk 13. After the first CD is copied, you will be prompted to locate the file label.asc on the second CD. 14. Insert the second DB Export CD. 15. Locate the file label.asc on the CD and click Open (see Figure 72). Figure 72. Locate label.
16. A log file will be displayed (see Figure 73). This file is in c:\users\\install and can be viewed later. This is the step that will take several hours. Figure 73. R3INST Log File 17. After the database load, insert the Report Load CD. 18. Locate the file EXNTI000.TOC in the DATA directory and then click Open (see Figure 74). This step takes about 10 minutes. Figure 74. Locate File on Report Load CD 19. Exit R3INST. 3.6 Starting SAP R/3 To start SAP: 1.
Figure 75. Starting SAP To stop SAP: 1. Click Stop on the Service Manager window (this does not stop the database). 2. Go to a command prompt. 3. Enter sapdba -shutdown to shut down the database. 3.7 Installing an Application Server To install an application server or dialog instance, proceed as follows: 1. Install the required components of Oracle as described in 3.3, “Installing Oracle” on page 93. 2. Insert the SAP Kernel CD. 3. Click Start/Programs/R3INST and click Continue. 4.
12. Click Install/Do it. 13. After message " Installation of application server finished" (see Figure 77), exit R3INST. Figure 77. Application Server Installation Log 3.8 Post-installation Items There are several additional steps that are required after the database, central instance, and application servers are installed. Please refer to the SAP installation manual in the section called "Completing and Checking the SAP Software Installation".
Chapter 4. IBM’s Software Products that Complement SAP R/3 In this chapter, we discuss IBM’s commitment to Windows NT and the various software products available on Windows NT from IBM that complement SAP R/3. 4.1 IBM’s Commitment to Windows NT When IBM first announced it would deliver much of its software on Windows NT, plenty of eyebrows shot up, because IBM and Microsoft have long been in direct competition and now they would be cooperating.
collective issues. IBM also receives detailed technical support and is included in all Microsoft education and training programs for Windows NT 5. 4.3 Overview of IBM’s Software that Complement SAP R/3 IBM and Lotus offer more than 100 Windows NT solutions. They offer a growing resource to corporate developers, independent software vendors and business partners for creating enterprise-class business solutions on NT and taking advantage of network computing. 4.3.
protocols are involved. You’ll cut development and maintenance costs, deploy business solutions faste, and gain a greater return on that hefty investment you’ve made in systems and resources. 4.3.6 ADSTAR Distributed Storage Manager (ADSM) Searching the heavens for enterprise-wide storage management? All worlds fall easily into orbit around ADSM. It supports the broadest range of platforms, devices and protocols.
• IBM Component Broker • Lotus Bean Machine 4.3.9 Lotus Domino Here's the first application and messaging server that allows you to take advantage of secure, interactive business solutions for the Internet and intranet. You can quickly build, deploy and manage applications to bring co-workers, partners and customers together. Domino provides support for a variety of clients and devices, including Web browsers, Notes clients, and POP3 mail clients. 4.3.
4.3.14 DataJoiner A new class of data access middleware. DataJoiner is a multi-database server that offers your business an unprecedented level of data access. With DataJoiner you view all your data--IBM and multi-vendor, relational and non-relational, local and remote--as though the data were local. You’ll be able to access and join tables located across multiple data sources with a single SQL statement, even without knowing the location of each source. 4.3.
Version 2 or Version 3 server platform, which can be different from the database platform. 4.5 ADSM and SAP: A Powerful Combination ADSM integrates with both your SAP R/3 system and your database tools, enabling the entire environment to be backed up, including database files such as executables, control files, and user data.
Figure 78. Backup/Restore of SAP R/3 System using ADSM In addition to SAP’s Oracle tools, ADSM supports other Oracle backup and restore techniques, including Oracle’s Enterprise Backup Utility(EBU), Oracle8 Recovery Manager(RMAN), and BMC Data Tool’s SQL-BackTrack. For additional details about all of the Oracle ADSM backup techniques, see the redbook Using ADSM to Back Up Databases, SG24-4335. 4.7 SAP R/3 and Archiving ADSM is more than a backup/restore product.
112 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Chapter 5. SAP R/3’s System Management This chapter provides a brief overview of SAP R/3’s systems management and Tivoli’s Module for SAP R/3. 5.1 The Computing Center Management System (CCMS) The CCMS is the SAP R/3 system management solution. It is available as a standard tool. Since in a client/server environment the different components are spread over several hardware servers, it is important to have a systems management tool. CCMS comprises System Monitoring and Systems Management.
5.1.2 Database and Archiving Management A majority of the database administration tasks can be performed within R/3 from the CCMS. CCMS Database Planning Calendar can schedule and track the results of online and offline database backups, log backups, and other operations. A database monitor has been also added to monitor in-depth analysis. Oracle and Informix databases can also be managed using CCMS’s SAPDBA program.
79. The module greatly simplifies the R/3 administrator’s job by correlating all events generated by multiple SAP R/3 instances into one centralized console, offering an unparalleled view of the entire R/3 environment. This gives SAP administrators unprecedented control over their R/3 systems. 5.2.3 Client Installation and Configuration The main difficulty in managing large numbers of heterogeneous R/3 clients is installing and deploying the SAP R/3 graphical user interface(GUI).
When R/3’s shared memory segment generates a less-than-helpful message, the module will drill down to provide more meaningful data to administrators. This ability makes diagnosis and remedy of problems much easier. When R/3 provides a single alert, such as a yellow alert and then doesn’t display subsequent alerts of the same level, the module acknowledges the first alert and displays the additional alerts. This gives the administrator a more accurate view of the SAP environment. 5.2.
5.2.10 TEC Event Server Rule Base The TEC event server rule base provides intelligent event processing and correlation.
5.2.10.5 Automatic Diagnostics Framework The combination of the TEC automated tasks, the Module for R/3 tools, and the R/3 RFC interface makes an excellent framework for developing a comprehensive set of automatic diagnostic tasks. 5.3 IBM Netfinity Manager IBM Netfinity Manager is IBM’s comprehensive hardware systems management tool for your complex system installations in network or stand-alone environments. That includes your server as well as your workstations and non-IBM products.
having all the base services locally, it can include the following extra functions if they are chosen at install time: • • • • Remote Workstation Control Service Processor Enhancement World Wide Web Enhancement Capacity Management 5.3.2 The Client Services for Netfinity Client Services for Netfinity Manager is the managed portion of the system. This is a foundation that provides the underlying services for several levels of administration, including remote system and user management facilities.
– Windows 95 – Windows NT 3.51 or 4.0 – NetWare 3.11, 3.12, 4.1 or 4.11 – Windows 3.x • Netfinity Manager is designed to work with the existing protocols on the network and includes support for: – NetBIOS – TCP/IP – IPX – Serial – SNA (LU. 6.2) (except on NetWare and Windows 3.x) 5.3.4 IBM Netfinity Manager 5.x Functional Enhancements The following items are new in Version 5.
• Microsoft SNA Server Version 2.11 with Service Pack 1 and WCPIC32.DLL dated 01/22/97 or later • ODBC Support Netfinity Manager supports exporting data via ODBC for use on SQL or DB2 database systems. The Netfinity Manager Database Administrator is provided to create, delete and grant access on these databases tables. For more information on Netfinity's database support, see redbook Netfinity V5.0 Database Support, SG24-4808. The following items are new in Version 5.
Figure 80. A Typical Netfinity Manager Main Menu The following full list of functions that are available in a standard installation are briefly discussed below. Complete instructions on how to use each of these services can be found in the online help provided with the product and in the redbook Netfinity Server Management, SG24-5208.
All Services Installed? The GUI program files for ECC configuration, System Partition Access, RAID administration, Predictive Failure Analysis and DMI Browser will be installed regardless of whether your system has the associated hardware features installed. This enables a network administrator to remotely access these services on other systems. But the icons in the Netfinity Manager main menu of these services are available only if the managed systems have certain system configurations.
received, type and severity of the alert, the ID of the application that generated the alert, as well as any text that was generated and any action taken by the Alert Manager. Individual or multiple alerts can be selected from the log and printed for later reference, or deleted once problems are corrected. This service is available for both stand-alone and network use. 5.3.5.
desktop computers will become easier, and desktop computers will become easier to manage in a network. 5.3.5.5 ECC Memory Setup The ECC Memory Setup allows for monitoring of ECC memory single-bit errors, and can automatically scrub, or correct, the ECC memory when errors are detected. Also, you can keep a running count of single-bit errors, and can set a single-bit error threshold that will cause a non-maskable interrupt (NMI) if the ECC single-bit error threshold is exceeded.
ANSI-standard SMART SCSI protocol and lead to the setting up of the SMART working Group (SWG). The SMART standard has now been extended to IDE/ATA drives. Netfinity Manager and Client Services for Netfinity Manager for OS/2 or Windows NT support PFA-enabled hard disk drives that conform to the SMART standard. Note: Support for SMART hard disk drives is available only on systems running Netfinity Manager or Client Services for Netfinity Manager for OS/2 or Windows NT.
Otherwise, systems included in a rack group behave exactly like systems included in a system group. You can use the Netfinity Rack Configurator to define a configuration for a rack, then save it to be imported into Netfinity Manager. The Rack Configurator software is contained in the ServerGuide on the Application Guide CD-ROM 3A or the latest version on the World Wide Web at http://www.pc.ibm.com/us/products/netfinity/download.html in the Configurator Tools section. 3.
System-defined keywords are automatically assigned to a remote system, if they have certain hardware or software characteristics. These allow an administrator to group machines of similar configuration. For information on application keywords and a entire list of system-defined keywords, see "Using Application Keywords" in Chapter 22 of the Netfinity Manager User’s Guide. 5.3.5.14 Remote Workstation Control This feature in Netfinity Manager 5.
Warning: Security Not Enabled After installation, one user ID will be defined in the security manager, with all accesses granted. Since this user ID is the user ID, it means that everyone has access to your system. The first step after installation should be to open the Security Manager, and revoke all disallowed actions to . Don't forget to uncheck the box that authorizes security manager access.
directly access and control a remote system’s ASMA card over the Serial Connection Control service. In addition, Service Processor Manager enables you to remotely monitor, record, and replay all textual data generated by a remote system during POST. While monitoring a remote system during POST, you can enter key commands on your keyboard which will then be relayed to the remote system. 5.3.5.
for any of the monitored components. When exceeded, these thresholds will generate user-configured alerts. Data is continually collected from the time the system starts. A sophisticated data-handling technique is used to weigh the individual values, average concurrent samples, and post single values that accurately reflect long-term system activity. This technique allows you to maintain system activity records without creating enormous data files.
You can use the Web Manager Configuration service to limit access to the to specific TCP/IP addresses or ranges of addresses. When enabled, all authorized systems running a Web browser, can access a subset of the Netfinity Manager manager functions. This enables you to do remote system management over the Internet, without having to install Netfinity Manager. Note: The Remote Workstation Control and any of the RAID actions are not accessible from the browser.
Appendix A. Hardware and SAP R/3 Configurations Used for This Book We worked with the following hardware setups and SAP R/3 configurations for this book. 1. Centralized Installation • • • • • • IBM Netfinity 7000 Model 8650-RM0 768 MB of main memory Four Pentium Pro 200 MHz 512KB 2nd Level Cache processors IBM ServeRAID II adapter with the 8 MB Battery-Backup Cache Option 6x4.51 GB IBM Hard Disk Drives in the Netfinity 7000 6x4.
IBM ServeRAID Adapter connections • Channel 1 -- connected to IBM Netfinity 7000 Backplane with six internal 4.51 GB Hard Disk Drives • Channel 2 -- connected to IBM Netfinity EXP10 Storage Expansion Unit SCSI Bus 1 with 3 4.51 GB Hard Disk Drives • Channel 3 -- connected to IBM Netfinity EXP10 Storage Expansion Unit SCSI Bus 2 with 3 4.51 GB Hard Disk Drives Table 10 shows the configuration of ServeRAID arrays, logical drives and operating system partitions. Table 10.
Table 11 shows the disk distribution of the operating system and SAP R/3 installation. Table 11.
136 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Appendix B. Certified IBM Netfinity Server Configurations To run SAP R/3 on Windows NT and Intel-based server platforms, all hardware vendors require a certification by SAP to ensure an appropriate performance and compatibility. This certification is done exclusively through the SAP contractor iXOS Software AG in Munich, Germany. The decisive critical components to certify a server system for R/3 are processor generation, mainboard, main I/O controller.
• IBM PC Server 704 with the IBM PC ServeRAID Adapter is certified for Windows NT 4.0 and as Windows NT 4.0 Application Server for DB2 on an IBM S/390. • IBM PC Server 330 Pentium II model with the IBM ServeRAID II Adapter is certified for Windows NT 4.0. • IBM PC Server 330 Pentium Pro model with the IBM PC ServeRAID Adapter is certified for NT 4.0 and as Windows NT 4.0 Application server for DB2 on an IBM S/390.
Appendix C. IBM Netfinity for Ready-to-Run R/3 Ready-to-Run R/3 is a new concept initiated by the SAP AG Walldorf, Germany. R/3 is considered by many as difficult to implement and to install. This could hinder SAP as they want to increase market share particularly in the small and midrange business areas. Today, implementation time and project costs are additional issues. Ready-to-Run R/3 is a strategic SAP initiative and designed to solve these problems.
140 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Appendix D. SAP R/3 Sizing and Installation Planning IBM offers a facility to existing SAP customers on sizing of Netfinity Servers, according to their environment. This facility is offered through Internet. To make use of this facility and get help on Netfinity sizing, you need to go through Quick Sizer. Quick Sizer is a online sizing tool available from SAP that help customers perform quick sizing for their environment.
Figure 81. Welcome to SAPNet 4. Click on SELF SERVICE in the top bar and you will get to the screen for Services. On the left hand side, click Quick Sizing as shown in Figure 82. Figure 82. SAPNet Self Services 5. The screen shown in Figure 83 gives a brief description of Quick Sizing. On the left hand side, click Start Quick Sizing.
Figure 83. Quick Sizing 6. In the screen shown in Figure 84, enter your customer number and projectname, and then select the option given at the bottom of page I agree. Some sample screens of Quick Sizer are shown in Figure 85, Figure 86, Figure 87, and the final result is shown in Figure 88. You may select the vendor, for example, IBM, in our case.
Figure 84. Start Quick Sizing (Registration) Figure 85.
Figure 86. Start Quick Sizing (Quantity-Structure-Dialog) Figure 87.
Figure 88. Quick Sizer Result Figure 89.
5.4 Installation Planning of Database for the SAP R/3 System This section is divided into three subsections on the basis of the database being used (for example, DB2, Oracle and MS SQL Server). 5.4.1 DB2 Database Server Installation Planning 5.4.1.1 Distribution 1. Distribute database files(:\db2\\sapdata) and archive log files(:\db2\\SQLOGDIR) to different disks. 2. The archive log files should be located on the disk with low I/O.
5.4.1.4 Data Integrity Requirements As data integrity is important in any database management system, hence it is recommended that the file system containing the log files (\db2\\SQLOGDIR) should be mirrored. Note A production system must run in log retain mode. If a test system is not running in log retain mode, all data which has been written since the last complete backup will be lost after a system crash. 5.4.1.
5.4.2 Oracle Database Installation Planning 5.4.2.1 Distribution of SAP Software using RAID It is recommended that a minimum of three logical disk volumes are used to separate the online redo logs, offline redo logs and database files because of safety and performance issues. The online redo logs(\ORACLE\\origlogA and \ORACLE\\origlogB) and the offline redo logs (\ORACLE\\saparch) must reside on different logical disk volumes using RAID 1(Disk Mirroring).
Note: A production Netfinity system running SAP must run in ARCHIVELOG mode. 5.4.2.3 Oracle Control Files The following Oracle control files should be stored on separate disks: \ORACLE\\origlogA\ctrl.ctl \ORACLE\\saparch\ctrl.ctl \ORACLE\\sapdata1\ctrl.ctl 5.4.2.
Appendix E. Special Notices This publication is intended to help specialists and consultants who are responsible for configuring IBM Netfinity servers and SAP R/3 on Windows NT. The information in this publication is not intended as the specification of any programming interfaces that are provided by IBM or SAP. See the PUBLICATIONS section of the IBM Programming Announcement for Nefinity Servers and SAP R/3 for more information about what publications are considered to be product documentation.
The following document contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples contain the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Reference to PTF numbers that have not been released through the normal distribution process does not imply general availability.
Appendix F. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. F.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 155. • Implementing PC ServeRAID SCSI and SSA RAID Disk Subsystems, SG24-2098.
154 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at http://www.redbooks.ibm.com/.
How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: • Online Orders – send orders to: In United States In Canada Outside North America IBMMAIL usib6fpl at ibmmail caibmbkz at ibmmail dkibmbsh at ibmmail Internet usib6fpl@ibmmail.com lmannix@vnet.ibm.com bookshop@dk.ibm.
IBM Redbook Order Form Please send me the following: Title First name Order Number Quantity 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.
158 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
List of Abbreviations ADSM ADSTAR Distributed Storage Manager MIB Management Information Base ASMA Advanced System Management Adapter MSCS Microsoft Cluster Server NMI Non-Maskable Interrupt APC American Power Conversion NIC Network Interface Card BDC Backup Domain Controller NTFS Windows NT File System BIOS Basic Input Output System PCI CCMS Computing Center Management System Peripheral Component Interconnect POST Power-on Self-test DBMS Database Management System PFA Predictiv
160 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
Index Numerics 7133 15 90-day startup support 6 A abbreviations 159 acronyms 159 ADSTAR Distributed Storage Manager (ADSM) 107 Advanced System Management Adapter (ASMA) 6, 51 Alert Manager 123 allocation of server memory 84 American Power Conversion (APC) 12 APC UPS 21 application layer 10 Application Server 133 installing 103 managing 114 archived database log files 149 archiving 111, 114 array, creating 64 ASMA Card 85 ASMA COM ports 53 B battery-backup cache 65 BIOS and firmware level 47 BIOS updates
L R logical drive, creating 64 Lotus Domino 108 Lotus Notes 108 R/3 Application Servers, managing 114 R3INST 92 RAID Cluster Adapter 4 RAID Manager 126 RAID PCI Adapter 4 RDISK command 87 read ahead option 62 Ready-to-Run R/3 139 recommended disk configuration 148 Redundant Network Interface Card 40 Remote Session 126 Remote System Manager 126 Remote Workstation Control 128 RRR (Ready to Run R/3) 139 M Management Information Base (MIB) 13 managing R/3 Application Servers and Database Servers 114 memory
sizing, SAP R/3 141 Software Inventory 130 stop an application server service 26 Stripe Unit Size 62 synchronization for RAID level 5 logical drives 78 System Configuration Utility (SCU) 51, 53 System Diagnostics Manager 130 System Information Tool 130 System Monitor 130 System Partition Access 131 System Profile 131 SystemXtra 6 T TCP/IP Auto-Discover 127 Third Channel Cable 44 three-tier hardware configuration 11 Tivoli TME 10 108 TME 10 Enterprise Console (TEC) 116 TME 10 Module for R/3 114 two-tier con
164 Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT
ITSO Redbook Evaluation Optimizing IBM Netfinity Servers for SAP R/3 and Windows NT SG24-5219-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.
