Skip to main content

Server Requirements

Multiple, Load-Balanced Servers

Hitachi ID Identity Manager supports multiple, load-balanced servers.

Each server can host multiple Identity Manager instances, each with its own users, target systems, features and policies.

Identity Manager instances can and normally do span multiple servers. Every server hosting a given instance is functionally identical. User traffic is load balanced between servers supporting the instance. Load balancing may be accomplished using DNS (round-robin is built into most DNS servers) or at the IP level with a device from Cisco, F5, etc.

High availability is accomplished by combining load balancing with server health monitoring and automatic fail-out. Identity Manager includes server monitoring tools that can be configured on each server to monitor its peers and when a failure is detected to trigger an alarm (e.g., by e-mail) and to automatically update DDNS records to remove the failed server from circulation. Hitachi ID Systems also provides these tools for Unix/BIND with traditional DNS.

There is no coded limit to the number of concurrent, replicated servers. In practice, with more than 10 servers, replication may become slow. Since the three largest customers of Hitachi ID Systems run with just two production servers each, this is only a theoretical problem.

Server Platform

Identity Manager must be installed on a Windows 2012 or Windows 2012/R2 server.

Installing on a Windows server allows Identity Manager to leverage client software for most types of target systems, which is available only on the "Wintel" platform. In turn, this makes it possible for Identity Manager to manage passwords and accounts on target systems without installing a server-side agent.

The Identity Manager server must also be configured with a web server. Since the Identity Manager application is implemented as CGI executables, any web server will work. The Identity Manager installation program can detect and automatically configure IIS but Apache can be manually configured instead if required.

Identity Manager is a security application and should be locked down accordingly. Please refer to the Hitachi ID Systems document about hardening Identity Manager servers to learn how to do this. In short, most of the native Windows services can and should be removed, leaving a very small attack surface, with exactly one inbound TCP/IP port (443):

  1. No ASP, JSP or PHP are used, so such engines should be disabled.
  2. .NET is not required on the web portal and in most cases can be disabled on IIS.
  3. No ODBC or DCOM are required inbound, so these services should be filtered or disabled.
  4. File sharing (inbound, outbound) should be disabled.
  5. Remote registry services should be disabled.
  6. Inbound TCP/IP connections should be firewalled, allowing only port 443 and possibly remote desktop services (often required for some configuration tasks), plus a handful of port numbers between Identity Manager servers, for replication.

Each Identity Manager server requires a database instance. Microsoft SQL 2012 is the most common option, Microsoft SQL 2014 will be officially supported in Q1, 2016. Oracle database is also supported in the current release.

** Please note that support for using an Oracle database is being discontinued as of version 10.0 which is scheduled for release in Q1, 2016.

Application Server Hardware and Operating System

Production Identity Manager application servers are normally configured as follows:

  • Hardware requirements or equivalent VM capacity:
    • An Intel Xeon or similar CPU. Multi-core CPUs are supported and leveraged.
    • At least 8GB RAM -- 16GB or more is typical for a server.
    • At least 500GB disk, preferably configured as RAID for reliability and preferably larger for retention of more historical and log data. More disk is always better, to increase log retention.
    • At least one Gigabit Ethernet NIC.

  • Operating system:
    • Windows 2012R2 Server, with current service packs.
    • The server should not normally be a domain controller and in most deployments is not a domain member.

  • Installed and tested software on the server:
    • TCP/IP networking, with a static IP address and DNS name.
    • Web server (usually IIS).
    • Client software: web browser, Acrobat or other PDF reader, native clients for the systems that Identity Manager needs to interface with.
    • SQL Server client or Oracle client to connect to the Identity Manager back-end database.
    • SSL server certificate, for HTTPS connections to the web portal and SOAP API.

  • A database instance is required to host the Identity Manager schema. Most customers use Microsoft SQL Server 2012, but Oracle 11gR2 is also supported up to version 9.0. (support for using Oracle database is being discontinued as of release 10.0 (Q1, 2016)). The SQL Server database software can be deployed on the same server as the Identity Manager application, as this reduces hardware cost and allows application administrators full DBA access for troubleshooting and performance tuning purposes.

Database Configuration

In addition to a web/application server, Identity Manager requires a database server. In most environments, the database server software (Microsoft SQL Server or Oracle Database Server) is installed on the same hardware or VM as the Identity Manager software, on each Identity Manager server node. This reduces hardware cost, eliminates network latency and reduces the security surface of the combined solution.

Database I/O performance on a virtualized filesystem (e.g., VMDK or equivalent) may not be ideal. If a VM is used to host the database server software, please consider a NAS or SAN solution for disk I/O.

Identity Manager can leverage an existing database server cluster. Hitachi ID Systems recommends a dedicated database server instance, however, for a number of reasons:

  1. The data managed by Identity Manager is extremely sensitive, so it is desirable to minimize the number of DBAs who can access it (despite use of encryption).
  2. MSSQL and Oracle have limited ability to isolate workloads between database instances on the same server. This means that a burst of activity from Identity Manager (as happens during nightly auto-discovery) would cause slow responses in other applications. Conversely, other applications experiencing high DB load would slow down Identity Manager.
  3. Identity Manager already includes real-time, fault-tolerant, WAN-friendly, encrypted database replication between application nodes, each with its own back-end database. Use of an expensive DB server cluster is neither required nor beneficial.

The Identity Manager replicating data service can be configured to use any of the following SQL database engines as its physical data store:

  • Microsoft SQL Server 2012, Standard Edition (64-bit)
  • Microsoft SQL Server 2012, Express Edition, with Advanced Services (free download from
  • Oracle 11gR1 or 11gR2, Enterprise Edition.

** Please note that support for using an Oracle database is being discontinued as of version 10.0 which is scheduled for release in Q1, 2016.

Read More:

  • Network architecture:
    Identity Manager network architecture.
  • Replicated, High Performance Database Architecture:
    Identity Manager includes built-in data replication and uses stored procedures to ensure optimized transaction processing.
  • Included Connectors:
    Connectors included in Identity Manager and their capabilities.
  • Auto-Discovery System:
    How the Identity Manager automatically discovers new, deleted and changed users on integrated systems and applications.
  • Reconciling User IDs:
    How Identity Manager maps user IDs on different systems back to their human users, both automatically and with human assistance.
  • Integrations:
    Integrations between Identity Manager and other parts of an IT infrastructure.
  • Custom Business Logic:
    How organizations can implement their own business logic without modifying the core Identity Manager product or impairing system reliability or upgradeability.
  • Dynamic Workflow:
    How Identity Manager invites business users to review and approve changes to user profiles.
  • Reliable Authorization:
    Using parallel invitations, reminders, escalation and delegation to get reliable results from human authorizers.
  • Roles & Rules:
    Using roles and rules to simplify the management of user provisioning policies.
  • Self-service Group Management:
    Using the included Group Manager module to move AD group management to a self-service model.
  • Event Notification:
    Identity Manager can alert people and other systems of changes that it detects on target systems and of events that took place within identity management and access governance business processes.
  • Server Requirements:
    How to configure Identity Manager servers and how many are required.
  • Customizable User Interface:
    How the Identity Manager user interface can be branded, rearranged and adapted to specific customer requirements.
  • Language Support:
    Languages in which Identity Manager can display its user interface.
page top page top