Sign Up for Training |
Jet Express Support |
Jet Reports Company Site
Jet 365 Financials
Jet Professional
Jet Enterprise
Downloads
Community
Submit a Request
Feedback

Manually Move a Project from a Development Environment to a Production Environment


 

Overview

This document describes how to copy a project from the development server to the product server manually. To make the process as easy as possible, it is recommended that the names and locations of the different databases as well as any SQL Server logins are duplicated in both environments.

There are two ways of achieving this goal. The first method is to export the project to an XML file on the development server and import this XML on the production server. The second option is to back up the development repository and restore it on the production server.

Process

  1. Export the project to XML



    If possible select a location that is easy to reach from the production server


  2. Open Jet Data Manager on the production server and import the XML file



    Select the file you exported under Step 1



    If a project with the same name already exists in the repository you will be asked to save it as the latest version of the project.


  3. Run the connection manager to ensure all connections are working

    You can skip this if you know the database names and any SQL Server logins are identical on both servers.
    After a successful import you will be asked if you want to run the connection manager.



    Click Yes and then click Run Wizard to start the connection manager wizard



    A total of 4 dialogs will appear and you can modify the settings for each connection to correspond with your production settings



    After you have modified the connections you can verify the settings by testing the connections. The connection state for all connections should turn green if the connections are working correctly.



    Close the connection manager.
  4. Execution Packages
    You may need to add or enable the execution packages in your Production environment that were disabled (or nonexistent) in your Development environment. Please refer to the following link for instruction for Setting up Execution Packages .
  5. Deploy and execute the project
    After the import you need to deploy and execute the project by clicking Manual Development and Execution or CTRL-ALT-M



    Click Start to deploy and execute the project.

You have now successfully copied the development project to your production server.


Backup and Restore Method

Step-by-step guide

  1. In SQL Server Management Studio create a backup of the development repository
  2. Restore the backup of the repository on the production server with the same name as the productive repository
    This will overwrite the existing production repository meaning any projects in production that are not in the development repository will be permanently lost. If the repositories are not identical please use the Export/Import method described above.
  3. Open the project in Jet Data Manager on the production server
  4. Run the connection manager and follow the steps as described in step 3 for the Export/Import method above.



  5. Execution packages
    If your Development project does not have execution packages set up or they are disabled, add/enable them as appropriate in your Production environment. Please refer to the following link for instruction for Setting up Execution Packages .

  6. Deploy and execute the project
    After the import deploy and execute the project by clicking Manual Development and Execution or CTRL-ALT-M



    Click Start to deploy and execute the project.

You have now successfully copied the development project to your production server.
 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments