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
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.
Administration Console
Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as publishing stores, refreshing the registry, and scheduling jobs. You can access the Administration Console at a site-level, or for a particular store.
Jobs
A job is a WebSphere 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: regular jobs, store level jobs, and broadcast jobs.
Scheduling a site-level job
Use the Administration Console to schedule a job on the site level.
Scheduled job states
The SCHACTIVE table contains the list of jobs that are scheduled to run, and the execution time for each scheduled job. The execution history for each scheduled job is kept in the SCHSTATUS table.

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.
    - Stores in WebSphere Commerce
      WebSphere Commerce supports several different types of entities that are defined as stores. The assets of these store entities may be edited using the WebSphere Commerce Accelerator.
    - Enabling registered users to access all stores in the Extended Sites business model
      WebSphere Commerce users can access storefronts by virtue of having the role of Registered Customer in the organization that owns the store, or in any organization above it. The roles a user has access to during registration are defined within the MemberRegistrationAttributes.xml file.
    - Configuration Manager
      To configure a WebSphere Commerce instance, use the Configuration Manager. The Configuration Manager interface shows mandatory fields and provides help.
    - Administration Console
      Site Administrators use the Administration Console to control a site or store by completing administrative operations and configuration tasks such as publishing stores, refreshing the registry, and scheduling jobs. You can access the Administration Console at a site-level, or for a particular store.
      - 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.
      - Opening the Administration Console
        Users with Site Administrator access can open the Administration Console.
      - Enabling WebSphere Commerce components
        Enabling a component with the Administration Console enables the component until the WebSphere Commerce Server is restarted. To permanently enable a component use Configuration Manager.
      - Disabling WebSphere Commerce components
        Disabling a component using the Administration Console disables the component until the WebSphere Commerce Server is restarted. To permanently disable a component use Configuration Manager.
      - Registry Manager
        The Registry Manager maintains a set of registries for caching WebSphere Commerce runtime data. Each registry provides methods to enable adding, deleting, and refreshing of the registry content. These methods are available to the URL interface by using the ListRegistry and the RefreshRegistry commands.
      - Jobs
        A job is a WebSphere 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: regular jobs, store level jobs, and broadcast jobs.
        Scheduling a site-level job
        Use the Administration Console to schedule a job on the site level.
        Deleting a scheduled job
        Use the Administration Console to delete a scheduled job and stop it from running for your site.
        Editing the configuration for a scheduled job
        Use the Administration Console to edit the configuration for a scheduled job.
        Removing job status records from the SCHSTATUS table
        Use the Administration Console to remove job status records from the SCHSTATUS table.
        Scheduling a broadcast job
        Use the Administration Console to schedule a broadcast job to run for your site.
        Scheduled job states
        The SCHACTIVE table contains the list of jobs that are scheduled to run, and the execution time for each scheduled job. The execution history for each scheduled job is kept in the SCHSTATUS table.
        Viewing scheduled jobs
        Use the Administration Console to view a list of jobs scheduled to run for your site.
        Configuring the scheduler to run a job on an instance or cluster member
        You can configure the WebSphere Commerce scheduler to run a job on a particular WebSphere Commerce instance or cluster member. This can be useful if you want to devote one server for scheduled jobs.
        Setting up the scheduler to process subscriptions and recurring orders
        The SubscriptionSchedulerCmd job processes subscriptions and recurring orders. In this task you create a new job to monitor all active subscriptions and recurring orders to process their child orders on an hourly basis.
        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 WebSphere Commerce Server. Periodically clean up the SCHSTATUS table.
        Configuration parameters
        You can change scheduler parameters to control behavior. You can control behaviors such as expiry time, waiting time between checks for jobs, and the number of threads to allocate to an application type.
        Marketing jobs
        If your store uses the services-based marketing system, the following scheduled jobs are added. You can adjust the schedule on which these jobs run if necessary.
        WebSphere Commerce Search jobs
        If your store uses WebSphere Commerce Search, the following scheduled jobs are available. You can create and adjust the schedule on which these jobs run if necessary.
        Search engine optimization jobs
        If your store uses the search engine optimization feature, the following scheduled jobs are available. You can create and adjust the schedule on which these jobs run if necessary.
        ATP-inventory jobs
        If your store uses ATP-inventory, there are some jobs that must be scheduled for the store before the order flow process can be completed.
        Using an external system of record
        WebSphere Commerce manages ATP inventory as it is received at a fulfillment center, when adjustments are performed, and when orders are processed and released to fulfillment. An external system of record generally manages the flow of materials into and out of a fulfillment center. If you want to use an external system of record to maintain the current inventory levels for a store, the store must be configured properly, and inventory levels must be periodically updated using an external feed.
      - Message resend
        Site Administrators can use the resend function in WebSphere Commerce to resend messages that are stored in the WebSphere Commerce system.
      - Transport methods
        WebSphere Commerce provides several transport methods. By default, the e-mail transport method is configured and active. You can also use these transport methods: File, IBM MQ, or a sample adapter. You can configure transport methods for the site, or for particular stores.
      - Message types
        WebSphere Commerce predefines several message types and sets them as active. You can change the parameters for message types.
    - Organization Administration Console
      The Organization Administration Console enables administrators to manage organizations, business users and member groups. Access Control policies can also be managed and approval requests can be processed.
    - Common installation and administration tasks
      The following tasks are common tasks that you need to perform, often repeatedly, as part of WebSphere Commerce installation and administration duties.
  - 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.
  - 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

Scheduled job states

The SCHACTIVE table contains the list of jobs that are scheduled to run, and the execution time for each scheduled job. The execution history for each scheduled job is kept in the SCHSTATUS table.

The state of a scheduled job corresponds to the SCSSTATE column in the SCHSTATUS table or in the SCHACTIVE table. To determine the most recent execution state of a scheduled job, complete the following steps:

Find the record for the scheduled job whose state you want to determine, that has the greatest timestamp value in the SCSEND column of the SCHSTATUS table.
Look at the value in the SCSSTATE column for the record in the SCHSTATUS table that you found in the previous step.

The following table lists all of the possible states that a scheduled job can have.


State	Description
I	This state indicates that the scheduled job has to run at the preferred start time, which is recorded in the SCSPREFSTART column of the SCHSTATUS table or of the SCHACTIVE table.
IF	This state indicates that the scheduled job is being rescheduled to run because of a previous failed attempt to execute the job.
R	This state indicates that the scheduled job is currently running. The job execution start time is recorded in the SCSACTLSTART column of the SCHSTATUS table or of the SCHACTIVE table. The SCSQUEUE column in either of these two tables indicates which JVM process is running the job.
RF	This state indicates that the scheduled job is running because of a previous failed attempt to execute the job.
C	This state indicates that the scheduled job has finished running. The job execution finish time is recorded in the SCSEND column of the SCHSTATUS table or of the SCHACTIVE table. This particular execution of the job was successful.
CF	This state is the same as state C except there was an exception while executing the scheduled job. This means that the job failed to execute successfully.
W	This state indicates that there is a check task command assigned to the scheduled job. This means that before the job is executed, there is a side process that will execute to determine whether the job really needs to be run. This saves the overhead of running a scheduled job when it does not need to be run. (This parameter is mostly used for store level scheduled jobs.)