Technical setup

License

In order to use Supply Chain Integration, the Supply Chain Integration module must be activated in your license.

Web service

Supply Chain Integration uses a web service that enables the systems to communicate with each other. You need to install this web service, called Isah Supply Chain Message Service, on your server.

Database role for web service user

The database user Isah uses to log in to the web service must have the SupplyChainRole assigned. The database role assignment is validated during the installation of the web service. It is possible to ignore the warning displayed during the installation if the user does not have the appropriate role, but that will create problems later on when Isah attempts to log in to the web service in order to use the Supply Chain Integration functionality.

Web service address

In the Isah License Server, you need to specify the address of the Isah Supply Chain Message Service. To do so, follow these steps:

Start the Isah License Server.
Click Tools and then click Options.
Click the Database tab.
Select the database you are using.
Click Edit.
Click the Supply chain tab.
Enter the address of the Isah Supply Chain Message Service as http://[IP address]:[Port number]. For example: http://192.168.1.10:3090. The correct URL can be found in the IIS Management Tool.

Tip: To check whether the address has been filled in, go to Help, Info, Technical information in Isah. If your company has a license for Supply Chain Integration, a menu item called Supply Chain Integration is available, allowing you to check the address, service type, database name, and other details.

SCSN interface

If you are using the SCSN delivery method, then you will send and receive electronic messages via an automatic web interface, and not via another channel such as email. To use this interface, you need to install the following:

Microsoft Message Queue (MSMQ)
IIS URL-Rewrite
IIS Application Request Routing; after installation, you need to activate it as a proxy:
- Open Internet Information Services (IIS) Manager
- Under Connections, select the server.
- Double-click Application Request Routing Cache.
- Under Actions, click Server Proxy Settings.
- Activate Enable proxy.
- At the bottom right-hand side, under Actions, click Apply.
.NET Core Runtime 2.1 or 2.2 (3.0 is not supported)
Isah Supply Chain Interface Service.

Then configure the following settings in Isah Configuration and on the Isah Supply Chain Website:

Isah Configuration:

Choose General Settings, and then choose Supply Chain Integrator to display the settings needed for the website to function properly.

Isah Supply Chain Website:

Add your Message Service. It is possible to use more than one Message Service, but in practice, you will only do so if you have multiple internal databases.
For each Message Service, specify how you log in to another party's system (outgoing authentication). In order to send and retrieve messages, the Message Service has to be able to communicate with the web interface of that other party (company). These other companies give you access by providing you with login details. For each company you are exchanging messages with, create a line on which you enter these login details.
Create access details for every company you will be exchanging messages with via the web interface. Now send these login details to the other company, to allow them to log in to your web interface.

In conclusion: The SCSN interface uses a company's SCSN code as a unique identifier. Even if you are using a different identification method in your messages (GLN, for example), then the interface still requires an SCSN code. Therefore, for all companies you send messages to using the interface, enter the SCSN code on the Supply Chain Integration tab, and also do this for your own company (customer and supplier '99999').

You can choose your company's SCSN code as long as the codes are unique within your system. This means that you could the GLN, for example, as GLNs are unique all around the world.