While I have mentioned the Infor CRM SLX mobile sight several times in this blog over the years, it has mostly been in passing, or in relation to some other topic. As it has a few unique features, I will explain a bit about the mobile client site in Infor CRM SLX, and how it relates to the main client site. At its core, the Infor CRM SLX mobile client site is another way of displaying the same information as the main web client. It does have a different format; with fewer options than the web client, and sized for a phone screen rather than a computer screen. You can even connect to and us the mobile site from a desktop web browser if desired, though it’s obvious it was designed for a narrow display.
When it comes to how the mobile client is handled on the server, things are a bit less straightforward. In some places in Infor CRM SLX the mobile client site is treated as its own separate site, but in others it is treated as a extension of the main web client. If you will be using the mobile client, you will want to download and install the latest version of the mobile client into your Infor CRM SLX environment (or the most recent compatible version if you are running an older version of CRM). The current version of mobile client is Infor CRM SLX Mobile 4.3, which works on CRM versions 8.4 or later. The mobile client installs as a web bundle in Application Architect, so you will need to build and deploy after installing it.
If the mobile site is installed on your instance of Infor CRM SLX, it is included whenever you build the client site in Application Architect. The mobile site is not, however, part of the deployment unless you manually add it. Once it is added, either as component of an existing portal, or on its own standalone portal, it will deploy along with all the other components. It is listed in Application Architect as SlxMobile. If you are already able to route outside traffic to your Infor CRM SLX web client site, then it would make sense to just add the mobile client as a part of the same portal. But in some circumstances, such as the mobile client is to be only CRM site available to outside traffic, it would likely be best to give it its own portal in Application Architect.
In IIS, things are organized similarly to the way they are in the Application Architect portal list. The mobile client will show up as application (still labeled SlxMobile) under the site corresponding to whatever portal it was added under in Application Architect. As an application, it will also belong to an application pool. Generally this will be the same one as all the applications under its site, and all the standard app pool rules apply. You might notice that SlxMobile itself has no setting for authentication. As I have mentioned before, the mobile client actually uses SData for authentication, and it will use whatever authentication settings the SData site uses.
