Program guide > (deprecated) Partitioning facility > Manage the partitioning facility environment > Performance monitoring

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

The partitioning facility PMI statistics retrieval

If you are interested in the Performance Monitoring Infrastructure (PMI) statistics of a particular partition or a server, you can directly retrieve it using wsadmin tool or the Java™ Management Extensions (JMX) MBean.

About this task

If you have subscribed to the partitioning facility PMI statistics using the wpfadmin command or WPFJMX MBean, you can use wpfadmin to retrieve the statistics:

• wpfadmin.bat|wpfadmin getTransactionCount --id PMI_SUBSCRIPTION_ID

• --top REFRESH_INTERVAL.

• wpfadmin.bat|wpfadmin getResponseTime --id PMI_SUBSCRIPTION_ID

• --top REFRESH_INTERVAL.

• REFRESH_INTERVAL.

• wpfadmin.bat|wpfadmin getFailedTransactionCount --id PMI_SUBSCRIPTION_ID

The PMI_SUBSCRIPTION_ID is the client ID you get when you subscribe the partitioning facility PMI. If you use --top option, the output is updated every specified refresh interval, like the Unix top command. Also, you can also use Java code, jacl script or jython script to get the WPFJMX MBean to get the statistics similar to the examples shown in 10.5.2.

1. Run the following command to get the PMI data.

   wpfadmin getResponseTime --id 1
   

   You will see the following output:

   WPFC0065I: Id set to 1
   
   PartitionName TotalResponseTime TransactionCount  MinTime  MaxTime  
   StartTime  SumOfSquaresWPFC0045I: No statistics are available! 
   Please wait and try again.
   

   You do not see any statistics data because there are no PMI data in the system yet. Now, you can run the client to generate some statistics.

2. Open a new command window or shell, and run the following command:

   <ND_install_root>/bin/launchClient 
   <ND_install_root>/installedApps/<CELL_NAME>/WPFKeyBasedPartitionSample.ear 
   -CCproviderURL=orbaloc::HOSTNAME:SERVER_RMI_PORT
   

   where, HOSTNAME is the name of the host that has the application server, and SERVER_RMI_PORT is the RMI port of that server, for example, 9811. You will see client runs with a similar output like this:

   IBM WAS, Release 5.1
   J2EE Application Client Tool
   Copyright IBM Corp., 1997-2003
   WSCL0012I: Processing command line arguments.
   WSCL0013I: Initializing the J2EE Application Client Environment.
   WSCL0035I: Initialization of the J2EE Application Client Environment 
   has completed.
   WSCL0014I: Invoking the Application Client class 
   com.ibm.websphere.wpf.client.WPFKeyBasedPartitionClient
   Create Partitions from PK000001 to PK000010
   1st call: PK000001->partiton=PK000001,server=Tiger1/clus1srv1
   2nd call: PK000001->partiton=PK000001,server=Tiger1/clus1srv1
   3rd call: PK000001->partiton=PK000001,server=Tiger1/clus1srv1
   1st call: PK000002->partiton=PK000002,server=Tiger1/clus1srv1
   2nd call: PK000002->partiton=PK000002,server=Tiger1/clus1srv1
   3rd call: PK000002->partiton=PK000002,server=Tiger1/clus1srv1
   1st call: PK000003->partiton=PK000003,server=Tiger1/clus1srv1
   2nd call: PK000003->partiton=PK000003,server=Tiger1/clus1srv1
   3rd call: PK000003->partiton=PK000003,server=Tiger1/clus1srv1
   1st call: PK000004->partiton=PK000004,server=Tiger1/clus1srv1
   2nd call: PK000004->partiton=PK000004,server=Tiger1/clus1srv1
   3rd call: PK000004->partiton=PK000004,server=Tiger1/clus1srv1
   1st call: PK000005->partiton=PK000005,server=Tiger1/clus1srv1
   2nd call: PK000005->partiton=PK000005,server=Tiger1/clus1srv1
   3rd call: PK000005->partiton=PK000005,server=Tiger1/clus1srv1
   1st call: PK000006->partiton=PK000006,server=Tiger1/clus1srv1
   2nd call: PK000006->partiton=PK000006,server=Tiger1/clus1srv1
   3rd call: PK000006->partiton=PK000006,server=Tiger1/clus1srv1
   1st call: PK000007->partiton=PK000007,server=Tiger1/clus1srv1
   2nd call: PK000007->partiton=PK000007,server=Tiger1/clus1srv1
   3rd call: PK000007->partiton=PK000007,server=Tiger1/clus1srv1
   1st call: PK000008->partiton=PK000008,server=Tiger1/clus1srv1
   2nd call: PK000008->partiton=PK000008,server=Tiger1/clus1srv1
   3rd call: PK000008->partiton=PK000008,server=Tiger1/clus1srv1
   1st call: PK000009->partiton=PK000009,server=Tiger1/clus1srv1
   2nd call: PK000009->partiton=PK000009,server=Tiger1/clus1srv1
   3rd call: PK000009->partiton=PK000009,server=Tiger1/clus1srv1
   1st call: PK000010->partiton=PK000010,server=Tiger1/clus1srv1
   2nd call: PK000010->partiton=PK000010,server=Tiger1/clus1srv1
   3rd call: PK000010->partiton=PK000010,server=Tiger1/clus1srv1
   

3. Wait at least one to two minutes to let the aggregator sort the statistics, then run wpfadmin getResponseTime -id 1 again. You will see the following output.

   WPFC0065I: Id set to 1
   
   PartitionName TtlRspnsTm  TrnsctnCnt  MinTime MaxTime  StartTime   SumOfSqrs
   PK000004      1625           3            7     903  1094180666309 1226203
   PK000010      1543           3          260     671  1094180667170 892385
   PK000005      1423           3           51     965  1094180666389 1099475
   PK000008       932           3           99     482  1094180666990 365326
   PK000002       862           3          217     364  1094180666038 258546
   

   Notice that the TotalResponseTime in the output might be different from the one here, since the response time is generated as a random value.

Parent topic:

Performance monitoring

Related concepts

Performance monitoring

+

Search Tips   |   Advanced Search