Jump to main content

Customer Support Software Academy Community Forums

Product overview
WebSphere Commerce search
Precision marketing
What's new
User Guide
Reference
Other versions

Home
Reference

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.
- 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

Reference

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.
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.
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
API changes between releases
If you are migrating from a previous version of WebSphere Commerce, review the API changes between releases.
OpenLaszlo API
The OpenLaszlo source (LZX) files for the Management Center are located within the WEB-INF/src/lzx directory within the LOBTools web module. These files are compiled into a SWF (Flash) file that is the binary representation of the Management Center. There are two groups of LZX files: restricted and customizable files.
Scheduler URLs
The server subsystem consists of functions that are associated with URLs that are run by the scheduler.
Utilities
Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
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.
Analytics for IBM WebSphere Commerce
WebSphere Commerce provides a framework that you can configure to integrate your store with an external Web analytics solution. This framework includes a tag library that you can use in store page JSP files to provide appropriate analytics information to the external analytics system.
WebSphere Commerce web services
WebSphere Commerce provides many web services.
Data Load utility CSV column and XML element definitions
Look up the database column name and definitions for business objects to find details about the required and optional fields, and the values that they can contain.

Share: Email
Twitter

Disclaimer
Privacy
Terms of use
Cookie Preferences