Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
Migrating
The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+. The process consists of an initial migration of your database contents. This is followed by a code migration. Both are fully described.
Migrating 9.1 databases
This document provides step-by-step instructions for migrating Commerce+ databases (DB2 or Oracle) from version 9.1.x.0 to HCL Commerce+ using the wcim_ant utility. It includes guidance for Development, Staging, and Production database environments.
Migrating the production database
In this section, you will learn how to efficiently migrate the production database, ensuring a smooth and reliable transition process.
Completing the offline database migration
After you successfully migrate your database, complete the final database migration tasks.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ overview. Explore these feature overviews to learn how Commerce+ operates. Refer to the related links listed at the end of each topic to access expanded product documentation.
- Deploying
  This section provides details on deploying HCL Commerce+. It explains how to download the Docker images and Git bundles that comprise the product, how to create a minimal environment, and how to plan for a full deployment. It details supported software versions, patches, and configurations to ensure the platform performs well.
- Migrating
  The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+. The process consists of an initial migration of your database contents. This is followed by a code migration. Both are fully described.
  - Migrating 9.1 databases
    This document provides step-by-step instructions for migrating Commerce+ databases (DB2 or Oracle) from version 9.1.x.0 to HCL Commerce+ using the wcim_ant utility. It includes guidance for Development, Staging, and Production database environments.
    - Migrating the staging database
      In this section, you will learn how to efficiently migrate the staging database, ensuring a smooth and reliable transition process.
    - Migrating the production database
      In this section, you will learn how to efficiently migrate the production database, ensuring a smooth and reliable transition process.
      - Preparing to migrate your production database
        Now that you have migrated your development environment and deployed your containers in HCL Commerce+, you can now build and deploy your customizations, and migrate your HCL Commerce Version 9.1 database to HCL Commerce+.
      - Migration an offline version of your production database
        Before you can migrate your live HCL Commerce Version 9.1 database to your HCL Commerce+ environment, you must migrate an offline version of your HCL Commerce Version 9.1 database, so you can perform the necessary testing of your migrated HCL Commerce Version 9.1 assets. The offline HCL Commerce Version 9.1 database is the HCL Commerce Version 9.1 database that you restored to your HCL Commerce+ environment.
      - Completing the offline database migration
        After you successfully migrate your database, complete the final database migration tasks.
  - Migrating the HCL Commerce Version 9.1 code
    To migrate your HCL Commerce Version 9.1 code to Commerce+, run the migration commands. This procedure applies to customers migrating Version 9.1 code for use with the Transaction server in Commerce+. It does not apply to customers migrating to PBC mode. As part of this migration, you must remove all IBM-related code, such as com.ibm.commerce, and include only the code that is proprietary to your organization.
  - Migrate Solr search to Commerce+
    Migrate your Solr-based search solution from HCL Commerce Version 9.1 to Commerce+. This is the first step in adopting Commerce+, letting you run your existing customizations on the new runtime with your current database before you optionally move to PostgreSQL.
  - Migrate Elasticsearch to Commerce+
    Migrate your Elastic-based search solution from HCL Commerce Version 9.1 to Commerce+. This is the first step in adopting Commerce+, letting you run your existing customizations on the new runtime with your current database before you optionally move to PostgreSQL.
- Operating
  The topics in this section focus on tasks that are performed by business users, marketers, and customer support representatives to connect with partners and attract and satisfy customers.
- Administering
  The site administrator performs the tasks needed to support day to day operations of the Commerce+ site.
- Extending
  Using Commerce+'s xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
- Securing
  These topics describe the security features of 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 Commerce+ site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ reference documentation.

Completing the HCL Commerce Version 9.1 offline database migration

After you successfully migrate your database, complete the final database migration tasks.

Procedure

Update your SITE table by running the following two commands with appropriate MOD and FIXPACK values.

delete from site where COMPNAME not IN ('BASE');

UPDATE SITE SET VERSION = 25, RELEASE= 3, MOD = 19, FIXPACK = 0;

Run the updatedb command from your utility docker.

What to do next

Perform all necessary testing of your migrated custom assets with the migrated database.