Verify you have the right prerequisites
You need to verify that DB2, Performance Expert V3.2, and the optional
WebSphere Application Server are at the minimum-required levels to run
Performance Expert Extended Insight feature, as described in the
"Prerequisites" section. For more
details, see
"IBM
DB2 Performance Expert for Linux, UNIX, and Windows Installation and
Configuration" document (see Resources).
Verify DB2 level
Performance Expert Extended Insight Feature requires a minimum of DB2 9
for the monitored DB2. It's recommended to have DB2 9, Fix Pack 5 or
DB2 9.5 (base). To validate what level you have, open a DB2 command
window. Enter the command db2level, then
press the Enter key. Figure 3 shows an
example of db2level output that indicates
the running of DB2 9.5, Fix Pack 3.
Verify DB2 Performance Expert
server level
The minimum required version of DB2 Performance Expert is 3.2. It's
strongly recommended that you also install DB2 Performance Expert V3.2
Fix Pack 2 (see Resources for a link).
To validate what level you have on Windows, open a DB2 command window
and enter pelevel. Figure 3 shows an
example of pelevel output:
Figure 3. Verifying
your Performance Expert server level in your Windows
environment
On UNIX, log in as the PE DB2 instance owner. Then from the
<Performance Expert Installation>/bin directory, enter
pelevel. Figure 4 shows an example of
pelevel output in UNIX:
Figure 4. Verifying
Performance Expert Server level in UNIX
Verify WebSphere Application
Server level (optional)
Performance Expert Extended Insight requires WebSphere Application
Server V6.1, Fix Pack 21 or WebSphere Application Server V7. WebSphere
Application Server V6 and WebSphere Application Server V7 both require
additional ifix APAR PK74962. To obtain the ifix, contact WebSphere
Support. If you're running WebSphere Application Server V6.1.0.25,
V7.0.0.5, or later, then you do not need to apply any additional fixes
to your WebSphere Application Server.
To find your WebSphere Application Server version, enter
versioninfo.bat for your Windows
environment and versionInfo.sh for your
UNIX environment. The default WebSphere Application Server install
directory for Windows is <app_server_root>\bin;
for UNIX, it is <app_server_root>/bin.
(app_server_root denotes the default install directory for
WebSphere Application Server.)
The following list shows the default installation root directories for
WebSphere Application Server for each platfom:
- AIX: /usr/IBM/WebSphere/AppServer
- HP-UX: /opt/IBM/WebSphere/AppServer
- Linux: /opt/IBM/WebSphere/AppServer
- Solaris: /opt/IBM/WebSphere/AppServer
- Windows: C:\Program Files\IBM\WebSphere\AppServer
 | |
If you are installing this on a different
system that does not meet the minimum prerequisite for WebSphere
Application Server, visit the Maintenance Download Wizard for
WebSphere Application Server V6.1 Web site (see
Resources).
|
|
By default, WebSphere Application Server is installed in system-owned
directories. Root user or administrator user (on a Windows system) may
be required to access these default directories.
WebSphere Application Server can be installed in any directory where
you have write access. Profiles can be created in any valid directory
where you have write access.
As shown in Figure 5 and
Figure 6, the Installation Status Reports (for
Windows and UNIX, respectively) indicate that WebSphere Application
Server is at V6.1 Fix Pack 21, which is the minimum support level.
Even if you run the versionInfo command
using any of the additional parameters, the ifix APAR PK74962 will not
be included in the report.
Figure 5. Verifying your
WebSphere Application Server level in Windows
environment
Figure 6. Verifying your
WebSphere Application Server level in UNIX
To start WebSphere Application Server from the Windows desktop, click
on Start > Programs > IBM WebSphere
Application Servers Network Deployment V6.1 >
Profiles >
<profile_name>
> Start the server, as shown in Figure 7:
Figure 7. Start WebSphere
Application Server from your Windows desktop
If you prefer to use the command line, enter
<profile_root>\bin\ startServer.bat
<server>.
For UNIX, enter
<profile_root>/bin/startServer.sh
<server>.
<profile_root> denotes the following default
directories for a profile <profile_name> for each
platform:
- AIX:
/usr/IBM/WebSphere/AppServer/profiles/<profile_name>
- HP-UX:
/opt/IBM/WebSphere/AppServer/profiles/<profile_name>
- Linux:
/opt/IBM/WebSphere/AppServer/profiles/<profile_name>
- Solaris:
/opt/IBM/WebSphere/AppServer/profiles/<profile_name>
- Windows: C:\Program
Files\IBM\WebSphere\AppServer\profiles\<profile_name>
<profile_name> denotes the profile you assigned to
your WebSphere Application Server, and <server>
denotes the name of the application server to start.
Figure 8. Start WebSphere
Application Server from your Linux environment
To verify your WebSphere Application Server is running, from a Windows
command line enter
<profile_root>\bin serverstatus.bat <server> –profileName
<profile_name>.
Let's take a look at an example. Notice in Figure 9
that the <profile_name> is AppSrv02 and the
<server> is server1:
-
C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv02\bin
serverstatus.bat server1 –profileName AppSrv01
- Enter
serverstatus.bat server1 –profileName
AppSrv01.
Figure 9. Verifying
WebSphere Server is running in Windows
From UNIX, from the command prompt, enter
<profile_root>/bin/serverStatus.sh <server>
–profileName <profile_name>.
Let's take a look at an example. Notice in
Figure
10 that the
<profile_name> is AppSrv01 and the
<server> is server1:
-
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
- Enter
./serverStatus.sh server1.
Figure 10. Verifying
WebSphere Server is running in UNIX (Linux)
Java Client Driver (IBM
Driver for JDBC and SQLJ)
To verify your Java client driver, go to the jcc driver directory,
then enter the following command (as shown in Figures
11 and 12):
java –cp "<Path for your jcc driver>\db2jcc.jar" com.ibm.db2.jcc.DB2Jcc –version |
Performance Expert Extended Insight Feature requires a JDBC Type 4
driver to connect to the Data Server. The following JCC drivers are
supported:
- JCC 3.53 with APAR IZ43011 for JDBC 3 clients or later
- JCC 4.3 with APAR IZ43011 for JDBC 4 clients or later
Figure 11. Verifying your Java
Client driver on Windows
Figure 12. Verifying
your Java Client driver on UNIX
Note: To use Performance Expert Extended Insight, you must have
at the minimum JCC version. 3.53.72. Refer to "How to find IBM DB2
Driver for JDBC and SQLJ version and environment information" in the
DB2 9 for Linux, UNIX, and Windows Information Center for more
information (see Resources for a link).
| 
