Using the Product in a WebSphere Application Server Environment › Monitor WebSphere Application Server › Scenario 2—User Suspects a Specific Problem

Scenario 2—User Suspects a Specific Problem

This scenario assumes that you are aware of suspected problem areas or have already monitored the suspect transactions in nontargeted mode.

In this scenario, you target specific transactions with the use of transaction filters and generate detailed reports.

1. Request additional WAS targeting data by providing specific transaction filters.

   In the following example the filter value *plants* will cause only those transactions containing the value plants to be reported.

   CA MAT ------------- WebSphere Application Server Criteria ---------------
   COMMAND ===>
   
   Expert Mode ==> N    Y - Collect PSW samples
                        N - Disable PSW sampling
   
   Specify Application URL Filters:
   => *plants*
   => 
   => 
   => 
   
   Specify System Class Filters:
   => 
   => 
   => 
   
   Specify values. Press END to return to Monitoring Criteria
   

   You can specify several filter patterns in each input field, separated by a comma (*plants*,*admin*,/burn*).

2. Submit a monitor for each occurrence of the associated J2EE Servant Regions, unless you already know the Servant Region.

   There can be 1 to n occurrences of this Servant address space.

3. Analyze the monitor data sets to identify specific causes of application performance issues.

   The WebSphere Transactions report will only contain transactions whose URL names match the filter criteria, as shown next.

   CA MAT ------------ WebSphere Transactions ----------------- Row 1 to 2 of 2 
   COMMAND ===>                                                SCROLL ===> HALF  
                                                                                  
   Primary commands: MOde URL/Application/Via/Current,          Profile: PLANTS2 
                     GARbage, WAS (Environment info), SQL          Mode: URL     
                                                                                  
      Line commands: A - Application Classes   S - SQL                            
                     V - Via Classes           D - Delays                         
                     C - Current Classes       N - URL Name                       
                                                                                  
                                                                                  
   LC Transaction URL                  Active% InvWait% VolWait% Total% Visual    
      ________________________________ _______ ________ ________ ______ _________
   >-----------------------------------------------------------------------------
   
   __ /PlantsByWebSphere/servlet/Shopp  83.11    0.00     0.00    83.11 ========>
   __ /PlantsByWebSphere/servlet/Image  16.89    0.00     0.00    16.89 =>        
   *********************************End of Table ********************************