Managing an inRiver integration project

The inRiver Connector consists of two parts:

• One on the inRiver server, Litium.AddOns.Inriver.dll, that transfers data to a shared folder or an FTP.
• The other on the Litium server, Litium.AddOns.InRiver.Integration.dll, reads data from the shared folder or FTP and runs it through the API to populate Litium with the data.

It is important that all partners work together and communicate closely to bring the project to success.

Parties involved in an inRiver integration project

Litium

Responsible for the product. Any bugs in Litium can be reported to Litium directly through the bug report form. Please read the instructions on how to fill in the form. Information on how bugs are prioritised and fixed can be found in the bug fix policy. If you want information on how to implement certain functions you can contact Litium support, or get help from expert services.

Project partner

The project implementation can be split between two partner developers, one for inRiver and one for Litium, or both parts can be implemented by the same partner.

Hosting partner

Apart from hosting inRiver and Litium, the hosting partner manages the infrastructure for data transfer between inRiver and Litium. The different components can be hosted by different partners.

Merchant

Responsible for the data.

Project implementation

The implementation partner is responsible for the actual project implementation. If there are two partners, the inRiver partner is responsible for the export from inRiver and the Litium partner is responsible for the import into Litium. It is important that the inRiver data that is exported matches the Litium data model. The partners need to communicate closely if any changes are made to the inRiver data model.

More information on different deployment scenarios can be found here.