Building a Robust and Highly Scalable Distributed Architecture using VB.NET - How to Test Remoting Component Using Windows Service
(Page 6 of 6 )
The following are the steps which are to be followed very strictly (we are about to work with projects 1, 3, 6 and 7):
- This is continuation from previous sections.
- Now move to MyTrail\BusinessComponentService\bin folder using the same command prompt and execute the following command at the prompt to register the service in the windows services registry.
Installutil BusinessComponentService.exe
- Open Programs -> Administration Tools -> Services and check whether ‘RemoteAccessAgent’ service (our own service) is started or not. If not, start it. (show in the Fig 6)
- Now move to ‘MyTrail\ConsoleServiceClient\bin‘ folder using the same command prompt and execute ‘ConsoleServiceClient.exe’, which should return a message ‘Successful’.
- Check your table ‘tAreas’ where a dummy value ‘from Remoting Client (with WinService)’ gets inserted just to prove the Windows Service with Remoting Functionality.
Conclusion
Strictly speaking, these many tests are not at all required to design the architecture. But this methodology at every level (or layer) with simple Console applications makes our life easier in examining the reliability of the respective component together with debugging. You can also further extend this with a Web service so that it is accessible globally across platforms!
All of the above tests can also be executed within Visual Studio.NET environment. But the registrations are to be done manually (like gacutil, installutil). You are also required to change your ‘start up projects’ within the solution accordingly to meet the respective criteria of tests.
In all of the above projects, I kept my coding as simple as possible and arranged ‘heavy commenting‘ wherever necessary, just to understand the implementation of distributed architecture. With a very good implementation of DAL, life becomes very much simpler together with Business Components. I hope this would give you a very good start on an INTRODUCTION to designing and implementing scalable distributed architectures using .NET Enterprise Services.
I used Windows Server 2003 standard edition, Visual Studio.NET 2003 Enterprise Architect together with SQL Server 2000 to have this solution completed. But the same should also work with Windows 2000 family too. In case, if it doesn’t work, you need to check out at MSDN (as COM+ 1.5 version of Windows 2003 and XP has got some enhancements when compared with COM+ 1.0 version of Windows 2000). But the modifications would be very minor, and that too just changing the attributes in coding. The execution is always the same.
I leave it to the programmers for further enhancements. Any doubts, comments, suggestions, bugs, errors or feedback are welcomed at the discuss link at the bottom of the page.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 42 
