For the enterprise that requires multiple Profile Managers to support many sites, the new benefit of the PFM Proxy is having one Profile Client configuration. When implemented with a launcher, the Site Map in the PFM Proxy dynamically reconfigures the Profile Client to attach to the correct Profile Manager and PTT Pro instance. Consider the following example.
Original Profile Client Config
{
"customer_id": "20",
"sfs_url": "https://<pfm-server1>",
"proxy_url": "https://<pfm-proxy-server>",
"proxy_url_api_key": "<api_key>",
"site_id": 199,
"log_level": "debug",
"confirm_role": false,
"power_connected_logout": false,
"log_file": true,
"config_settings": 0
}
This WFCDFSConfig.json file can be loaded in all devices throughout the deployment.
When the User signs into the device Launcher, among other elements, the Launcher sends the Site ID to the Profile Client via intent. The Site ID is updated in the JSON file and the device connects to the PFM Proxy.
The PFM Proxy has a listing of all the Sites and responds back to the Profile Client with the correct PFM URL (sfs_url) and the PFM Tenant ID (customer_ID). The Profile Client configuration is dynamically updated for the correct server connection.
{
"customer_id": "21",
"sfs_url": "https://<pfm-server2>",
"proxy_url": "https://<pfm-proxy-server>",
"proxy_url_api_key": "<api_key>",
"site_id": 299,
"log_level": "debug",
"confirm_role": false,
"power_connected_logout": false,
"log_file": true,
"config_settings": 0
}
The Device then attaches to the correct servers and the user is presented with their appropriate Roles and configuration.
For this functionality to work across multiple PFM Servers and PTT Pro Clusters, the serial number for the device must be present in each Profile Manager and PTT Pro Cluster.
