To maintain the points that provide the instrumentation instructions that tell the probe what to monitor in your application, navigate to the Configuration tab in the Java Diagnostics Profiler and click Edit... for either the Shared Instrumentation or the Instance Instrumentation. The
Instrumentation Points dialog opens:
You can edit the instrumentation in two ways: visually, using a list or tree of points on the Instrumentation Points tab; or via the source of the capture points file on the Source tab.
Selecting and Viewing an Existing Point
The navigation bar in the Instrumentation Points dialog helps locate the points in the capture points file that you would like to maintain. By making a selection from the View as dropdown, you can
choose the format in which the points are listed.
When you select Layers Tree from the dropdown, you see a list of the points in the capture points file in a tree structure according to the layers and sublayers you assigned to the point:
When you select Points List from the dropdown, you see a list of the points in the capture points file in ascending alphabetical order:
When you locate the point you want to view or maintain, select the point in the navigation bar. Then you see the details of the selected point in the view/edit panel where you can maintain the point.
Updating an Existing Point
When you select a layer or sublayer from the navigation bar, the view/edit panel contains only a prompt to remind you to select a point.
To update an existing point, select the point from the navigation bar so that the Profiler displays the details for the point in the Instrumentation Points tab of the view/edit panel:
The arguments that are commonly used when defining a point in the capture points file are displayed as separate data fields to make it easier for you to make any necessary updates. More advanced arguments are displayed in the Advanced Attributes tab at the bottom of the display.
Comments for the point are displayed in the Comment tab. After making changes click OK. And remember to apply all of the changes made using the Configuration tab by clicking Apply Changes.
The arguments that can be used to define a point in the capture points file are documented in
"Coding Points in the Capture Points File" on page 113.
The following is an example of the Source tab:
Deleting an Existing Point or Layer
You could delete a point or layer listed in the navigation bar.
To delete a point or layer:
1. Select the point or layer from the Navigation bar on the Instrumentation Points tab.
2. Click Delete Point ( ). The Profiler deletes the selected entity from the list in the navigation bar.
The selected entity is not actually deleted from the capture points file until you apply all of your instrumentation points updates from the Configuration tab in the Profiler.
3. Close the Instrumentation Points dialog by clicking OK.
4. Apply all of the changes made using the Configuration tab by clicking Apply Changes.
Adding a New Point
You could add a point to the instrumentation.
To add a point:
1. Click New Point ( ). The Profiler displays the Select New Point Type dialog box:
2. Select the appropriate point type from the dropdown and click OK.
The Profiler displays the Instrumentation Points tab with the view/edit section initialized for creating a new point for the selected point type.
3. Enter the arguments and comments for the new point into the appropriate locations on the tab.
When you enter the Layer information, the entry for the new point in the navigation bar is updated to show the point in the correct existing layer or, if the layer that you specified does not already exist, with a brand new layer.
The new point is not actually added to the capture points file until you apply all of your instrumentation points updates from the Configuration tab in the Profiler.
4. Close the Instrumentation Points dialog by clicking OK.
5. Apply all of the changes made using the Configuration tab by clicking Apply Changes.
Activating OVTA-like Points
Points are included in the Java probe instrumentation for Servlet Filters and EJB local home methods. These instrumentation points provide additional functionality similar to the OVTA (OpenView Transaction Analyzer) Java Monitor.
The ServletFilter point requires that the HttpCorrelation2 point also be activated for server filters to be monitored correctly. This is because servlet filters sometimes are the first time Diagnostics sees an HTTP server request.
The EJBLocalHome, ServletFilter, and related HttpCorrelation2 instrumentation points are not active by default. Inactive points are indicated by a red symbol on the icon next to the
instrumentation point, as shown below. To use these points, set active=true in the auto_
detect.points file through the UI or by directly editing the file.
Locate these points in the Profiler UI as described in"Selecting and Viewing an Existing Point" on page 172and navigate to the Business Tier>EJB>LocalHome>EJBLocalHome point or the Web Tier>Servlet>ServletFilter point and HttpCorrelation2 point.
To set these points to active:
1. Select the point from the Instrumentation Points navigation bar so that the Profiler displays the details for the point. Check the active check box.
2. Close the Instrumentation Points dialog by clicking OK.
3. Apply all the changes made using the Configuration tab by clicking Apply Changes. Restart your application server (which restarts the probe) for the newly activated points to take effect.
Restoring Default Points
When you finish diagnosing a problem using the Profiler or Diagnostics Enterprise User Interface, you can restore the default instrumentation to avoid incurring the overhead from a more robust instrumentation.
To restore the default settings to the instrumentation:
1. Click Restore Defaults.
The instrumentation points are not actually added to the capture points file until you apply all of your instrumentation points updates from the Configuration tab in the Profiler.
2. Close the Instrumentation Points dialog by clicking OK.
3. Apply all of the changes made using the Configuration tab by clicking Apply Changes.