Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. 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. Business users can also use AI enabled content management capabilities.
Administering
Topics in the Administering category highlight tasks that are typically performed by the Site Administrator, to support daily operations of the HCL Commerce site.
Overview of administering an HCL Commerce site
In HCL Commerce the person who performs administrative tasks is called a Site Administrator. The Site Administrator installs, configures, and maintains HCL Commerce and the associated software and hardware. The administrator responds to system warnings, alerts, and errors, and diagnoses and resolves system problems. Typically, this person controls access and authorization (creating and assigning members to the appropriate role), manages the Web site, monitors performance, and manages load balancing tasks. The Site Administrator might be responsible for establishing and maintaining several server configurations for different stages of development such as testing, staging, and production. The Site Administrator also handles critical system backups and resolves performance problems.
Administration Console
Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as refreshing the registry. You can access the Administration Console at a site-level, or for a particular store.
Jobs
A job is HCL Commerce command that is scheduled to run on behalf of a site or store at a specified time or interval. The three types of jobs are: site level jobs, store level jobs, and broadcast jobs.
Maintaining the scheduler
The SCHSTATUS table contains one entry for every execution of a job in the SCHCONFIG table. Because of the large number of jobs that are run by the scheduler, there are many job status records in the SCHSTATUS table. This size can have an adverse affect on the performance of the Transaction server. Periodically clean up the SCHSTATUS table.

Maintaining the scheduler

The SCHSTATUS table contains one entry for every execution of a job in the SCHCONFIG table. Because of the large number of jobs that are run by the scheduler, there are many job status records in the SCHSTATUS table. This size can have an adverse affect on the performance of the Transaction server. Periodically clean up the SCHSTATUS table.

Procedure

Use the Administration Console Scheduler Status Display page to delete jobs. Deleting job status records reduces the size of the SCHSTATUS table by cleaning up jobs based on time stamp and job reference number.
Schedule the CleanJob job to run and automatically trim the size of the SCHSTATUS table. Use the endTime parameter to specify whether you want to remove job status records for the previous week or the previous month. When the CleanJob command is used to trim the size of the SCHSTATUS table, it is not logged in to the table itself.
When you clean up the scheduled jobs by using the CleanJob command, the publishing utility cannot retrieve the publish status for previously published store archives. As a result, the publish status for a successfully published store archive will be Not Published, although the store archive was successfully published.
Set the autoClean parameter to on in the configuration file. This parameter causes all SCHSTATUS entries to be removed whenever the job completes.