Migrating Dynamic Content

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

The Apache to IIS 6.0 Migration Tool transfers the files that make up the dynamic content to the target server during the Web site content migration. However, the dynamic content typically cannot run on IIS and requires further tailoring. Table 7.5 describes the advantages and disadvantages of the methods for migrating dynamic content.

Table 7.5 Comparison of Methods for Migrating Dynamic Content

Migration Method Advantages Disadvantages

Run dynamic content on a preprocessor that ships with IIS and Windows Server 2003.
  • Requires minimal migration effort, depending on the extent of changes to the dynamic content.

  • Requires no purchase of additional preprocessor.
  • Might not run as efficiently as dynamic content written in ASP or ASP.NET.

Run dynamic content on a preprocessor external to IIS and Windows Sever 2003.
  • Requires minimal migration effort, depending on the extent of changes to the dynamic content.
  • Might not run as efficiently as dynamic content written in ASP or ASP.NET.

  • Requires purchase of an additional preprocessor.

Rewrite the dynamic content in ASP or ASP.NET.
  • Runs the dynamic content more efficiently than the other methods.

  • Requires no purchase of additional preprocessor.
  • Requires the most migration effort because the dynamic content must be completely rewritten.

Important

When you run dynamic content written in preprocessors, you need to enable the Web service extensions (request handlers, such as Perl and CGI, that extend IIS functionality beyond serving static pages) for the preprocessor. For more information, see Configuring Web Service Extensions in IIS 6.0.

Run Dynamic Content on a Preprocessor that Ships with IIS

When you select this method for migrating the dynamic content, you must have the source code to the dynamic content and you must use a preprocessor that ships with IIS 6.0 and Windows Server 2003, such as CGI or Perl. You might have to adjust the code to accommodate any differences between preprocessors on Apache and IIS and between Linux and Windows.

Ensure that the version of the preprocessor supported on IIS 6.0 and Windows Server 2003 is compatible with the version of the code in the dynamic content. You will most likely need to modify the code in the dynamic content to compensate for version and platform differences. For example, CGI scripts migrated from Apache Web sites typically require modification to run on IIS 6.0 and Windows Server 2003.

Run Dynamic Content on a Preprocessor External to IIS

This method for migrating the external module assumes that you have the source code to the dynamic content and you can purchase or obtain a version of the preprocessor that runs with IIS, such as PHP. You might have to adjust the code to accommodate any differences between preprocessors on Apache and IIS 6.0.

For example, if the dynamic content is written in PHP, you must obtain a version of a PHP preprocessor for IIS to install and configure the PHP preprocessor on IIS 6.0. You must then adjust the PHP code to accommodate any differences between the PHP preprocessors on Apache and IIS 6.0.

Rewrite the Dynamic Content in ASP or ASP.NET

When you select this method for migrating the dynamic content, you need to evaluate the function of the original dynamic content, draft a functional specification for the dynamic content, and then develop a version of the dynamic content in ASP or ASP.NET.

For more information about selecting either ASP or ASP.NET, see Active Server Pages and ASP.NET.