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/9.0.0/install/concepts/v9enhancement.html
The configuration should be performed by an experienced RAD developer.
Note
For customizing HCL Commerce 8.0, please refer to ???.
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 customization package for the store server (
websphere-commerce-crsarchive). It contains the required customizedcrs-webpackage to be added to theCusDeploydirectory of your store server Docker image.The customization package for the transaction server (
websphere-commerce-tsarchive). It contains the required customized code to be added to theCusDeploydirectory of your transaction server Docker image.The customization package for the search server (
websphere-commerce-searcharchive). It contains the required search configuration and search customization code to be added to theCusDeploydirectory of your transaction server Docker image.The Sample Data for HCL Commerce archive (
websphere-commerce-sample-dataarchive). 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 all files on the CoreMedia releases download page at https://releases.coremedia.com/cmcc-10
The customization involves the following aspects:
Section 4.1, “Building Custom Docker Image” describes how to deploy the deployable custom packages in your HCL Commerce.
Section 4.2, “Preparing the RAD Workspace” describes how to apply the required customization to your HCL Commerce workspace.
Section 4.3, “Copy Libraries” describes how to copy libraries to your HCL Commerce workspace.
Section 4.4, “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 4.5, “Extending REST Resources to BOD Mapping” describes how you have to configure the mapping of REST resources to the Business Object Document nouns.
Section 4.6, “Configuring REST Handlers” describes which REST handlers you have to add and configure.
Section 4.7, “Applying Changes to the Management Center” describes the deployment of the Management Center customization.
Section 4.8, “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 4.9, “Customizing HCL Commerce JSPs” describes how to apply customizations to HCL Commerce JSPs.
Section 4.10, “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 4.11, “Setting up SEO URLs for CoreMedia Pages” describes how to set up SEO URLs for CoreMedia Pages.
Section 4.12, “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.
