There are some scenarios where it is desirable to install the Jet Data Manager in an environment in which SQL Server will not be installed. For example, an organization may want to have one server contain all of the SQL databases and then have another server that contains the Jet Data Manager application. It is also possible to have the Jet Data Manager reside on a user's local machine and remotely interact with the SQL components on the SQL Server.
The Jet Data Manager utilizes SQL Management Objects (SMO) for many of the tasks that are completed during deployment and execution of a project. While these objects will already be present on a machine that has SQL installed, it will most likely be necessary to install them on a machine that does not already have SQL present. Installation of these objects can be reviewed here:
When running SQL 2012, it may also be necessary to install the Microsoft SQL Server 2012 Analysis Management Objects for the OLAP roles to properly deploy.
It is also generally a best practice to have the Jet Data Manager installed on the machine where the SQL databases reside. This copy of the Jet Data Manager can be configured to run the regular execution packages that update the data. Installing the Jet Data Manager solely on a user's local machine introduces the risk that the machine will be regularly powered off, which will prevent the scheduled execution packages from running. Having the execution packages scheduled on the server will eliminate these risks, as the server will generally be powered on when it is time to run the packages.
Installing the Jet Data Manager
The Jet Data Manager can be downloaded from the Jet Global Download Page. The correct installer should be downloaded (32-bit or 64-bit) based on the configuration of the machine that the Jet Data Manager is to be installed on.
Double-click the Setup.exe file and follow the normal installation process. When prompted, "Typical" installation should be used.
Once the Jet Data Manager has been installed, an icon will be placed on the desktop. Double-clicking the icon will launch the Jet Data Manager for the first time. Since it is the first time using this installation of the Jet Data Manager, the user will be prompted to activate the product. The user should select Internet - I have a license code and then paste in the activation code that was previously supplied by Jet Global.
After activating the Jet Data Manager, the user will be prompted that a project repository cannot be found. The user should input the server name and database name for the main project repository database.
As stated in the prerequisites, the best practice is to do the initial implementation of Jet Analytics on the server so the project repository would already exist. Installing the Jet Data Manager on local machines allows users to interact with the Jet Data Manager without having to be physically logged in to the server.
Configuring the Project
Since the machine on which the Jet Data Manager was installed does not have any SQL components, SQL Server Integration Services (SSIS) will not be used. In order to construct SSIS packages, the SSIS components would need to be on the same machine as the Jet Data Manager. Because of this, the use of Integration Services needs to be disabled in the project.
To disable the use of Integration Services in the project, right-click the project name at the top node of the Data tab and click Edit Project. The user should uncheck the boxes for Use Integration Services and Use Integration Services Folder.
Click OK. This will cause the Jet Data Manager to utilize ADO.NET packages instead of SSIS packages.