Connector for HCL Commerce Manual / Version 2107
Table Of Contents
Note
Only required when you want to use the eCommerce Blueprint
This section describes how you have to adapt your HCL Rational Application Development (RAD) environment in order to integrate with CoreMedia Content Cloud.
In general, certain configuration files need to be adapted in the HCL Commerce workspace. Depending on your degree of already applied customization, you might need to merge the provided configuration snippets with your custom code.
This chapter also contains small configurations in the CoreMedia system. These tasks are highlighted in the margin.
Note
Deployment to HCL Commerce servers, including Staging, Production and Development, is not part of this manual. Please refer to appropriate HCL documentation in the info center at https://help.hcltechsw.com/commerce/index.html
The configuration should be performed by an experienced RAD developer.
Note
For customizing HCL Commerce 9.0, please refer to Chapter 4, Customizing HCL Commerce 9.0.
Note
This chapter does not apply to HCL Commerce 9.1 either. With HCL Commerce 9.1 no customizations are required. Please refer to Chapter 5, Supporting HCL Commerce 9.1.
Scope of delivery
In order to connect Content Cloud with your HCL Commerce server you will get the following artifacts from CoreMedia:
The HCL Commerce Workspace archive (Workspace archive, for short). It contains the required resources to customize the HCL Commerce Server and JAR files with extensions for Content Cloud to be added to the classpath of your HCL Commerce workspace and deployment packages. These files include the configuration described in the following chapters.
The Sample Data for HCL Commerce archive (Sample Data archive, for short). The archive contains sample data for the HCL system, which corresponds with the test data for the CoreMedia system in CoreMedia Blueprint.
You will find both files on the CoreMedia releases download page at https://releases.coremedia.com/cmcc-10
The customization involves the following aspects:
Section 3.1, “Preparing the RAD Workspace” describes how to apply the required customization to your HCL Commerce workspace
Section 3.3, “Configuring the Search” describes how you have to add the CoreMedia search profile and the Solr index. This enables the CoreMedia system to get additional information necessary for the integration.
Section 3.4, “Extending REST Resources to BOD Mapping” describes how you have to configure the mapping of REST resources to the Business Object Document nouns.
Section 3.5, “Configuring the Cookie Domain” describes how you enable session synchronization between the CoreMedia and HCL system for content-led scenario.
Section 3.6, “Multiple Log Ins for the Same User” describes how you configure the HCL Commerce system to accept multiple logins with the same user.
Section 3.7, “Configuring REST Handlers” describes which REST handlers you have to add and configure.
Section 3.8, “Applying Changes to the Management Center” describes the deployment of the Management Center customization.
Section 3.9, “Deploying the CoreMedia Fragment Connector” describes the deployment of the fragment connector, which renders content from Content Cloud as fragments to HCL Commerce pages.
Section 3.10, “Customizing HCL Commerce JSPs” describes how to apply customizations to HCL Commerce JSPs.
Section 3.11, “Deploying the CoreMedia Widgets” describes the deployment of the CoreMedia widgets, which can be used to add content or assets from Content Cloud to HCL Commerce pages using the fragment connector.
Section 3.12, “Setting up SEO URLs for CoreMedia Pages” describes how to set up SEO URLs for CoreMedia Pages.
Section 3.13, “Event-based Commerce Cache Invalidation” describes how to enable event based commerce cache invalidation.
Section 3.14, “Deploying the CoreMedia Catalog Data” describes how to import the CoreMedia catalog content from the Sample archive into the HCL Commerce.
Note
In the following sections WCDE-INSTALL stands for the installation
directory of your HCL Commerce RAD installation.
