Fully Integrated, Easy to Use
Without an integrated reporting tool, businesses face several hurdles. Not only must they install, build and maintain infrastructure for these standalone systems, but the majority of reports must be manually created and customized. Tightly integrated into the ForgeRock platform, Hub City Media’s Reporting tool (HCM IDR™) eliminates requirements for reporting system integration and provides intuitive functionality for ForgeRock users!
Meet Compliance and Understand System Health
With Hub City Media's Reporting tool (HCM IDR™), you can quickly and efficiently meet compliance and get a comprehensive understanding of your systems. It includes a wide variety of reporting options, spanning Systems Access, Certification, Policy Violations and much more. While it was built with many commonly required out-of-the-box reports, creating new reports is simple and intuitive.
View and Export in Simple Formats
The below information contatins prerequisites for installing and running Reporting for ForgeRock (HCM IDR™):
ForgeRock IDM: HCM IDR™ version 1.0 is designed to work with ForgeRock IDM version 4.0, 4.5, 5.0, 5.5 and 6.0.
Repositories: HCM IDR™ is supported on the following databases: MySQL version 5.5, 5.6 and 5.7 with MySQL JDBC Driver Connector / J 5.1.18 or later, Microsoft SQL Server 2012 and 2014, Oracle Database 11gR2 and 12, PostgreSQL 9.3 and 9.4, IBM DB2 10.x, Microsoft SQL 2016
HCM IDR™ does not support IDM’s packaged evaluation database, OrientDB.
Operating Systems: HCM IDR™ is supported on the following operating systems: Red Hat Enterprise Linux 6.x/7.x, Ubuntu 14.04, Windows Server 2008 R2, Windows Server 2012 R2
Browsers: HCM IDR™ is supported on the following browsers: Chrome (latest stable release), Firefox (latest stable release), Safari (latest stable release), Internet Explorer (9 and later)
Java Environment: HCM IDR™ requires Java Runtime Environment 7 or 8. Hub City Media recommends the use of Oracle Standard Edition HotSpot or OpenJDK.
System Requirements: HCM IDR™ requires at least 400MB disk space and 2GB memory for non-production implementations. Production sizing will depend on number of users and report size requirements.