This week I’ve looked into fetching list prices using the list price rule defined in commerce. There isn’t any GUI to set the rule used for your list prices. And if you just fetch the value from CatalogEntryDataBean getListPrice you will get the value in the table LISTPRICE which should be deprecated in FEP6. You…
When using the marketing trigger “Current page” with “Customer is viewing a catalog entry”. The template you use is actually saying look for a specific productId on a command called ProductDisplay. If you look in the dmeletemplate table you could find all the templates for the different triggers and other elements used by marketing. In…
We’re looking into a solution using log4j to consolidate our logs in an third-party system using Application server and IBM has disabled the support for log4j in the application servers logging framework. I tried to reverse this process and check what was needed to enable this feature again. First of we need the log4j framework…
Trying to implement a SQRL login for Websphere Commerce I ran in to the issue of changing the logged in user from another session. To accomplish this I used the persistent sessions in commerce fetching an activity and changing what user ran in that session. If you want to enable this behavior you need to…
If you’ve added the JSP performance enhancements I’ve discussed in an earlier post. Then I talked about a flag that disabled JSP compilation. In order to run without compilation enabled you need to precompile your JSP files. This could be done with the JspBatchCompiler command found in {WAS_ROOT}/bin This command has multiple parameters but only a…
I was looking into an performance issue the other day and came by some small interesting changes you could do to your Websphere Application Server to increase performance and remove locks. The first was located in the file Stores.war/WEB-INF/ibm-web-ext.xml a file that I’ve never looked at. Seems that the WAS developers enabled support for handling the…
I had a problem with some webservices connections timing out in our environments and I thought that the timeouts where a bit long. Most of our webservices run inline with a user request and some of the default timeouts didn’t make the cut. com.ibm.websphere.webservices.http.connectionTimeout=300 com.ibm.websphere.webservices.http.maxConnection=50 com.ibm.websphere.webservices.http.SocketTimeout=300 The settings above is the onces set in Websphere…