ahk2chan

WebSphere Commerce allows you to enable or disable login timeout for a register user. If the feature is enabled, then once a user is logged on but idle for a certain amount of time, the session will expire and the user has to re-log on again if the user becomes active.

(more about WebSphere Commerce Enable / Disable Login Timeout in Instance XML…)

If you are looking for the java source codes that are translated by WebSphere from JSPs, here is the location you can find the java files:

WAS_root_dir/temp/server_name/instance_name/instance/your_jsp_path/xxx.java

If the JSP is throwing exception, you should be able to see the exception in SystemOut.log. There you can find the translated java file name. Then you can do a find on that file name root from WAS_root_dir/temp.

IBM HTTP Server (IHS) 2.0.47 is the same as Apache HTTP Server 2.0.47. You can cache static objects such as images and static HTML pages on the web server layer. There are a number of parameters that you can use to configure web server caching, and here are 2 of them: CacheMaxExpire and CacheDefaultExpire…

(more about IBM HTTP Server Memory Cache Configuration Parameters – CacheMaxExpire and CacheDefaultExpire…)

Here is a list of WebSphere Commerce Trace components that you can specify at WAS admin console.  To enable them, from WAS admin console, go to Troubleshooting -> Logs and Trace -> Your Server -> Diagnostic Trace -> Configuration -> Enable trace.

(more about Configure Logging – WebSphere Commerce Trace Components…)

I have been doing some more researches about how to configure WebSphere Plugin for fail over. Basically the configuration manages how WAS requests will be dispatched to different application servers in a cluster environment. There are 3 parameters in particular that I looked at (for fail over): ConnectTimeout, ServerIOTimeout, and RetryInterval.

(more about Configure WebSphere Plugin for Fail Over In Cluster Environment…)

Within a WebSphere Commerce command execution, when the commitCopyHelper method is called on a particular AccessBean, the data will NOT be updated immediately.  The data will actually be stored in EJB Cache, until the performExecute method exits successfully without any exception, that is the transaction is commited.  So if you use EJB to update, and then within the command (i.e. the same transaction), you try to use a direct JDBC query to retreive the information out, then your query will NOT see the newly inserted data!  So…

(more about EJB AccessBean commitCopyHelper Method Not Writing To Database – Use WebSphere Commerce BaseJDBCHelper flush method…)

In order to cache properly with DynaCache, on all JSPs, make sure that c:import and jsp:import are wrapped around by flush. That is, an out.flush before the import AND an out.flush after the import…

(more about WebSphere Commerce DynaCache Tip – flush Before Import…)

WebSphere EJB Cache size specifies the number of buckets in the active instance list within the EJB container. The default is set to 2053. Decode: Forget about the buckets, basically we need the right number, not too many (waste memory) and not too little (slow response). According to documentation, the limit is soft limit, that is, beans will still be added to cache even the limit is exceeded. To find the proper EJB Cache Size…

(more about WebSphere Commerce – Tuning WebSphere EJB Cache Size…)

For the same page request (for example: CategoryDisplay), if you want to have 2 different cache entries in Dynacache, one for the secure request (HTTPS) and one for the non-secure request (HTTP), all you need to do is from your cachespec.xml, define the protocol as part of the cache key (i.e. in the cache-id section). Here is the component you need to define…

(more about Dynacache Separate Cache Entries for Secure (HTTPS) and Non-Secure (HTTP) Requests…)

WebSphere Commerce stores the scheduled job status in the SCHSTATUS table.  Each time a scheduled job is run, it will have a status row in the table.  The status field is SCSSTATE, and the possible values are…

(more about WebSphere Commerce Possible Scheduled Job Status (SCHSTATUS.SCSSTATE)…)