Collecting DB2 JDBC Driver Tracing Configuration in WAS

The DB2 JDBC driver allows trace configuration through the following data source custom properties. 

traceLevel – Set to “-1” by default to capture all JDBC driver trace data.

                

If the value is null and the WAS.database=all or com.ibm.ws.db2.logwriter=all is included in the WAS trace specification, then the trace will be integrated with the WebSphere Application Server trace.

Append the following to a WebSphere connection pool trace:

WAS.database=all OR com.ibm.ws.db2.logwriter=all

The “WAS.database=all” trace property allows an integrated trace to enabled and disabled during runtime.

Troubleshooting and performance using ServiceLogger

ServiceLogger is a new lightweight trace that can be used in mainly in Production environment. This feature available in 7.0.0.4 onwards.

Add the  following code to web.xml file for the Stores.war project. This is for logging of JSP execution times with ServiceLogger requires a new Servlet Filter is registered in web.xml file.


<filter>
  <filter-name>JspExecutionServiceLoggingFilter</filter-name>
<filter-class>com.ibm.commerce.webcontroller.JspExecutionServiceLoggingFilter</filter-class>
  <init-param>
    <param-name>ServletName</param-name>
    <param-value>JspExecutionServiceLoggingFilter</param-value>
  </init-param>
</filter>


<filter-mapping>
  <filter-name>JspExecutionServiceLoggingFilter</filter-name>
  <url-pattern>/*</url-pattern>
  <dispatcher>FORWARD</dispatcher>
  <dispatcher>INCLUDE</dispatcher>
  <dispatcher>ERROR</dispatcher>
</filter-mapping>

Enabling the Logger in the WAS Admin Console:-

com.ibm.commerce.foundation.logging.ServiceLogger={fine,finer,finest}

The difference with this logger is that it will write more or less depending on the logging level selected {fine,finer,finest}. This  fine grained control allows to minimize the performance impact for use in production and other environments.

Websphere Commerces Change CommonsHttpSolrServer To HttpSolrServer

WCS Fix Pack 8 and Feature Pack 7, IBM does not changed from
CommonsHttpSolrServer class to HttpSolrServer in JSPs, its still referring old CommonsHttpSolrServer class in JSP files, so when open any starter store, solr search throws exception. 

In solr 4.0 onwards CommonsHttpSolrServer is not available, so just replace it with HttpSolrServer.It does not documented anywhere.

Solution:-

1. Find all he JSPs which contain CommonsHttpSolrServer reference

2. Replace with HttpSolrServer and save JSPs

3. Restart the app server and enjoy the new feature of FEP-7

 

WCS fixpack 8 and feature pack 7

IBM officially released WCS Fix Pack 8 and Feature Pack 7.  It would be good to have your new project.

TITLE: Fix Pack 8 (7.0.0.8) for WebSphere Commerce V7.0

URL: http://www.ibm.com/support/docview.wss?uid=swg21665674&myns=swgws&mynp=OCSSYSYL&mynp=OCSSZMJX&mynp=OCSSPK6A&mync=E

TITLE: Feature Pack 7 for WebSphere Commerce V7.0

URL: http://www.ibm.com/support/docview.wss?uid=swg21661516&myns=swgws&mynp=OCSSYSYL&mynp=OCSSZMJX&mynp=OCSSPK6A&mync=E