Adding a remote store SFTP transport

Configure the SFTP transport method in the HCL Commerce Administration Console. Doing so allows you to work with the remote store Data Load utility scheduler job to periodically retrieve and apply changes to frequently-updated data.


  1. Open the Administration Console.
  2. Select Site on the Administration Console Site/Store Selection page.
    Or, select Store and your store name to configure the transport at the store level.
  3. Click Configuration > Transports.
    The Transport Configuration page displays.
  4. Click Add.
    The Add Transport page displays.
  5. Select the DataloadSFTP transport method and click Add.
    The DataloadSFTP transport is added and placed in active state.
  6. Configure the DataloadSFTP transport method. Select the check box beside the DataloadSFTP transport method and click Configure.
    The Transport Configuration Parameters dialog opens.
  7. Enter the values to be used by the transport method:
    Host The host name or IP address for your external site.
    Port The port number for your external site. The default port number is 22.
    User name The user name that is used to access the external site.
    Password The password that is used to access the external site.
  8. Click OK to accept the changes, or click Cancel to return to the Transport Configuration page.

What to do next

Store data:

After you create your custom store and populate its bootstrap data, you can use the Catalog Upload feature in the Catalogs tool to upload sales catalogs, categories, catalog entries (products, SKUs, bundles, and kits), attributes, asset references, and more into Management Center.

Or, if you indicated withSample=sampleData when you loaded the HCL Commerce Developer database schema, you can use the Aurora starter store sample data as a development base.

Cache invalidation:

After publishing your store, if cache invalidation function is enabled, the new published store can be browsed directly without restarting server by completing the following flow: After the remoteStoreDataload scheduler is completed, wait for the predefined DynaCacheInvalidation schedule to be completed. Then, update the registry from the Administration Console.