Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
IBM WebSphere Commerce V7
  • Product overview
  • WebSphere Commerce search
  • Precision marketing
  • What's new
  • User Guide
  • Reference
  • Other versions
  1. Home
  2. Reference
  3. Shopping flow URLs

    WebSphere Commerce shopping flow URLs are organized by subsystem.

  4. Marketing subsystem URLs

    The Marketing subsystem includes all logic and data relevant to marketing concepts for your site, such as campaigns, Web activities, customer segments, email activities, and collaboration.

  • Reference
    • Cross-reference of data beans, EJB beans, and tables

      Data beans are grouped into several component groups.

    • Cross-reference of commands, tasks, and tables

      URL commands, controller commands, task commands, view commands and tables are related to each other.

    • Cross reference: Commands to beans to database tables

      Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.

    • HCL Commerce API reference

      Legacy API classes can be browsed via Javadoc. New API classes are exposed using the REST interface.

    • Shopping flow URLs

      WebSphere Commerce shopping flow URLs are organized by subsystem.

      • Catalog subsystem URLs

        Catalog subsystem URLs include all logic and data relevant to a catalog, including categories, products and their attributes, items, and groupings of each, and any associations or relationships among them.

      • IBM Gift Center actions

        Each IBM Gift Center action is a Struts action that calls the service interface for the gift registry to perform a requested action. If you are developing a store using the gift registry feature (for example, creating JSP files), you should be familiar with the actions. The actions are executed from a browser.

      • Marketing subsystem URLs

        The Marketing subsystem includes all logic and data relevant to marketing concepts for your site, such as campaigns, Web activities, customer segments, email activities, and collaboration.

        • ClickInfo

          Captures site usage statistics for marketing events by incrementing the clickthrough count in either the CPGNSTATS table if called by an e-Marketing Spot for campaigns, the EXPSTATS table if called by an e-Marketing Spot for experiments, or the PCSTATS table if called from a Product Comparison metaphor.

        • Product Advisor

          The URLs in this section are related to Product Advisor.

        • Customer care

          The following URLs are related to customer care:

      • Member subsystem URLs

        The Member subsystem includes all logic and data relevant to registration, authentication, and grouping of all members. A member can be a user, an organization or organizational entity, or a member group.

      • Messaging system URLs

        The following URLs relate to the Messaging system.

      • Order Management subsystem URLs

        The Order Management subsystem includes all logic and data relevant to placing, processing, and managing orders. The Order Management subsystem also deals with returns.

      • Trading subsystem URLs

        The Trading subsystem includes all logic and data relevant to negotiating or determining the price and associated quantity of an individual product or set of products. In particular, this area deals with the auctioning of goods and services, contracts, and RFQs (Requests for quotes).

      • Scheduler URLs

        The server subsystem consists of functions that are associated with URLs that are run by the scheduler.

    • WebSphere Commerce search URLs

      The starter stores consist of pages that are associated with URLs that are run by WebSphere Commerce search. You can use the following URLs to invoke various WebSphere Commerce search tasks.

    • WebSphere Commerce database schema

      The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.

    • Data models

      Any given database data model displays the relationship among database tables in the schema.

    • WebSphere Commerce store pages properties
    • Caching defaults

      During installation, WebSphere Commerce sets up the caching system with the default values.

    • Cache-entry elements

      The root element of the cachespec.xml file, <cache>, contains <cache-entry> elements. The WebSphere dynamic cache service parses the cachespec.xml file during startup, and extracts a set of configuration parameters from each <cache-entry> element.

    • Ant targets

      A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.

    • IBM Sales Center extension points

      The extension points listed on this page are provided by IBM and used in the IBM Sales Center.

    • IBM Sales Center Business Object Document response builders available by default
    • WebSphere Commerce REST API

      WebSphere Commerce REST services are JAX-RS REST services that are built on top of Apache Wink. The implementation classes contain JAX-RS annotations such as @Path, @Produces, @Consumes, @QueryParam, and @PathParam.

    • Payments subsystem

      In WebSphere Commerce Version 6.x the Payments subsystem was introduced. Payment processing using the WebSphere Commerce Multipayment Framework (used in version 5.x) and payment processing using the Payments subsystem is fundamentally different.

    • WebSphere Commerce Payments command reference

      Parameters for the commands described here apply to the framework only. Note that in most cases, WebSphere Commerce Payments does not check for duplicate parameters. If more than one instance of a parameter is specified, then the last instance will be used.

    • Data Load utility configuration file schema

      The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.

    • Glossary

Marketing subsystem URLs

The Marketing subsystem includes all logic and data relevant to marketing concepts for your site, such as campaigns, Web activities, customer segments, email activities, and collaboration.

You can use the following URLs to manage marketing concepts for your site:
  • ClickInfo URL

Product Advisor:

  • UpdateSearchSpaces URL
  • AddProductsToSearchSpace URL
  • URL
  • RemoveProductsFromAllSearchSpaces URL

Customer Care:

  • RetrieveShoppingCartCmd URL
  • RetrieveShopperProfileCmd URL
  • ClickInfo URL
    Captures site usage statistics for marketing events by incrementing the clickthrough count in either the CPGNSTATS table if called by an e-Marketing Spot for campaigns, the EXPSTATS table if called by an e-Marketing Spot for experiments, or the PCSTATS table if called from a Product Comparison metaphor.
  • Product Advisor URLs
    The URLs in this section are related to Product Advisor.
  • Customer care
    The following URLs are related to customer care:
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences