Switch the Mobile App to the native API integration
Updated in 2021.1
Starting with version 2.0, Alloy Navigator Mobile App no longer needs the Mobile App Service (formerly, "the Mobile Portal") as a backend. Instead, it uses the native API integration, which significantly improves the application performance. As soon as your technicians update their Mobile App to version 2.0, the app will prompt them to update the application URL, warning that the existing address is being deprecated.
In Alloy Navigator 8.7, we retired the Mobile App Service and replaced it with the API module. However, technicians could still use the "deprecated" URL until you were ready to install the API module.
In Alloy Navigator 2021, we permanently removed the Mobile App Service. If you still use the Mobile Portal as the backend, you need to switch over your Alloy Navigator mobile app to the native API before or during the upgrade of the API module.
To switch the Alloy Navigator mobile app to the native API integration:
Install the latest version of the API module and configure it for Access Token authentication.
INFO: For instructions, see Installing and Configuring the API Module
If you already have the API module of a previous version, upgrade it to the latest version.
IMPORTANT: The API must be configured for Access Token authentication.
In your Web Configuration tool, view the API URL. The URL is displayed in the main pane on the right-hand side, among other configuration information.
This is the new URL that Mobile App users should use to sign in to Alloy Navigator now.
Give the new URL to all technicians and ask them to update the application URL in their Mobile App.
When all technicians update the application URL, you can uninstall the Mobile App Service from your IIS server. You will not need it anymore.
NEXT STEP: Redirect Alloy Discovery Synchronization to the production Alloy Discovery database.