UNIX Application Migration Guide
was written with two groups in mind: first, Corporate Information Officers (CIOs), Information Technology (IT) directors, data center managers, and senior
The first few chapters examine the planning and practical issues involved in migration or coexistence between UNIX and Windows. These chapters discuss whether a move to Windows is the best choice for your organization, and review the different ways to carry out such a migration. If you are an IT decision maker, chapters 2 through 6 cover your area of primary focus.
Subsequent chapters have sections for both UNIX and Windows programmers. If you are a UNIX programmer, you will see how you can adapt your code so that it can be recompiled to run in a Windows Win32 or native UNIX Interix environment. If you are a Windows programmer, you will learn about how you can port UNIX functions to Windows and how you can ease the process of rewriting an application within the Microsoft Win32 API framework. Chapters 8 through 14 contain detailed information
Finally, Chapter 7, which covers tools and technologies, and Chapter 15, which discusses future migrations, include content of interest to both audiences.
Because this guide is aimed at two separate audiences, knowledge prerequisites can
Chapters 8 to 14 assume a detailed knowledge of either the UNIX environment or the Microsoft Win32 environment. This includes familiarity with the C, C++, or Fortran languages and syntax and the ability to write new code or to analyze and adapt existing code to fit the migration or coexistence scenario.
This guide uses the style conventions and terminology shown in Table 0.1.
Characters that you type exactly as shown, including commands and switches. Programming elements, such as
Variables for which you supply a specific value. For example,
could refer to any valid file
The folder in which Windows 2000 is installed.
Alerts you to supplementary information.
Alerts you to supplementary information that is essential to the completion of a task.
Alerts you to possible data loss, breaches of security, or other more serious problems.
Alerts you that failure to take or avoid a specific action might result in physical harm to you or to the hardware.
Because migration to UNIX can
Administrative migrations (for example, moving
Database migrations, such as Oracle or MySQL to Microsoft SQL Server 2000
Migrating Java 2 Enterprise Edition to Visual Studio or .NET
Linux-Apache-MySQL-PHP or iPlanet to
Applications written in languages other than C, C++, or Fortran
Apache to Microsoft Internet Information Server (IIS) migration and converting Common Gateway Interface (CGI) programs to ISAPI.NET
For more information about these topics, see the following Web sites:
Migrating Oracle Databases to SQL Server 2000
See the white paper at http://www.microsoft.com/sql/techinfo/deployment/2000/MigrateOracle.asp
Migrating Linux-Apache-MySQL-PHP platform to Windows 2000
See the white paper at http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/iis/deploy/depovg/Miglamp.asp
Planning a Web server migration project
See the article at http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/iis/deploy/planning.asp
Migrating Microsoft Hotmail
See the technical case study at http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/deploy/depopt/hotmailg.asp