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.
Request for Quote objects

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.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
- Administering
  - Overview of administering a WebSphere Commerce site
    In WebSphere Commerce the person who performs administrative tasks is called a Site Administrator. The Site Administrator installs, configures, and maintains WebSphere 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.
  - WebSphere Commerce instance
    Every WebSphere Commerce installation requires at least one instance to function, and each WebSphere Commerce instance can contain one or more stores.
  - Managing features
    You can administer the features for your store and site, such as attribute, catalog, promotion, marketing, order management features, and more. The administration tasks that you can complete differ depending on the type of feature and the tool that you use to administer your store and site.
  - Logging services
    WebSphere Commerce provides facilities for logging. For existing customers, ECTrace and ECMessage are still supported. For new implementations, use the WebSphere Application Server recommendation for logging and tracing.
  - Business auditing
    Business auditing is the capturing of the business logic and objects during a WebSphere Commerce operation. You may want to audit your business for various reasons: generic, such as to review various tasks performed weekly; or specific, such as to track the steps involved in a particular Customer Service Representative's order. A report on business auditing is available in the Administration Console.
  - Business events
    Each time that a command triggers a business event, a record is added to the BUSEVENT database table to persist data from the event. Event listeners and external systems (such as the Marketing component, a back end order management system, or an external analytics system) can use this data to perform further processing.
  - Staging server
    The WebSphere Commerce staging server is a part of the production environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production server.
  - 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 connection validation
      The database connection validation utility tests the connection to the WebSphere Commerce database and logs the connection test results. Use this information to troubleshoot database-related problems. The utility tests whether a connection can be established for a WebSphere Commerce utility or process with the configured parameters.
    - 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.
      - Implementing a data maintenance strategy
        By implementing an effective data maintenance strategy when a site goes live, you can avoid database issues such as performance degradation, exceeding available storage, and increased backup and restore times.
      - Managing the KEYS table for non-sequential key enabled tables
        WebSphere Commerce provides data load utilities to load data. If you are using a custom utility to load data into WebSphere Commerce tables, you must update the corresponding entries in the KEYS table.
      - 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.
        Setting the PATH environment variables for WebSphere Commerce utilities
        Before you use the Database Cleanup utility or the staging server, ensure that you set the required PATH environment variables for your operating system.
        Configuring the staging environment to run the utility
        You can use the Database Cleanup utility to cleanup data in a staging environment when your staging and production environment databases are synchronized.
        Configuring the utility to delete more data
        The Database Cleanup utility is configurable. You can define tables and rows to clean in addition to the cleanup configurations that are defined by default. You can define tables and rows to delete by updating the utility configuration data in the CLEANCONF table. To extend the Database Cleanup utility, specify values for the jdbcDriver and jdbcUrlPrefix parameters when you are running the utility.
        Database Cleanup utility objects
        To determine which tables and which rows to delete, the Database Cleanup utility uses the CLEANCONF table.
        Cleaning the database
        Use the Database Cleanup utility to delete unused or obsolete objects from the database.
        Access log data
        Address objects
        Available to promise inventory objects
        Attachment objects
        Base item objects
        CACHEIVL objects
        Calculation code objects
        Calculation rule objects
        Catalog group objects
        Catalog version objects
        Contract objects
        To delete contract objects from the database, use the Database Cleanup utility.
        Distributor objects
        Expected inventory record objects
        Details about expected inventory record objects
        Fulfillment center objects
        Inventory code adjustment objects
        Inventory adjustment objects
        Item specification information objects
        Marketing activities that are expired
        Marketing activity statistics
        Marketing experiment data
        Marketing user behavior data that is obsolete
        Order objects
        Organization objects
        Returned item objects
        Return reason objects
        Request for Quote objects
        Scheduled job object
        Session objects
        Staged objects
        Store objects
        Subscription objects
        User objects
        User traffic log objects
        Vendor objects
    - Database connection acquisition for utilities and Ant tasks
      WebSphere Commerce utilities and Ant tasks are updated to reference a single class to configure the acquisition of a database connection. This unified database connection method ensures that each utility and Ant task can reference this class to acquire a database connection, regardless of the JDBC driver that a database uses.
  - Dynamic caching
    In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
  - Extracting, transforming, and loading data
    WebSphere Commerce provides multiple utilities for preparing and loading data into a WebSphere Commerce database. The loading utilities are flexible and you can continue to use these utilities when you customize the WebSphere Commerce schema.
  - Payment plug-ins
    To configure a payment plug-in define payment and refund methods; payment and refund rules; and the payment protocols that you intend to use.
  - WebSphere Commerce Search
    For a fully functioning WebSphere Commerce Search implementation, you must understand and complete the search administration tasks, which include search index management and ongoing maintenance.
  - Deploying a WebSphere Commerce dual cell environment
    Consider deploying a dual cell environment to achieve continuous availability and ensure that shoppers are minimally affected by planned or unplanned outages.
  - IBM Customer Service for WebSphere Commerce
    IBM Customer Service for WebSphere Commerce is a separately purchased product that provides a light-weight customer service solution that is embedded in the Aurora B2C and Aurora B2B storefronts. Even though this solution is a separately purchased product, it is not a separate application. Stores that are enabled with IBM Customer Service for WebSphere Commerce allow a customer service representative (CSR) to act on behalf of guest customers and registered customers. A CSR can manage customer accounts, cancel and reorder orders, and shop as customer. A CSR can also act on behalf of Buyer Administrators to help complete Aurora B2B tasks from the storefront, without having to access the Organization Administration Console.
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting

Deleting Request for Quote objects

To delete Request for Quote (RFQ) objects from the database, use the Database Cleanup utility.

Procedure

From the WC_installdir/bin directory, run the following script:
- - ./dbclean.sh -object rfq -type obsolete -instance.xml instancename -db dbname -dbuser user -loglevel loglevel
  - dbclean -object rfq -type obsolete -instance.xml instancename -db dbname -loglevel loglevel
- - ./dbclean.sh -object rfq -type obsolete -instance.xml instancename -db dbname -loglevel loglevel -dbtype oracle -dbuser user -dbpasswd password
  - dbclean -object rfq -type obsolete -instance.xml instancename -db dbname -loglevel loglevel -dbtype oracle -dbuser user -dbpasswd password
Examine the WC_installdir/instances/instance_name/logs/DBClean/DBClean.timestamp.log file.