Sign Up for Training |
Jet Global Company Site
Community
Downloads
Training
Submit a Request
Become a Jet Insider
Give Feedback

Pre-Installation Checklist for Jet Analytics


Moderate - requires SQL experience and Admin permissions

Overview

To ensure a fast and successful deployment of Jet Analytics (Jet Data Manager), please complete the following checklist prior to installation.

Process

  1. Confirm the server operating system meets minimum requirements

    • The server operating system must be a currently supported Microsoft OS (i.e. Windows Server 2008 or later)
    • All user machines must be joined to the domain where the Jet Analytics databases and components will be installed.
    • The latest available Windows service packs, updates and patches should be installed on servers and user desktops
    • Refer to the Server Sizing Recommendations article for questions regarding hardware requirements.
  2. Confirm the server has internet access

    This will be required to activate the Jet Data Manager.

    SQL Server Analysis Services and SQL Server Database Engine must be open to inbound connections from the internal network. The default TCP ports are 2383 and 1433.  

  3. Confirm SQL Server components are installed with the latest service packs

    Jet Analytics requires Microsoft SQL Server 2008 R2 through SQL Server 2017 (Standard, Enterprise, or Business Intelligence edition) to be installed with the latest service packs. The following components must be installed prior to Jet Analytics installation:

    • SQL Server (Database Engine)
    • SQL Server Integration Services (SSIS)
    • SQL Server Analysis Services Multidimensional (SSAS)

    Pre-release versions of SQL Server are not compatible with Jet Analytics. We aim to be compatible within a month of the version's release date.

    If using the Analysis Services Tabular Model, SQL Server 2012 or newer is required.

    In order to determine which version of SQL you are currently using please refer to the following article: How To Determine Your Version Of SQL Server

    In order to determine which SQL Server Components are installed, please refer to the following article: Ensuring SQL Server Components are Installed

  4. Ensure proper access to SQL components

    During the installation, we will need permissions to each SQL Server component as outlined in this documentJet Data Manager Minimum SQL Server Permissions

  5. Confirm that the latest version of Microsoft .NET Framework (Version 4.6.2 or later) is installed

  6. Create an Active Directory user account (Utility User)

    The utility user serves to run the scheduled updates and will be used as the log on user for the scheduler service.

    This user account needs Read Only (db_datareader role) permissions on all source databases. During the install, we will create Jet databases and assign the utility account the db_owner role on them. This account also needs to be an Analysis Services administrator so it can update the Cubes.
  7. Confirm that the client machines are joined to the domain

    Active Directory is the primary method of authentication used by Jet products. OLAP cubes are only accessible from computers joined to the domain.

Ensure Dynamics Elements are Prepared

  1. Install data source drivers if needed

    Microsoft Dynamics (GP, AX, NAV 2013-2018 and Business Central) and SQL Server data sources do not require additional drivers to be installed. Some other data sources will require an ODBC driver to facilitate a connection. Most ODBC drivers can be found on the installation media, or online by visiting the software vendor's website.

    Excel data sources require Excel to be installed on the server. If you choose not to install Excel on the server, the ACE OLEDB provider will need to be installed. It is available from the Microsoft website.

  2. If using Dynamics NAV 2009 or older, complete special setup steps

    1. There are a set of NAV objects that are added to the NAV database when using NAV 2009 and older. In order to properly import and run these objects during the installation process, you will need to have a granule added to your NAV license that permits you to do so.
      You can refer to details about getting the granule added to your NAV license in the KB article here: NAV Adapter Licensing 
    2. If you are using a NAV Native database, Jet will require the use of an ODBC connection. You will need to have a Nav Native ODBC Driver installed. The ODBC driver needs to match your NAV version. You can find the ODBC driver in the NAV installation media under the NODBC folder. You must have the NAV Adapter objects imported and processed in your NAV database before configuring the ODBC connection.

      Jet only supports NAV Native database versions 4.0 and newer, this is different from your executable version. Please verify your NAV Native database is supported.
    3. During the installation, we will need to import our adapter objects into the NAV database. This is referred to as the NAV Adapter. In order to import these objects we will need to access the following environments with "Super" permissions:

      • NAV Development Environment (NAV 2013 or later)
      • NAV Classic Client (NAV 2009 or older)

      For an overview of the adapter import process please refer to:

  3. If using Dynamics AX, ensure access to AX resources.

    During the installation, you will need to import our adapter objects into the AX database. This is referred to as the AX Adapter. In order to import these objects you will need to access the following environments with "admin" permissions:

    For an overview of the adapter import process please refer to:

Was this article helpful?
0 out of 0 found this helpful

Comments