Microsoft Windows. Integration with iseries. Front cover. ibm.com/redbooks. Understand the new support for Windows Server 2003

(1)

Front cover

Microsoft Windows

dows

Server 2003

3 Integration with iSeries

Series

Nick Harris

Phil Ainsworth

Anders Ahl

Andy Elsey

Mike Woiwood

Understand the new support for

Windows Server 2003

Review planning and implementation

requirements for Windows

Server 2003

Learn how to set up Windows Server

2003 clusters

(2)

(3)

International Technical Support Organization

Microsoft Windows Server 2003 Integration with

iSeries

(4)

This edition applies to Version 5, Release 2, of OS/400 and iSeries.

Note: Before using this information and the product it supports, read the information in “Notices” on

(5)

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include 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.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

(14)

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

1-2-3®

Advanced Function Printing™ AFP™ AIX® AS/400® AS/400e™ DataPropagator™ Domino™ DB2® DFS™ ^™ IBM® iSeries™ Lotus® MQSeries® Netfinity® NetVista™ OS/2® OS/400® PowerPC® Redbooks™ Redbooks(logo) ™ ServerGuide™ ServerProven® Tivoli® X-Architecture™ xSeries®

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

(15)

Preface

This IBM® Redbook highlights the benefits of running a Windows® server on an IBM Integrated xSeries® Server (IXS), or an xSeries Server attached via the IBM Integrated xSeries Adapter (IXA), rather than on a separate PC server. It provides the information needed to plan, install, and manage the Integrated xSeries Server in your IBM^® iSeries™ server.

This book helps the reader gain detailed insights and explanations about the support provided by the OS/400® Integration for Microsoft® Windows Server software. The intended audience includes IBM customers, Business Partners, service providers, and personnel who need an in-depth understanding of how to implement Microsoft Windows Server running on the IXS for iSeries or on an xSeries server attached via IXA.

The team that wrote this redbook

This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Rochester Center.

Nick Harris is a Consulting IT Specialist for the iSeries and has

spent the past five years in the International Technical Support Organization, Rochester Center. He specializes in LPAR, iSeries hardware and software, external disk, Integrated xSeries Server for iSeries, and Linux, and he writes and teaches IBM classes worldwide on areas of AS/400® system design and server consolidation. He spent 13 years in the United Kingdom AS/400 Business and has experience in S/36, S/38, AS/400, and iSeries servers. His e-mail address is mailto:niharris@us.ibm.com.

Anders Ahl is an Advisory IT Specialist for IBM Global Services

in Sweden. He is a Citrix Certified Administrator and an MCSE with more than 10 years of experience in the Windows NT/2000 field. His areas of expertise include IBM^ xSeries systems management, Citrix Metaframe, and TCP/IP

communication. Since he started working for IBM in 1997 he has written extensively about various Microsoft-related topics, and this is his fifth IBM Redbook.

Phil Ainsworth is a Senior Technical Specialist from Melbourne,

Australia. He has 21 years of experience with IBM and has worked on S/34, S/36, S/38, AS/400, and iSeries servers. His areas of expertise include Windows NT® running on the

Integrated Netfinity® Server, Client Access, communications, and PC connectivity. Phil has also participated in other residencies on subjects such as Client Access, Novell NetWare coexistence with Client Access, and connecting Apple Macintosh to the AS/400 system.

(16)

Andy Elsey is an IT Specialist for IBM Global Services in the

United Kingdom and a member of the Enterprise Services for Microsoft Technologies. He has more than 13 years of experience as an application developer. His areas of expertise include C#, ASP.NET, Visual Basic, IIS, and Microsoft Office.

Mike Woiwood is a Staff Software Engineer with more than 18

years of experience working with IBM Midrange computers. For the past eight years Mike has worked in the Rochester Support Center supporting iSeries integrated operating environments. He has supported the FSIOP, IPCS, INS, IXS or IXA hardware created to run Warp Server, Netware, Domino™, iSeries Firewall, Microsoft Windows NT, and Microsoft Windows 2000 servers. He can be contacted at mailto:woiwood@us.ibm.com.

Thanks to the following people for their contributions to this project: Bob Schuster Russ Garvey George Gaylord Mark Goff Tom Haze Nancy Kryka Jeff Meaden Marilyn Oliver Mike Petrich Leif Rush Mike Schambureck Andy Tauferner Scott Timmerman Kyle Wurgler Elisabeth Rédei Microsoft, Sweden Ola Svensson Volvo IT, Sweden

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions while getting hands-on experience with leading-edge technologies. You will team with IBM technical professionals, Business Partners, and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

(17)

Comments welcome

Your comments are important to us. We want our Redbooks™ to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an e-mail to:

redbook@us.ibm.com Mail your comments to:

IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2

3605 Highway 52N

(18)

(19)

Chapter 1.

Overview

This chapter presents an overview of the Windows Server 2003 running on the Integrated xSeries Server for iSeries (IXS) server or an xSeries Server attached via an Integrated xSeries Adapter (IXA). It also describes the benefits you can achieve by setting up this environment.

IBM has combined the iSeries and xSeries servers into one integrated package capable of running OS/400 and Windows Server. This provides additional benefits over and above those provided by each system operating independently. With the delivery of OS/400 Version 4 Release 2, IBM extended its range of AS/400 support to include Windows NT Server 4.0. Now, with OS400 Version 5 Release 2, IBM has announced new IXS hardware for the Windows server. IBM also added considerable new functions to the implementation of a Windows server running in the OS/400 environment.

(20)

1.1 Windows Integration

IBM iSeries and xSeries Windows Integration Solutions:

Integrated xSeries Server for iSeries is a Microsoft Windows Server 2003 or Windows 2000 Server on a card that runs inside an IBM^ iSeries server.

Integrated xSeries Adapter (IXA) enables direct connection of an n-way xSeries server to an iSeries server for greater power and flexibility.

Both products leverage iSeries storage and systems management resources and integrate iSeries and xSeries operations to help reduce cost and complexity.

Innovative integration

Many businesses today operate heterogeneous environments that include Intel®-based servers running Microsoft Windows applications in addition to core business applications on iSeries. This mix of servers may be necessary in order to deploy the applications the business needs; however, it may grow into a challenging environment that involves supporting many discrete Intel servers and can lead to higher costs and a more difficult operation to manage.

IBM iSeries offers two solutions that provide a powerful, flexible, and highly cost-effective alternative to Intel-based server farms: the Integrated xSeries Server and the Integrated xSeries Adapter.

Both the IXS and the IXA deliver tightly integrated, easily managed Windows Server 2003 and Windows 2000 Server deployment solutions that help provide a cost-effective and efficient alternative to running Windows on multiple stand-alone Intel servers.

The difference between the two solutions is how the iSeries and xSeries hardware integration is accomplished. Each solution is designed to meet different requirements.

A better way to do Windows

The IXS is an Intel-based server on a PCI card that plugs into an iSeries server. It delivers a powerful 1.6 GHz Intel Xeon processor with hyperthreading technology, which makes a single physical processor appear as two logical processors. It has a built-in 10/100 Mbps Ethernet Adapter. The IXS leverages iSeries’ system management, communication, and storage resources, but otherwise operates as if it were a standalone Windows server. As many as 48 discrete Windows servers can be installed inside a single iSeries server, creating an entire server farm in a single, easily managed platform — capitalizing on the reliability,

manageability, and flexibility of the iSeries.

The IXA is a PCI-based interface card that installs inside selected models of xSeries servers1, providing a 1 GBps high-speed link to an iSeries server. This enables centralized storage, integrated operations, and systems management.

IXAs enable the direct attachment of as many as 60 n-way xSeries servers to a single iSeries server, enabling the deployment of greater Intel processing power and taking full advantage of the latest IBM X-Architecture™ innovation. Each xSeries server has its own processors, memory, and IXA and, like the IXS, shares iSeries’ disk, tape, DVD, CD, and systems management resources.

Both xSeries server options are designed for local consolidation of Intel servers and storage as well as centralized management of iSeries and xSeries servers in distributed offices. These solutions allow you the flexibility to configure a consolidated infrastructure that best fits your specific requirements. If you need to efficiently deploy a large number of smaller Windows servers, choose a single iSeries server and install many IXSs in it. Or, if you need mission-critical processing power and scalability, you might connect powerful 2-way, 4-way or

(21)

8-way xSeries servers to your iSeries via IXAs. Either way, you get true integration that gives you the best of both iSeries and xSeries servers and provides the freedom to run the best mix of applications for your business while operating your entire implementation as a single infrastructure with minimum complexity.

1.1.1 Integrated operations

Improving or reducing the operational overheads of any group of servers is very important for any IT organization. This section discusses the improvements that can be made with

Windows Integration on iSeries.

Centralized, graphical server management

iSeries Navigator provides a graphical user interface for managing both iSeries and Windows servers. Administrators may easily start and stop servers, enroll Operating System 400 (OS/400) users to a Windows domain and perform storage management tasks such as adding new virtual disks to a Windows server. iSeries Navigator for Wireless enables administrators to view server status, start and stop servers, and run Windows commands for IXSs from a Web-enabled cell phone, Personal Digital Assistant (PDA), or a Web browser.

Synchronized security

With iSeries Windows integration solutions, OS/400 and Windows Server 2003 or Windows 2000 Server user IDs and passwords can be integrated and centralized. When a user is added to OS/400, the user also can be added automatically to the Windows environment with proper authorities. In addition, when the user changes their OS/400 password, their Windows password can be synchronized automatically. This integration helps reduce user

administration costs because it cuts down on juggling multiple user IDs, passwords, and authorizations across multiple IT environments.

Consolidated backup

iSeries Integrated xSeries solutions provide consolidated OS/400 and Windows server backup solutions, enabling businesses to fully leverage hardware and IT support resources. In a typical Windows server farm, data may be scattered across multiple servers, with backup processes running on each one and multiple tape drives to manage. With iSeries and xSeries integration, iSeries and Windows server storage and backup resources are shared and consolidated, and one tape device can perform automated backup for the entire infrastructure.

Reliable, secure, high-speed communications

iSeries enables OS/400 and integrated Windows servers to communicate over high-speed Virtual Ethernets. These networks may be utilized for Windows-to-Windows and

Windows-to-OS/400 communication. Because there are no cables, connectors, hubs, or routers, there are fewer points of potential failure. Network traffic travels inside the iSeries, not across external networks. Virtual Ethernets can provide more reliable and secure

communications, faster network communications (1 GBps) between servers, and reduced external network traffic.

Exceptional storage management

One of the most significant advantages of the iSeries is its unique storage architecture: All disks can be managed as a single pool of RAID-5 protected storage. This means that users and system administrators need not concern themselves with the exact physical location of data. It is all managed dynamically, transparently, and simply by the iSeries.

(22)

The advanced iSeries storage architecture can provide more flexibility than conventional Windows server implementations where, typically, dedicated disk drives are attached to every server and each server’s capacity is managed separately.

With the integrated iSeries solution, there can be one pool of disk drives that OS/400 and the Windows servers utilize, and iSeries can automatically spread the data across all disk drives on the system. This architecture can provide tremendous performance advantages as well as more efficient use of hardware resources.

With the IXS and IXA, the iSeries’ superior storage area network-like management capabilities are made available for Windows transparently. Disk storage is allocated to Windows by creating a storage space object (i.e. virtual disk space) from the iSeries pool of disk resources. Up to 32 storage spaces can be created and linked to each IXS or

IXA-attached xSeries server. Each storage space can be between 1 MB and 64 GB in size, for a maximum of up to 2 TB per Windows server.

In addition, multiple storage spaces can be linked together using the Windows disk

administrator utility for large volume sets. Storage spaces can be added dynamically to the Windows server using iSeries storage management facilities.

Flexible and Reliable Server Deployment

iSeries and xSeries integration and storage virtualization provide innovative options that can enable customers to enhance the reliability and recoverability of their Windows server environment. If a Windows server fails, you can quickly and easily switch the server’s storage spaces to another “hot spare” xSeries server without restarting your iSeries server. This may easily reduce the overall number of Intel servers needed to provide increased availability. It also adds flexibility by enabling one “spare” server to be used to protect multiple production servers.

If automatic fail-over is required to support Windows application availability, iSeries and xSeries integration supports Microsoft Cluster Services in Windows Server 2003 Enterprise Edition and Windows 2000 Advanced Server.

In a typical Windows server implementation, there may be several server configurations consisting of production servers, development servers, and test servers, each with its own set of software and device drivers. Testing and deploying changes across multiple servers can be problematic because of the number of different configurations that must be maintained. A test server may have to be made available for every different configuration, or a test server may have to be rebuilt from scratch to match a production server whenever there are changes to be deployed.

With iSeries and xSeries integration, one xSeries server may be used to support multiple test and deployment environments. One xSeries can be made to “look like” any of the other servers, because the server hardware may be completely divorced from the storage spaces on which a specific Windows server configuration and data is installed. There is no physical boot drive within the xSeries server; all Windows “drives” are just storage space objects in the iSeries storage pool.

Storage virtualization provides tremendous flexibility for deploying new Intel servers, because everything needed to operate each Windows server is just data within a storage space. By copying storage spaces, new servers may be deployed and changes tested easily. Restoring storage spaces can enable rapid recovery of complete Windows servers in the event of a software failure or data corruption.

(23)

Other key benefits of iSeries and xSeries integration:

Proven application solutions: The IXS is an xSeries ServerProven® platform on which software vendors can validate their applications, accelerating the time it takes to get them into production. The IXA is a ServerProven hardware adapter. Many of the complementary applications available for the xSeries are also ServerProven.

Support for complementary applications: Some software providers are delivering applications that leverage multiple server platforms. With these complementary

applications, both OS/400 and Windows server environments are required to support the total solution. The IXS and xSeries attached via IXA are ideal ways to meet this

requirement, by offering an integrated IBM solution.

Managed delivery of Windows applications: Support for Citrix MetaFrame and Microsoft Windows Server 2003 and Windows 2000 Server (with built-in terminal server support) to deliver Windows personal productivity applications to the desktop. By serving Windows desktop applications on the server instead of installing them on every desktop,

management can be simplified dramatically. Application software changes are done only once, at the server level, then they are automatically and transparently rolled out to every desktop in the organization.

1.1.2 Integrated xSeries Server

The IXS has been available in a variety of packages. The current packages are listed below:

2.0 GHz Integrated xSeries Server

2.0 GHz Intel Xeon processor with Hyperthreading technology

512 KB L2 cache

400 Mhz front side bus (FSB)

Up to 4 GB of ECC DDR memory

Up to 2 TB disk storage

Integrated 10/100 Mbps Ethernet, plus up to three additional hot-plug network adapters, which can be a mix of 10/100/1000 Mbps Ethernet and 100/16/4 Mbps token-ring adapters

4 Universal Serial Bus 1.1 ports

Device drivers to share iSeries disk, tape, DVD, and CD devices

Supported on iSeries Models with OS/400 V5R2 or higher

Supports Windows Server 2003 Standard or Enterprise Editions, Windows 2000 Server, or Windows 2000 Advanced Server

1.6 GHz

Integrated xSeries Server

1.6 GHz Intel Xeon processor with Hyperthreading technology

512 KB on-chip L2 cache

Up to 4 GB of ECC DDR200 memory

Up to 2 TB disk storage

Integrated 10/100 Mbps Ethernet, plus up to three additional hot-plug network adapters, which can be a mix of 10/100/1000 Mbps Ethernet and 100/16/4 Mbps token-ring adapters

4 Universal Serial Bus 1.1 ports

(24)

Supported on iSeries Models with OS/400 V5R2 or higher

Supports Windows Server 2003 Standard or Enterprise Editions, Windows 2000 Server, or Windows 2000 Advanced Server

1 GHz

Integrated xSeries Server

Intel Pentium® III 1 GHz processor.

256 KB on-chip L2 cache.

Up to 4 GB of ECC SDRAM memory.

Up to 2 TB disk storage.

Up to 3, Gigabit Ethernet, 10/100 Mbps Ethernet, 100/16/4 Mbps token-ring adapters (hot-plug), or a combination of any of these.

2 Universal Serial Bus ports.

Device drivers to share iSeries disk, tape, DVD, and CD devices.

Supported on iSeries models with OS/400 V5R1 or higher.

Supports Windows Server 2003 Standard or Enterprise Editions, Windows 2000 Server, Windows 2000 Advanced Server, or Windows NT Server 4.0.

Multiple IXSs can be installed in a single iSeries system. See iSeries support for

Integrated xSeries Servers for details about the number of IXSs supported by each iSeries model.

1.1.3 Integrated xSeries Adapter

The IXA provides attachment capability for external PC servers.

64-bit, 66 MHz PCI adapter.

Installed in selected xSeries servers including the 235, 255, 360, and 440 models. For a complete list of models visit:

http://www-1.ibm.com/servers/eserver/iseries/windowsintegration/xseriesmodels/

Uses High-Speed Link cables to connect to iSeries.

Supported on iSeries Models with OS/400 V5R1 or higher.

Supports Windows Server 2003 Standard or Enterprise Editions, Windows 2000 Server, or Windows 2000 Advanced Server.

Multiple xSeries servers can be directly attached via IXAs to a single iSeries system. See iSeries support for Integrated xSeries Adapters (IXA) for details about the number of IXAs supported by each iSeries model.

Windows Server requirements

Windows Server 2003 Standard, Enterprise, and Web Editions, Windows 2000 Server, and Windows 2000 Advanced Server are available from Microsoft resellers.

1.2 New in V5R2

iSeries IXS and IXA offerings are enhanced with support for Virtual Ethernet LAN, Microsoft Clustering Service, and Automatic Cartridge Loader support. In addition, the new iSeries

(25)

models 870 and 890 can consolidate more Windows servers with support for up to 48 IXSs and 60 IXAs.

Virtual Ethernet: The iSeries Virtual Ethernet LAN introduced in V5R1 to enable high-speed communications between OS/400 and Linux partitions within the iSeries server is extended to support IXS and xSeries servers attached with IXAs. With this support, Windows servers can now communicate with each other and with OS/400 and Linux partitions over fast, more secure, and reliable Virtual Ethernet LANs.

Clustering Service: iSeries Windows integration support has been extended to support the Microsoft Clustering Service. With the clustering support provided in Windows Server 2003 Enterprise Edition and Windows 2000 Advanced Server, two IXS or two xSeries servers attached with IXAs can form a cluster and utilize the 16 new shared storage spaces that are available with V5R2. In the cluster environment, if there is a planned or unplanned outage on one of the Windows servers, the storage spaces can be switched to the second Windows server and the applications can be restarted automatically to reduce the length of the system outage.

Auto Cartridge Loader: Customers who have systems with large amounts of data often have Auto Cartridge Loader (ACL) tape devices (3570, 3580, and 3590) for use with backup/restore operations. Support is now added in the Windows integration product for ACLs to automatically load the next tape cartridge in the magazine during backup/restore operations initiated from the Windows Server.

Microsoft Windows Server 2003: IBM supports Microsoft Windows Server 2003 on the IXS and on xSeries servers attached to iSeries with the IXA.

Other enhancements:

– New iSeries Navigator functions that enable the user to run Windows commands and perform iSeries Integration for Windows Server service functions

– User administration enhancements, including support for organizational units and improved control of domain enrollment processing

– Windows system drive now a maximum of 64,000 MB in size – Support now available for a virtual optical media library

– Improved iSeries Integration for Windows Server service and device locking functions

For more details about V5R2 enhancements, visit the What's new for V5R2 topic in the Windows Server on iSeries section of the iSeries Information Center at:

http://publib.boulder.ibm.com/pubs/html/as400/infocenter.html

1.3 Windows Integration background

The Intel processor-based adapter has been available from IBM on AS/400, AS/400e™, and iSeries servers since V3R1. The hardware was initially known as the File Server IOP

(FSIOP), and then the Integrated PC Server (IPCS). In V4R4, the server hardware was again renamed to the Integrated Netfinity Server (INS).

Integrated xSeries Server

(IXS) is now the generic name that applies to all current models of the iSeries server features.

1.4 The midrange server marketplace

In the commercial marketplace, companies normally run their commercial and business applications on a midrange server, such as the iSeries server. When using the iSeries server for these applications, it is common for companies to install PC-based servers alongside the

(26)

iSeries server for PC file and print serving. OS/400 is optimized for multi-user application and database services. Network operating systems, such as Microsoft Windows Server and Novell NetWare, are optimized for PC file and print services.

Today, many companies are considering the Windows Server as their network operating system for sharing files, printers, and personal productivity applications. The Windows Server server also provides the ability to run server-based applications natively, such as Microsoft Exchange.

The iSeries server has always excelled in the commercial midrange marketplace by focusing on the value of integration for database, security, and application services, and more recently e-business and native IBM Lotus Domino. The integrated architecture of the iSeries server reduces complexity in customers’ installations, lowering their total cost of ownership. iSeries customers want to extend that same integrated model to include their PC servers. The IXS achieves this goal by combining iSeries server and PC server hardware inside the same physical package. In addition, the iSeries server and Windows Server share resources such as disk, tape, DVD, and CD devices, and employ combined operations and systems

administration.

By packaging the Integrated xSeries Server inside the iSeries hardware platform, benefits are gained from sharing hardware resources and combining management and operations. Tasks and costs involved in installing, managing, and maintaining separate PC-based servers can be reduced with this integrated solution. Hardware support for the IXS is covered by one company, and maintenance charges for the IXS are included in the iSeries support agreement.

The Windows server running on the Integrated xSeries Server addresses these three markets in particular:

Distributed branch offices: The Windows Server on the Integrated xSeries Server is ideally suited for customers with distributed branch offices where centralized management is required. For example, an OS/400 operator can remotely start, stop, and allocate

additional disk resources to a Windows Server running on the IXS. The Tivoli® IT Director management product can be used to enhance the remote management of the Windows Server. IT Director provides the ability to take control of the Windows Server console remotely, distribute software to the server, and perform hardware and software

administration tasks. This remote management function is also supported with the two administrator Terminal Services Clients in the Windows 2000 server.

Server consolidation: Because the iSeries server is capable of managing multiple IXSs, it is possible to consolidate a number of PC servers into a single system. Depending on the iSeries model, up to 48 IXSs, each running its own copy of the Windows Server, can be installed in a single iSeries server. complex

Application server for network computers: The Windows Server on the IXS also supports Microsoft Windows Server Terminal Services and the Citrix MetaFrame product that provide multi-user support for applications running on the Windows Server. This enables network stations to use Windows-based personal productivity applications running under the Windows Server on the IXS.

1.5 Installation

The Windows Server is installed on the Integrated xSeries Server using an OS/400 command that runs an automated installation program. (See Figure 1-1 on page 9.) You insert the Windows Server CD into the iSeries DVD or CD drive, enter information into the command prompts, and press Enter.

(27)

Figure 1-1 Windows Server installation

The operation of the Windows Server on the IXS is divided between the server console and the Windows Server console. The installation and disk configuration are performed from an OS/400 display. Messages from the IXS can be collected in OS/400 message queues and job logs. On the other hand, Windows Server operations are performed directly on the Windows Server console that is connected to the IXS. This preserves the Windows Server graphical interface for most operations, including the installation of Windows Server applications.

Refer to Chapter 3, “Installation” on page 51, for more information about installing Windows Server on the Integrated xSeries Server.

1.6 Shared devices

One benefit of running the Windows Server on the iSeries server is the ability to take advantage of iSeries disk storage reliability and management flexibility. This is particularly useful when providing operational support for remote installations, where adding disk storage to a PC-based server often requires significant downtime. When you use iSeries disk drives, Windows Server files are automatically protected using the iSeries RAID-5 and mirroring technology (provided these functions have been enabled on the iSeries server). There is no benefit to be gained by configuring RAID-5 or mirroring on the Windows Server.

The integration support enables the Windows Server backup applications to use the iSeries tape drive for backup and restore. The iSeries tape drive is varied off and then allocated to the Windows Server. The tape drive is available for use by the Windows Server backup and restore utilities. Then, the tape drive is reallocated to the iSeries server for normal tape operations after the Windows Server backup or restore operation has completed. You can also save the Windows Server files directly from the iSeries server to a tape drive at a file level using the new file level backup capability or at a storage space level for disaster recovery purposes.

The iSeries DVD/CD drive can be dynamically allocated to a Windows Server. See Figure 1-2 on page 10 for an example of how this concept works.

W indows

server CD

W indows server

console

(28)

Figure 1-2 iSeries server and Windows Server device sharing

1.7 Disk administration

iSeries disk storage is allocated to the Windows Server by creating an object called a

network

server storage space

(also referred to as NWSSTG space or simply storage space), which resides in the system auxiliary storage pool (ASP) or a user ASP. Each storage space can be from 1 MB to 64,000 MB in size.

The task of assigning new disks to a Windows Server can be performed at a central iSeries server, using native OS/400 commands. Telnet or SNA pass-through shutting down the Windows Server. After shutdown, a storage space can be linked to the server. After the Windows Server is brought up again, the remote operator can use, for example, Windows 2003 Server Terminal Services configured in administrator mode to take over the Windows Server console and format the disk. This entire process can be completed from a central location, or directly at the iSeries server and Windows Server consoles.

Windows Server disk images can be saved on a central iSeries server and then transmitted as a save file, or sent on tape to a remote site. This allows the addition or replacement of a complete disk image on a remote server without any hardware changes. For example, this technique could be used when a company periodically needs to distribute a catalogue of parts or sales information to its remote branches. An example of disk administration is shown in Figure 1-3 on page 11.

iSeries

server

Windows Server

2003

(29)

Figure 1-3 Disk administration scenario

Refer to Chapter 5, “Disk Management” on page 113, for more information about disk administration.

1.8 User administration

The user integration function enables the enrollment of OS/400 users and groups in a Windows Server domain or on an individual server. This also enables the synchronization of user passwords from OS/400 to the Windows Server domain or server. This feature can significantly reduce the overhead required to administer two separate operating systems.

For example, when an OS/400 group profile is enrolled in the Windows Server domain or on an individual server, you optionally can enroll user profiles in the group and the group profile itself. A predefined account template on the Windows Server can be used to set up the appropriate Windows Server group memberships and user preferences. As new users are added to the group profile in OS/400, they are propagated automatically to the Windows Server domain or server.

Figure 1-4 User enrollment and password synchronization

When OS/400 users who are enrolled in the Windows Server domain change their passwords, the changes are automatically propagated to the Windows Server domain. As shown in Figure 1-4, password synchronization is from OS/400 to Windows Server only. Refer to Chapter 6, “User enrollment” on page 131, for more information about user administration.

W indows 2003 on the Integrated xSeries S erver Adm inistrator m anages the branch office server New H Disk H Disk G Disk F Disk New Disk New Disk Save File Head office iSeries server Branch office iSeries server

O S /400 users, group s,

an d p assw ord s

W in d ow s 2003

d om ain

(30)

1.9 Backup and restore

Windows 2003 files can be backed up from either OS/400 or Windows Server. (See Figure 1-5.) From OS/400, you can save a complete storage space for disaster recovery purposes or perform a file level backup from the Windows Server server or OS/400.

Figure 1-5 Backup and restore options

The ability to save and restore individual Windows files from OS/400 using CL commands is called

OS/400 file level backup

. It uses the QNTC file system to gain access to directory shares on a Windows server running on the Integrated Netfinity Server.

You can view the backup and restore of Windows files from two perspectives: OS/400-centric or Windows-centric. Currently, the following four methods can be used to back up and restore files on a Windows Server (or Windows NT 4.0) server running on the IXS:

From the OS/400 side, you can use the following three methods:

– Disaster recovery backup is the term that is used when backing up Windows files at a storage space level.

– OS/400 file level backup can be used to back up individual Windows files using the QNTC file system.

– IBM Tivoli Storage Manager can also be used to back up individual Windows files.

From the Windows side, you can back up files using Windows backup applications to either an iSeries or PC tape drive.

Most iSeries tape drives can be used by Windows backup applications to provide fast and reliable saves of Windows files.

Refer to Chapter 7, “Backup and recovery” on page 179, for more information about backup and restore.

1.10 Multi-user Windows environment

Many companies that want to consolidate their Windows Servers on the iSeries server are also considering replacement of their PC workstations with network computers, to reduce costs and simplify their operational environment.

The iSeries server is an ideal platform to fulfill the role of a host server for IBM Network Stations. The iSeries can act as a boot manager and as a server for Domino, Internet, and legacy applications.

OS/400-centric Windows 2003-centric Windows 2003 backup applications File level backup using Tivoli Storage

Manager or the QNTC file system

Disaster recovery backup

1

2

(31)

Figure 1-6 Multi-user Windows environment on the IXS

As shown in Figure 1-6, a Windows Server can be added to this environment to provide IBM Network Stations access to Windows-based personal productivity applications, such as Lotus® 1-2-3® and Microsoft Word. Windows Server 2003 Terminal Services provides Remote Desktop Protocol (RDP), which is used to connect Windows clients to Terminal Services on the Windows Server 2003. Citrix MetaFrame provides the ICA protocol, which is used to connect IBM Network Stations or other devices using ICA to Terminal Services.

Another possibility is to use the NetVista™ Windows-based terminal to connect directly to a Windows Server 2003 without using Citrix MetaFrame. This could be a cost-effective and easy way to change to a thin client network architecture if the network has no more than 30 to 50 clients.

Refer to Chapter 10, “Terminal Services and Citrix MetaFrame” on page 271, for more information about Windows Terminal Services.

1.11 PC server consolidation

Many companies deploy multiple PC-based Windows servers, each dedicated and tuned to an individual application. These applications commonly include file and printer sharing, database serving, Internet and intranet serving, remote access capability, fax, groupware, e-mail, firewall, and so on. Although the single-server-per-application concept has availability advantages (for example, a fax server failure does not affect the Internet server), it also introduces significant space, maintenance, and systems management considerations.

These issues often translate into additional costs to the organization. Therefore, a server that can consolidate multiple application servers onto a single physical platform should have inherent advantages over the discrete-server model. A consolidated platform can provide multiple separate Intel-based servers and be housed and managed in a single physical package.

The iSeries server performs this consolidation function by hosting multiple Integrated xSeries Servers or Integrated xSeries Adapter attached xSeries Servers, each running its own copy of the Windows Server.

The iSeries models support up to 60 IXA attached xSeries servers, offering huge

consolidation. Each xSeries server operates as an individual entity, yet can be managed from the iSeries. The disk, backup, restore, and user administration are hosted by iSeries, but the xSeries LAN adapters are located in the actual PC server.

C i t r i x M e t a F r a m e a n d

W i n d o w s 2 0 0 3 T e r m i n a l S e r v i c e s o n t h e I n t e g r a te d x S e r i e s S e r v e r

(32)

The iSeries server accommodates up to 48 Integrated xSeries Servers, depending on the model. Each IXS runs independently but is controlled by the iSeries server for the purposes of disk storage management, backup and restore, and user administration. Figure 1-7 shows an example of server consolidation.

Figure 1-7 Consolidation in iSeries

The iSeries Server platform provides these enhanced features:

Unique high-availability characteristics improves Windows Server reliability.

Centralized reset and IPL of individual servers removes the requirement for physical access to the PC reset switch.

Sharing of disk, tape, DVD, and CD devices between servers optimizes hardware investment.

Single OS/400 console for centralized administration and error monitoring improves operator productivity and convenience.

Internal links between OS/400 and Windows Servers enables management of the integrated servers to continue during times of network disruption.

1.12 Remote management of the Windows 2003 Servers

For many iSeries customers, a typical scenario has an iSeries server divided between the head office location and distributed branch offices, sometimes in a single region but often worldwide. In this distributed computing model, operators at the head office are often responsible for administering computing services in the branches. Typically, the branches have few operational skills. Figure 1-8 on page 15 shows an example of remote management.

1 to 59 Windows 2003 Servers

with IX A _{48th IX S or 60th IX A}

can be a Hot spare 1 to 47 IX S Windows 2003 Servers

2.0 GHz IXS

xSeries 445

+ IXA card

Virtual PC disk

(33)

Figure 1-8 Remote management of branch office servers

Distributed iSeries servers in a network running Windows Server on the IXS can be managed easily from a central location.

Using remote communications (such as Telnet or SNA pass-through), a central administrator can sign on to a remote iSeries server and perform tasks such as bringing the Windows Server up or down, adding new disk volumes, and managing users. These tasks are difficult, if not impossible, to perform on a remote PC server. You can also save a Windows Server disk image on one iSeries server, transmit it across the network, and restore it for use by a Windows Server on another server. With Windows Server, there are now two ways to take over remote control of a Windows server. One way is integrated in Windows Server. You can set up Windows Server 2003 Terminal Services for use by administrators only. This enables you to access the Windows Server console from a remote Windows client to perform any operation that you can do on the console locally. The second method is to use a product such as Tivoli IT Director, with which you can also take over the Windows Server console remotely.

1.13 iSeries and Windows application integration

Many companies that have a mixed iSeries and Windows Server environment want to exchange data between the two operating systems or have a Windows Server application access the OS/400 database directly.

Database integration and other integrated applications are ideally suited to the Integrated xSeries Server environment because of the internal bus-level communication link between the iSeries server and Windows Server. This

internal

virtual Ethernet LAN connection

between the two operating systems provides a secure, reliable conduit between the iSeries server and Windows Server. It is not dependent on token-ring or Ethernet connections to the external LAN. This link emulates an Ethernet LAN and is designed to run the TCP/IP protocol (only) between the Windows Server and the iSeries server. Although the virtual Ethernet LAN is used for some integration functions such as user administration, there is relatively little traffic with this connection. Therefore, you can expect consistent performance across this link.

For example, IBM MQSeries® could be used to write a communications application in which the iSeries server and Windows Server exchange transactions across the virtual Ethernet LAN. Figure 1-9 on page 16 shows an iSeries and Windows 2000 application integration.

Windows Server 2003 on the Integrated xSeries Server

OS/400 operator manages branch

office server Head office

(Chicago) Branch office_{(San Francisco)}

Reboot, add disk, monitor Windows messages

(34)

Figure 1-9 iSeries and Windows 2000 application integration

Modification to the OS/400 Client Access ODBC driver enables it to be used by a Windows Server service. This implementation enables the virtual Ethernet LAN to act as a conduit for Windows Server client applications that need to access the OS/400 database using ODBC. This provides additional flexibility in application design.

Other ways to interchange data in this environment include IBM DataPropagator™, which can be used to replicate data between databases on the iSeries and Windows Server.

1.14 Benefits of running Windows Server on the iSeries server

This section describes some of the benefits of running the Windows Server on an IXS instead of on a separate PC.

1.14.1 Reduced user administration

OS/400 users can be enrolled on a Windows Server 2003 domain and then be maintained automatically by the integration software. This reduces Windows Server administration. For example, you can enroll an OS/400 group profile in a Windows Server 2003 domain. Then, every time a new user is added to this group profile on the OS/400 system, the new user is automatically propagated to the Windows Server 2003 domain.

When enrolled users change their OS/400 passwords, the new passwords are automatically updated on the Windows Server. This can eliminate one of the biggest problems of

maintaining user profiles in two separate operating environments: password synchronization. With this feature, users do not have to change multiple passwords, and Windows Server administrators do not have to waste time continually resetting user accounts.

1.14.2 Higher availability

Running the Windows Server on the Integrated xSeries Server or IXA enables you to take advantage of the following high-availability features of this environment:

Integrated hardware and software package

All hardware and drivers used to run Windows 2003 on the Integrated xSeries Server or IXA are supplied as a package by IBM. Therefore, the possibility of a conflict between a hardware component and an incompatible driver is unlikely.

DB2/400 Database

Windows Server

applications

Secure, internal Virtual Ethernet LAN connection between the iSeries and Windows Servers

Microsoft Windows. Integration with iseries. Front cover. ibm.com/redbooks. Understand the new support for Windows Server 2003

Front cover