All components of the Jet Excel add-in, Jet Hub, the Jet Service Tier, and the Jet Dashboard Builder can be installed from a single installation program.
This guide will go in-depth on installing all components of the Jet Reports software. If you are an end user and you have any questions on the content of this article, contact your IT administrator, or email email@example.com in order to speak with our Support team to answer any questions.
After downloading the installation set (from the insightsoftware Download site), right-click the downloaded file and select Extract All.
Navigate to the Jet Reports folder and open Jet Setup.exe
Initially you will see our End User License Agreement, this needs to be scrolled through in its entirety to be able to Agree.
Within the installation program, you can choose whether to proceed with only Client Components, only Server Components, or All Components:
Client Components are those applications that typically reside on a local workstation. The Jet Excel add-in is the primary example of this.
Server Components are those items that typically reside on a server (for example: Jet Hub and the Jet Service Tier). These would require an administrator to implement properly.
For more information about the components of Jet Reports and Jet Analytics (and on which computers they should be installed), you may want to...
Watch the Video!
Note: Video is available in English, only
Once you have selected the category of components, you will be able to choose the specific features you want to install.
Server components (Jet Service Tier and Jet Hub) should be installed on only one server within an organization.
Client components (Jet Excel Add-In and Jet Administration Console) may be installed on any number of individual workstations.
If you do not use Jet Hub or the Jet Service Tier, you can simply choose Jet Excel Add-In and click Next to allow the installation of Jet Reports to proceed.
From this point, several screens will be skipped if you select to only install client components. You can skip ahead to the correct window for what you are installing.
Jet Service Tier
Next, you will need to specify some information needed by Jet Hub - specifically: the name of the server and port number used to access for the Jet Service Tier, and the URL (web address) that will be used for connecting to Jet Hub.
The Jet Service Tier field will pull the fully-qualified domain name (FQDN) of the machine that the installer is running on. If this is the machine that you are installing the Jet Service Tier on, this will need to stay the same.
The Jet Hub URL should also usually be set to the FQDN of the server it will reside on. If you do not know what to put here, it is generally correct to copy the first box into the third box, and click Next.
Next, you'll want to choose which type of User Management your organization uses. Traditionally, most organizations use Active Directory. However, the use of Office 365 credentials and Azure Active Directory are becoming more common.
Check with your system administrator if you are not sure. If you are not using the Jet Hub or Jet Service Tier, select Active Directory (do not check O365 Single Sign-on).
Optionally, you can enter your organization's Activation Code (this will save you and/or others from having to manually activate the Jet Excel add-in later). If you are installing the Jet Service Tier or Jet Hub, this step is required.
You will need to specify the Account that will be used to run the service tier (Network Service is recommended). If you do not have a dedicated Service account, Network Service already has all required permissions to run as a service. Firewall rules are required to run the Jet Service Tier and Jet Hub, so it is recommended to leave this checked.
Jet Hub settings
The installation program will automatically enable the required features in Microsoft's Internet Information Services so that you do not have do so manually.
Then, you will need to enter the name of the SQL Server instance and database name that will be used to store the Service Tier information. The service account chosen to run the Jet Service Tier will need access to this server, and will need at least "db_datareader" and "db_datawriter" on the JetServices database after installation.To test connection, check the drop down for the database name to ensure it is displaying the databases Jet will connect with. If you get an error, the account selected above most likely cannot access the SQL server you are trying to use. You may need to select to log in with database authentication, and try a sysadmin account.
If you choose an existing Jet Services database, you have the option of upgrading that database to the latest version or replacing the database. Whichever choice you make, it is recommended that "Backup database" remains checked.
Once all information has been entered, you can click Install to begin the installation process.
Installation was a success! You are now able to utilize the Jet components you have installed!
Connecting Jet Hub with your new install
The Jet Hub requires an SSL cert to be bound to the site. An admin user can do so through the IIS manager on the Jet Hub server.
- From the Connections menu in the main Internet Information Services (IIS) Manager window, select the name of the server to which the certificate was installed.
- Under Sites, select the Jet site to be secured with SSL.
- Select Jet Hub
- From the Actions menu (on the right), click on Bindings... This will open the Site Bindings window.
- In the Site Bindings window, select the Port (usually 443) that was specified during the installation of the Jet Hub and then click Edit... This will open the Edit Site Binding window.
- Select Edit
Generally, it is recommended not to change settings in this window, aside from the SSL cert. From the SSL Certificate drop-down list, select the certificate name that you just installed.
If the Jet Hub and the Jet Service Tier are installed on the same server, the Jet Service Tier Self Signed Cert is recommended.
On the server where the Jet Hub is installed, after the installation has completed and the certificate is bound, you must restart the server or reset IIS.
To reset IIS, open Command Prompt(CMD) as administrator and run the following command.