About
The MobileServerURL or Mobile Service URL is utilized for connections to Capacity IQ® Mobile applications. We will review how to identify this information. This workflow is meant for Application, Server, or Network Administrators that have access to the servers in which TeleTracking® components are installed.
Steps
Navigate to the Mobile Server
Generally the IQ Connector Server, also referred to as a Gateway Server, houses the mobile web components.
Uncommonly the components would be installed on the Capacity Management Suite® application server.
Identifying via the SSL Cert
Primary Install
In IIS expand Sites
Select Default Web Site
Open Bindings
Navigate to HTTPS
Select Edit
View the Site Binding
Navigate to Details
Select Subject
The value of CN takes place of the <TOKEN> formatted as
https://<TOKEN>
In this case we have a full URL of
https://VXCPITSVWTS001.teletracking.com
Proceed to Verifying the Mobile URL
Secondary Install
A Secondary Install will have the mobile web components installed to another path in IIS.
Expand the Default Web Site
You will see the additional mobile application path
The <Path> would be added to the previous URL path found
https://<URL>/<PATH>
In this case we have a full URL of
https://VXCPITSVWTS001.teletracking.com/Mobile_CDS
Proceed to Verifying the Mobile URL
Identifying any redirects or alternate names
It is possible that your configuration includes additional routing layers such as redirects and load balancers.
Depending on the configuration, that may have been accounted for in the SSL certificate common name.
You may need to work with a network resource to identify any additional configuration in your network.
Verifying the Mobile URL
The MobileServerURL is formatted as either:
Without a Secondary Path -
https://<CommonNameFromSSLCert>
With a Secondary Path -
https://<CommonNameFromSSLCert>/<SecondaryInstallPath>
You can confirm this is the correct domain by adding /swagger to the end of the URL such as
https://<CommonNameFromSSLCert>/<SecondaryInstallPath>/swagger
The page should be redirected to */swagger/ui/index and you should see a green banner as below:
Best Practices
Any connections to mobile must include https in the path to function properly.