Jet Enterprise Pre-Installation Checklist

Jet Enterprise Pre-Installation Checklist
Pg. 1
| 11/13/2012
Jet Enterprise
Pre-Installation Checklist
Jet Enterprise
Pre-Installation Checklist
To ensure a fast and successful deployment
of Jet Enterprise, please complete the
following checklist prior to installation:
1) Confirm the operating system on the server meets minimum requirements
• The operating system on the server must be Microsoft Windows Server 2003, Windows Server
2008 or Windows Server 2008 R2.
• The latest available Service Packs should also be installed for the operating system. Note – for demonstration purposes the Jet Data Manager can also be installed on a desktop or
laptop running Windows 8, Windows 7, Windows XP or Vista.
2) Confirm the Server has Internet Access
This will be required to install the Jet Data Manager.
3) Confirm the SQL Server components are installed with the latest service packs.
Jet Enterprise requires Microsoft SQL Server 2005 – 2012 (Standard, Enterprise or Business
Intelligence version) to be installed with the latest Service Packs and running with the following
components: Pg. 2
► SQL Server
► SQL Server Integration Services (SSIS)
► SQL Server Analysis Services (SSAS)
If using SQL 2008, backwards compatibility tools are required.
If using SQL 2008 R2, this KB might be needed http://support.microsoft.com/kb/2315727/
| 11/13/2012
Copyright © 2011 - Jet Reports International, Inc.
Jet Enterprise
Pre-Installation Checklist
4) Confirm that the latest version of Microsoft .NET Framework is installed (v4.0 or later)
5) Set up a utility user with appropriate rights
A 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.
• If connecting to Dynamics NAV using a SQL Server data store this login need to have db_
owner role or Super (Data) rights on the Dynamics NAV database.
• If connecting to a Dynamics AX database this login needs to have sufficient privileges to access the Application Object Tree (AOT).
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.
Pg. 3
| 11/13/2012
Copyright © 2011 - Jet Reports International, Inc.
Jet Enterprise
Pre-Installation Checklist
6) Ensure SQL Server tools are started, and running under the appropriate
“Log On As” users
The “Log On As” for SSAS and SSIS should be set to the “utility user” as defined in the prior step. These should not be set to “Local System”.
Ensure that all three services are started.
7) Confirm that the drivers exist for connection to the data source
If connecting to a Microsoft Dynamics NAV, AX, or GP database, confirm that the ODBC driver
has been installed and properly configured.
8) Identify the server and database name of your Dynamics database.
9) Confirm SQL Server has port 2383 open to allow communication with SSAS (it is
uncommon that this port is closed).
Pg. 4
| 11/13/2012
Copyright © 2011 - Jet Reports International, Inc.
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

advertisement