Deprecated functionality

Deprecated features

If a feature is listed as deprecated, HCL might remove this capability in a subsequent release of the product.

Registry Manager

Note: From HCL Commerce version 9.1.2.0 and above, Registry Manager can maintain a set of registries from the Administration Console as well as Management Center. However, the Administration Console functionality is deprecated. Management Center is recommended for managing registries

`http` headers are now configured in the web server rather than in wc-component.xml

The following security headers were previously configured in wc-component.xml. Their configuration now happens in the web server. They have been added to httpd.conf for ts-web and tooling-web, and to virtual-host-6443.conf for store-web:

Header setifempty Permissions-Policy "geolocation=(), microphone=(), camera=()"
Header setifempty Referrer-Policy "strict-origin-when-cross-origin"

You can still configure these headers in wc-component.xml but risk duplication of the web server serttings.

`X-XSS-Protection` htttp header replaced by the `Content-Security-Policy` (CSP) header

The X-XSS-Protection http header is deprecated because most modern browsers (including Chrome, Edge, and Firefox) have removed built-in XSS filtering support. That makes this header ineffective and, in some cases, capable of introducing additional security vulnerabilities. It is recommended that you use the Content-Security-Policy (CSP) header instead for XSS protection. CSP is configured in the web server and provides a more robust and flexible mechanism to prevent cross-site scripting.

IBM json4j.jar replaced by wink-json4j-1.4.jar

The IBM json4j.jar file is deprecated. It still works but the recommended version is wink-json4j-1.4.jar. The JAR contents are repackaged and for ongoing development, instead of being inside org.apache.commons.json.*, the classes are now in org.apache.wink.json4j.*. For example,

org.apache.commons.json.JSONArray
 org.apache.commons.json.JSONObject

in JSON4J.jar becomes

org.apache.wink.json4j.JSONArray 
org.apache.wink.json4j.JSONObject

in the replacement Wink .jar file.

When building new customizations, refer to the new .jar file. For example, replace

import org.apache.commons.json.JSONArray;
import org.apache.commons.json.JSONException;
import org.apache.commons.json.JSONObject;

with


import org.apache.wink.json4j.JSONArray
import org.apache.wink.json4j.JSONException
import org.apache.wink.json4j.JSONObject

Commerce Accelerator catalog filter

Previous versions of HCL Commerce allowed for the creation and modification of catalog filters within Commerce Accelerator.

Recommended action: To create and modify catalog filters for use within Commerce Accelerator, use the Catalog Filter and Pricing tool within the Management Center for HCL Commerce.

HCL Commerce SOI services

Working with HCL Commerce services involves developing client libraries, new commands, and business logic.

Recommended action: Use the REST service framework to work with the command framework and develop business services. Java Persistence API.

Data service layer

The data service layer (DSL) provides an abstraction layer for data access that is independent of the physical schema.

Recommended action: Use the Java Persistence API. For more information, see Java Persistence API.

HCL Commerce use of Open Applications Group (OAGIS) messaging in the storefront

Previous version of HCL Commerce service interfaces were defined using the OAGIS message structure from The Open Applications Group. In HCL Commerce Version 9.1, the storefront no longer uses and BOD services.

Note: BOD services and OAGIS messaging for integration usage is not deprecated.

Recommended action: Use REST tags in the storefront. Use the REST service framework to implement new back-end services. For more information, see Java Persistence API.

Request for Quote (RFQ)

The RFQ functionality, originally introduced in HCL Commerce version 5, is deprecated in HCL Commerce Version 9.

Recommended action: Integrate with IBM CPQ to leverage the RFQ functionality in Sterling Configure Price Quote.

ATP inventory model

Available to promise (ATP) inventory allocation, a method of allocating inventory using HCL Commerce as the inventory system of record, is deprecated in HCL Commerce Version 9.

Return process

The return process and the data model is deprecated in HCL Commerce Version 9.

Recommended action: Integrate with IBM OMS to manage return orders, or reverse orders.

MultipleQueryComponent and MultipleFacetComponent

MultipleQueryComponent and MultipleFacetComponent used to join or filter subcores are deprecated in the HCL Commerce Version 9.

Recommended action: Use the Solr join feature for cross cores filter operation.

Session management with URL redirection

Using URL rewriting for session management was deprecated in HCL Commerce Version 9.1.

Recommended action: Use cookie-based session management.

encryptChallengeAnswer utility

The encryptChallengeAnswer utility is deprecated in HCL Commerce Version 9.1 as of 9.1.6.0.

Recommended action: Use the MigrateEncryptedInfo utility to encrypt USERREG.CHALLENGEANSWER. You must first set the MemberSubSystem/challengeAnswerEncrypted flag in the wc-server.xml configuration file to true.