
Troubleshooting: Ingest indexing fails due to certificate issue
After updating to HCL Commerce Developer 9.1.17.0, or updating your stack manually to WebSphere Application Server 9.0.5.21 or greater, a certificate issue can cause the Elasticsearch-based Ingest search indexing process to fail.
Problem
After updating to HCL Commerce Developer 9.1.17.0, or updating your stack manually to WebSphere Application Server 9.0.5.21 or greater, a certificate issue can cause the Elasticsearch-based Ingest search indexing process to fail.Ingest job failed for storeId: 1. The error is: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching es-db2-data.hclcomdev.com found.This error is caused by WebSphere Application Server 9.0.5.21 hostname verification on SSL certificates. See Hostname verification for WebSphere Application Server traditional for more information.
Solution
To resolve this issue, choose one of the following solutions:
- Solution #1:Configure the hostname for Ingest to be
ingest.- Run the configureElasticSearch
configuration utility, specifying the Ingest hostname as
ingest.configureElasticSearch.bat elasticSearchDataQueryHost elasticSearchDataQueryPort ingest 30801 elasticSearchHost 30200 http redisHost 6379 toolingSDKInstallDir reactStoreSDKInstallDir - Add an entry in your HCL Commerce development environment hosts file to
associate the hostname with an IP
address.
ip-address ingest
- Run the configureElasticSearch
configuration utility, specifying the Ingest hostname as
- Solution #2: Configure and restart your Transaction server
(
ts-app).- Add the Java system property
com.ibm.ssl.verifyHostname, and set it to false within your Transaction server.Review Setting a Java system property in the WebSphere Application Server for instructions on setting the Java system property.
- Restart the Transaction server.
- Add the Java system property
Result
The Ingest indexing process now completes as expected.