|  | (Optional) Enable DB2 Performance Expert Extended Insight on
your WebSphere V6.1 Fix Pack 21 + ifix
- Start the WebSphere Application Server.
- Open a Web browser, then enter the URL for your WebSphere
Application Server Integrated Solutions Console. For example,
https://localhost:9043/ibm/console/logon.jsp.
In Windows, you
can start the WebSphere Application Sever for AppSrv01 profile
by either entering the above URL or by clicking on
Start > All Programs > IBM
WebSphere > Application Server Network
Deployment V6.1 > Profiles >
AppSrv01 > Administration
Console.
From the command line in UNIX, enter
<profile_root>/bin/startServer.sh
<server>;
or for Windows, enter
<profile_root>\bin\ startServer.bat
<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.
- Enter the user ID and password, then click on the Log in
button:
Figure 19.
WebSphere Application Server Administration Console
login
- Click on Resources > JDBC > JDBC
Providers:
Figure 20.
WebSphere Application Server, configure JDBC
driver
- Double-click on Derby JDBC Provider:
Figure 21.
WebSphere Application Server, configure JDBC driver:
Select Derby JDBC provider
- Scroll down the page, and click on the Class path text
box.
- Scroll to the end of the line and hit the Enter key to
create a new line:
Figure 22.
WebSphere Application Server, configure JDBC driver:
Create a new line
- Enter the Performance Expert Extended Insight Feature pdq.jar
file, then hit the Enter key to create a new line.
Here
is a list of default locations of the Performance Expert
Extended Insight Feature pdq.jar file for each platform:
- AIX: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdq.jar
- HP-UX: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdq.jar
- Linux: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdq.jar
- Solaris: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdq.jar
- Windows: C:\Program Files\IBM\DB2 Performance Expert
Extended Insight Feature\pureQuery\pdq.jar
- Enter the Performance Expert Extended Insight pdqmgmt.jar file:
Here is a list of default location of the Performance
Expert Extended Insight Feature pdqmgmt.jar file for each
platform:
- AIX: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdqmgmt.jar
- HP-UX: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdqmgmt.jar
- Linux: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdqmgmt.jar
- Solaris: /opt/IBM/DB2 Performance Expert Extended Insight
Feature/pureQuery/ pdqmgmt.jar
- Windows: C:\Program Files\IBM\DB2 Performance Expert
Extended Insight Feature\pureQuery\pdqmgmt.jar
Figure 23.
WebSphere Application Server, configure JDBC driver: Add
Performance Expert Extended Insight Feature to your class
path
- Scroll down the page, then click on the Apply button:
Figure 24.
WebSphere Application Server, configure JDBC driver: Apply
changes
- Click on Save:
Figure 25.
WebSphere Application Server, configure JDBC driver: Save
changes
- If you are running WebSphere Application Server V7, then you are
done. Click on Logout.
If you're running
WebSphere Application Server V6, then you will need to create and
specify customer properties for your enterprise information system
(EIS) data source to access DB2. Note: You only need to do
this for WebSphere Application Server V6.
- From the main menu on the left side of the screen, select
Resources > JDBC > Data
Sources.
- Select the name of your data source. In this example, the
name of the data source is "Trade Data Source":
Figure 26.
WebSphere Application Server, configure data
sources
- Click on Custom properties:
Figure 27.
WebSphere Application Server, configure data
sources: Click on Custom properties
- Click on New:
Figure 28.
WebSphere Application Server, configure data
sources: Creating new custom properties for your
enterprise information system
- Enter the following field information, then click on
Apply:
- Name:
enableEndToEndMonitoringFeature
- Value:
true
Figure 29.
WebSphere Application Server, configure data
sources: Applying your new custom properties for
your enterprise information system
- Click on Save:
Figure 30.
WebSphere Application Server, configure data
sources: Save your new custom properties for your
enterprise information system
- Scroll down to verify the entry has been added. You may
have to click on the "Next" button (right arrow) to view
the next page:
- Click on Logout:
Figure 31.
Logout
- Close the browser.
- After you make changes to the WebSphere Application Server, you
need to stop and restart it.
- To stop the WebSphere Applications Server from the Windows
desktop, click on Start > All
Programs > IBM WebSphere >
Application Server Network Deployment V6.1
> Profiles > AppSrv01 >
Stop the server:
Figure 32. Stop
WebSphere Application Server from Windows
desktop
If you prefer to use the command line, enter the
following:
<profile_root>\bin\ stopServer.bat <server> |
For UNIX, enter the following, as shown in
Figure 33:
<profile_root>/bin/stopServer.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 stop.
Figure 33. Stop
WebSphere Application Server from UNIX
(Linux)
- 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 serverL
Figure 34.
Start WebSphere Application Server from your
Windows desktop
If you prefer to use the command line, enter the
following:
<profile_root>\bin\ startServer.bat <server> |
For UNIX, enter the following:
<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 35.
Start WebSphere Application Server from your Linux
environment
 |
| |
|
