This article details the process one must take to migrate Jet Enterprise to a new sever.
The project repository contains all of the necessary instructions to rebuild the infrastructure critical to the Jet Enterprise platform. This information lives in a SQL database that will generally be hosted on the server that Jet Enterprise is being migrated from. Because of this, the project repository database is the only database that will be required to be migrated to the new server.
The most efficient manner to accomplish the migration is to take a SQL backup of the project repository database from the original environment and restore it to the new server environment.
Jet Data Manager Installation
Once the project repository database has been successfully restored to the new environment you will install and configure the rest of the solution using the Jet Data Manager (JDM). The latest version of the Jet Data Manager can be downloaded from:
The most common installation package used will be the 64-bit package as most servers operate in this environment. If your server uses a 32-bit operating system or if you utilize ODBC connectors as additional data sources you will want to install the 32-bit version of the JDM.
Once the Jet Data Manager has been installed you will be prompted for the location of the project repository database. You should select the project repository database that was restored to the new server in the previous section.
If a newer version of the JDM that is installed on the new server it will prompt you to upgrade the project repository. You will want to click the “Upgrade” button and then select “Web Service” as the upgrade method. For instructions on upgrading to a new version of the Jet Data Manager see: Upgrading the Jet Data Manager
The next step is to configure the project to ensure that the database components are properly set up. To do this, right click the project name at the top node of the Data table and click “Connection Manager”. You will then click the notepad icon to the left of the green checkbox for each of the following components:
- Staging database
- Data warehouse
- OLAP server
For each of these you will want to ensure that the server name is set properly. If these databases reside on the local server you can type localhost as the server name. For the staging database and data warehouse you will want to click the Create button to create these databases on the new server.
You can now click the “Test Connections” button and all buttons should be green.
Jet Data Manager Scheduler Service
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 migrating to a new server you will need to configure this service to start automatically. 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 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 installation server to determine which account was previously used. The password is required.
The service account that is used will need to have proper SQL permissions set up so that it can process the databases and the cubes. This service account should have SQL “db_owner”permissions set for the project repository, staging, and data warehouse databases and should be set as an administrator for the Analysis Services component of SQL Analysis Services. This can be accomplished through the SQL Management Studio. For more details see: Setting Permission on SQL Server
Right click the Jet Data Manager 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 JDM, 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
Deployment and Execution of the Project
The final step is to complete the initial deployment and execution of the project so that the SSIS packages are created and the database warehouse and cubes are populated. This is achieved by opening the JDM and clicking “Manual Deployment and Execution” at the top. Click “Start”. This will start the initial deployment and execution process.
Once the initial deployment and execution process is completed the migration to the new server has been completed.