Website and Network Stress MonitoringWritten by Vadim Mazo and David Leonhardt
Continued from page 1
Why a stress monitoring network?
If target audience is across globe, or even across country, a company needs to monitor its website and applications stress loads from different locations across globe. The web server must provide reasonable performance from wherever customers are located. In such a situation software solution is unlikely to meet company's requirements.
Organizations must use external website stress monitoring tools, which provide detailed performance reports on servers that are tested from different locations. The outcome of these tests can help in fine-tuning settings at their ISPs and in optimizing performance of servers. Besides this, external stress testing also include monitoring of other network infrastructures that connect to web server, such as routers, firewalls and leased lines that provide back-end connectivity.
This is why Dotcom-Monitor's stress test tool offers its clients stress test agents located in various countries such as USA, UK and Germany. This service provides performance data about website from these and other locations spread across globe.
So if you run a business on Internet, it is important that your website and all associated web applications perform to their optimum levels. They handle transactions quickly and in turn offer faster response times to your user requests. Using web stress services you can get information you need to ensure superior throughputs and gain a reputation for high-performance dependability among your customers.
Vadim Mazo runs a website monitoring network, with more information on external website monitoring. David Leonhardt is a Canadian website marketing strategies consultant and an author of self-help books.
Web Services InteroperabilityWritten by Senthil Krishnamurthy from Aspire System (India) Pvt. Ltd.
Continued from page 1
2. In URL box type http://localhost:8888/axis/servlet/AxisServlet (or u can give web service URL) 3. Now it will show list of services that are available. From that select Get Order (wsdl) link. 4. Click Add Reference button. We need to create a proxy client to access this web reference. For that we need wsdl file of that particular web service. Save WSDL file The AxisServlet generates wsdl file for web service. To get wsdl for Get Order Web service, Type this URL in browser: http://localhost:8888/axis/servlet/AxisServlet. Click on wsdl link belongs to Get Order Web service. It will display wsdl xml content. Save this content with .wsdl extension. Create Proxy Client For creation of proxy client we can utilize wsdl tool of Microsoft Visual Studio. Now, open Command Prompt (preferably Visual Studio.NET Command Prompt, which verifies PATH environmental parameters are set correctly). Navigate to directory containing GetOrder.wsdl file. Type following at command prompt: wsdl /o:GetOrderService.cs GetOrder.wsdl Now GetOrderService.cs file will be created. This is proxy class for referenced web service. So, add this file into assembly of your C# project. By making instance to this proxy client we can call Get Order Web service as following code, GetOrderService GOService = new GetOrderService (); string strOrders; strOrders = GOService.getOrder (); Accessing .Net Web Service from Java For accessing .Net web service we can use org.apache.soap package and it sub package rpc. We need to provide Service URL, Target namespace and Soap Action which is present in wsdl file. By using Call class we can invoke Web service method as in following code: String URLString = "http://localhost/WebService1/Service1.asmx"; String TargetNamespace = "http://localhost/WebService1/Service1"; String SOAPAction = "http://Walkthrough/XmlWebServices/sendMessage"; URL url = new URL (URLString); //setup a invocation Call call = new Call(); call.setTargetObjectURI (TargetNamespace); call.setMethodName ("sendMessage"); call.setEncodingStyleURI (Constants.NS_URI_SOAP_ENC); Response resp = call.invoke (url, SOAPAction);
Messaging Concepts In given architecture, u can see JMS and MSMQ messaging concepts are used. Here brief notes on these concepts.
JMS JMS is a set of interfaces and associated semantics that define how a JMS client accesses facilities of an enterprise-messaging product. Enterprise messaging is recognized as an essential tool for building enterprise applications and Ecommerce systems, and JMS provides a common way for Java programs to create, send, receive, and read an enterprise messaging system's messages. You can learn more about JMS in following URL: http://www.chrispeiris.com/articles/JavaMessageService.html MSMQ Microsoft Message Queuing (MSMQ) technology enables .net applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues. You can get more details on MSMQ from http://www.microsoft.com/windows2000/technologies/communications/msmq/default.asp Conclusion In this part of Web services tutorial we learned how to write interoperable Web services. All examples were focused on integration of MS .NET and Java. We demonstrated that Web services technology gives us opportunity to pick best technology for each particular piece of our system. Some of us may want to know how to create web services in Java and C#, and also more details on integration of JMS and MSMQ with web services. Those things we are not discussed here. If you have doubts on those areas, please feel free to contact me at firstname.lastname@example.org
K. Senthil B.E., is working in Aspire Systems (India) Pvt. Ltd.