ITCAM for SOA 7.2 Fix Pack 1

Testing and debugging Web services

By now you have installed IBM® Tivoli® Composite Application Manager for SOA. You have started using it to monitor Web services and collect metric and content data, storing it locally in log files or, if your environment is configured for historical data collection, writing the data to the warehouse database. Now that you have also installed IBM Web Services Navigator, you are ready to view and analyze Web services that you are currently monitoring in your test or production environment.

To view and analyze Web services, use the following steps:

Deploy the Web services to your appropriate application servers.
If you are collecting historical Web services data and writing it to the warehouse database, note the start and end time in Greenwich Mean Time (GMT) of the data collection so that you can later retrieve the correct data from the warehouse.
1. If you are in a test environment and not storing data in the warehouse, delete or move existing log files so they are not included with your retrieved data.
2. If you are in a production environment, and not storing data in the warehouse, note which log files exist so that you use log files only with newly retrieved data.
Move the Web services traffic through the deployed Web services.
1. If multiple application servers are being used to monitor Web services, collect the log files from all the application server computers to the computer where you have installed the IBM Web Services Navigator.
Launch the IBM Web Services Navigator.
1. If you are storing data in the warehouse, import the data of interest from the warehouse database.
2. If you are not storing data in the warehouse, use the import function of IBM Web Services Navigator on your local computer, and import the resulting log files in to the Navigator view of the IBM Web Services Navigator.
  1. On the Eclipse menu bar, select File -> Import.
    (Optional) Right-click in the Navigator view and select Import.
  2. On the Import Select page, expand the Other node, select Import local data collector log files and click Next.
  3. On the ITCAM4SOA log file import page, specify the project name where the combined target log file is to be stored, in the Project field. You can enter the project name in the format /Name, or click Browse and navigate to the preferred project.
  4. In the File Name field, specify the name of the combined target log file to be stored in the selected project. The file name must end with the .log suffix (for example, data1.log). See Figure 1
  5. Click Select log files to select one or more log files to combine in to the target log file. Navigate to the preferred log file directories, %CANDLE_HOME%\KD4\logs, %CANDLE_HOME%\KD4\logs\KD4.DCA.CACHE, or %CANDLE_HOME%\KD4\logs\KD4.DCA.CACHE\archive on your local system, or to similar directory locations on networked systems in your Web services environment. Highlight all of the files to be included in the combined target log file, and click Open.
    You are returned to the ITCAM4SOA log file import page, where your selected files are displayed.
  6. After you have selected all of the preferred log files from one or more monitored systems in your Web services environment, click Finish.
View your data in the various available views, and verify that Web services are functioning as expected.

If your Web services are not functioning as expected, the reason might be due to various problems, for example:

Your Web services client applications might not be written according to the conventions described in chapter 4 of Java™ Specification Request 109 (JSR 109), Java Web Services for J2EE. Refer to the specification found at the following Web location:
http://www.jcp.org/aboutJava/communityprocess/final/jsr109/
The monitoring criteria that was configured in IBM Tivoli Composite Application Manager for SOA might not be defined for the data you expect. See the IBM Tivoli Composite Application Manager for SOA Installation Guide and the online help for more information about configuring monitoring and filtering criteria.
If you are monitoring Web services in a BEA WebLogic application server environment, the client side application code needs to be modified for proper operation of the monitoring agent. See the IBM Tivoli Composite Application Manager for SOA Installation Guide for more information.

For additional installation help, refer to Troubleshooting in this publication and the similar chapter in the IBM Tivoli Composite Application Manager for SOA Troubleshooting Guide.

For additional information about using IBM Web Services Navigator, including example tasks and tutorial information, see the online help information by completing the following steps:

In the Eclipse workbench window, click Help –> Help Contents.
The help system for the IBM Web Services Navigator is displayed in a separate window.
In the table of contents section, click IBM Web Services Navigator.
Navigate to the various sections of the online information for help on the topics of interest.

Feedback