I had a local copy of a WebSphere Commerce database that was performing horribly, and I decided to create a script that would retrieve a list of all available tables for all non-system schemas, and perform a RUNSTATS and REORG for those tables.
Working on a project recently I found the need to determine the master catalog for a list of stores within a WebSphere Commerce database. Seeing as a WebSphere Commerce instance can contain a variety of stores, ranging from your traditional Consumer Direct model to a more extensible Extended Site model, I generated the following query which can be run against the WebSphere Commerce database to properly determine the master catalog identifier for each store.
The following SQL statements can be used to reset the default “wcsadmin” account password on a developer’s toolkit, back to its default value of “wcsadmin”, assuming the following criteria have been met.
This post builds upon a previous post, WebSphere Commerce v7.0 Store Functions, and goes into the checking the status of enabled or disabled store functions within your Java code.
WebSphere Commerce v7.0 Feature Pack 2 introduced a new way to handle change flows, now referred to as store functions. For those not familiar with store functions, a store function is basically a way to handle and control pieces of your pages and/or logic from display or execution based upon the availability of the feature within your store.
