This next program I am going to cover is a bit of a departure. After covering several Infor CRM SLX programs (Connection Manager, Administrator, Application Architect, twice), in this post we will be covering IIS (Internet Information Server). IIS is not an Infor CRM SLX program. It is, in fact, a Microsoft MMC snap-in used to control Windows server’s built-in web server. Because there are so many IIS settings that affect the CRM web client, I wanted to include it in this series.
By default, IIS is not installed on Windows Server, but must be added using Windows Server Manager. The official prerequisites given for Infor CRM SLX call for every single feature of IIS, with the exception of WebDAV publishing, to be installed. If this has been done, it will show that 42 of 43 roles have been installed. If it turns out an any point you are missing a server role that you need, you can come back to Windows Server Manager and install it.
They are many, many settings for sites published through IIS. If you allow Infor CRM SLX to create the site, the settings it uses should be the correct ones for most situations. If you create the website manually, there are two settings that will need to be changed from the default. In IIS, double click on Application Pools, right click on the application pool that Infor CRM SLX uses (usually titled Saleslogix), and choose Advanced Settings. For manually-created app pools, you will need to change Enable 32-Bit to True, and change the Identity from ApplicationPoolIdentity to the WebDLL account (or whatever account you are using for the Infor CRM SLX service account).
There are a few settings that can be edited the parent site level. The one I most often have occasion to use is Edit Bindings. You can add or remove bindings that determine which addresses, IPs, and/or ports the site is listening on. It is most commonly used to add a port, or to limit the site to a certain URL. If you are using an SSL site, this is also where you would go to bind a certificate to the site. Do be aware that it is no longer possible to create an SSL site (one beginning with https://) without a certificate. In previous versions, if you were to create an SSL site and not bind a certificate, it would let you publish it (though users would get a certificate error when visiting). In the current version of IIS, if you have an SSL site without a valid certificate, IIS will not let the site run. And worse, the error it gives when you try to start the site says the issue in an IP address conflict, which has confused me more that once when troubleshooting.
Most of the other settings you might need to look at are at the child site level. As a result, if there are any changes you need to make in the settings for the entire Saleslogix deployment, you will need to make those changes individually on each of the deployed child sites: SlxClient, SData, and an any others that might exist such as the Customer Portal. The changes that you can make at this level include setting the default document for when users log in, and changing the authentication used by one of the child sites.