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.
Migrating
Before you migrate to HCL Commerce Version 9.1, review this information to help plan and execute your migration.
... from IBM Websphere Commerce Version 7
The following section presents the high-level steps that you must complete to migrate from IBM Websphere Commerce Version 7 to HCL Commerce Version 9.1. Select the IBM Websphere Commerce Version 7 Feature Pack that you are migrating from to begin your migration.
... Feature Pack 8 to HCL Commerce Version 9.1
The following section outlines the high-level steps that you must complete to migrate to HCL Commerce Version 9.1. Begin by migrating your development environment, which includes your development database, custom assets, storefront, and search application. With a successfully migrated development environment, you can migrate your production databases, and deploy your migrated assets to your HCL Commerce Version 9.1 production environments.
Migrating WebSphere Commerce Developer
The following section outlines the WebSphere Commerce Developer migration process. It is likely that your migration is completed in planned chunks, starting with migrating your development environments. Once complete, review the WebSphere Commerce migration section to cover how to package and deploy your migrated assets for your production environment, and how to migrate your production database and switch your live traffic to your version 9.1 production environment.
Migrating HCL Commerce Search
Whether you used BOD-based Search or REST-based Search in previous versions of HCL Commerce, you can migrate your custom Search assets to use REST-based Search in HCL Commerce Version 9.
Migrating BOD-based Search
Migrate your BOD-based HCL Commerce Search index and configurations to REST-based Search in HCL Commerce version 9.0.0.3+.
Mapping between search result filters and postprocessors
A description of the mapping between search result filters that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.

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.
  - Planning to migrate WebSphere Commerce
    Most businesses treat investments in technology updates and migrations as overhead expenses. Even though you might need to upgrade or migrate to the latest HCL Commerce version to take advantage of the technological offering, providing a business justification to do so requires outlining the business benefits, strategy, and migration plan.
  - ... from IBM Websphere Commerce Version 7
    The following section presents the high-level steps that you must complete to migrate from IBM Websphere Commerce Version 7 to HCL Commerce Version 9.1. Select the IBM Websphere Commerce Version 7 Feature Pack that you are migrating from to begin your migration.
    - ... Feature Pack 6 to HCL Commerce Version 9.1
      The following section outlines the high-level steps that you must complete to migrate to HCL Commerce Version 9.1. Begin by migrating your development environment, which includes your development database, custom assets, storefront, and search application. With a successfully migrated development environment, you can migrate your production databases, and deploy your migrated assets to your HCL Commerce Version 9.1 production environments.
    - ... Feature Pack 7 to HCL Commerce Version 9.1
      The following section outlines the high-level steps that you must complete to migrate to HCL Commerce Version 9.1. Begin by migrating your development environment, which includes your development database, custom assets, storefront, and search application. With a successfully migrated development environment, you can migrate your production databases, and deploy your migrated assets to your HCL Commerce Version 9.1 production environments.
    - ... Feature Pack 8 to HCL Commerce Version 9.1
      The following section outlines the high-level steps that you must complete to migrate to HCL Commerce Version 9.1. Begin by migrating your development environment, which includes your development database, custom assets, storefront, and search application. With a successfully migrated development environment, you can migrate your production databases, and deploy your migrated assets to your HCL Commerce Version 9.1 production environments.
      - Migrating WebSphere Commerce Developer
        The following section outlines the WebSphere Commerce Developer migration process. It is likely that your migration is completed in planned chunks, starting with migrating your development environments. Once complete, review the WebSphere Commerce migration section to cover how to package and deploy your migrated assets for your production environment, and how to migrate your production database and switch your live traffic to your version 9.1 production environment.
        Migrating site security
        Manually migrate your site security from your IBM Websphere Commerce Version 7 Feature Pack 8 development environment to your HCL Commerce Version 9.1 development environment.
        Migrating configuration files
        Migrate your IBM Websphere Commerce Version 7 configuration files by manually merging them with or copying them to your HCL Commerce Version 9.1 development environment.
        Migrating your development database
        To migrate your development database from Feature Pack 8 to HCL Commerce Version 9.1, you must first prepare your Feature Pack 8 development database and your HCL Commerce Version 9.1 development environment. Next, you run the migration utility to migrate your Feature Pack 8 development database to HCL Commerce Version 9.1, then run the updatedb utility to bring your database up to the HCL Commerce Version 9.1 level.
        Migrating Assets tool assets
        After the reintroduction of the Assets tool in Management Center for HCL Commerce with HCL Commerce version 9.1.8.0, you can migrate your IBM Websphere Commerce Version 7 Feature Pack 8 assets, and ensure that your Assets tool configuration is correct, to continue using the tool in HCL Commerce Version 9.1.
        Migrating the Aurora store web project
        Complete this task to migrate your IBM Websphere Commerce Version 7 Feature Pack 8 Aurora store to HCL Commerce Version 9.1. After migration, your store will remain a local store.
        Migrating WebSphere Commerce Accelerator-based marketing
        If you are migrating from WebSphere Commerce Version 7 with legacy WebSphere Commerce Accelerator-based marketing, your implementation must be updated to the web service Management Center-based marketing for use on HCL Commerce Version 9.1.
        Migrating customized struts assets
        HCL Commerce Version 9 uses Apache Struts 2 as the preferred platform for developing enterprise Java web applications. Struts 2 provides plugin support for REST and Spring, which are important components of the HCL Commerce platform. It is also designed for more streamlined development and is fully integrated with the HCL Commerce deployment pipeline.
        Migrating HCL Commerce Search
        Whether you used BOD-based Search or REST-based Search in previous versions of HCL Commerce, you can migrate your custom Search assets to use REST-based Search in HCL Commerce Version 9.
        Migrating BOD-based Search
        Migrate your BOD-based HCL Commerce Search index and configurations to REST-based Search in HCL Commerce version 9.0.0.3+.
        Migrating index cores from BOD-based search to Rest-based search
        To migrate your Search index cores, you must individually register the configurations for each core in the SRCHCONF and SRCHCONFEXT database tables. During Search server startup, your index cores are created according to the configurations defined in the SRCHCONF and SRCHCONFEXT tables.
        Migrating custom index fields and indexing scripts from BOD-based search to REST-based search
        Any customization that is made to any of the index schemas, or to the preprocessing and indexing scripts can be reapplied when you migrate from BOD-based search to REST-based search.
        Migrating custom configuration files
        Search-related configuration updates under the HCL Commerce EAR application extension directories can be moved into the corresponding extension directories under the HCL Commerce search EAR application. For example, the com.ibm.commerce.catalog-ext and com.ibm.commerce.foundation-ext directories.
        Migrating custom Java classes from BOD-based Search to REST-based Search
        You can migrate custom Java classes either by reusing them where applicable, or reimplementing them in an alternative way.
        Migrating storefront services
        Any custom storefront pages that use any of the search-related CatalogNavigationView BOD services must be updated to use the corresponding new search server REST services.
        Mapping between BOD and REST services
        This topic shows the mapping between the search-related CatalogNavigationView BOD expression builders from the HCL Commerce server and the corresponding search REST services from the search server.
        Mapping between search profiles
        This topic shows the mapping between the search profiles that are used by the search-related CatalogNavigationView BOD services and the corresponding search profiles that are used by the search REST services from the search server.
        Mapping between search expression providers
        This topic shows the mapping between the search expression providers that are used by the related search CatalogNavigationView BOD services and the corresponding search expression providers that are used by the search REST services from the search server.
        Mapping between search preprocessors
        This topic shows the mapping between the search preprocessors that are used by the related search CatalogNavigationView BOD services and the corresponding search preprocessors that are used by the search REST services from the search server.
        Mapping between search result filters and postprocessors
        A description of the mapping between search result filters that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.
        Mapping between search mediators and postprocessors
        This topic shows the mapping between the search mediators that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.
        Migrating custom search services
        The following topic illustrates how to migrate your BOD-based search service to a REST-based search by extending the search-rest-ext.war directory, then configuring the build and deploy processes for Search.
        Migrating REST-based Search
        Migrate your REST-based Search index and configurations from a previous version of HCL Commerce to HCL Commerce version 9.0.0.3+.
        Migrating EJB entity beans to Java Persistence API
        Enterprise Java Entity Beans are no longer supported in HCL Commerce Version 9. By using a combination of tools and manual steps, you can migrate your EJB 1.1 entity beans to JPA, and update your code to use HCL Commerce Version 9 APIs.
        Migrating Management Center
        If you have customized Management Center in the LOBTools project in your IBM Websphere Commerce Version 7 development environment, you will need to follow the procedure below to re-apply your customizations on HCL Commerce Version 9.1.
        Migrating custom Physical Service Data Objects
        Manually migrate your custom physical service data object from your IBM Websphere Commerce Version 7 Feature Pack 8 development environment to your HCL Commerce Version 9 development environment.
        Migrating Command and Data Bean projects
        Migrating Command and Data Bean projects involves several steps. The WebSphereCommerceServerExtensionsLogic project must be exported from your old development environment, and imported into HCL Commerce Version 9 development environment.
        Completing post-migration tasks on your development environment
        After you migrate your Feature Pack 8 development database and application to HCL Commerce Version 9, complete the following post-migration steps.
        Verifying your migrated assets on your development environment
        Now in the migration, you have a fully migrated development environment. Verify that your migrated assets are working as designed in your development environment.
      - Migrating WebSphere Commerce
        The following section outlines the production environment migration process. Once you are done migrating your staging and production database environments, you can deploy your migrated assets for your production environment, and switch your live traffic to your new HCL Commerce Version 9.1 site.
  - ... from IBM Websphere Commerce Version 8 to HCL Commerce Version 9.1
    The following section outlines the high-level steps that you must complete to migrate to HCL Commerce Version 9.1. Begin by migrating your development environment, which includes your development database, custom assets, storefront, and search application. With a successfully migrated development environment, you can migrate your production databases, and deploy your migrated assets to your HCL Commerce Version 9.1 production environments.
  - ... from HCL Commerce Version 9 to HCL Commerce Version 9.1
    The following section presents the high-level steps that you must complete to upgrade from an earlier version of HCL Commerce Version 9 to a newer version of HCL Commerce Version 9.1.
  - ... to HCL Commerce Version 9.1 solutions
    The following section presents the high-level concepts and steps that you must understand and complete in order to upgrade from earlier WebSphere Commerce technologies to those introduced in HCL Commerce Version 9.1.
- 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.
- 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.

Mapping between HCL Commerce Search result filters and search postprocessors

A description of the mapping between search result filters that are used by the related search CatalogNavigationView BOD services and the corresponding search postprocessors that are used by the search REST services from the search server.

Note: The search server does not support result filters, as they operate on BOD objects. The search server uses postprocessors, which operate on native

Java List
Objects

.


BOD-based search result filter	REST-based search postprocessor
SearchCatalogEntryMerchandisingAssocResultFilter	SearchCatalogEntryViewMerchandisingAssocQueryPostprocessor
SearchCatalogEntryViewAttachmentsResultFilter	SearchCatalogEntryViewAttachmentsQueryPostprocessor
SearchCatalogEntryViewAttributesAllowedValueResultFilter	SearchCatalogEntryViewAttributesQueryPostprocessor
SearchCatalogEntryViewAttributesResultFilter	SearchCatalogEntryViewAttributesQueryPostprocessor
SearchCatalogEntryViewDescriptionResultFilter	SearchCatalogEntryViewDescriptionQueryPostprocessor
SearchCatalogEntryViewPackageBundleResultFilter	SearchCatalogEntryViewComponentsQueryPostprocessor
SearchCatalogEntryViewPriceResultFilter	SearchCatalogEntryViewPriceQueryPostprocessor
SearchCatalogEntryViewSingleSKUResultFilter	The logic that is deprecated by indexing the childCatentry_id field
SearchCatalogEntryViewSKUResultFilter	SearchCatalogEntryViewSKUQueryPostprocessor
SearchCatalogEntryViewStoreDisplayAttributesResultFilter	SearchCatalogEntryViewAttributesQueryPostprocessor
SearchCatalogGroupEntitlementResultFilter	SearchCategoryEntitlementQueryPostprocessor, SearchChildCategoryEntitlementQueryPostprocessor
SearchCatalogNavigationViewDynamicKitResultFilter	SearchCatalogEntryViewDynamicKitQueryPostprocessor
SearchCatalogNavigationViewPreviewResultFilter	SolrRESTSearchPreviewQueryPostprocessor
SearchCatalogNavigationViewSEOTitleMetaDataFilter	The Search Server does not return SEO metadata. Metadata is returned from the HCL Commerce server.
SearchNavigationSuggestionsResultFilter	SearchCategorySuggestionQueryPostprocessor, SearchBrandSuggestionQueryPostprocessor