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.
Download and Installation
The latest version of the Jet Data Manager is available from on our website:
You will find the latest files in the Installation Files section of this page.
The proper 32-bit or 64-bit version should be downloaded and installed. This should match your current installation.
Once the appropriate file has been downloaded, unzip the installation package and run the Setup.exe file. Select Typical from the list of installation types when prompted.
Once the installation has completed there will be an icon on the desktop for the new version of the Jet Data Manager. Double click this icon to launch the new version. The first time that the new version is opened it will prompt the user for an Activation Code. Select Internet – I have a license code.
On the following screen paste or type in your organization’s Activation Code and click Send :
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.
Click OK, and 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 .
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:
You will then be prompted for the upgrade method. Select Web service .
The upgrade scripts will be downloaded and processed. At this point the Jet Data Manager has been installed and the project repository has been upgraded to be compatible with the new version of the client.
Please note that it is highly recommended that once the project repository has been updated, a full project deployment should be completed prior to a full project execution.
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.