Upgrade Ouvvi 2.0 to Ouvvi 2.5
The upgrade from Ouvvi 2.0 to 2.5 is quite simple but there are a number of Steps to follow which you can find here
The upgrade from Ouvvi 2.0 to 2.5 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
The first step is to uninstall Ouvvi from your system, it is important that you do not have multiple Ouvvi instances running targeting the same database as this will cause you many problems.
You should also obtain a Backup of your Ouvvi Database as you will likely need to update the Schema and it's good practice to have a backup before you continue.
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.
Next 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.
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.
Under the Authentication Settings for the site you must disable the Anonymous option and enable Windows Authentication.
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.
Now move the Ouvvi.config file that contains the Database connection details from the Global/Old Ouvvi location into the root of your Ouvvi Tenant.
Move the file from
C:\ProgramData\Simego\Ouvvi\Ouvvi.config into the Root Tenant Folder i.e.
You can now browse to the Ouvvi Site where you will need to go through the schema update wizard.
On completion of the Schema Upgrade takes you to the Ouvvi Homepage if successful.
Next you will need to configure some of the Ouvvi paths to point to the directories under the tenant Path. Go to Settings->System Settings and update Log Folder, Path to Data Sync, Data Sync Snapshot, Data Sync Connection Library.
Since the Connection Library is now private to the tenant you will also want to move/copy the Connection files from the Global location C:\ProgramData\Simego\DataSyncStudio30\Registry into your Tenant Connection Folder i.e. “D:\Tenants\DEV\Connections”. You only need to move or copy the connections that you know your Ouvvi projects use.
Now 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).
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.
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.