Starting with Version 6.1.0.9, Collection Services, a component
of WebSphere® Application Server for IBM® i,
collects Performance Monitoring Infrastructure (PMI) data for stand-alone
application servers. This PMI data is collected at specified intervals,
providing a snapshot of activity during that time.
About this task
Perform the following steps enable Collection Services
for WebSphere Application Server. When Collection Services is enabled,
it writes the collected data into the following new database files:
- QAPMWASCFG
Server configuration data. This data includes
information about the different WebSphere Application Server jobs.
This information is static and therefore does not change during life
of the server. There is one record per server.
- Server data
One record is created for each active server
job per interval. Much of the data comes from WebSphere Application
Server PMI data and transaction counters.
- Application data
It contains one record for each application
module per interval. WebSphere Application Server PMI counters are
the source for many of the fields in this file. For the JavaServer
Pages (JSP) section, the data in each field represents a sum over
all JSPs running in a given application.
- QAPMWASEJB EJB data
This data includes information
about applications with Enterprise JavaBeans (EJB) running on the
WebSphere Application Server. Each record represents one type of enterprise
beans per application module per interval. If there is no bean activity
for a particular EJB type, then no record is written.
- QAPMWASRSC
Pooled resource data. This data includes
information about pooled resources associated with WebSphere Application
Server. Each record represents one pooled resource per interval. The
type of pooled resource might be a Java Database Connectivity (JDBC)
connection pool, a J2EE Connector (J2C) connection pool, or a thread
pool. Not all fields are applicable to each pooled resource type.
If a resource exists but is not being used (nothing is created, destroyed,
allocated or returned), no record is written.
Procedure
- Install and enable the Collection Services custom service:
- Type the following command on an i5/OS command line to start the
Qshell environment:
STRQSH
- Type the following command:
cd install_root/bin
- Type the following command to install and enable the Collection
Services custom service:
manageWASCollectionServices -profileName pName -server.name sName -enable
where pName is
the name of the WebSphere Application Server profile to manage and sName is
the name of the Application Server to manage.
- Enable PMI and set
the level using the administrative console.
- Stop and restart the application server.
- Perform the following steps to configure Collection Services:
- On an i5/OS command line, type CFGPFRCOL (Configure
Performance Collection) and press the F4 key.
- Make note of the collection library specified to create the management
collection object (Collection library parameter, LIB keyword).
- Make note of whether or not database files are automatically created
(Create database files parameter, CRTDBF keyword).
- Type the following command to start the performance collection:
STRPFRCOL
- If you configured Collection Services with CRTDBF(*YES),
new records are written to all of the above files at every collection
interval. If CRTDBF(*NO) is specified, no database files are created
automatically, you need to do it manually using the CRTPFRDTA command.
Here are two examples: