Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Administering
WebSphere Commerce database
As a site administrator, maintain the WebSphere Commerce database and ensure that any WebSphere Commerce utilities and processes that load and retrieve data from the database is configured to connect to the database properly.
Database maintenance guidelines
A WebSphere Commerce site can experience significant performance degradation if its database is not properly maintained. To prevent performance issues, implement a data maintenance strategy to remove obsolete data, periodically reorganize database tables, and maintain current database table statistics.
Database Cleanup utility
The Database Cleanup utility provides you with the ability to delete objects from the database. It is recommended that you run the database cleanup periodically, especially if a lot of information changes in your database and your database includes unused tables or rows.
Cleaning the database
Use the Database Cleanup utility to delete unused or obsolete objects from the database.
Access log data

Deleting access log data

To delete access log data objects from the database, use the Database Cleanup utility.

Before you begin

Run the following SQL statement:

insert into cleanconf (objectname, type, statement, namearg, sequence, daysarg) values ('accessLog', 'obsolete', 'delete from acclogmain where (acclogmain.acclogmain_id in (select distinct acclogmain_id from acclogsub where (days(CURRENT TIMESTAMP) - days(logtime)) > ?))', 'no', 1, 'yes')
insert into cleanconf (objectname, type, statement, namearg, sequence, daysarg) values ('accesslog', 'obsolete', 'delete from acclogmain where (acclogmain.acclogmain_id in (select distinct acclogmain_id from acclogsub where (sysdate - logtime > ?)))', 'no', 1, 'yes')

Procedure

From the WC_installdir/bin directory, run the following script:
- - ./dbclean.sh -object accessLog -db dbname -dbuser type obsolete -days daysold -loglevel loglevel
  - dbclean -object accessLog -type obsolete -db dbname -days daysold -loglevel loglevel
- - ./dbclean.sh -object accessLog -dbdbname -type obsolete -days 2 -loglevel 1 -dbtype oracle -dbuser user -dbpasswd password
  - dbclean -object accessLog -dbdbname -type obsolete -days 2 -loglevel 1 -dbtype oracle -dbuser user -dbpasswd password
  Use host:port:sid for the database name for example, myhost:1521:mydb.
Examine the WC_installdir/instances/instance_name/logs/DBClean/DBClean.timestamp.log file.