|  |
Data Collector for IBM Web Services Navigator
A tool that intercepts and instruments Web service requests and responses and writes information about the Web services to a log file used by IBM Web Services Navigator.
Date Posted: January 20, 2005
|
|
|
|
|
What is the Data Collector for IBM Web Services Navigator?
The Data Collector for IBM Web Services Navigator intercepts and instruments Web service requests and responses and writes information about the Web services to a log file. This log file is used by an Eclipse-based viewer called the IBM Web Services Navigator. The Navigator processes log files that are generated by the Data Collector and generates visual representations of various characteristics of the monitored Web services.
The Data Collector is implemented as a JAX-RPC handler that is installed into the application
servers that are hosting the monitored Web services and their clients. This handler is
given control when either of the following actions occur:
- A client application invokes a Web service. This is referred to as a client-side interception.
- The Web service request is received by the hosting application server. This is referred to as a server-side interception.
The IBM Web Services Navigator is another alphaWorks technology. These two technologies complement each other to make a true technology preview.
How does it work? The Web service data collector supplements the Web service request with correlation information so that the flow of the logical transaction can be followed through a series of Web service invocations. The Web service data collector also records monitoring information in a local log file that is imported into the IBM Web Services Navigator. Two or more log files from various monitored application servers can be manually combined into a single log file. When this combined log file is imported into the IBM Web Services Navigator, information can be displayed about all of the monitored Web services and the interactions between them at the same time.
The Data Collector focuses on the simple object access protocol (SOAP) engine of WebSphere® Application Server.
Note: The Web services data collector supports only JavaTM 2 Enterprise Edition (J2EE) client and server container environments because JAX-RPC handlers are supported only in these environments. It is possible to write Web service client programs that adhere to the conventions described in Java Specification Request 101 (JSR 101) and to run them inside a J2EE container. Because of the way that these Java Specification Requests are implemented in the WebSphere environment, the JAX-RPC handler will not be invoked by these client applications. To ensure proper operation of the JAX-RPC handler, verify that your client applications are written according to the conventions described in Chapter Four of Java Specification Request 109 (JSR 109), Java Web Services for J2EE. For additional information, refer to the specification.
|
|
|
| | About the technology author(s):
Kevin Dunphy has been developing Enterprise software products for IBM since graduating from N. C. State University in 1992. Mr. Dunphy has a background in mainframe and TCP/IP communication protocols and security, and he has led projects dealing with test automation, internal-use tools, globalization, and software serviceability.
John Harter has been a software engineer with IBM since 1983 after graduating from the University of Maine at Orono. During his career at IBM, he has worked on mainframe operating systems, network file system implementions, and on various infrastructure and security projects in Tivoli. Mr. Harter's programming experience includes C/C++, Java, and WebSphere application development.
John Walczyk is a software engineer working with Tivoli Software Group. His area of expertise is design, development, and support of enterprise class software products. He is currently working on Web services management solutions, and he specializes in security- and privacy-based products. Mr. Walczyk worked on the IBM Secureway Firewall and is experienced with proxy components, VPN technology, and secure message transfer protocols. He can be reached through e-mail.
|
|
|
| |
|
