Configure
Basic configuration options for the connector: how to configure the connector to generate appropriate field types and template, resource fields and product relationships.
Configuration options for the connector is found in two files.
- \\Program Files\inRiver AB\inRiver Connect\OutboundConnectors\Litium.AddOns.InRiver.dll.config
- \\<Integration folder>\InRiveLitiumIntegration\Model\FieldTypeSettings.xml
Do not change the inRiver model and the FieldTypeSettings.xml file (see below) at the same time. Instead, if you have model changes, change the inRiver model first according to instructions given below, and then change the FieldTypeSettings.xml next according to instructions given 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 connector is started. It contains the settings for property fields that will be transfered to Litium.
When the inriver connector in inRiver server is starting, it will read this file, and use the information in it when generating the "<integration folder>\inRiverLitiumIntegration\Model\ModelMapping.xml" file. It is this Model\ModelMapping.xml file that will be used by the Litium side to generate the fields and field templates.
Changing configuration options and inRiver model
Follow the following steps when changing configuration options.
- Wait for existing integration trasfer jobs to finish.
- You may check any exports ongoing from the \\Program Files\inRiver AB\inRiver Connect\Log\inRiver.Connect.log or you may monitor the \\<Integration folder>\InRiverLitiumIntegration\SyncCommands folder to see whether new files are getting created. If you are using FTP transfer, you should also see whether new files are comming to \\<Integration directory>\InRiverLitiumIntegration\SendToFtpQueue and that \\<Integration folder>\InRiverLitiumIntegration\FtpPickUp directory is empty.
- You may check any imports ongoing from the Litium backoffice, in Products > Products panels > inRiver Command Queue. The list should be empty. (note that the list is not auto-refreshing, you should refresh the page manually).
- Stop the inRiver Connect windows service.
- If you have FieldTypeSettings changes also, 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.
- Do the configuration changes or inRiver model changes (in model tool).
- Start the inRiver Connect windows service. When starting the connect service any model changes will be transfered to the Litium automatically if you had not stopped the import task (as in step 3 above)
- If you have field typeSettings changes,
- delete the generated Sync commnad files from \\<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 back the Litium inRiver connector start-up task you removed previously and start Litium website, which will cause the inRiver importer to run automatically.
Some configuration changes will take effect when you start working on the rich-client.
Inriver languages may need to be mapped to Litium languages, this article explain how to configure.
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.
The files moved into archive folder are deleted periodically. This section describes how to configure and what files would be deleted.