Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. 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. Business users can also use AI enabled content management capabilities.
Customizing
The topics in the Customizing section describe tasks performed by an application developer to customize HCL Commerce.
Customizing HCL Commerce
You can extend the HCL Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use HCL Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
Member subsystem
The Member subsystem is a component of the Transaction server that includes data for participants of the HCL Commerce system. A member can be a user, a group of users (also known as a member group), or an organizational entity (which can be an organization, such as "IBM" or an organizational unit within an organization, such as "Electronic Commerce Division"). Business logic in the Member subsystem provides member registration and profile management services. Other services which are closely related to the Member subsystem include access control, authentication, and session management.
Member search
The member search feature provides a mechanism for performing member searches without the need to write new EJB code. You can create query objects and customize them to suit particular search requirements.
ECUserQuery object
The ECUserQuery object, used to perform member search, can be extended. This object is used to find users in the WebSphere Commerce database.

Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. 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. Business users can also use AI enabled content management capabilities.
- Getting started
  HCL Commerce has different advantages for business users, administrators and developers. HCL Commerce targets each of these roles with a tailored set of offerings so that each of your users can get maximum benefit.
- Installing and deploying
  Learn how to install and deploy HCL Commerce development environments and HCL Commerce production environments.
- Migrating
  Before you migrate to HCL Commerce Version 9.1, review this information to help plan and execute your migration.
- Operating
  Topics in the Operating category highlight tasks that are typically performed by business users, customer support representatives, to complete their day-to-day tasks in the operation of the HCL Commerce site.
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using HCL Commerce in combination with other products.
- Administering
  Topics in the Administering category highlight tasks that are typically performed by the Site Administrator, to support daily operations of the HCL Commerce site.
- Customizing
  The topics in the Customizing section describe tasks performed by an application developer to customize HCL Commerce.
  - Customizing Management Center for HCL Commerce
    HCL Commerce allows you to pull the GIT bundle of Management Center source code and start the application locally to customize the Management Center.
  - Managed asset deployment
    Managed assets are files that are uploaded by business users to be used for store marketing, or to supplement products. They are added to HCL Commerce through the Assets tool or the Marketing tool in Management Center. By default, managed assets are extracted and deployed through the HCL Commerce EAR. To maintain performance in a large-scale production environment, site administrators must switch to alternative extraction and deployment methods for managed assets.
  - HCL Commerce development environment
    HCL Commerce Developer is the development toolkit for customizing a HCL Commerce application.
  - Functional architecture
    Functional architecture provides both the set of patterns used to implement the business functionality and the frameworks in which these business functions execute.
  - Persistent object model
    HCL Commerce deals with a large amount of persistent data. There are numerous tables defined in the current database schema. Even with this extensive schema, however, you might need to extend or customize the database schema for your particular business needs.
  - Creating your custom store
    After you install and set up your programming environment, you can create your custom store and customize your storefront. You must ensure that the store server is properly configured, and that your store assets are moved to the Store server.
  - Presentation layer
    HCL Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
  - Controller layer
    The Controller layer is the conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response.
  - Business logic layer
    The business logic layer is the business components that provide OAGIS services to return data or start business processes. The presentation layer uses these OAGIS services to display data, or to invoke a business process. The business logic provides data required by the presentation layer. The business logic layer exists because more than just fetching and updating data is required by an application; there is also additional business logic independent of the presentation layer.
  - Persistence layer
    The interaction between the business objects and persistence layer is isolated in an object called the Business Object Mediator. Business object document (BOD) commands interact with the Business Object Mediator to handle the interaction with the logical objects and how they are persisted.
  - Business model information model
    A business model, a representation of the business processes used throughout the site, provides a sample commerce solution which includes an organization structure, default user roles and access control policies, one or more starter stores, administration tools, and business processes that demonstrate best practices. A business model can be customized to support business requirements and scenarios. HCL Commerce provides sample business models that show some common commerce solutions. These business models are created by setting up an organization hierarchy structure, access control policies, stores, and contracts that help satisfy the necessary business requirements.
  - Business models
    Before starting to develop your site with HCL Commerce, you need to determine the business model supported by HCL Commerce that best represents the purpose of your site. Usually sites created with HCL Commerce will be implemented based on of one of these business models.
  - Store data information model
    Store data is the information that is loaded into the Transaction server database, which allows your store to function. The URL Registry Entries and View Registry Entries packages are included in the diagram, but they are not database assets. These entries are presentation configuration (that is, struts actions and forwards) that must be deployed. URL registry entries are shown in the diagram to illustrate the entire store data information model. To operate properly, a store must have the data in place to support all customer activities. For example, in order for a customer to make a purchase, your store must contain a catalog of goods for sale (catalog data), the data associated with processing orders (tax and shipping data), and the inventory to fulfill the request (inventory and fulfillment data).
  - Customizing HCL Commerce
    You can extend the HCL Commerce product to fit your business needs. This topic describes the prerequisite skills and required knowledge that you need to customize business logic. After you have the required knowledge, use HCL Commerce Developer to take tutorials that guide you step-by-step through various customization scenarios.
    - Choosing a customization model
      You can customize HCL Commerce using the traditional development model, or the externalized Customizations (xC) framework. Which approach you use depends on how complex your requirements are, and how beneficial it is to you to isolate your customization code.
    - Extending HCL Commerce with xC extension points
      For some parts of HCL Commerce, you can write extension code to extend HCL Commerce controller or task commands. You create extension code in the development environment.
    - Understanding access control
      Access control in an HCL Commerce application is composed of the following elements: users, actions, resources, and relationships.
    - Supporting globalization
      The HCL Commerce architecture is designed to support globalization. Globalization is the proper design and execution of systems, software, services, and procedures so that one instance of software, running on a single server or end-user machine, can process multilingual data and present culturally correct data in a multicultural environment such as the Internet.
    - Adding and modifying price lists and price policies
      You can add additional price lists, if you require multiple price lists to support cost and list prices.
    - Business relationship assets
    - Catalog subsystem
      The catalog subsystem is a component of the Transaction server that provides online catalog navigation, partitioning, categorization, and associations. In addition, the catalog subsystem includes support for personalized intrest lists and custom catalog display pages. The catalog subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them.
    - Member subsystem
      The Member subsystem is a component of the Transaction server that includes data for participants of the HCL Commerce system. A member can be a user, a group of users (also known as a member group), or an organizational entity (which can be an organization, such as "IBM" or an organizational unit within an organization, such as "Electronic Commerce Division"). Business logic in the Member subsystem provides member registration and profile management services. Other services which are closely related to the Member subsystem include access control, authentication, and session management.
      - Defining custom attributes for member URLs
        The steps on this page describe how to define custom attributes for member URLs
      - Membership hierarchy
        Users and organizational entities within the Member subsystem are organized into a hierarchy. Generally this hierarchy mimics a typical organizational hierarchy, with entries for organizations and organizational units, and entries for users in the leaf nodes. The hierarchy includes artificial organizational entities created specifically to support access control.
      - Users
        When a user first accesses an e-commerce site and is browsing product pages, the user is running as a generic user. The generic user has a common user ID (-1002) that is used across the entire system. The use of a common user ID on the site minimizes system resource usage. Once the user performs an operation that requires a unique identity, for example, adding a product to the shopping cart, the user is converted from a generic user to a unique guest user. A guest user has a unique user ID, but no password. This user implicitly belongs to the Default Organization and does not have any roles in the site. Depending on the business model of the store, and the access control policies, the user may be able to do other operations on the site, for example, placing an order. Both the generic user and a unique guest user have the registration type of "G" (Guest user). If the guest user registers to the current store, then the user is converted to a registered user, and any assets that the guest user owned will now be owned by the registered user.
      - Organizations
        An organizational entity is a type of member in HCL Commerce. An organizational entity is classified into one of three types: an organization, an organization unit, or an authorization domain. For site administrators, one of your first tasks after installing and configuring HCL Commerce is setting up and managing access to your e-commerce site. This process involves creating organizations that participate at your site, and defining users that are members of those organizations. After an instance is created, you can publish a starter store that defines the organization structure. Sometimes, organizations joining your site might be buyer organizations. In other cases, you might have customers registering at your site who are engaged in a business-to-consumer relationship with your business. Defining the organizational structure of site is an important step in managing the types of access that members have to your system.
      - Member groups
        A member group is a grouping of members - users, organizations, or other member groups - used for various business purposes. Two kinds of member groups exist: implicit and explicit. An implicit member group contains users that share common attributes and are therefore considered members of a specific member group. An implicit member group specifies criteria or attributes that users must satisfy in order to be considered members of that member group. You can also explicitly exclude certain users although they satisfy the criteria. An explicit member group contains explicitly assigned users, who may or may not share common attributes. A member group can be both implicit and explicit at the same time.
      - Membership profile management
        A basic user profile incorporates registration information, demographics, address information, purchase history, and other miscellaneous attributes. A business user profile contains the same information as a basic user profile, as well as employment information, such as an employee number or a job title, or a job description. The business profile may also contain a link to the business organization to which the user belongs.
      - Sample: Member subsystem properties files
        The Member subsystem uses PropertyResourceBundle files to store information specific to locales.
      - Range-based customer registration information
        Some of the information captured during customer registration uses a range to store its value. For instance, the default implementation for specifying a customer's age defines a range of numbers from 0 to 6. Each number represents an age range that might include the customer's age. When customers register, they select the range in which they belong, and the selection is stored in the HCL Commerce database as an integer between 0 and 6. These ranges are defined in the UserRegistration.properties file in the properties directory.
      - Member subsystem roles
        HCL Commerce defines a default set of roles that govern what a user is allowed to access in the system. In the access control system, policies are set up for each role. These access control policies grant access to a specified set of actions, such as executing commands and views or displaying data beans.
      - MemberRegistrationAttributes XML and DTD files
        The MemberRegistrationAttributes.xml configuration file specifies attributes that can automatically be assigned to users and organizations during user and organization registration and some authentication scenarios. This file follows the format that is defined by the MemberRegistrationAttributes.dtd file.
      - Member search
        The member search feature provides a mechanism for performing member searches without the need to write new EJB code. You can create query objects and customize them to suit particular search requirements.
        Extending the ECOrganizationQuery and ECUserQuery objects
        When you use the member search feature, you can extend the query objects.
        ECOrganizationQuery object
        The ECOrganizationQuery object, used to perform member search, can be extended. The ECOrganizationQuery object works just like the ECUserQuery object.
        ECUserQuery object
        The ECUserQuery object, used to perform member search, can be extended. This object is used to find users in the WebSphere Commerce database.
    - Currency
      You can display prices in your site in one currency, or you can use multiple currencies by following the instructions for the euro. For a site with multiple stores, you can use different currencies for the stores, or you can assign currencies to the store group. Depending on the type of site that you are creating, you can specify what currencies you want to use and how they are displayed. You can also allow customers to select a shopping currency.
    - Returns
    - Tax codes
      A tax calculation code indicates the tax calculation for order items. A store typically collects two type of taxes: sales or use tax, and shipping tax. The tax codes are unique within each tax type for a store. Only one tax calculation code of each tax type is applied to a particular order item.
    - Calculation framework
      Commerce systems need to calculate monetary amounts and apply them to business objects. Business rules and legal requirements specify how and when these monetary amounts should be calculated. When these rules and requirements change, a good commerce system can adapt to the changes with little or no programming changes.
    - Order Management subsystem
      The Order Management subsystem is a component of the Transaction server that provides shopping carts, order capture, order fulfillment, inventory, and payment function support.
    - Stored procedure error codes
      The following table describes the error codes that are returned by specific HCL Commerce stored procedures. You should receive these error messages only when a problem with the data requires further investigation by a technical person. If you receive one of these errors (other than error code 0) and you cannot determine the cause of the error, contact HCL Commerce support for assistance.
    - Trading subsystem
  - Run Engine command framework
    The Run Engine command framework provides predefined commands, that you can use to change environment parameters or container configurations. This framework is built into the HCL provided Docker images.
  - GraphQL for HCL Commerce
    The GraphQL markup language is available for any API. It is a server-side interpreter for processing queries using a data type system you design. With GraphQL, your data and code are independent of any database or storage system.
  - Representational State Transfer (REST) services
    HCL Commerce uses Representational State Transfer (REST) services to provide a framework that can be used to develop RESTful applications on several platforms. These platforms can include web, mobile, kiosks, and social applications.
  - Web services
  - Search
    HCL Commerce comes with a powerful and fully integrated search function. The search functions in HCL Commerce provide an enriched customer experience, with features such as automatic search term suggestions and spelling correction. Since it is built on industry standards, HCL Commerce Search is highly flexible and extensible. Starter stores can use the search engine's most sophisticated features without requiring extra customization. Starting with Version 9.1, HCL Commerce Search with Elasticsearch microservices manage indexing and other crucial tasks, with no performance impact on the storefront or transaction server.
- Tutorials
  HCL Commerce provides many tutorials to help you customize and understand your HCL Commerce instance and stores.
- Samples
  Topics in the Samples category highlight the various samples that are provided with HCL Commerce.
- Compliance
  The following section describes how you can leverage HCL Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of HCL Commerce and how to configure these features.
- Performance
  Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of HCL Commerce site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with HCL Commerce, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the HCL Commerce reference documentation.

ECUserQuery object

The ECUserQuery object, used to perform member search, can be extended. This object is used to find users in the WebSphere Commerce database.

The ECUserQuery object supports the following tables:
Database table	Description
USERS	The user's record
USERREG	The user's registry record
USERDEMO	The user's demographics information
USERPROF	The user's profile information
ORGENTITY	The user's parent organization
ADDRESS	The user's self address (the address of the user's parent organization)
BUSPROF	The user's business profile information
ACCOUNT	Accounts owned by the parent organization
MBRROLE	Roles played by the user
MBRATTRVAL	Custom member attributes for the user
MBRREL	The user's ancestors

This means that you can search based on any numeric or string attribute in any of these tables.

Example 1: Search by logonId

In this example, the query object generates an SQL query to find all users whose logonId is LIKE %myLogon%. The query has only one condition, a search condition on USERREG.LOGONID where the search type is case insensitive containing. The USERREG table is automatically joined with the USERS table for the search.


ECUserQuery query = new ECUserQuery(); 

WhereClauseSearchCondition whereClause = 
  new WhereClauseSearchCondition(
  new TableField("USERREG", "LOGONID"),
  WhereClauseSearchCondition.SEARCHTYPE_CASEINSENSITIVE_CONTAINS,
  "myLogon"); 

query.setWhereClause(whereClause); 

Vector vecResults =
  (new UserSearchAccessBean())
  .executeCustomizeableMemberSearch(query);

Example 2: Find all users with a given logonId and with a given parent organization

This example shows searching by logonId and parent organization name.


ECUserQuery query = new ECUserQuery(); 

WhereClauseSearchCondition whereClause = 
  new WhereClauseSearchCondition(
  new TableField("USERREG", "LOGONID"),
  WhereClauseSearchCondition.SEARCHTYPE_CASEINSENSITIVE_CONTAINS, 
  "myLogon");
whereClause.appendANDCondition(
  new WhereClauseSearchCondition(
  new TableField("ORGENTITY", "ORGENTITYNAME"),
  WhereClauseSearchCondition.SEARCHTYPE_CASESENSITIVE_STARTSWITH,
  "myParentOrgName")); 

query.setWhereClause(whereClause); 

Vector vecResults =
  (new UserSearchAccessBean())
  .executeCustomizeableMemberSearch(query);

In this example, two where clauses have now been combined with an AND condition. The JOIN condition for the ORGENTITY table stipulates that it should search based on the parent organization.