EOS下控制檯以及圖形界面打印sql語句

時間 2019-11-30

原文原文鏈接

EOS下控制檯以及圖形界面打印sql語句

場景需求：在eos中打印sql語句，包括數據實體，查詢實體和命名sql的sql語句。java

所需資源：mysql

P6spy：負責攔截sql，並打印。
Sqlprofiler：解析p6spy攔截的sql，在基於swing的圖形界面上顯示，並提供監控分析功能。
Spy.properties：p6spy配置文件，用來指定數據庫驅動，打印sql的目的地（文件，控制檯，sqlprofiler界面），打印格式等。web

文件下載方式：連接: https://pan.baidu.com/s/1idR310V8Ff0QLOzx3oRWMQ 提取碼: 4p4c 複製這段內容後打開百度網盤手機App，操做更方便哦sql

EOS控制檯打印

複製p6spy.ar,sqlprofiler.jar到web應用的lib目錄下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
複製spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
修改系統配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改數據源的驅動路徑爲：com.p6spy.engine.spy.P6SpyDriver。
修改spy.properties文件爲以下：（默認狀況下，本文件已經修改完畢，注意：默認鏈接Oracle數據庫，mysql數據庫需更改數據庫驅動配置）

################################################################P6Spy Options File #數據庫

See documentation for detailed instructions #
#################################################################
#################################################################
MODULES #
#
Modules provide the P6Spy functionality. If a module, such #
as module_log is commented out, that functionality will not #
be available. If it is not commented out (if it is active), #
the functionality will be active. #
#
Values set in Modules cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
module.log=com.p6spy.engine.logging.P6LogFactory
#module.outage=com.p6spy.engine.outage.P6OutageFactory
#################################################################
REALDRIVER(s) #
#
In your application server configuration file you replace the #
"real driver" name with com.p6spy.engine.P6SpyDriver. This is #
where you put the name of your real driver P6Spy can find and #
register your real driver to do the database work. #
#
If your application uses several drivers specify them in #
realdriver2, realdriver3. See the documentation for more #
details. #
#
Values set in REALDRIVER(s) cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
oracle driver
realdriver=oracle.jdbc.driver.OracleDriver
mysql Connector/J driver
realdriver=com.mysql.jdbc.Driver
informix driver
realdriver=com.informix.jdbc.IfxDriver
ibm db2 driver
realdriver=COM.ibm.db2.jdbc.net.DB2Driver
the mysql open source driver
realdriver=com.mysql.jdbc.Driver
#specifies another driver to use
realdriver2=
#specifies a third driver to use
realdriver3=

#the DriverManager class sequentially tries every driver that is
#registered to find the right driver. In some instances, it's possible to
#load up the realdriver before the p6spy driver, in which case your connections
#will not get wrapped as the realdriver will "steal" the connection before
#p6spy sees it. Set the following property to "true" to cause p6spy to
#explicitily deregister the realdrivers
deregisterdrivers=false
################################################################
P6LOG SPECIFIC PROPERTIES #
################################################################
no properties currently available
################################################################
EXECUTION THRESHOLD PROPERTIES #
################################################################
This feature applies to the standard logging of P6Spy. #
While the standard logging logs out every statement #
regardless of its execution time, this feature puts a time #
condition on that logging. Only statements that have taken #
longer than the time specified (in milliseconds) will be #
logged. This way it is possible to see only statements that #
have exceeded some high water mark. #
This time is reloadable. #
#
executionthreshold=integer time (milliseconds)
#
executionthreshold=
################################################################
P6OUTAGE SPECIFIC PROPERTIES #
################################################################
Outage Detection
#
This feature detects long-running statements that may be indicative of
a database outage problem. If this feature is turned on, it will log any
statement that surpasses the configurable time boundary during its execution.
When this feature is enabled, no other statements are logged except the long
running statements. The interval property is the boundary time set in seconds.
For example, if this is set to 2, then any statement requiring at least 2
seconds will be logged. Note that the same statement will continue to be logged
for as long as it executes. So if the interval is set to 2, and the query takes
11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
#
outagedetection=true|false
outagedetectioninterval=integer time (seconds)
#
outagedetection=false
outagedetectioninterval=
################################################################
COMMON PROPERTIES #
################################################################
filter what is logged
filter=false
comma separated list of tables to include when filtering
include =
comma separated list of tables to exclude when filtering
exclude =
sql expression to evaluate if using regex filtering
sqlexpression =
turn on tracing
autoflush = true
sets the date format using Java's SimpleDateFormat routine
dateformat=yyyy-MM-dd HH:mm:ss:SS
#list of categories to explicitly include
includecategories=
#list of categories to exclude: error, info, batch, debug, statement,
#commit, rollback and result are valid values
excludecategories=info,debug,result,batch

#allows you to use a regex engine or your own matching engine to determine
#which statements to log
#
#stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
#stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
stringmatcher=
prints a stack trace for every statement logged
stacktrace=false
if stacktrace=true, specifies the stack trace to print
stacktraceclass=
determines if property file should be reloaded
reloadproperties=false
determines how often should be reloaded in seconds
reloadpropertiesinterval=60
#if=true then url must be prefixed with p6spy:
useprefix=false
#specifies the appender to use for logging
#appender=com.p6spy.engine.logging.appender.Log4jLogger
appender=com.p6spy.engine.logging.appender.StdoutLogger
#appender=com.p6spy.engine.logging.appender.FileLogger
name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
logfile = spy.log
append to the p6spy log file. if this is set to false the
log file is truncated every time. (file logger only)
append=true
#The following are for log4j logging only
log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n
#log4j.appender.SQLPROFILER_CLIENT=org.apache.log4j.net.SocketAppender
#log4j.appender.SQLPROFILER_CLIENT.RemoteHost=localhost
#log4j.appender.SQLPROFILER_CLIENT.Port=4445
#log4j.appender.SQLPROFILER_CLIENT.LocationInfo=true
log4j.logger.p6spy=INFO,STDOUT

#################################################################
DataSource replacement #
#
Replace the real DataSource class in your application server #
configuration with the name com.p6spy.engine.spy.P6DataSource,#
then add the JNDI name and class name of the real #
DataSource here #
#
Values set in this item cannot be reloaded using the #
reloadproperties variable. Once it is loaded, it remains #
in memory until the application is restarted. #
#
#################################################################
#realdatasource=/RealMySqlDS
#realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource
#################################################################
DataSource properties #
#
If you are using the DataSource support to intercept calls #
to a DataSource that requires properties for proper setup, #
define those properties here. Use name value pairs, separate #
the name and value with a semicolon, and separate the #
pairs with commas. #
#
The example shown here is for mysql #
#
#################################################################
#realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb

#################################################################
JNDI DataSource lookup #
#
If you are using the DataSource support outside of an app #
server, you will probably need to define the JNDI Context #
environment. #
#
If the P6Spy code will be executing inside an app server then #
do not use these properties, and the DataSource lookup will #
use the naming context defined by the app server. #
#
The two standard elements of the naming environment are#
jndicontextfactory and jndicontextproviderurl. If you need #
additional elements, use the jndicontextcustom property. #
You can define multiple properties in jndicontextcustom, #
in name value pairs. Separate the name and value with a #
semicolon, and separate the pairs with commas. #
#
The example shown here is for a standalone program running on #
a machine that is also running JBoss, so the JDNI context #
is configured for JBoss (3.0.4). #
#
#################################################################
#jndicontextfactory=org.jnp.interfaces.NamingContextFactory
#jndicontextproviderurl=localhost:1099
#jndicontextcustom=java.naming.factory.url.pkgs;org.jboss.nameing:org.jnp.interfaces
#jndicontextfactory=com.ibm.websphere.naming.WsnInitialContextFactory
#jndicontextproviderurl=iiop://localhost:900
啓動eos服務器，控制檯在調用數據庫查詢的時候會打印以下的內容，即配置成功：

文件中打印

複製p6spy.ar,sqlprofiler.jar到web應用的lib目錄下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
複製spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
修改系統配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改數據源的驅動路徑爲：com.p6spy.engine.spy.P6SpyDriver。
修改spy.properties文件爲以下：

#################################################################express

P6Spy Options File #
See documentation for detailed instructions #
#################################################################
#################################################################
MODULES #
#
Modules provide the P6Spy functionality. If a module, such #
as module_log is commented out, that functionality will not #
be available. If it is not commented out (if it is active), #
the functionality will be active. #
#
Values set in Modules cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
module.log=com.p6spy.engine.logging.P6LogFactory
#module.outage=com.p6spy.engine.outage.P6OutageFactory
#################################################################
REALDRIVER(s) #
#
In your application server configuration file you replace the #
"real driver" name with com.p6spy.engine.P6SpyDriver. This is #
where you put the name of your real driver P6Spy can find and #
register your real driver to do the database work. #
#
If your application uses several drivers specify them in #
realdriver2, realdriver3. See the documentation for more #
details. #
#
Values set in REALDRIVER(s) cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
oracle driver
realdriver=oracle.jdbc.driver.OracleDriver
mysql Connector/J driver
realdriver=com.mysql.jdbc.Driver
informix driver
realdriver=com.informix.jdbc.IfxDriver
ibm db2 driver
realdriver=COM.ibm.db2.jdbc.net.DB2Driver
the mysql open source driver
realdriver=com.mysql.jdbc.Driver
#specifies another driver to use
realdriver2=
#specifies a third driver to use
realdriver3=

#the DriverManager class sequentially tries every driver that is
#registered to find the right driver. In some instances, it's possible to
#load up the realdriver before the p6spy driver, in which case your connections
#will not get wrapped as the realdriver will "steal" the connection before
#p6spy sees it. Set the following property to "true" to cause p6spy to
#explicitily deregister the realdrivers
deregisterdrivers=false
################################################################
P6LOG SPECIFIC PROPERTIES #
################################################################
no properties currently available
################################################################
EXECUTION THRESHOLD PROPERTIES #
################################################################
This feature applies to the standard logging of P6Spy. #
While the standard logging logs out every statement #
regardless of its execution time, this feature puts a time #
condition on that logging. Only statements that have taken #
longer than the time specified (in milliseconds) will be #
logged. This way it is possible to see only statements that #
have exceeded some high water mark. #
This time is reloadable. #
#
executionthreshold=integer time (milliseconds)
#
executionthreshold=
################################################################
P6OUTAGE SPECIFIC PROPERTIES #
################################################################
Outage Detection
#
This feature detects long-running statements that may be indicative of
a database outage problem. If this feature is turned on, it will log any
statement that surpasses the configurable time boundary during its execution.
When this feature is enabled, no other statements are logged except the long
running statements. The interval property is the boundary time set in seconds.
For example, if this is set to 2, then any statement requiring at least 2
seconds will be logged. Note that the same statement will continue to be logged
for as long as it executes. So if the interval is set to 2, and the query takes
11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
#
outagedetection=true|false
outagedetectioninterval=integer time (seconds)
#
outagedetection=false
outagedetectioninterval=
################################################################
COMMON PROPERTIES #
################################################################
filter what is logged
filter=false
comma separated list of tables to include when filtering
include =
comma separated list of tables to exclude when filtering
exclude =
sql expression to evaluate if using regex filtering
sqlexpression =
turn on tracing
autoflush = true
sets the date format using Java's SimpleDateFormat routine
dateformat=yyyy-MM-dd HH:mm:ss:SS
#list of categories to explicitly include
includecategories=
#list of categories to exclude: error, info, batch, debug, statement,
#commit, rollback and result are valid values
excludecategories=info,debug,result,batch

#allows you to use a regex engine or your own matching engine to determine
#which statements to log
#
#stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
#stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
stringmatcher=
prints a stack trace for every statement logged
stacktrace=false
if stacktrace=true, specifies the stack trace to print
stacktraceclass=
determines if property file should be reloaded
reloadproperties=false
determines how often should be reloaded in seconds
reloadpropertiesinterval=60
#if=true then url must be prefixed with p6spy:
useprefix=false
#specifies the appender to use for logging
#appender=com.p6spy.engine.logging.appender.Log4jLogger
#appender=com.p6spy.engine.logging.appender.StdoutLogger
appender=com.p6spy.engine.logging.appender.FileLogger
name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
logfile = c:/abc/spy.log
append to the p6spy log file. if this is set to false the
log file is truncated every time. (file logger only)
append=true
#The following are for log4j logging only
#log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
#log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
#log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n
#log4j.appender.CHAINSAW_CLIENT=org.apache.log4j.net.SocketAppender
#log4j.appender.CHAINSAW_CLIENT.RemoteHost=localhost
#log4j.appender.CHAINSAW_CLIENT.Port=4445
#log4j.appender.CHAINSAW_CLIENT.LocationInfo=true
log4j.logger.p6spy=INFO,STDOUT

#################################################################
DataSource replacement #
#
Replace the real DataSource class in your application server #
configuration with the name com.p6spy.engine.spy.P6DataSource,#
then add the JNDI name and class name of the real #
DataSource here #
#
Values set in this item cannot be reloaded using the #
reloadproperties variable. Once it is loaded, it remains #
in memory until the application is restarted. #
#
#################################################################
#realdatasource=/RealMySqlDS
#realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource
#################################################################
DataSource properties #
#
If you are using the DataSource support to intercept calls #
to a DataSource that requires properties for proper setup, #
define those properties here. Use name value pairs, separate #
the name and value with a semicolon, and separate the #
pairs with commas. #
#
The example shown here is for mysql #
#
#################################################################
#realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb

#################################################################
JNDI DataSource lookup #
#
If you are using the DataSource support outside of an app #
server, you will probably need to define the JNDI Context #
environment. #
#
If the P6Spy code will be executing inside an app server then #
do not use these properties, and the DataSource lookup will #
use the naming context defined by the app server. #
#
The two standard elements of the naming environment are#
jndicontextfactory and jndicontextproviderurl. If you need #
additional elements, use the jndicontextcustom property. #
You can define multiple properties in jndicontextcustom, #
in name value pairs. Separate the name and value with a #
semicolon, and separate the pairs with commas. #
#
The example shown here is for a standalone program running on #
a machine that is also running JBoss, so the JDNI context #
is configured for JBoss (3.0.4). #
#
#################################################################
#jndicontextfactory=org.jnp.interfaces.NamingContextFactory
#jndicontextproviderurl=localhost:1099
#jndicontextcustom=java.naming.factory.url.pkgs;org.jboss.nameing:org.jnp.interfaces
#jndicontextfactory=com.ibm.websphere.naming.WsnInitialContextFactory
#jndicontextproviderurl=iiop://localhost:900
啓動前請在指定的路徑下新建日誌文件（logfile = c:/abc/spy.log），啓動EOS服務器會在c:/abc/spy.log看到以下內容，表示配置成功：

圖形界面中打印

複製p6spy.ar,sqlprofiler.jar到web應用的lib目錄下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib）。
複製spy.properties到classpath下（如D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\classes）。
修改系統配置文件user-config.xml(D:\Primeton\eos702\apps_config\default\config)，修改數據源的驅動路徑爲：com.p6spy.engine.spy.P6SpyDriver。
修改spy.properties文件爲以下：

#################################################################apache

P6Spy Options File #
See documentation for detailed instructions #
#################################################################
#################################################################
MODULES #
#
Modules provide the P6Spy functionality. If a module, such #
as module_log is commented out, that functionality will not #
be available. If it is not commented out (if it is active), #
the functionality will be active. #
#
Values set in Modules cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
module.log=com.p6spy.engine.logging.P6LogFactory
#module.outage=com.p6spy.engine.outage.P6OutageFactory
#################################################################
REALDRIVER(s) #
#
In your application server configuration file you replace the #
"real driver" name with com.p6spy.engine.P6SpyDriver. This is #
where you put the name of your real driver P6Spy can find and #
register your real driver to do the database work. #
#
If your application uses several drivers specify them in #
realdriver2, realdriver3. See the documentation for more #
details. #
#
Values set in REALDRIVER(s) cannot be reloaded using the #
reloadproperties variable. Once they are loaded, they remain #
in memory until the application is restarted. #
#
#################################################################
oracle driver
realdriver=oracle.jdbc.driver.OracleDriver
mysql Connector/J driver
realdriver=com.mysql.jdbc.Driver
informix driver
realdriver=com.informix.jdbc.IfxDriver
ibm db2 driver
realdriver=COM.ibm.db2.jdbc.net.DB2Driver
the mysql open source driver
realdriver=com.mysql.jdbc.Driver
#specifies another driver to use
realdriver2=
#specifies a third driver to use
realdriver3=

#the DriverManager class sequentially tries every driver that is
#registered to find the right driver. In some instances, it's possible to
#load up the realdriver before the p6spy driver, in which case your connections
#will not get wrapped as the realdriver will "steal" the connection before
#p6spy sees it. Set the following property to "true" to cause p6spy to
#explicitily deregister the realdrivers
deregisterdrivers=false
################################################################
P6LOG SPECIFIC PROPERTIES #
################################################################
no properties currently available
################################################################
EXECUTION THRESHOLD PROPERTIES #
################################################################
This feature applies to the standard logging of P6Spy. #
While the standard logging logs out every statement #
regardless of its execution time, this feature puts a time #
condition on that logging. Only statements that have taken #
longer than the time specified (in milliseconds) will be #
logged. This way it is possible to see only statements that #
have exceeded some high water mark. #
This time is reloadable. #
#
executionthreshold=integer time (milliseconds)
#
executionthreshold=
################################################################
P6OUTAGE SPECIFIC PROPERTIES #
################################################################
Outage Detection
#
This feature detects long-running statements that may be indicative of
a database outage problem. If this feature is turned on, it will log any
statement that surpasses the configurable time boundary during its execution.
When this feature is enabled, no other statements are logged except the long
running statements. The interval property is the boundary time set in seconds.
For example, if this is set to 2, then any statement requiring at least 2
seconds will be logged. Note that the same statement will continue to be logged
for as long as it executes. So if the interval is set to 2, and the query takes
11 seconds, it will be logged 5 times (at the 2, 4, 6, 8, 10 second intervals).
#
outagedetection=true|false
outagedetectioninterval=integer time (seconds)
#
outagedetection=false
outagedetectioninterval=
################################################################
COMMON PROPERTIES #
################################################################
filter what is logged
filter=false
comma separated list of tables to include when filtering
include =
comma separated list of tables to exclude when filtering
exclude =
sql expression to evaluate if using regex filtering
sqlexpression =
turn on tracing
autoflush = true
sets the date format using Java's SimpleDateFormat routine
dateformat=
#list of categories to explicitly include
includecategories=
#list of categories to exclude: error, info, batch, debug, statement,
#commit, rollback and result are valid values
excludecategories=info,debug,result,batch

#allows you to use a regex engine or your own matching engine to determine
#which statements to log
#
#stringmatcher=com.p6spy.engine.common.GnuRegexMatcher
#stringmatcher=com.p6spy.engine.common.JakartaRegexMatcher
stringmatcher=
prints a stack trace for every statement logged
stacktrace=false
if stacktrace=true, specifies the stack trace to print
stacktraceclass=
determines if property file should be reloaded
reloadproperties=false
determines how often should be reloaded in seconds
reloadpropertiesinterval=60
#if=true then url must be prefixed with p6spy:
useprefix=false
#specifies the appender to use for logging
appender=com.p6spy.engine.logging.appender.Log4jLogger
#appender=com.p6spy.engine.logging.appender.StdoutLogger
#appender=com.p6spy.engine.logging.appender.FileLogger
name of logfile to use, note Windows users should make sure to use forward slashes in their pathname (e:/test/spy.log) (used for file logger only)
#logfile = spy.log
append to the p6spy log file. if this is set to false the
log file is truncated every time. (file logger only)
append=true
#The following are for log4j logging only
#log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
#log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
#log4j.appender.STDOUT.layout.ConversionPattern=p6spy - %m%n
log4j.appender.SQLPROFILER_CLIENT=org.apache.log4j.net.SocketAppender
log4j.appender.SQLPROFILER_CLIENT.RemoteHost=localhost
log4j.appender.SQLPROFILER_CLIENT.Port=4445
log4j.appender.SQLPROFILER_CLIENT.LocationInfo=true
#log4j.logger.p6spy=INFO,STDOUT
log4j.logger.p6spy=DEBUG, SQLPROFILER_CLIENT

#################################################################
DataSource replacement #
#
Replace the real DataSource class in your application server #
configuration with the name com.p6spy.engine.spy.P6DataSource,#
then add the JNDI name and class name of the real #
DataSource here #
#
Values set in this item cannot be reloaded using the #
reloadproperties variable. Once it is loaded, it remains #
in memory until the application is restarted. #
#
#################################################################
#realdatasource=/RealMySqlDS
#realdatasourceclass=com.mysql.jdbc.jdbc2.optional.MysqlDataSource
#################################################################
DataSource properties #
#
If you are using the DataSource support to intercept calls #
to a DataSource that requires properties for proper setup, #
define those properties here. Use name value pairs, separate #
the name and value with a semicolon, and separate the #
pairs with commas. #
#
The example shown here is for mysql #
#
#################################################################
#realdatasourceproperties=port;3306,serverName;ibmhost,databaseName;mydb

#################################################################
JNDI DataSource lookup #
#
If you are using the DataSource support outside of an app #
server, you will probably need to define the JNDI Context #
environment. #
#
If the P6Spy code will be executing inside an app server then #
do not use these properties, and the DataSource lookup will #
use the naming context defined by the app server. #
#
The two standard elements of the naming environment are#
jndicontextfactory and jndicontextproviderurl. If you need #
additional elements, use the jndicontextcustom property. #
You can define multiple properties in jndicontextcustom, #
in name value pairs. Separate the name and value with a #
semicolon, and separate the pairs with commas. #
#
The example shown here is for a standalone program running on #
a machine that is also running JBoss, so the JDNI context #
is configured for JBoss (3.0.4). #
#
#################################################################
#jndicontextfactory=org.jnp.interfaces.NamingContextFactory
#jndicontextproviderurl=localhost:1099
#jndicontextcustom=java.naming.factory.url.pkgs;org.jboss.nameing:org.jnp.interfaces
#jndicontextfactory=com.ibm.websphere.naming.WsnInitialContextFactory
#jndicontextproviderurl=iiop://localhost:900
打開命令行窗口，進入sqlprofiler所在的路徑，我這裏是：D:\Primeton\eos702\apache-tomcat-5.5.20\webapps\default\WEB-INF\lib，執行