The eG Installation Guide - eG Innovations

Installing and Configuring on Unix
i. Start WebLogic Server by running startWebLogic.cmd.
ii. Start the Administration Console tool by navigating to http:/ :7501/console.
iii. Navigate to the -> Services -> JDBC -> Connection Pools node
and set the Driver Classname for each Connection Pool to
com.p6spy.engine.spy.P6SpyDriver.
f. If using RDBMS Security Realm, configure P6Spy to monitor your realms (in this example,
commercePool, dataSyncPool, and wlcsRealm) by completing the following steps:
i. Using the Administration Console, navigate to the -> Security ->
Realms node.
ii. Select the security realm.
iii. Click the Database tab.
iv. Set the Driver parameter to com.p6spy.engine.spy.P6SpyDriver.
g. Using the Administration Console, shut down the WebLogic Server. Right-click on the
-> Servers -> node and select Stop this Server from the
pop-up menu.
h. Restart WebLogic Portal by running startWebLogic.cmd.
i. The JdbcStatsTest can be applied to other application servers as well. When doing so,
refer to the p6spy home page (http://www.p6spy.com/) to determine how to setup p6spy to
interoperate with the application server being considered (Note that eG Enterprise uses a
version of p6spy that is augmented with database monitoring and reporting capabilities
specific to the requirements of eG Enterprise). When configuring p6spy for an
application server, note that the location of the properties file -
spy.properties - can be specified by defining the environment variable "p6.home". For
example, if the spy.properties file is in the directory /opt/egurkha/lib, this
can be indicated to the application server by using the java argument
-Dp6.home=/opt/egurkha/lib i.e.,
java -Dp6.home=/opt/egurkha/lib ....
j. eG Enterprise uses a JSP page hosted on the application server to
extract measurements by interfacing with the p6spy driver configured in the previous
step. For WebLogic servers, this JSP is a part of the egurkha.war application that is
configured for the WebLogic server. For other servers, copy the file JdbcStatsTest.jsp that
exists in the \lib directory into the appropriate location of the application
server, so that the JSP can be accessed via HTTP/HTTPS from the eG agent. The prefix of
the URL that the agent must access to collect database related statistics is specified as an
argument to the JdbcStatsTest. The agent appends /egurkha/JdbcStatsTest.jsp to the URL
prefix and uses this check for database statistics.
k. To minimize the overhead of the JDBC monitoring, eG Enterprise can be
configured to only consider database queries that take more than a pre-defined threshold
period to execute. The variable executionThreshold in the spy.properties file
denotes the threshold value of the query processing time in milliseconds. If a query takes
less than this value, it is not considered for reporting by the eG agent as detailed
diagnosis for the JdbcStatsTest.
83