New Feature Experience of Windows Server 2003

xiaoxiao2021-03-06  99

Written / Guo Hongjun Keywords .NET Frameworks IIS Server This article introduces the most compelling new features of Windows Server 2003, .NET Framework 1.1 integration, IIS6 functional enhancements, and many other improvements.

When you see this article, Windows Server 2003 has been officially released. As a microsoft, it is another attempt to enter the enterprise calculation after Windows 2000. Microsoft tried to use this more scalability, more reliable server operating system, to protect the traditional UNIX share, and against Linux's violent attack. In this article, we will stand in the developer's perspective to see what changes will Windows Server 2003 bring us. Net Framework 1.1 is close to developers, there is no doubt that the most important thing is that Windows Server 2003 is closely integrated with .NET Framework 1.1. As the core of the .NET strategy, Microsoft's development tools will be expanded for .NET Framework 1.1, which means that most of the applications will run in this running environment in the future. After Windows Server 2003 integrates .Net Framework 1.1, there is no need to worry about the release of the program.

The .NET framework is an infrastructure of the entire .NET platform. This framework combines the general language runtime (CLR) and a set of unified class libraries, including Windows, ADO.NET, ASP.NET, and other capabilities. Windows Server 2003 default .NET Framework is 1.1 instead of 1.0, .NET Framework 1.1 version has added some new features on the 1.0 version, enhances existing features. The main new (enhanced) functions are as follows: Side By Side executes the side-by-column execution supported by the .NET Framework will enable the system administrator to store and execute multiple versions of the application (or components) on the same machine. This means that you can have multiple versions of the .NET Framework distribution package like multiple versions of the application (or components) on the same machine. Support for the invocation of WinForm's Assemblies in the Internet. For example, the WinForm control is embedded in a web page or WinForm's assemblyMBlies exists on an Internet server, he can simultaneously from the browser with system.reflection.assembly. The loadFrom () method is called. This use method can now be performed by a SEMI-Trusted method. The default security policy has been modified to enable the Assembly allocated by the CLR to access the Internet area. Code set. And in .NET Framework 1.0 SP1 and SP2, such an application will not have permission. Note: When we use this method, the client will not give full privilege if the client will give full privileges. By default, due to the security settings of code access, these codes are run in a limited way, and they only have few permissions to ensure the normal operation of the code security. This code cannot destroy your data or system, and you can't steal your personal privacy. Support access to ODBC and Oracle Database

Now we can operate the ODBC's easy to use the Oracle database directly in the .NET. I used ODBC before .NET, we must also download ODBC.NET using ODBC. Now .NET has provided us with system.data.odbc namespace, now we don't have to worry. The same now .NET also gives us a namespace for System.Data. OracleClient, which uses OCI (Oracle Call Interface) to implement data access. (Figure 1) Unified programming model .NET Compact Framework provides CLR, WinForm Controls and other features, are designed for some small devices, and .NET Compact Framework also supports most .NET Framework class libraries and optimizes to adapt to small devices. Supported devices include Pocket PC 2000, Pocket PC 2002, etc. Operating Windows CE.NET 4.1, pay attention to this previous version of CE is not supported: Compact CLR is good to use control code (such as memory management) benefits Adapt to a small device. Internet Information Services (IIS) 6.0IIS is now self-evident in Microsoft's strategy. As a platform running web and more important web services, IIS is critical. Compared with IIS5.0, the change in IIS6.0 is huge, redesigned architecture and operating models, making IIS, whether there is significant progress in performance, reliability or security. Here is the specific improvement of IIS6.0.

The new request processing structure IIS 5.0 is designed to have only one main web server process - IITINFO.EXE, which can be used to assign request to one or more process applications (DLLHOST.exe). In contrast, IIS 6.0 is designed as two new components that use new kernel mode drivers. This allows IIS to leave the web server core code from the application processing code. These two new components are HTTP listeners in kernel mode - http.sys and user mode configured with process manager --Web management services; application handlers are loaded into a stand-alone worker process. These workers process takes a service to request a request for application pools in http.sys. The initial tests made on a server with eight processors show that the ASP design of the ASP.NET benchmark can reach 100% throughput. Http.sys - New kernel mode driver http.sys is a new kernel mode driver that handles all coming (server-side) HTTP requests. This provides a higher performance connection for the HTTP server application. The driver is located on top of TCP / IP, receives all connection requests from the IP / port combination it liss. Http.sys is also responsible for all connection management, bandwidth and web server logs. Preliminary test shows that compared with IIS5.0, the static content can increase 200% throughput; the cache response can be achieved by 165% throughput. Cache Policies and Thread Manage IIS 6.0 has an advanced algorithm to determine cached, frequently accessed applications or site sets. Just because a certain item is cache, it is meaningless to add an item to the memory buffer because it is necessary to pay at the time of managing the project and the memory it. Therefore, IIS6.0 uses a new algorithm to determine which items should be cached based on requests received by a particular application. This means that the web server can make full use of resources on the server while maintaining frequent performance performance, meaning that its scalability is improved. The Web Farmweb Farm is an application pool, where multiple processes provide services to the request of the pool. The worker process in Web Farm can be configured to bind it to a set of specified CPUs in the multiprocessor system. Through Web Farm, web applications improve its extension, because a software lock in progress does not block all requests to the application. If there are 4 processes in Web Farm, a specific software lock generally only blocks 1/4 request. The continuous ASP template is bundled in IIS 5.0. Before the ASP code execution, the ASP is prior to compiling the ASP file as an ASP template. These ASP templates are stored in memory. If the site contains a lot of ASP pages, the cache will release the most old template occupied memory, and provide space for the new template. In IIS 6.0, these templates are continuously saved on disk. If one of the ASP files are re-requested, the ASP is proud to load the template page instead of loading the ASP file, compiling it again with another CPU. The initial test showed that the performance of IIS 6.0 and ASP was increased due to continuous storage in disk cache, and its throughput increased by 50%. By default, IIS is a worker process run at a lower privileged account to run as NetWorkService, and the privilege of this built-in account is very low. Running with low privilege account is a very important security principle. If the worker process is very small in the underlying system, the attack on the potential security weakness can be strictly restricted. IIS 6.0 also provides status monitoring to discover, recover, and prevent web applications failures. On Windows Server 2003, Microsoft ASP.NET uses new IIS process models locally. These advanced applications status and detection functions can also be used in existing applications running in Internet Information Server 4.0 and IIS 5.0, most applications do not require any modifications. IIS 6.0 Fault Recovery Process Model IIS 6.0 provides an architecture to improve the degree of isolation of the application software.

Administrators can create multiple application pools and assign applications to these pools to provide isolation. Application software pools can be monitored and automatically regenerated to ensure availability of application software. The COM service in the ASP is in IIS 6.0, the IIS and COM groups are separated from the components and allow the ASP application to use COM services. In addition to the services existing in Windows 2000 COM , some new services have been added in the ASP and supported: aggregation support - ASP application can use specific versions of system runtime DLL or typical COM Component. Division Support - Com Division allows administrators to define different configurations for different users for different users. The configuration includes security and versioning information. For more information on COM , please consult your COM document. ASP.NET: Integrated ASP.NET integration in IIS 6.0 In the Internet Information Services (IIS) 6.0 processing model, multiple application software can be supported. This means that the individual's ASP.NET application software is isolated and directs the HTTP listener conversation with the core mode. This causes the number of jumps during the processing, while allowing the ASP.NET application to support the core mode of file cache. ASP.NET: Advanced Compile. NET Framework Advanced Compilation By compiling instead of explaining to perform web pages to provide enhanced performance. It supports both pre-compiled applications, also supports online compilation applications. ASP.NET supports more advanced thread models, which allows it to perform asynchronous I / O to improve performance and scalability. The practice of converting the server-side code before performing is not necessary, so that server resources are saved, and the performance and scalability of the server are improved. ASP.NET: Smart Cache ASP.NET Programming Model provides a cache API that allows programmers to activate cache services to improve performance. An output cache saves a complete web page, while the clip cache stores some web pages. The corresponding classes are provided so that the application software, the HTTP module, and the requesting processor can store any object in the cache in the cache according to their respective needs. Other improvements, of course, as an operating system that is time-consuming years, the improvement of Windows Server 2003 is not allowed, in which the developers will affect the impact.

New Application Programming Interface (APIS) Windows Server 2003 introduces a large number of new application programming interfaces (APIs) that make it a more efficient and flexible development platform. These new application programming interfaces (APIs) include: Managing IP Security: Windows Server 2003 contains a local system management API to control IP protocol security (IPSec).

Improved COM Windows Server 2003 has made several aspects of the component object model, including: uses the application as a service: Improvement to General Object Model COM 1.x allows you to configure a COM server application into one Services, and putting a service as a COM server application. This provides more control over the COM application startup process. Taking the app as a service to run means that the built-in dynamic link library (DLL) is loaded in memory when the system is started. This will make a COM application software available and allows it to be installed on a cluster server. Application Software Partition: Application Software Allows to install and configure multiple versions of COM applications on the same computer. This will make server applications to manage more economically. Application Software Process Dump: Pause / Prohibition Application provides a new process dump feature to dump all status of a process without having to end the process. Component alias: COM 1.x provides component alias. This provides the ability to make multiple configurations for physical implementation of the same component. Configurable Isolation Level: COM 1.x provides the ability to configure isolation levels, which is flexible than ever. Low memory activation threshold: COM 1.x blocks the error path from running on the server. COM checks the memory when it creates a COM server or an object, rather than passively waiting for a part of the code to get memory allocation. If the virtual memory percentage of the application is reduced to a fixed threshold, the activation operation of the memory will fail before the object is created. Process regeneration: This improvement allows you to manage the regeneration of the process through the COM management software development package (SDK) through the COM management software development package or planned. Based on several standards, the process can be turned off or regenerated, including the time, memory usage, the number of calls, and the number of activations. Internet Protocol 6 (IPv6) IPv6 is the Internet layer protocol in the next-generation TCP / IP protocol group. IPv6 solves issues with address loss, security, automatic configuration, scalability, etc. in Internet Protocol 4 (IPv4). The IPv6 protocol in Windows Server 2003 Family improves common TCP / IP tools (including IPCONFIG, ROUTE, NETSTAT, PING, TRACERT, and PATHPING), extending API support (including Windows Sockets, remote procedure calls, Iphelper). System components that support IPv6 include Internet Explorer, Telnet client, FTP client, Internet Information Services (IIS) 6.0, files, and print sharing. This does not mean that IPv6 will cause problems related to IPv4. Windows Server 2003 Family supports IPv6 and IPv4 coexistence with some technologies, such as 6TO4 and Site Auto Channel Resolution Protocol (ISATAP).

The command line management of the command line is significantly enhanced by the command line structure of the Windows Server 2003 series, enabling the administrator to perform the vast majority management tasks without using the graphical user interface. Most importantly perform the functions of most tasks by using the information store enabled using the Windows Management Specification (WMI). This WMI command line (WMIC) feature provides a simple command line interface, interacts with existing shells and utility commands, and can be easily extended by scripts or other-oriented applications. For example, the following two new features:

Use the solution at any time available to you can use or you can use it. All tools have consistent, standard grammar, and easy access to command line documents (/? Help text) and comprehensive HTML Help files -: "NTCMDS.CHM". Remote Management All new tools support remote server operations through / s parameters (eg, remote system names, / s myserver), and can run under Telnet and Terminal Services, fully implementing remote command line management.

Small knot Windows Server 2003 has a significant performance on performance indicators that are concerned about enterprise-class computing, such as reliability, scalability, and security. It is also very considerate for developers' support. For the majority of Windows old users, the upgrade is worth it.

转载请注明原文地址:https://www.9cbs.com/read-124221.html

New Post(0)