JVM Inventory uses information that is only available at runtime (Java main class) to map Java applications to Oracle JVMs that are actually being used. Migration teams can quickly notify application owners that these instances are being replaced. This can slash weeks or months of effort off the average 6-9 month timeline to migrate off Oracle Java to OpenJDK solutions such as Azul Platform Core.
JVM Inventory retains the ongoing usage history of JVMs to continuously track migration progress to compliance, reducing the burden of running multiple scans with SAM tools and analyzing spreadsheet reports as the sole means of validating Oracle burndown.