Jet Data Manager Server Upgrade Overview
This document will outline the steps necessary to upgrade your production environment to use a new version of the Jet Data Manager. It will cover the download and installation of the software, upgrading the project repository, and ensuring that the Jet Data Manager Scheduler service for the new version is up and running.
Please note that the existing installation of the Jet Data Manager (the "old" version) should be uninstalled after the upgrade is complete.
Download and Installation
The latest version of the Jet Data Manager is available from the downloads page on our website.
You will find the latest files in the Download Jet Analytics link on that page.
1. Once the file has been downloaded, unzip the installation package, navigate through the files 1 - Jet Analytics - REQUIRED > 64 bit - Jet Data Manager Server and run the Jet Analytics Setup.exe file. There is no need to uninstall the previous version, first.
2. Read and scroll to the bottom of the EULA and check the box indicating you have read and agreed.
Note: You will not be able to check the box until you have scrolled to the bottom of the EULA
Note: There will be no popup upon completion of the installation.
3. Once the installation has completed, navigate to the new version of the Jet Data Manager in your Programs and Apps and open it. The first time that the new version is opened, it will prompt the user for an Activation Code. Enter your license key and click Activate to activate your product.
This will synchronize with our licensing server and enable all of the proper license features into the Jet Data Manager.
The user may then receive a warning message that the project repository settings are invalid.
4. On the next screen, type in the server name that your current project repository resides on. Select the drop down arrow for the Database and select your current project repository. Click OK .
5. The Jet Data Manager will recognize the old repository and prompt that it needs to be upgraded to be compatible with the new version of the Jet Data Manager. Click the Upgrade button:
Note: Upgrading the repository cannot be undone. It is highly recommended to take a full SQL Server backup of your repository before upgrading so that you can revert if needed.
During the installation process there is a service installed on the local machine that controls the execution packages. These execution packages handle the regular updates made to the data warehouse and the cubes. When installing a new version of the Jet Data Manager you will need to configure this service to start automatically for the new version. To configure the service, open the Services window for the server. This can generally be accessed through the Start menu by typing Services in the search bar and selecting Services from the list that is returned.
Right click the Jet Data Manager Server Scheduler service and select Properties
On the General tab, the Startup Type should be set to Automatic (Delayed Start). If this is not available due to older versions of Windows Server then Automatic should be selected.
On the Log On tab, a service account should be used. You can refer to the original Jet Data Manager Scheduler service to determine which account was previously used. The password is required.
Right click the Jet Data Manager Server Scheduler service and click Start. The service should start normally
If you receive a message that the service started and then stopped, the most common cause is that the JDM configuration files have not been created for service account that was specified to start the service. The proper solution is to log on to the server using this service account, open the Jet Data Manager, and point to the project repository when prompted. This will create the configuration files required by the service account.
You can now log off and log back on as the original user. You should now be able to properly start the service. For more details see: Troubleshooting Execution Packages
Once all of the previous steps have been successfully followed you can now uninstall the old version of the Jet Data Manager.