Websphere Commerce Developer SQL Profiling

SQL Profiling on developer toolkit is a very handy tool during development and performance tuning of the application, recently I came across this link on developerworks and had to include few minor hacks to make it work on my V7 toolkit. here are few key steps which will supplement this article on developerworks

Reference link: http://www.ibm.com/developerworks/websphere/library/techarticles/0905_roberts/0905_roberts.html

1. Copy the downloaded jar jdbcProfiler.jar to

SDP\runtimes\base_v7\lib\ext\

http://www.ibm.com/developerworks/apps/download/index.jsp?contentid=391299&filename=sql_profiler.zip&method=http&locale=worldwide

2. I tried these changes for embedded Apache Derby database, this invloves editing following entry.
in WCDE_ENT70\workspace\WC\META-INF\ibmconfig\cells\defaultCell\applications\defaultApp\deployments\defaultApp\resources.xml
 I replaced the driver impl class name as below (highlighted in RED)
    <resources.jdbc:JDBCProvider description="Cloudscape JDBC Driver"
        implementationClassName="com.ibm.issw.jdbc.wrappers.WrappedDerbyDataSource"

For Oracle DB change the corresponding entry for Oracle with following impl class.

com.ibm.issw.jdbc.wrappers.WrappedOracleDataSource 

3. Download the RAD plugin by pointing to site.xml from downloaded file. This will download the required RAD plugin.

NOTE: Follow the steps in http://www.ibm.com/developerworks/websphere/library/techarticles/0905_roberts/0905_roberts.html
to install the plugin, first download sql_profiler.zip from http://www.ibm.com/developerworks/websphere/library/techarticles/0905_roberts/0905_roberts.html#download,extract updatesite.zip from it and then follow instructions in section "Installing the client plug-in in Eclipse" to install the plugin

4. You need to change the listener port for the SQL profiler from the default 26000, this involves following changes

a. Set a JVM custom property "com.ibm.issw.jdbc.profiler.port" as follows


b. Change the listening port number from RAD.

5. Do a Clean/Publish from your RAD, during startup you should be able to see a similar message as below, this indicates the SQL profiler has started successfully.
00000014 JdbcProfilerD I   Jdbc Profiler listening to socket 2075

6. During server startup notice that you have selected SQL Profiler Prospective, you should be able to see sql tracing during server startup as shown below.

Pituluik Media

Blogger | Freelancer |Operations Manager | Marketing and Sales Manager | Lancer Evo 4 Community. Indonesian Bloggers Who Become Bloggers Because of Hobby. Feel free to connect with me on Social Media Instagram @alberandesko

Share this post