Software prerequisites
Omada Identity supports the following browsers:
- Microsoft Edge
- Chrome (version 69 is the earliest one supported, but it's recommended that you regularly update to the newest one)
For users that are only going to use the end-user features (including dashboards, process launch page, work item list, work item dialog, data object list, and data object dialog), the following browser is also supported:
- Safari for iPad
Enterprise Server is a web-based solution that relies on:
- JavaScript
- Cookies
Since the Enterprise Server uses these features, it's a general requirement that you don't disable these common web features for the end-users who need to access the application.
Test that your specific browser settings are working before you begin any large-scale deployments.
Server software requirements
The following tables provide an overview of the software components needed for the different modules in Omada Identity. For details for each module, see the following sections.
| Type | Software Component | ES | ODW | RoPE | OPS |
|---|---|---|---|---|---|
| Operating System | One of the following:
| ✅ | ✅ | ✅ | ✅ |
| Database Engine | SQL Server 2016 Enterprise or Standard Required patch level:
| ✅ | ✅
| ✅ | ✅ |
| Database engine | SQL Server 2022 Enterprise or Standard Required patch level:
| ✅ | Not supported | ✅ | ✅ |
| .NET Runtime | .Net Framework 4.8 | ✅ | ✅ (For SSIS and SSRS server) | ✅ | ✅ |
| .NET Runtime | .Net Framework 3.5 | ✅ |
The SQL Server 2016 Enterprise or Standard is a minimal requirement for the Database engine if you are planning to use SSAS Tabular model. Please refer to the 1 0.1 SSAS Tabular model section.
To avoid any potential import failures, check the Microsoft's recommendations for the SQL Server MAXDOP setting configuration.
The installation of Omada Identity using Omada Identity Installation Tool on SQL Server 2022 is currently not supported.
Installation time requirements
During the installation of the Omada Identity components, the SQL Server Native Client (version 11) is required to perform installation actions towards the database server. The driver is installed automatically by the OPS, RoPE, or ODW installers if not present on the server. The Enterprise Server installer does not install this driver.
To remove the SQL Native client 2012 dependency, follow the steps described in the Omada Identity post-installation activities section.
As part of the installation of the SQL Server Native Client, the SQL Server database and integration (SSIS) services may need to be restarted.
If you use Omada Identity Installation Tool for installation that is in a non-interactive mode, you must install the SQL Server Native Client manually before running Omada Identity Installation Tool.
Omada Identity Enterprise Server
Here are information about:
- The software that you must install before you install Enterprise Server and the order in which this must take place.
- The detailed software requirements for the web/application tier and the database tier.
You must apply the latest Microsoft service packs for your environment. You can find information about the latest service packs at http://www.microsoft.com.
The following table provides an overview of the software you must install on one-tier or two-tier solutions and the order in which to install the products. There are some steps that you should take care of before you install Omada Identity Enterprise Server. These are marked in bold writing in the table below.
| Step | Database Tier | Application / Web Tier | One Tier |
|---|---|---|---|
| 1. Install Windows Server | ✅ | ✅ | ✅ |
| 2. Install SQL Server | ✅ | ✅ | |
| 3. Install Internet Information Services (IIS) | ✅ | ✅ | |
| 4. Install Microsoft .NET Framework 4.8 | ✅ | ✅ | |
| 5. Create a database in SQL Server | ✅ | ✅ | |
| 6. Install Enterprise Server | ✅ | ✅ | |
| 7. Run Configuration Utility | ✅ | ✅ | |
| 8. Set up the Omada Identity Portal Website | ✅ | ✅ | |
| 9. Install and configure Role and Policy Engine | ✅ | ✅ | |
| 10. Install Microsoft Report Viewer 2012 Runtime 1 | ✅ | ✅ | |
| 11. Install feature packages | ✅ | ✅ |
You can use the Report Viewer 2015 instead of 2012 version. To do so, follow the steps described in the Omada Identity post-installation activities section.
Application/Web tier
Install the following roles and features on the web/application level:
Application Server
- .NET Framework 4.8
- Web Server (IIS) Support
IIS (Web Server)
- Web Server
- Management Tools:
- IIS Management ConsoleIIS Management Scripts and Tools
- Features
- .NET Framework 4.8 Features
Database tier
Install the Database Engine Microsoft SQL Server feature in the database tier.
For guidelines on how to set up the Database Engine, go to Install SQL Server Database Engine.
Omada Identity Role and Policy Engine (RoPE)
Omada Identity Role and Policy Engine runs as a Windows service. Before you install the Role and Policy Engine, you must install and configure the following software packages:
- Omada Identity Enterprise Server
- Omada Identity Data Warehouse
You can install the Role and Policy Engine in a single-server environment or in a distributed environment. The installation consists of two main features:
- Role and Policy Engine Service
- Role and Policy Engine Management Agent
Both features have their own installer, and you can either install each of these features on different servers or on the same server. These features are described in more detail in the Omada Identity Role and Policy Engine.
Data Warehouse
You can install Omada Identity Data Warehouse in a single-server environment or in a distributed environment.
Databases
There are three Omada Identity Data Warehouse databases:
- Omada Identity Data Warehouse
- Omada Identity Data Warehouse Staging
- Omada Identity Data Warehouse Master
Before you install the databases, you must install and configure the Database Engine Microsoft SQL Server features on the database server.
SSIS Packages
Before you install the SSIS packages, you must install and configure the following SQL Server features on the SSIS Server:
- Database Engine (mandatory unless you want to deploy SSIS packages to a different SQL Server instance)
- Integration Services
- SQL Server Data Tools (in a development environment)
If you use an SQL edition and choose Standard Edition, you cannot use the fuzzy matching feature in Data Warehouse. This means that you can only use exact and custom match for joining accounts to identities.
To ensure acceptable report performance, Omada recommends that you use SQL Server Edition which supports column store indexes for the databases if you have more than 5000 identities or more than half a million of resource assignment rows.
For more information on the configuration of SSIS packages, see Customer Settings.
Please bear in mind that Omada recommends installing and running DTEXEC utility in the 64-bit version. Using DTEXEC utility in the 32-bit version may result in ODW memory issues.
SSRS Reports
Before you install this feature, you must install and configure the Reporting Services SQL Server feature on the reporting server.
See the SQL Server Reporting Services documentation available on Microsoft MSDN for information about supported browsers for the SQL Server that you are running.
SAP connectivity
For SAP integration with Omada Identity, use of the Omada SAP Connectivity Framework for SAP Solutions is required.
For more information, go to SAP connectivity guides.
Exchange connectivity
To import from Microsoft Exchange, the SQL Server Integration Services (SSIS) server must run PowerShell version 3.0 or higher.
SSAS Tabular model
If you are planning to use the analytics feature of Omada Identity, the SQL Server version 2016 (or later) is required. You also must install and configure the Analysis Services in Tabular model as a SQL Server feature.
For more information, go to the Advanced analytics.