Administration guide > Monitor the environment



Monitor eXtreme Scale information in DB2

When the JPALoader or JPAEntityLoader is used with DB2 as the back-end database, eXtreme Scale-specific information can be passed to DB2. You can view this information by a performance monitor tool such as DB2 Performance Expert to monitor the eXtreme Scale applications that are accessing the database.


Before you begin

You can set trace strings with many different methods. See Logs and trace for more information about the different methods that you can use.

When the loader is configured to use DB2 as the back-end database, the following eXtreme Scale information can be passed to DB2 for monitoring purposes:

Read about the DB2 Performance Expert to learn how to monitor database access.


Procedure


Results

After you turn on the trace function, data displays in the performance monitor tool such as DB2 Performance Expert.


Example

In the following example, user bob is authenticated as an eXtreme Scale user. The application is accessing the mygrid data grid using the DB2Hibernate persistence unit. The container server is named XS_Server1. The resulting information follows:

In the following example, user bob is authenticated using a WebSphere Application Server token. The application is accessing the mygrid data grid using the DB2OpenJPA persistence unit name. The container server is named XS_Server2. The resulting information follows:


Parent topic:

Monitor the deployment environment


Related concepts

Statistics overview

Monitor with vendor tools

JPA Loaders

Program for JPA integration

Loaders

Plug-ins for communicating with persistent stores


Related tasks

Monitor with the web console

Monitor with the statistics API

Monitor with the xsAdmin sample utility

Monitor with WAS PMI

Monitor with managed beans (MBeans)

Configure JPA loaders

Troubleshoot loaders

Troubleshoot Java Persistence API (JPA) applications