Omada Identity Installation
Install Omada Identity on-premises by first planning your deployment, preparing the required software, and then following the instructions for the components you need. Use this page as your starting point. The detailed requirements and procedures are in the linked guides.
Omada Identity is highly customizable and scalable, so the guidance in this documentation may not suit every environment. Plan the technical design with Omada consultants and adapt it to your system landscape and requirements.
Follow the installation path
- Plan your environment. Choose a deployment topology and review the infrastructure, sizing, storage, and resilience guidance in Plan your installation.
- Check prerequisites. Review Software prerequisites, including the requirements for the components and optional features you intend to use.
- Choose an installation approach. Use the Omada Identity Installation Tool to create a reusable configuration and install some or all components, use the Ansible package to automate deployment, or follow the manual component instructions below.
- Install and configure the components. Follow the component guides in the order that applies to your architecture. Check each guide for its prerequisites and required permissions.
- Complete the installation. Install the application packages and changesets required for your solution. If you install a version earlier than Omada Identity 15.0.2, also review the post-installation activities.
Your architecture determines which components and optional features to install. Use the planning guidance and component prerequisites to identify what applies to your environment.
Install the components
| Component or task | Use this guide |
|---|---|
| Enterprise Server (ES) | 👉 Install Enterprise Server |
| Omada Identity Data Warehouse (ODW) | 👉 Install and configure Data Warehouse |
| Role and Policy Engine (RoPE) | 👉 Install and configure RoPE |
| Omada Provisioning Service (OPS) | 👉 Install and configure OPS |
| Azure Structured Query Language (SQL) | 👉 Install with Azure SQL databases |
| Feature packages and changesets | 👉 Install application packages and import changesets |
How the components fit together
Omada Identity has two main application components:
- Enterprise Server (ES) provides the web application and works with its SQL Server database. Depending on your design, the application and database tiers can run on separate servers or on the same server.
- Omada Identity Data Warehouse (ODW) provides databases, SQL Server Reporting Services (SSRS) reports, and SQL Server Integration Services (SSIS) packages. Advanced Analytics Service/Tabular model is optional.
The ES also uses Windows services, including the Role and Policy Engine (RoPE), Timer Service, and Omada Provisioning Service (OPS). For an architecture overview and deployment examples, see Plan your installation.
Installation tools
Omada Identity provides two installation tools, as well as the option to install components manually:
- The Omada Identity Installation Tool creates a reusable configuration file for installing some or all components.
- The Omada Identity Ansible package automates the installation of the on-premises version. It is currently in Technical Preview.
👉 See Installation tools for an overview.