Once you have the feature for Jet Enterprise dashboards installed, there are a series of tasks that you will need to perform to ensure connectivity. This article details out each task and where possible provides links to demonstrate the activity.
1. Ensure the account you've setup to run the Jet Service Tier has the appropriate permissions to read/write from the Jet Services database. For this you will need to know A) what server the database was created on and B) what account you used during the installation for the 'Run As Account' setting.
A) If you installed all of the dashboard components to the same server, then the Jet Services database will be on this server. If you setup the environment following the 'Two Server Jet Mobile Architecture' layout, then you will be looking in the server that holds the databases.
B) Although it is recommended to use the 'Network Service' account (i.e. NT AUTHORITY\NETWORK SERVICE), you have the option of running the service as any other account during installation.
2. Confirm an existing (or create a new) Inbound Firewall rule for HTTPS connections.
A) The recommended port for use to access your dashboards is port 443. This is the standard port in use for the 'World Wide Web Services (HTTPS Traffic-In)' firewall rule. If you chose a separate port for use with your dashboards, you will need to create a new rule.
3. Ensure IIS Client Certificate Mapping Authentication
A) This should be installed as part of the dashboard feature installation process. If you find that it is not, please contact our support team with detailed information including your version of Windows and what version of the Dashboard Builder and Jet Service Tier you are installing.
4. Ensure ASP.NET v4.0 Application Pools are running (applicable only to Server 2008R2 and prior as well as Windows 7 and prior)
A) To do this, go to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 (This could be C:\Windows\Microsoft.NET\Framework\v4.0.30319 if not running 64-bit) Once there, right-click on 'aspnet_regiis' and select "Run as administrator".
B) You can confirm that this ran by checking the Application Pools. If ASP.NET v4.0 and ASP.NET v4.0 Classic appear as below, this will confirm the process completed successfully.