inRiver

Connect Sana to inRiver

When the inRiver add-on is installed into Sana you need to configure it in order to establish connection between inRiver and Sana.

In Sana Admin click: Apps > Add-ons. You can configure inRiver from any tab on the "Add-ons" page by clicking on the Configure button .

The table below provides the description of the inRiver add-on connection settings.

When connection between Sana and inRiver is configured, click Test connection to check whether the connection is available.

inRiver "Enabled" option

There are two options in Sana Admin which are used to enable or disable the inRiver add-on:

• You can enable or disable the inRiver add-on from any tab on the Add-ons page.

• On the Configuration page of the inRiver add-on you can see the additional Enabled option. This additional option is used to disable the inRiver add-on in the safe way.

When you run the Product import task for the first time after the inRiver add-on is installed and configured, the fields from inRiver will be imported and saved in Sana. If for some reason you disable the inRiver add-on, then the next time you start the indexing of products, the Product import task will fail. It happens because Sana requests the inRiver fields from the ERP system and the ERP system gives back errors in response, since it cannot find these fields.

To avoid the failure of the Product import task, you should disable the inRiver add-on using the additional Enabled option. This option completely disables the inRiver add-on. In this way, when the product indexing starts, the fields from inRiver will be removed from the ERP request and the task will not fail.

Both Enabled options should be set up in the same way, for example if you disable the inRiver add-on using one option, the other one should be also disabled.

inRiver connection troubleshooting

While testing the connection between Sana and inRiver, in certain cases the system can throw errors, meaning that the connection has not been established. The connection can fail for various reasons, here you can see the information about some errors and how they can be fixed.

Exception during creating remote manager: There was no endpoint listening at ...

This message will be shown, if the Web service URL is incorrect or could not be resolved. You should check if URL is correct and there is the endpoint which listens to this URL. Contact Sana or inRiver to get the details.

Exception during creating remote manager: Authentication failure

This message will be shown in case the connection via Web service was successfully established, but authentication failed.

Verify that you have entered the valid credentials (username, password), or try to enter your password again.

You should also check whether there are no leading or trailing spaces in the following fields:

• Username
• Password
• Environment

If some other errors besides those mentioned in this article are shown, you should contact Sana.