View and adjust your enterprise and business systems (I: Analyzing, Requirement) (ccBoy original)

And adjust your business and business systems (I: Analyzing, Requirement)

Stingy gods
For dotNET, this is a new technology, an application system that adapts to changes. You may not care about the beta version, but would rather wait and see it. You may have begun to get into touch with it and use these new technologies to start thinking about the structures of current and future enterprise or business applications. What will they be like? What will they look like in front of you? You may ask yourself the following questions:
Why-what is this new technology? What is used for? What are the advantages and disadvantages of existing technologies.
Who-Who will use this technology? Is it useful to me or my applications?
When-When can I apply it? When can I start to adjust my current system or application.
Where-Where to start? Where it will be affected, where it will start and continue.
Like me, you may have some Windows DNA applications or a system running before you get in touch with dotNET. To be honest, they have some problems, but they basically run well. On the other hand, they are very interested in dotNET, because it can solve some of the previous problems. Let's assume the current system and architecture:
I suppose it runs in a Windows 2000 environment with a standard Windows DNA architecture, as shown in the figure below:
The required data is in SQL Server, assuming it is Windows 2000 ADV + ms SQL 2000; all db and Biz components are installed in App Server, it is also assumed that Windows 2000 ADV is in the COM + 1.0 environment; Web Server is also Windows 2000 ADV is IIS 5.0; Web Client assumes that it is IE5; exe Client is an EXE program generated by VB or VC. The red dotted line in the middle is the firewall. The Proxy package of App Server will be installed on both Web Server and Exe Client.
How does one add the dotNET technology to improve the current structure and functions? Can it be as shown in the following figure:
Let's take a look at what benefits we can get, and what do we have to do to get these benefits?
Benefits:
1. It is obvious that the architecture has changed with the use of dotNET technology.
2. A wide array of clients can be almost any form that is currently popular, as long as it is compatible with WebService specifications and formats.
3. Firewall problems. In this architecture, there will be no problem of COM or DCOM traversing the firewall.
4. With WebService, you can quickly Show your previous applications, such as a stock system, a flight query system, or a price query system.
5. others, for example, can say goodbye to the previous painful COM component + ASP method, especially the messy code in HTML, and start to use Web Form and Mobil Form, I think developers like a lot of improvements and user interfaces.