How To

Install Ouvvi V2.5

Note: This is historical documentation and we recommend using the latest Ouvvi Version.

As of Ouvvi release 2.5 the installation is now manual in order to provide a multi-tenant flexible installation process.

You can now deploy multiple Ouvvi instances on a single server, each instance has it's own Database, Web App, Windows Service, Connection Library and version of Data Sync.

The installation is quite simple but there are a number of Steps to follow.


  • Windows Server 2012 or higher.
  • .NET 4.6.1 full version.
  • IIS Role with ASP.Net support, Windows Authentication.
  • SQL Server 2012 or higher, Express, Web, Standard or Enterprise.
  • ASP .NET MVC 4.0 Runtime.

Install Data Synchronisation Studio as normal selecting either 64 bit (recommended) or 32 bit as required for your system. Then activate Data Sync with your Server Edition License Key.

The first step is to copy the 'Ouvvi' folder from the Data Sync installation directory into a Folder that will hold your Tenants. This is a Snapshot if you like of the Version you are installing, later if you upgrade the version of Data Sync it will not affect your Ouvvi and Ouvvi Data Sync version unless you update the Tenant version.

Copy the Folder C:\Program Files\Simego\Data Synchronisation Studio 3.0\Ouvvi to the location to create the Tenant i.e.D:\Tenants\DEV

Ouvvi Folder

Tennants Location

You will now see that you have folders for the main parts of Ouvvi for this Tenant. Next we need to configure the IIS Site to point to the Web Folder and set the Domain Account on the AppPool.

Add a Site to IIS, set the Name and Point the Physical Path to location of the Web folder under your Tenant Folder i.e. D:\Tenants\DEV\Web, you will likely need to assign a Port for this instance unless you are using hostnames with your DNS server.

Add the Site

Under the Authentication Settings for the site you must disable the Anonymous option and enable Windows Authentication.

Authentication Settings

Next configure the Windows Account on the App Pool, locate the AppPool for this site, under Advanced Settings change the Identity to a Domain Service/Account that you want to use to run the Site.

Configure Windows Account

You can now browse to the Ouvvi Site to start the configuration of the Ouvvi Database.

Ouvvi Setup

You will need to configure sections 1,2 and 4.

  1. Enter the network credentials to create the SQL DB and this account will be the initial Ouvvi Administrator. Typically this account will also be the account of the AppPool but can be different.
  2. Enter the SQL Server name and a Name for the Database (Each Tenant must have a unique Database Name), we recommend you use Integrated Security with the Ouvvi DB so uncheck the SQL Authentication Mode and skip section 3.
  3. These are the paths to the folders within the Tenant, they should default to the correct path so you do not need change them, you can update them later in the UI.

Enter Details

Clicking Setup then takes you to the Ouvvi Homepage if successful where you can complete the install by setting up the Ouvvi Windows Service.

Locate the program Simego.Console.Service.exe under the Tenant Service folder and run this with Elevated Administrator permission, this is required to install the program in the Windows Service Control Manager.


Then under the File menu choose the Install Windows Service Option. (Note you also use this if you want to uninstall later).

Install Windows Service

Now give your service a name, click OK when complete you should close this program.


Now if you open the Windows Service Control Manager (services.msc) you will see 'Ouvvi Processing Service' with the Tenant Name in brackets. You now need to configure the Service to use a Network Domain Service account and set it to Start up Automatically.

Windows Services

After you start the service if you go back to Ouvvi and view the services under Services->System Services you should see all Green flags indicating that the service has started and is running. Note: You can provide a name for this Instance in the Title bar by updating the setting under system settings.


That's it, now you can repeat the process to create instance for UAT and PROD. You can deploy multiple instances* on your server however each one will be using resources so there will be a limit to the number of tenants you can feasibly run on a single server.