Reading indices in a Live environment

If you used custom-_Template-DatabaseETL in a Version 9.1.15+ Authoring environment, perform the following steps to acquire the Search Indices from the profit margin values in the Live environment.

Procedure

Use the following URL to access the Swagger UI interface with the HCL Commerce Search Ingest service API.

http://elasticsearchhostname:30800/swagger-ui/index.html?url=/v3/api-docs&amp;validatorUrl=#/Connector%20Configuration/createConnector

Inside the Swagger user interface, navigate to Connector Configuration > POST: /connectors/
Click on Try it out.

In the Request Body field, enter the following JSON code:

{ 
   "name":"custom.live", 
   "description":"This is the connector for the custom processing", 
   "pipes":[ 
      { 
         "name":"ProfitMarginSchemaUpdateConnector" 
      }, 
      { 
         "name":"ProfitMarginDatabaseConnectorPipe"   
      }, 
     {"name":"Terminal"} 
   ] 
}

Click Execute.
Verify that the custom.live connector is created with custom profit margin process groups. In this example, ProfitMarginSchemaUpdateConnector and ProfitMarginDatabaseConnectorPipe process groups will be added to the custom.live connector.
Update the process group live.reindex - SplitLink - Post-Index
1. Navigate to the live.reindex pipeline and double-click  live.reindex - SplitLink - Post-Index.
2. Double click on Launch Connector Right-click on a blank area of the window and select Variables from the context menu.
3. Update the split.connector.name attribute to custom.live.
4. Click Ok, then Apply and, then Close.
Update the live.reindex - WaitLink - Post Index process group .
1. Go to the live.reindex pipeline and double-click  live.reindex - WaitLink - Post Index.
2. Double click on Wait for Completion. Right-click on a blank area of the window and select Variables from the context menu.
3. Update the wait.connector.name attribute to custom.live.
4. Click Ok, then Apply and, then Close.
To replicate the search index in a production environment, use the following command within a REST client.
```
POST: https://CommerceServerName:ts-app-port/wcs/resources/admin/index/dataImport/build?connectorId=push-to-live&storeId=1 
```
Leave the body empty and use a basic authentication username as spiuser and password as spiuserPassword.
Note: The default password is QxV7uCk6RRiwvPVaa4wdD78jaHi2za8ssjneNMdu3vgqi. In the current example, the storeId is given as 1 (AuroraESite); replace this with the storeId value for your own store.
Verify the status by using the following REST interface.
```
GET: https://CommerceServerName:ts-app-port/wcs/resources/admin/index/dataImport/status?jobStatusId=jobStatusId 
```
Restriction:
If Catalog data changes are not available in your live stores after a push-to-live operation, trigger a WCT+ESINDEX invalidation operation when you make the update. For more information about the procedure and the caches to be updated, refer to Troubleshooting: Index changes are not reflected in storefront after Elasticsearch push-to-live and ensure that the profit margin field is indexed.