Program guide > (deprecated) Partitioning facility > An example of the partitioning facility > Run operations for the partitioning facility > Monitor transaction performance statistics


Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.


Enable performance monitoring


Before you beginAs a rule, the cluster should be stopped prior to starting this example. Stop the cluster through the administrative console.


About this task

The following commands enable the PMI performance monitoring infrastructure, allowing the partitioning facility's (WPF) performance monitoring extensions to provide transaction status.

  1. Open a new command line interface, leaving the launchclient window used previously to exercise the server after the performance monitoring is initialized in this section.

  2. Execute all the remaining steps in this section in the new window.

  3. Once the new window is open, change to the deployment manager's home directory. Then, change directory to the bin directory to run the wpfadmin script.

  4. To monitor WPF, the H PMI level is required.

  5. Use:

    wpfadmin enableWPFPMI H --c cluster
    

    wsadmin -lang jython -f wpfadmin.pty enableWPFPMI H --c cluster
    WASX7209I: Connected to process "Deployment Manager" on node CellManager 
    using SOAP connector;  The type of process is: DeploymentMana
    ger
    WPFC0065I: Cluster set to cluster
    WPFC0043I: The wpfModule of PMI is enabled for cluster cluster 
    and set to level H.
    

This cluster should now be started. Use the administrative console to restart the cluster cluster_name. Now, you can track a particular transaction count for a specific bean instance.

The following command tracks the transaction count - the top 10 instances every 30 seconds.

wpfadmin subscribeWPFPMI cumulative TransactionCount 
WPFKeyBasedPartitionSample WPFKeyBasedPartition 10  30000 --c cluster

ple WPFKeyBasedPartition 10 30000 --c cluster
WASX7209I: Connected to process "Deployment Manager" on node CellManager 
using SOAP connector;  The type of process is: DeploymentMana
ger
WPFC0065I: Cluster set to cluster
WPFC0040I: WPF PMI has been subscribed with options range=cumulative, 
type=TransactionCount, application name=WPFKeyBase
dPartitionSample, ejb name=WPFKeyBasedPartition, partition count=10, 
interval=30000
WPFC0041I: Your client id is 1. Use this in future wpfadmin PMI calls.

Note the client ID. It is the reference ID used to monitor this subscription. You now have the ability to actually begin active monitoring.

Before you can monitor, some existing transactions have to be completed. If not, the client application will report an error.

To ensure you have a valid transaction, run the launch client application as performed earlier. Without ensuring some transactions are completed, we will get the following error:

wpfadmin getTransactionCount --id 1 --top 15

C:\was\nd51\bin>wsadmin -lang jython -f wpfadmin.pty getTransactionCount 
--id 1 --top 15
WASX7209I: Connected to process "Deployment Manager" on node CellManager 
using SOAP connector;  The type of process is: DeploymentMana
ger
WPFC0065I: Id set to 1
WPFC0065I: Top interval set to 15

PartitionName       TransactionCount  TotalResponseTime  MinimumTime 
MaximumTime
WPFC0045I: No statistics are available! Please wait and try again.

launchclient c:\was\base51\installedApps\Cell\
WPFKeyBasedPartitionSample.ear
-CCproviderURL=corbaloc::<host>:<port>

Turn on the Partitioning Facility's monitoring application using the following command.

wpfadmin getTransactionCount --id 1 --top 15

wsadmin -lang jython -f wpfadmin.pty getTransactionCount --id 1 
--top 15

WASX7209I: Connected to process "Deployment Manager" on node 
CellManager using SOAP connector;  The type of process is: 
DeploymentManager
WPFC0065I: Id set to 1
WPFC0065I: Top interval set to 15

PartitionName       TransactionCount  TotalResponseTime  MinimumTime  MaximumTime
PK000010            3                 1418               207          639
PK000009            3                 1456               32           752
PK000008            3                 2254               586          907
PK000007            3                 1161               149          817
PK000006            3                 2130               663          760
PK000005            3                 1711               77           908
PK000004            3                 1040               109          784
PK000003            3                 703                22           400
PK000002            3                 1138               125          684
PK000001            3                 926                31           670
==================================

PartitionName       TransactionCount  TotalResponseTime  MinimumTime  MaximumTime
PK000010            3                 1418               207          639
PK000009            3                 1456               32           752
PK000008            3                 2254               586          907
PK000007            3                 1161               149          817
PK000006            3                 2130               663          760
PK000005            3                 1711               77           908
PK000004            3                 1040               109          784
PK000003            3                 703                22           400
PK000002            3                 1138               125          684
PK000001            3                 926                31           670

This option continues tracking as long as the user does not exit with a CTRL-C in the command window.

wpfadmin getTransactionCount --id 1

wsadmin -lang jython -f wpfadmin.pty getTransactionCount --id 1
WASX7209I: Connected to process "Deployment Manager" on node CellManager 
using SOAP connector;  
The type of process is: DeploymentManager
WPFC0065I: Id set to 1

PartitionName       TransactionCount  TotalResponseTime  MinimumTime  MaximumTime
PK000010            15                7904               99           894
PK000009            15                6964               32           866
PK000008            15                6880               3            998
PK000007            15                6766               64           946
PK000006            15                9253               210          993
PK000005            15                7897               21           971
PK000004            15                7191               109          994
PK000003            15                7076               6            931
PK000002            15                7210               84           789
PK000001            15                6375               31           949

To experiment further, use the active option rather than the cumulative option. Also, the launchclient command uses a -loop xxxxx parameter. After the PMI tracking is in place, the -loop option generates transactions against each partition endpoint in a looping manner, and the active transaction reflects how many new transactions occurred over a certain instance of time.

For example:

wpfadmin subscribeWPFPMI active TransactionCount WPFKeyBasedPartitionSample 
WPFKeyBasedPartition 10
30000 --c cluster

And the launch client command to loop:

launchclient c:\was\base51\installedApps\Cell\WPFKeyBasedPartitionSample.ear 
-CCproviderURL=corbaloc::<host>:<port> -loop 10000


Parent topic:

Monitor transaction performance statistics


Related tasks

Monitor transaction performance statistics