Configure the SData Sync Portal in Infor CRM SLX

One of the useful features of Infor CRM SLX is its ability to synchronize data with other applications. This sync is generally accomplished by allowing the other apps to connect to Infor CRM SLX using the SData portal. As a result, whenever you are setting up a synchronization in Infor CRM SLX, you must also set up the SData Sync Portal to serve as a point of connection for the system being integrated.

To configure the SData Sync Portal in Infor CRM SLX, log in to the web client as Admin, expand the Administration section on the left, and click on SData Sync Configuration. The Infor CRM Feed shows the URL with which to connect to the SData sync portal. You are not allowed to edit the feed address directly, but all those fields below it on the page are so you can set the values of various parts of the feed address. You will need to fill those out, then click the Save icon.

For the example below, I am on a server named “server”, and am using port 3333. In most Infor CRM SLX implementations, you would want to leave the Data Portal as sdata, though if your implementation has multiple data portals, you could specify a different one. Likewise, it is generally best to use the Admin account (and type in its password), but you could create another account to use and specify it instead. Once you have these values all entered, click save, the click test to verify that your sync portal is working.

The test button merely attempts to connect and gives the results. It will just be a success message if all is well, or the error a browser would display if the connection fails (authentication error if the password is wrong, server not found if the wrong server name, etc.). In most cases, an error will give you a clue as to what needs to be fixed to get the connection working. It might be prudent to check the IIS configuration if you are not sure what to use for some fields.

I also wanted to say a bit about SSL and the default ports. If you check the SSL box, it changes the address from http to https, which you will need to do if you are using SSL on your SData site. If you SData site is using one of the default ports (80 for http, or 443 for https), you should be able to leave the port field blank, as it will default to using the respective port. I have, however, encountered cases in which I had to actually specify the default port of 80 or 443 to get it working initially, and was then able to remove the from the configuration afterward. In these cases, not sure if something was stuck, or if it was just some sort of latency and would have worked eventually anyway.