Cost Mitigation for Identity Manager Implementation

Identity Manager typically requires 5 – 20 GB of schema space, depending on the size of engagement and level of auditing; existing DB infrastructures may be utilized to eliminate the purchase cost and additional maintenance of dedicated server hardware. Note, when fully leveraging compliance reporting, database footprint may vary dramatically based on number of audited resources, numbers of accounts, size of entitlements, and how long audit data is persisted in the database. Ensure that allocated schema has room to grow to upwards of 100 GB.

Pre-existing software / hardware load balancers may be used to provide availability, load balancing, failover, and SSL-acceleration, as determined by expected traffic. Load balancers should be configured for sticky sessions.

Ideally the test environment should exactly mirror the production environment to best facilitate testing, performance tuning, and issue resolution. To reduce costs this environment may be scaled down; however, it is recommended that number of instances remain sufficient for testing load balancing / failover and to reproduce / debug possible contention issues.

Given the high cost of database infrastructure and per-CPU licensing for enterprise applications, most customers allocate space on existing databases for Identity Manager. Note that Identity Manager is may be chatty in certain configurations, so sufficient space must be available for redo logs.