Upgrade

Pre-requisites

• inRiver connector v.5 need Litium 5 and inRiver v 6.3 with inRiver connect.

Important changes from v.4 to v.5

1. Integration sub-directory name is changed to InRiverLitiumIntegration.
2. \\<Integration folder>\InRiverStudioIntegration\ConnectorSettings\ConnectorSettings.xml is renamed and relocated to \\<Integration folder>\InRiveLitiumIntegration\Model\FieldTypeSettings.xml. Its structure and content has changed, you cannot use the old file, instead need to copy the settings to the newly generated file.
3. Command file naming and error file naming, their folders are changed. The information contained inside the command files are also changed.
4. xml documents which contain data being imported are changed. You cannot use the v.4 xml documents with v.5
5. Display images are handled in _images field in Litium, see below in configuring.

Upgrading inRiver to v 6.3

Makesure the upgrade of inRiver to v 6.3 is complete, and ensure following:

1. inRiver server and inRiver connect starts without crashes and exceptions.
2. All your channel structure is visible in inRiver rich client,
3. inRiver rich client does not freeze when you touch nodes and has finished caching of images, and other optimizations.

Upgrading steps

1. Install inRiver Connector. Refer Install section for more details.
   1. You need the new integration sub folder called InRiverLitiumIntegration.
   2. Do not need to delete or clear any data from Litium.
2. Configure the connector. Refer Configure section for more details.
3. Test connector with a new test assortment with atleast two product groups, one or two products, items and connected images. Makesure it all works ok with new test entities before proceeding. The very first changes may take time, depending on the size of your inRiver data.
4. Remove your test entities.
5. Do a full channel publish from inRiver.

Configuring Display Images

In after Litium 5, display images are in a special field called _images.

Move the display image links to following settings in the configuration file:

• categoryDisplayImageLinkTypeId=""
• baseProductDisplayImageLinkTypeId =""
• variantDisplayImageLinkTypeId =""

And remove the settings that were previously in the following attributes.

• resourceFieldGroupIds=""
• noOfImagesInResourceLinkTypeId=""
• resourceFieldDefinitionIds=""