null  User manual
Jet Enterprise Installation Process This document describes the process for installing, executing and deploying Jet Enterprise on a NAV data source. Steps are described at a high level, with links provided to additional material to provide more detail on specific steps. This document addresses the recommended setup on a Single Server. This setup is often used in organizations with a few developers that have administrative rights on the SQL Server or in a dedicated BI Server setup. This setup is by far the easiest to maintain and troubleshoot. Security needs to be taken into consideration, however, if the server is not a dedicated server for business intelligence, since the users will have sufficient rights to delete databases, modify objects, and so on. Please complete these steps prior to installation Ensure Software is installed and services are running: Prior to installation, the following software must be installed on the server: Operating System Microsoft Windows Server 2003 with latest Service Pack, Windows Server 2008 or Windows Server 2008 R2 (note – this is not required for a demonstration laptop or desktop) SQL Server SQL Server 2005 SP1 or higher (the following components must be installed with the latest Service Packs) o Database Engine o Integration Services (SSIS) o Analysis Services (SSAS) If using SQL 2008, backwards compatibility tools are required. If using SQL 2008 R2, this KB might be needed Go to Start > Control Panel > Administrative Tools > Services and check that the SQL Server, SSAS and SSIS services are started. The “Log On As” for SSAS and SSIS should be set to a user that is a Local System Administrator on the machine, and not as “Local System” as illustrated below. Supporting Software Latest version of Microsoft .NET Framework (v4.0 or later) Drivers Drivers for connection to data source (ie: the NAV ODBC driver if connecting to a Native NAV Server) Confirm User rights In a “live install” best practice is to set up a utility user that is part of the domain and serves to run the scheduled updates as well as make changes in the Jet Data Manager. This login needs to have sysadmin rights on the SQL server. On the Dynamics NAV database: • db_owner role • Super (Data) Note: The db_owner role is required only for NAV installations using a SQL Server data store. This role is required one‐time in order to import objects at installation time. Any user who can import objects into a NAV database already has this permission, so it is optional to assign it to the utility user. Super (Data) is a NAV role and is a simple way to set up security for the utility login. It is possible to use roles with more specific permissions, however this is not recommended since this login is specifically used to extract information during the scheduled update process. Because of this limited usage, granting Super (Data) access to this login is not generally a security risk. If issues are encountered when deploying the project, check to ensure that the following permissions are assigned: On the Staging and Data Warehouse Databases: • db_owner role • Alternatively: db_datareader, db_datawriter and db_ddladmin roles Note: The db_owner role is created automatically if the warehouse is initially set up using the utility user login. On the OLAP database: • db_ssisadmin role(db_dtsadmin on SQL 2005) Additional Requirements: 1) Your Jet Data Manager Activation license code is required. This is available from Jet Reports. This is not required for demonstration licenses. 2) You will need to know the server and database name for your NAV database. 3) SQL Server needs to have port 2382 open to allow communication with SSAS (it is uncommon that this port is closed). Installation Process Note: All videos can be accessed at:‐enterprise/ Download, install and execute NAV business objects A file of Navision Objects will need to be installed in the NAV database in order to create a connector to the Jet Data Manager. Please see the file titled Installation of NAV Adapter.docx or video Jet Enterprise NAV Adapter Setup for installation details. Download and install the Jet Data Manager The Jet Data Manager is the application which is used to build and maintain the Data Warehouse and Jet Cubes. This application needs to be installed onto the server. This file is titled Jet Reports (the ‘xx’ represents either 32 or 64 based on 32‐bit or 64‐bit operation system requirements). Please see the video How to Install the Jet Data Manager for installation details. Download, Deploy and Execute Project from Cube Store Please see the video How to Download, Deploy and Execute the Jet Cubes and Data Warehouse for installation details. Define security rights for OLAP Cubes Please see the video Jet Enterprise OLAP Server Security for installation details. This step would not be required for demonstration purposes, only on Cubes and databases which must be secured. Define security rights for Data Warehouse Please see the video Setting up User Permissions to the Data Warehouse for installation details. This step would not be required for demonstration purposes, only on Cubes and databases which must be secured. Define execution schedules for the Data warehouse and cubes Please see the video Scheduling and Automatic Execution for installation details. This step would not be required for demonstration purposes, only on Cubes and databases which must be secured. If the Data Warehouse and Cubes will be set to automatically update on a regular basis then the Jet Data Manager Scheduler service will need to be started as well. The service should be set to start automatically with the “Log On As” set to be the same user as above. 
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF