Perspective and Adjust your Enterprise and Business System (I: Analyzing, Requirement)
Small gas god 2001-10-09
For DOTNET, this is a new technology, an application system system that adapts to changes. You may not be a test version, you would rather wait and see; you may have begun to contact it, start thinking about the current and future business or business applications through these new technologies. What will they be, what will be a situation in front of you? Generally you will ask yourself:
Why - What is this new technology? Is it used for dry, and what is the advantage of existing technologies.
Who - Who will use this technology? Is it useful to me or my app?
When - when can I apply it? When started to adjust my current system or application.
Where is WHERE? Where will be affected, where to start and continue.
You may be like me, there are some applications of Windows DNA or a system running before contacting DOTNET. Honestly, they have some problems, but basically run well; another perspective, I am very interested in DOTNET, because from the current point of view it does solve some of the previous problems. Ok, let's assume that the current system and architecture:
I assume that it runs in a Windows 2000 environment, the standard Windows DNA architecture, as shown below:
What you need is in SQL Server, suppose it is Windows 2000 Adv MS SQL 2000; all DB and BIZ components are installed in the App Server, but it is a Windows 2000 ADV, which is the COM 1.0 environment; Web Server is also Windows 2000 Adv That is, IIS 5.0; Web Client assumes that it is IE5; Exe Client is the EXE program generated by VB or VC. The red dashed line in the middle is a firewall. The App Server's Proxy package will be installed on the Web Server and Exe Client.
How to join DOTNET technology to improve current structure and function? Can you like a picture below:
Let us see what benefits we can get, what must I do for these benefits?
benefit:
1. It is obvious that the DOTNET technology is started, and the architecture changes.
2. Client enriches, almost any form now, as long as it is compatible with the WebService specification and format.
3. The firewall problem, there is no problem with COM or DCOM through the firewall under such an architecture.
4. With WebService, you can quickly use Show you used to apply, such as your original, a stock system or a flight query system or a price query system, etc.
5. Other additional, such as the way you can bid farewell to the way COM components ASP, especially those that clamp in HTML, start using Web Form and Mobil Form, etc., I want to develop many improvements and user interfaces that developers like. aspect.
So what do you have to get these improvements and benefits?
1. I don't want to rewrite the existing components (will not be too painful!); Moreover, numerous business logic is still re-real, and how many errors will be generated, it will affect the current operation, 99.8% will not do this. 2. You also don't want to separately write a packaged WebService against each BIZ component, because this not only increases the future maintenance work but also these "encapsulation webservice", which is low, and the same conditions will be reduced more than previous performance.
3. Adjustment can, must ensure that there is no impact on the current operation, and some code is adjusted and written.
4. To connect the old architecture, if you can, if you can, new demands and functions are implemented with DOTNET, that is, ensure smooth slow switching to the new architecture of DOTNET, and old code does not have to change or rewrite.
5. Other additional, such as adjustment, future upgrade maintenance, etc., adjust the possible risks that may be brought.
Then I think the best is to simulate the current environment and generate a model. At the beginning, it may be a very simple idea, but I found that the entire process is an experience process, very interesting and interesting. I don't know if you will agree that I am in this article's last point or conclusion (if there is any conclusion and point of view Haha), but I want to be sure, that is, the platform, what platform is you programmed? Choosing a different platform, the environment you are in and face will be completely different, the perspective of development and thinking will also be completely different, maybe the first question you think in the future will be: You want to stand on that platform? .
Here is a few of the processes to discuss and involve it, and it is also the entire process I simulate:
1. Generate a COM DB and BUS, simulate current existing applications or features. Distributed on both machines. One is SQL Server (EricsVR) one is App (HenrySVR), putting the DB and BIZ components together, and IIS is also on this machine. The clients of IE and EXE are also on this machine or another machine (Dereksvr).
2. For the above BIZ, commercial logic, use Microsoft Soap Toolkit to generate WebService. Interestingly, I found that it is not as simple as Sample on Sample, but there is a large number of adoDb.recordset's return and application, so I want to know these Recordset What is the WEBSERVICE? Finally, I use VB and VS.NET to create a VB and DOTNET's Client to call the WebService on this HenrySVR on another machine (Dereksvr).
3. MS Soap Toolkit WebService, especially with AdoDb.Recordset, WebService, can be said to be a good WebService, but maybe not optimal, then I use vs.net to generate another form of WebService (ASP.NET WebService) This is that Recordset is encapsulated and can't see, because it is very familiar .asmx, for the client, close to the DOTNET architect chart showing. Finally, I only used a web form to call this WebService. The poorest is that Ericsvr is only 64m, and the MS SQL 2000 is also running, HenrySVR is also a few years ago, it is borrowed from Hub and NIC performances, but they use "strength" to prove they can accomplish these processes.
especially:
The above text involves other people's privacy and personal rights, such as non-authorized or agree, please do not publish, reprint, adapted, repost, or other forms of communication. All of the above texts and images are only used for internal communication, and do not make any news publishers and commercial purposes.
