Skip to main content

Configure Multiple Environments Manually

Overview

A Development Environment enables users to work within non-production environments. This is useful when an organization needs to ensure that the production environment is always available for end users. For example, the organization could have an environment called “ development ” where changes are made, dimensions are updated, measures are created, and so on. Once these modifications are tested they can be transferred to the live production environment.

This article details how to properly setup a development and production environment without the use of the Development Toolkit. For more information on the Development Toolkit see Development Toolkit.

One can setup a development and production environment on the same server or on a different server. The process is similar in either case. Where there is a difference it will be noted in the article

Create the Development Environment

When creating databases it is always a best practice to ensure that the collation used is the same across all your databases and that this collation matches the collation of Analysis Services. For example, the staging database, data warehouse, and OLAP server should be assigned the same collation.

Create Project Repository (Development)

  1. Open the Jet Data Manager.

  2. On the Tools tab select General Settings....

    The Project Repository Dialog window opens.

  3. In the Server Name field enter the name of the server. In this example we are using localhost.

  4. In the Database field assign a name for your project repository and click the Create button. In this example we are using DevProjectRepository.

  5. Click OK.

Download Project from the Cube Store

  1. Click the Jet logo and select CubeStore.

    Select the project you would like to use and click download.

  2. If the download button is grayed out click the Request Trial Button.

  3. Once downloaded the Connection Manager dialog will open, Click Yes.

  4. Click the Run Wizard button.

Creating the Staging Database (Development)

  1. In the Server name field enter the name of the server where you would like to create the staging database. In this example we will be using localhost.

  2. In the Database field assign a name for the staging database. In this example we choose DevNavStage.

  3. Click the Create button to create the database.

  4. Click OK.

Connecting the Data source

  1. In the Server Name field enter the name of the server that contains the data source database.

  2. In the Database field select the drop down and select the data source you wish to connect.

Create the Data Warehouse (Development)

  1. In the Server name field enter the name of the server.

  2. In the Database field enter the name of the data warehouse. In this example we choose the Name DevNavDwh.

  3. Click the Create button.

  4. Click OK.

Create the OLAP Server (Development)

  1. In the Server name field enter the name of the server where analysis services is located.

  2. In the Database field enter the name of the OLAP server. In this example we choose DevJetNavOLAP.

  3. Click OK.

Synchronizing Table Definitions

  1. Click the blue arrows.

  2. Click the Yes button.

  3. Accept the default values and click OK.

  4. Click Yes.

  5. Select the Company(s) you would like to report from and select the matching template. Click OK.

    If selecting more than one company select the template of the main company

  6. The Jet Data Manger will begin synchronizing the table definitions. Once completed the updated tables and fields will be displayed. Click OK.

  7. Close the connection manager dialog.

  8. On the Project tab click Manual Deployment and Execution.

  9. Click Start.

Exporting the Project from the Development Environment

Once changes have been made to the development environment we will need to transfer these changes to the production environment.

If the development and production environments are on different servers you must ensure that the activation code used to activate the Jet Data Manager on the development server is the same as the activation code used on the Jet Data Manager on the production server.

  1. click the Jet logo, click Import/Export and select Export Quick Cube Project

  2. Assign a name to the project and save the file as an XML document.

  3. Save the project if you haven't done so already and close the Jet Data Manager. Import the Project to the Production Environment

Import the Project and Create the Production Environment

  1. Open the Jet Data Manager.

  2. Navigate to ToolsGeneral Settings....

    The Project Repository Dialog window opens.

  3. In the Server Name field enter the name of the server. In this example we are using localhost.

  4. In the Database field assign a name for your project repository and click the Create button. In this example we are using ProdProjectRepository.

  5. Click OK

  6. Click the Jet logo and navigate to Import/Export and click Import Project...

  7. Select the XML file you exported in the prior section.

  8. Click OK.

    A success dialog will appear.

  9. Click Yes.

  10. Click Run Wizard.

Create the Staging Database (Production)

  1. In the Server name field enter the name of the server where you would like to create the staging database. In this example we will be using localhost.

  2. In the Database field assign a name for the staging database. In this example we choose ProdNavStage.

  3. Click the Create button to create the database.

  4. Click OK.

Connecting the Data Source

  1. In the Server Name field enter the name of the server that contains the data source database.

  2. In the Database field select the drop down and select the data source you wish to connect.

Create the Data Warehouse (Production)

  1. In the Server name field enter the name of the server.

  2. In the Database field enter the name of the data warehouse. In this example we choose the Name ProdNavDwh.

  3. Click the Create button.

  4. Click OK.

Create the OLAP Server (Production)

  1. In the Server name field enter the name of the server where analysis services is located.

  2. In the Database field enter the name of the OLAP server. In this example we choose ProdNavOLAP

  3. Click OK.

    Close the connection manager dialog.

  4. On the Project tab click Manual Deployment and Execution

  5. Click Start.

    To prevent the PROD and DEV environments from overwriting the SSIS packages, you must:

    • Use SSIS folders and either
    • Rename the project in PROD after copying the project over from DEV or
    • Rename the custom SSIS folder

    In this example:

    SSIS.png

    you must select Use SSIS folder and rename either Name (1) or Custom SSIS root folder (2).

Was this article helpful?

We're sorry to hear that.