Skip to main content
Version: Omada Identity on-premises 16.0.1

Omada Identity Data Warehouse

The user installing Omada Identity Data Warehouse (ODW) must have the following rights and database roles.

In Local Group settings, the user must belong to a group allowed to install software on the system. This is usually Local Administrators.

SSIS development environment software prerequisites​

Microsoft SQL Server 2022​

To perform custom Data Warehouse development with Microsoft SQL Server 2022, install:

  • SQL Server Data Tools for Visual Studio 2022

Microsoft SQL Server 2019​

To perform custom Data Warehouse development with Microsoft SQL Server 2019, install:

  • SQL Server Data Tools for Visual Studio 2017 or 2019

Microsoft SQL Server 2017​

To perform custom Data Warehouse development with Microsoft SQL Server 2017, install:

  • SQL Server Data Tools for Visual Studio 2015 or later

Run the installer​

Run the installer as an administrator. Double-click the relevant .exe file to launch the ODW installation wizard:

  • Omada Data Warehouse.x64 SQL 2022.exe
  • Omada Data Warehouse.x64 SQL 2019.exe
  • Omada Data Warehouse.x64 SQL 2017.exe

Click Next to continue.

note

The installer path is not saved in a configuration file. It resets when the installer starts.

  1. Enter the license key in the License Key field.

    note

    The license key entered during installation is stored in the ODW database. To update the license after installation, see Update the ODW license.

  2. Enter the name of the database server where you are installing the databases, then select an authentication method.

    note

    For a default instance, enter only the server name. For a named instance, enter the server name and instance name.

    Database Server page of the installation wizard with the database server field and the Windows and server authentication options
  3. Specify names for the ODW, ODW Staging, and ODW Master databases. You can also use the default names shown.

    Database Names page with the default names Omada Data Warehouse, Omada Data Warehouse Staging, and Omada Data Warehouse Master
  4. The Omada SSIS packages are stored in the msdb database on a SQL Server. On the Integration Services Server screen, specify the server and instance that contain the msdb database where you want to store the packages.

  5. If the msdb database is on the default instance, enter only the server name.

  6. If the msdb database is on a named instance, enter the server name and instance name. You might need to edit the SSIS Server configuration file if msdb is on a named instance. See Edit the SSIS Service Configuration File.

    Integration Services Server page with the Instance name field and the example SSISServer\InstanceName
  7. Click Next to install ODW in the default folder: C:\Program Files\Omada Identity Suite\Datawarehouse. To choose a different folder, click Change....

  8. On the Custom Setup page, select the program features to install and specify their installation locations. For example, you can install all features on the same server or distribute them across multiple servers.

Source Systems​

The Source Systems feature:

  • Installs the Omada Identity Data Warehouse databases.
  • Deploys SSIS packages for the selected connectors and points them to the configuration files.
  • Installs Omada .NET assemblies in the Global Assembly Cache (GAC).
note

SQL Server Integration Services is not a clustered or cluster-aware service. For this reason, Omada recommends that you do not install SQL Server Integration Services in a cluster.

For more information, see Integration Services (SSIS) in a Cluster.

In the recommended scenario, the databases and SSIS packages run on separate servers. In this case, run the installer for Source Systems on the SSIS server.

Reports​

The Reports feature:

  • Adds a license key to the ODW database.
  • Deploys SQL Server Reporting Services (SSRS) reports to the Support Files folder and updates their connection strings.
  • Deploys the Omada Localization assembly and files.
note

If SSRS is on a non-default instance, follow the steps in Install on a non-default SSRS instance.

If you cannot run the installer on the server running SQL Server Reporting Services, follow the steps in Manually deploy the Omada localization assembly.

Configuration Files​

The Configuration Files (Config Files) feature deploys the SSIS configuration files and updates connection strings. This feature has no software requirements.

To install the Configuration Files feature on a different server from the one where SQL Server Integration Services (SSIS) is installed, run the Omada Identity Data Warehouse installer on both servers.

After installing the Configuration Files feature, locate the Datawarehouse folder. The default location is C:\Program Files\Omada Identity Suite\Datawarehouse. The folder contains the Common, Localization, Source Systems, Support Files, and Templates subfolders. Share the Datawarehouse folder.

On the server where SSIS is installed, clear the Configuration Files feature on the Custom Setup page. When you click Next, the Universal Naming Convention (UNC) Path for Config Files page appears. Enter the Universal Naming Convention (UNC) path to the shared Datawarehouse folder, for example, \\<configfile-server>\Datawarehouse.

UNC Path for Config Files page of the installation wizard with the UNC Path field

Install the Reports feature on the SQL Server Reporting Services (SSRS) server from which you run the reports. If this server differs from the SSIS server, run the ODW installer on both servers.

note

If multiple SSRS instances are installed on the target machine, the ODW installer uses the default instance to apply the necessary file changes.

  1. On the Custom Setup page, select the Connectors to install. Select the Source Systems from which you want to import data. You can use only connectors for which you have a valid license. Click Next.
  2. After entering all the required information, click Install to start installing the Omada Identity Data Warehouse software.
  3. When the installation is complete, click Finish.
  4. If you used the default installation path, the Datawarehouse folder is under C:\Program Files\Omada Identity Suite.
tip

Omada recommends backing up the databases before importing data. This makes it easier to clean the databases if needed.

Edit the SSIS Service Configuration File​

If the msdb database is on a named instance, you might need to edit the SSIS Service configuration file.

For more information, see Integration Services Service (SSIS Service).

Install on a non-default SSRS instance​

The following steps explain how to install ODW on a non-default SSRS instance and how to manually deploy reports to a different server from the one where you run the installer.

  1. To support SSRS on a non-default instance, run:

    Omada Data Warehouse.x64 SQL 2022.exe /A

    note

    Use the installer version that matches your SQL Server version. For SQL Server 2017 or 2019, run the corresponding 2017 or 2019 installer.

    Specify the folder where you want to place the files. This starts an administrative installation.

  2. In the registry, find the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReportServer, where ReportServer is the name of the instance. The ImagePath property contains the path you need for the next step.

    Registry Editor with the ReportServer service key selected and its ImagePath value pointing to ReportingServicesService.exe
  3. Copy Omada.ODW.SSRS.Utils.dll to the ReportServer folder.

  4. Find the rssrvpolicy.config file in the parent folder of the bin folder identified in the previous step. Add the following CodeGroup before the section containing the two </CodeGroup> tags:

    <CodeGroup Description="" Name="Omada.ODW.SSRS.Utils" PermissionSetName="FullTrust" class="UnionCodeGroup" version="1">
    <IMembershipCondition PublicKeyBlob=
    "00240000048000009400000006020000002400005253413100040000010001002985C8DE09BDAD0E8706B11719FB09F4C5AD2A74F17984E09408CA709278FF497A9CD1C279DBB4B2C847B8AF0AEA943E37BFE17573BD1D80D843562B5AECBC7F6E2B81F69D5E5FE1BBCA88F53A10EA28114E68A23459900515A6561A1661CFCCD4C2E9C5F159397021883B785042FC5D3C78432F97272F9961AF191089EFD59F"
    class="StrongNameMembershipCondition" version="1">
    </IMembershipCondition>
    </CodeGroup>

Manually deploy Omada localization assembly​

The Omada Identity Data Warehouse installer deploys the report localization files and assembly. If you cannot run the installer on the server running SQL Server Reporting Services, follow these steps to deploy the files:

  1. Copy Omada.ODW.SSRS.Utils.dll from C:\Program Files\Omada Identity Suite\Datawarehouse\Support Files on the computer where you installed the Reports feature.

  2. Place Omada.ODW.SSRS.Utils.dll in the ReportServer\bin folder on the SSRS server. For SQL Server Reporting Services 2017 or later, the default path is C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\. If SSRS is installed in a different location, find the path in the ImagePath registry value, as described in Install on a non-default SSRS instance.

  3. Edit the rssrvpolicy.config file in the ReportServer folder. Insert the following XML just before the group of two </CodeGroup> tags:

    <CodeGroup Description="" Name="Omada.ODW.SSRS.Utils" PermissionSetName="FullTrust" class="UnionCodeGroup" version="1">
    <IMembershipCondition PublicKeyBlob=
    "00240000048000009400000006020000002400005253413100040000010001002985C8DE09BDAD0E8706B11719FB09F4C5AD2A74F17984E09408CA709278FF497A9CD1C279DBB4B2C847B8AF0AEA943E37BFE17573BD1D80D843562B5AECBC7F6E2B81F69D5E5FE1BBCA88F53A10EA28114E68A23459900515A6561A1661CFCCD4C2E9C5F159397021883B785042FC5D3C78432F97272F9961AF191089EFD59F"
    class="StrongNameMembershipCondition" version="1">
    </IMembershipCondition>
    </CodeGroup>
  4. Copy the Localization folder, or its contents, from C:\Program Files\Omada Identity Suite\Datawarehouse\ on the computer where you installed the Reports feature. Place it in the main folder for the SSRS server.

  5. In Registry Editor, add the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Omada\Omada Identity Suite\Omada Data Warehouse.

  6. Add a multi-string value named SSRS Localization Path. In Value, enter the path to the folder. You can now upload the Omada Identity Data Warehouse reports to the server.

Add a password encryption key​

Omada requires you to set a secret password encryption key instead of using the default key. Do this before entering any credentials that will be encrypted with this key.

To set the key, add a string value named PswEncryptionKey to the Windows registry path HKEY_LOCAL_MACHINE\SOFTWARE\Omada\Omada Identity Suite on every server that runs ODW. For more information, see Password encryption key.

Add a new record to dbo.tblApplicationSetting​

Before running the Configuration Package (Omada ODW Configuration.dtsx), add a record to the dbo.tblApplicationSetting table. This record specifies the path where Omada Data Warehouse (ODW) is installed.

note

If you do not create this record, the system uses the default path: C:\Program Files\Omada Identity Suite\Datawarehouse\.

Run the following script to add a record to the table:

INSERT INTO [dbo].[tblApplicationSetting]
([ID], [Key], [Description], [ValueStr], [Type])
VALUES
(
(SELECT MAX([Id]) + 1 FROM [dbo].[tblApplicationSetting]),
'installationFolder',
'The Folder where the ODW is installed',
'{PathToTheFolder}',
0
)

Update the ODW license​

The ODW license is stored separately from the Enterprise Server (ES) license and is not updated automatically. When you update the ES license, update the ODW license separately.

To update the ODW license, use SQL Server Management Studio to update the ValueStr column in the dbo.tblApplicationSetting table in the ODW database.

Run the following statement, replacing {ODW license key} with the new license key:

UPDATE [dbo].[tblApplicationSetting]
SET [ValueStr] = N'{ODW license key}'
WHERE [Key] = 'licenseString';

Troubleshooting​

Installer does not detect old version of OPS/ODW and will not upgrade​

Before Omada Identity 12.3, previous versions of Omada Provisioning Service (OPS) and Omada Identity Data Warehouse were installed per user. When upgrading from an earlier version to 12.3, use the same user who performed the original installation.

If you use a different user, OPS and ODW will not appear in the list of installed programs in Windows Control Panel under Programs and Features.

note

Upgrading to version 12.3 does not resolve this issue. The installer cannot convert a per-user installation to a per-machine installation.

From Omada Identity version 14 onward, OPS and ODW must be installed per machine. Therefore, remove OPS and ODW from the machine, then install them again without upgrading.