Enabling Sterling Omni-Configurator integration with HCL Commerce
Enable the Sterling Omni-Configurator integration with HCL Commerce by configuring Visual Modeler, Omni-Configurator, and HCL Commerce.
Before you begin
- Ensure that you meet the following system requirements:
- Your Sterling Configurator server is running JDK 1.8.
- Your Sterling CPQ 9.5 is using Fix Pack 7 (or later).
- If you are using a B2B store model, you must install HCL Commerce 9.0.0.7 (or higher).
- Download and install Sterling Visual Modeler.
- Deploy the Sterling Omni-Configurator.
To verify that your Omni-Configurator is properly deployed, access any Omni-Configurator basic REST service URL. For example, https://configuratorServer:port/configurator/api/organization/matrix/models?language=en&country=US.
Procedure
Configure Sterling Visual Modeler.
- Create a storefront by using the Sterling Configurator Visual
Modeler tool.Notes:
- Ensure that the correct product information is used for defining the models in the Sterling Configurator Visual Modeler by creating a storefront with the same Skin ID as the Organization Code of the catalog organization.
- When you create a storefront, you must set the External Partner ID.
- Configure Sterling Visual Modeler to connect to Omni-Configurator.
To view and test your compiled models, you need to connect the Omni-Configurator backend (REST APIs) and the Configurator UI to Sterling Configurator Visual Modeler.
Configure Omni-Configurator.
- Configure the tenant-specific Omni-Configurator adapter properties.
You can define communications between Omni-Configurator and HCL Commerce by configuring Omni-Configurator adapter properties.
- Deploy the Adapter JAR file and the dependency JAR file.
- Import the certificate from HCL Commerce.
Configure HCL Commerce.
-
Enable the Sterling Transport from the HCL Commerce Administration Console.
- Configure the Omni-Configurator server URL in your STORECONF database table by running
the following SQL statement.
insert into storeconf values ($storeId,'wc.configurator.url'$configuratorServerURL,1);
Where- storeId
- Your store ID. If your store is at the site level, use a
0
value. - configuratorServerURL
- The Omni-Configurator server URL; for example:
https://configuratorServer:port/configurator
- Enable the Sterling Configurator store function in HCL Commerce Management
Center.
- Log in to Management Center for HCL Commerce and open the Store Management tool.
- Select your store; for example, AuroraESite. Then, click the Catalog tab.
- Click the Sterling Configurator check-box.
- Import the Omni-Configurator certificate to HCL Commerce.
- For development environments:
- Log in to the WebSphere Application Server Administrative Console on your development environment.
- Go to .
- Complete the following fields.
Field Description Host The host name of your Configurator server. Port The port number for your Configurator server. SSL configuration for outbound connection Select NodeDefaultSSLSettings Alias The alias for your Configurator server. - Click Retrieve signer information, then click Apply.
- For production environments:
- Export the Omni-Configurator certificate.
- Log in to the Sterling Configurator Administrative Console on your runtime environment.
- Go to .
- Complete the following fields.
Field Description Certificate alias to extract The certificate alias. Certificate file name The certificate file name. Data type Your data type, for example, Base64-encoded ASCII data. - Click Apply.
- Import the extracted certification to the HCL Commerce Transaction
Server by one of two ways:
- Manage certificates
manually.Notes:
- When you copy the certificates to the JSON file, you must replace the
line-break with
\n
to ensure that the entire certificate string is on one line. - This integration with Omni-Configuration uses one-way SSL certificate
validation. For one-way SSL certificate validation, where one
application needs a certificate to communicate with another application
that has SSL enabled, you need only to define the
issuing_ca
in the JSON file. - Load the JSON files to the /SETUP/certs/custom/ directory of your Docker container.
- When you copy the certificates to the JSON file, you must replace the
line-break with
- Manage certificates with Vault.
- Manage certificates
manually.
- Export the Omni-Configurator certificate.
- For development environments: