Home
Reference
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.
Catalog groups
Catalog subsystem URLs include all logic and data relevant to groupings.
CatalogGroupDelete
This URL marks a catalog group and its description (plus all cascades) for deletion.

Reference
- WebSphere Commerce API reference
  WebSphere Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
- 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.
- API changes between WebSphere Commerce Version 7.0.0.9 and WebSphere Commerce Version 8.0.0.0
  If you are migrating version 7.0 of WebSphere Commerce, review the API changes between releases.
- 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.
- Payments subsystem
  In WebSphere Commerce, payment processing uses the Payments subsystem.
- 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.
- 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.
- WebSphere Commerce web services
  WebSphere Commerce provides many web services.
- Utilities
  Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
- 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.
    - Catalogs
      Catalog subsystem URLs include all logic and data relevant to a catalog,
    - Categories
      Catalog subsystem URLs include all logic and data relevant to categories.
    - Catalog groups
      Catalog subsystem URLs include all logic and data relevant to groupings.
      - CatalogGroupAdd
        This URL adds a new catalog group and its description, and adds a relationship between the new catalog group and the store.
      - CatalogGroupDelete
        This URL marks a catalog group and its description (plus all cascades) for deletion.
      - CatalogGroupMove
        This URL moves a catalog group from its current parent catalog group to a different, existing parent catalog group.
      - CatalogGroupUpdate
        This URL updates a catalog group and its description.
      - TopCatalogGroupAdd
        This URL adds a relationship between a catalog and a catalog group.
      - TopCatalogGroupDelete
        This URL deletes a relationship between a catalog and a catalog group.
      - CatGroupRelAdd
        This URL adds a relationship between a parent catalog group and a child catalog group.
      - CatGroupRelDelete
        This URL deletes a relationship between a parent catalog group and a child catalog group.
    - Catalog entries
      Catalog subsystem URLs include all logic and data relevant to a catalog entries.
    - Attributes
      Catalog subsystem URLs include all logic and data relevant to attributes.
    - Interest lists
      Catalog subsystem URLs include all logic and data relevant to interest lists.
    - Offers
      Catalog subsystem URLs include all logic and data relevant to offers.
    - Product sets
      Catalog subsystem URLs include all logic and data relevant to product sets.
  - 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.
  - 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.
- 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.
- Glossary

CatalogGroupDelete URL

This URL marks a catalog group and its description (plus all cascades) for deletion.

URL structure

http:// host_name/path/: The fully qualified name of your WebSphere Commerce Server and the configuration path.

Parameter values

catgroupId: Required: The reference number of the catalog group. You must specify either catgroupId or identifier.
identifier: Required: The external identifier of the catalog group. You must specify either identifier or catgroupId.
force: 0 = no, 1=yes. 0 will markForDelete this catalog group.
URL: The URL to be called when the command completes successfully.

Example 1

The following example deletes catalog group 6001 from the database permanently:


http://host_name/webapp/wcs/stores/servlet/CatalogGroupDelete?
catgroupId=6001&force=1&URL=LogonForm

Example 2

The following example deletes catalog group, with testCatalogGroup1 as the identifier, from the database permanently:


http://host_name/webapp/wcs/stores/servlet/CatalogGroupDelete?
identifier=testCatalogGroup1&force=1&URL=LogonForm

Behavior

When force is set to 1, all relationships with that catalog group will be cascade deleted.
When force is set to 0, relationships with that catalog group will not be deleted. This URL does not clean the relationships, however the cascade delete will remove any relationships associated with that catalog group.

Exception condition

None.