Windows 2000 has been released, and you may have begun to consider how to migrate ASP applications from Windows NT to 2000. If the existing Windows NT based ASP application does not change, can it run under Windows 2000? After all, migrating an application is not a simple task, what can be done to make the application more smoothly transition to Windows 2000?
Before you start porting work, you might want to know which features do not or will only have a small impact under Windows 2000, or which features require minimal improvement to optimize performance. You may also want to know what changes Windows 2000 and Microsoft Internet Information 5.0 have caused to potential problems with existing ASP applications? Specifically, you need a transplant program.
In order to get you into the situation faster, we wrote a step-by-step porting process. Although we'll discuss these in more detail in a later article, you should be aware of these basic steps.
1. Install and configure Windows 2000 and IIS5.0 on the development, testing, and eventual use of the computer.
2. Rebuild the original site on all computers, including the virtual path.
3. Set the security options in the test and final production environment (note).
4, copy all the ASP pages, as well as all related graphics, scripts to the development environment. In addition, ASP components that are not part of MTS are replicated to the development environment.
5, in the development environment will be MTS porting to COM + applications.
6, install Visual Studio (or other development tools).
7. Test each ASP module (ASP pages and related components) individually in the development environment, making appropriate modifications to ensure that the application behaves the same under Windows 2000 and Windows NT.
8, the tested and modified ASP and related COM + replication to the test environment for compatibility testing. In addition, you can adjust the settings for IIS 5.0 and use the Stress test tool to determine which settings are more appropriate for your application.
9. Porting tested and performance-adjusted ASP applications and associated COM + components to the final production environment, remembering to migrate only one application at a time. Tracks the performance of CPUs in each new ported ASP application, ensuring that new applications do not consume too much CPU time, and that CPU and bandwidth throttling can be implemented on new ASP applications if necessary.
10, use the new monitoring features provided by Windows 2000 (such as the CPU tracking tool) to monitor the application in the final environment.
These steps seem to correspond to a great deal of work, but one completes these. Your ASP application does not need to be developed to run the work, and will not be in the final production environment some unexpected things happen. Instead, you can move on to the new features offered by Windows 2000 and start thinking about how to use these new features to improve ASP applications.
* Note: Final production environment (Production environment)
