On the web server in Infor CRM software, the locations of some services are hard-coded into a couple of the config files. If you are using the same machine as your application and web server, you need not worry about this, as all those references will already be pointing to localhost. However, if you are using separate app and web servers, you will need to make sure these references are pointing to the application server, where those services are running.
The config files we need to edit are on the web server’s file system at Inetpub\wwwroot\(portal). They can also be found in Application Architect under Project Explorer > (Project) / Portal Manager / (portal) / SupportFiles. In this case (portal) is SlxClient, Sdata, and any other deployed portals. If you are doing this before you build and deploy, you only need to make these changes in Application Architect. If you going back trying to fix this after deployment (like I usually end up doing), you need to fix these files in the inetpub folder to get the web client working, then also fix them in Application Architect soit doesn’t overwrite you fix the next time you deploy.
We will be editing appSettings.config and web.config. These two files change quite a bit from version to version, so we are going to find the parts we need to edit by searching for the port numbers. Open appSetting.config and search for 1895. This should bring to to a line similar to:
<add key=”sage.scheduling.client.serverUrl” value=”http://localhost:1895″ />
Change localhost to the name of the app server, then save.
Now open web.config and search for 9001. This will take you to line that begins something like:
<endpoint name=”MessageBusService” address=”net.tcp://localhost:9001/Server/MessageBus”
Once again, change localhost to the name of your app server. Now, still in web.config, search for 11211. This will take you to the line:
<add address=”127.0.0.1″ port=”11211″ />
In this case, you need to replace 127.0.0.1 with the IP address of the app server. Now save this file.
If you are on the live site, and IIS reset will make the changes live. If you are in Application Architect, those files are now ready for the next build and deploy.