Configure
Basic configuration options for the connector. How to configure the connector to generate appropriate field types and templates, resource fields and product relationships.
The configuration options for the connector is located in two files:
- \Program Files\inRiver AB\inRiver Connect\OutboundConnectors\Litium.AddOns.InRiver.dll.config
- \<Integration folder>\InRiverLitiumIntegration\Model\FieldTypeSettings.xml
Do not change the inRiver model and the FieldTypeSettings.xml file (see below) at the same time. If you want to make changes to the data model, first make them in the inRiver model according to the instructions below, and then change the FieldTypeSettings.xml according to instructions below.
Litium.AddOns.InRiver.dll.config
This file contains the basic configuration options that affect the data generation by the connector.
FieldTypeSettings.xml
This file is generated the first time the connector is started. It contains the settings for the property fields that will be transfered to Litium.
When the inriver connector starts on the inRiver server, it will read this file, and use the information in it when generating the \<integration folder>\inRiverLitiumIntegration\Model\ModelMapping.xml file. This file will be used by Litium to generate the fields and field templates.
Changing configuration options and the inRiver model
Follow these steps when changing the configuration options.
- Wait for any ongoing integration transfer jobs to finish. You can check ongoing exports in any of the following ways:
- Check the \Program Files\inRiver AB\inRiver Connect\Log\inRiver.Connect.log.
- Check if new files are created in the folder \<Integration folder>\InRiverLitiumIntegration\SyncCommands.
- If you use FTP transfer, you can check if new files are added to the folder \<Integration folder>\InRiverLitiumIntegration\SendToFtpQueue and that the \<Integration folder>\InRiverLitiumIntegration\FtpPickUp directory is empty.
- You may check if any imports are ongoing from the Litium backoffice in Products > Products panels > inRiver Command Queue. The list should be empty. Note that the list is not automatically refreshed, you need to refresh the page manually.
- Stop the inRiver Connect Windows service.
- If you want to make changes to FieldTypeSettings, remove the Litium inRiver connector start-up task from web.config and start the Litium website, which will cause the inRiver importer to not run automatically.
- Make the configuration changes or inRiver model changes (in Model Tool).
- Start the inRiver Connect Windows service. When starting the service any changes to the model will be transfered to Litium automatically, if you have not stopped the automatic import task (step 3 above).
- If you want to make changes to FieldTypeSettings, do the following:
- Delete the sync command files from the \<Integration folder>\InRiverLitiumIntegration\SyncCommands folder.
- Stop the inRiver Connect Windows service again.
- Change the FieldTypeSettings.xml file.
- Start the inRiver Connect Windows service again.
- Add the Litium inRiver connector start-up task that you removed in step 3 above and start the Litium website. This will make the inRiver importer run automatically.
Some configuration changes will take effect when you start working on the Rich Client.
This section explains how fields are mapped from inRiver to Litium Studio and how to configure their names and data types.
This section explains how the display templates and field templates are generated and how to change the corresponding settings.
This section explains how images (and files) are exported from InRiver and Imported into Litium.
According to inRiver recomended practise, the file data type in inRiver should only be used with inRiver resource entity types. Therefore, for all other entity types, the File data type should not be used. The images and files for a entity are connected resource entities through appropriate link types.
inRiver link types that are not part of the normal entity structure (i.e. excluding ChannelNodes and Product-Item-Resource model links) becomes either Bidirectional or Directional links in Litium where appropriate.
This article explains how to create product relationships in Litium using inRiver connector.
This article explains how to export prices from inRiver to Litium.
There is no inbuilt functionality in inRiver to represent prices. However, your ERP system may export the prices as item fields to the inRiver , and they can be imported into Litium through the connector.
This article explains how to configure the connector to change "Publish" tab in Litium variant and categories.
inRiver SKUs are the units by which the ERP system keeps track of items sold. Therefore, they are variants in Litium. This article shows how to define Sku fields for default connector implementation. Projects may extend this functionality based on the merchant and ERP requirements.
product urls are generated from the display names and SEO title and description from item display name and display description. This article explains best practices to adopt.
inRiver connector 5.0 is more streamlined to work with Litium 5 with Accelerator 5. This article explains the configuration steps.
Certain architectural differences in Litium and inRiver may make some data not published in Litium, and inRiver Litium connector has a integrity check scheduled task to detect bad data if present.