Identifying the Role of the Migration Tool
Updated: August 22, 2005
Applies To: Windows Server 2003, Windows Server 2003 with SP1
Before you migrate Apache Web sites to IIS 6.0, you must know which steps of the migration process are automated by the Apache to IIS 6.0 Migration Tool and which steps you must complete manually. This will allow you to have the appropriate tools and resources available when you are ready to start the migration. In addition, you need to determine the configuration and placement of your Web site after running the tool. The automation provided by the Apache to IIS 6.0 Migration Tool is the same for static and dynamic content. However, depending on the content in your Apache Web site, further configuration might be required after running the tool.
The following steps in the Apache Web site migration process are automated by the Apache to IIS 6.0 Migration Tool:
Copying of Web site content
The migration tool creates a copy of the files and folders containing Web site content. The copied files are converted from standard UNIX text file format (end-of-line denoted by carriage return) on the server running Apache to standard Windows text file format (end-of-line denoted by carriage return and line feed characters) on the server running IIS. The Web site content is placed on the server running IIS in a location selected while running the tool.
Translation of Web site configuration
The configuration of the Apache Web server and individual Web sites is translated to the corresponding IIS Web server and Web site configuration settings in the IIS metabase.
Migration of ~user directories
~user directories are private virtual Web directories that contain individual user Web sites. The tool migrates the contents of these directories, creates corresponding users, and converts permissions found in these virtual Web directories.
Translation of .htaccess permissions
The .htaccess file sets permissions for access for the virtual Web directories on an Apache Web server. The permissions in this file are translated by the tool into the corresponding directory permissions in the NTFS file system.
Migration of MIME types and port numbers
MIME types define the types of static files that are served by the Web server. The tool automatically determines the MIME types defined on the Web server running Apache and then creates the associations of MIME types to extensions on the Web server running IIS.
Migration of FrontPage Server Extensions
The tool detects the presence of FrontPage 2000 Server Extensions and FrontPage 2002 Server Extensions on the Apache Web server; enumerates the Web sites and subweb sites; enumerates the FrontPage Server Extensions settings, users, and roles; creates the Web sites and subweb sites; and recalculates the links for each Web site and subweb site.
Creation of status file
The tool creates a file that contains the status of the migration steps completed by the tool. The status file can be used for confirming that the migration completed successfully or for troubleshooting any problems encountered while performing the migration with the tool.
The following steps in the Apache Web site migration process need to be completed after running the Apache to IIS 6.0 Migration Tool:
Convert code within dynamic content
Dynamic content, such as PHP or CGI, on Apache needs to be modified to run on IIS 6.0.
Modify database connectivity within dynamic content
For the Web sites and applications that have database connectivity, the content needs to be modified to use database connectivity provided by IIS 6.0 and Windows Server 2003.
Migrate external modules used by Web sites
After migration, you need to migrate external modules that are used by the Web sites and applications.
Add Web service extensions used by the Web sites
Any dynamic content types that are not automatically migrated by the tool must be added as Web service extensions. These new Web service extensions might be necessary for any modifications or conversions of dynamic code.
Configure advanced Web site properties
After the tool completes its migration tasks, the Web sites are configured comparably to how they were on Apache. You might want to configure the Web site to take advantages of the advanced security and availability features in IIS 6.0.
Obtain server certificates for SSL
For each Web site on the Apache Web server that uses SSL, you must either renew the existing server certificates in a format that is compatible with IIS 6.0 or you must request new server certificates in a format that is compatible with IIS 6.0. This is because the server certificates on the Apache Web server are in a format that is incompatible with IIS. Once you have the server certificates, you must import the certificates into IIS and configure your Web sites to use the appropriate certificates.