The report consolidates deployment information from both servers and clients, maps Java installations to specific versions, and calculates licensing requirements based on Oracle’s published rules. It highlights not only which versions are deployed, but also where devices may fall out of support or require further investigation.
Graphical Overview
The graphical overview provides a high-level summary of your Java landscape, segmented by deployment types, versions, and licensing implications:
-
Deployment Summary:
Devices are grouped by type (e.g., servers, clients), allowing visibility into where Java is installed across your environment. -
Java Version Distribution:
A breakdown of devices by Oracle Java version helps you identify concentrations of legacy, current, or unsupported releases, enabling version standardization strategies. -
Licensing Requirements:
Based on Oracle’s licensing framework, the report calculates potential license exposure using recognized metrics, including Java-specific entitlements. -
Legacy Metric Breakdown:
Java products are mapped to processor and NUP counts using legacy licensing metrics for cost estimation or reconciliation purposes. -
Actionable Insights:
Key risks are flagged—such as devices running out-of-support Java versions or those with missing hardware data—paired with suggested remediation steps to support audit readiness and compliance planning.
Oracle Java Licensing
The Oracle Java Licensing table provides a detailed, device-level breakdown of Java deployments, highlighting which installations are likely licensable under Oracle’s policies. This view supports license validation efforts by identifying potential non-compliant usage and helping you prioritize verification steps.
Key columns include:
- Device and Software Info: Lists the detected device names, software name, and Java version to track where each instance is running.
- Licensable: Indicates whether the deployment requires a license based on Oracle’s entitlement criteria.
- Free for Personal Use: Identifies whether the product qualifies for personal or non-commercial use, which may be exempt from licensing under certain Oracle terms.
- Recommendation: Offers guidance for further validation—for example, verifying whether a deployment is used for non-production purposes. Where applicable, references to the Oracle Technology Network (OTN) License Agreement are noted.
Licenses Required Details
This table provides a breakdown of Java SE license requirements by version, helping you assess licensing obligations at a product level. It calculates the number of processor and NUP (Named User Plus) licenses required based on deployment data.
The table includes the following metrics:
- Product: Identifies the specific Java SE version in use.
- Number of Devices: Reflects how many devices are running each Java version.
- Processor Licenses Required: Estimates the total processor-based licenses required for that version.
- NUP Licenses Required: Calculates the minimum number of NUP licenses needed.
All Java Installations
This section provides a comprehensive inventory of all detected Java installations across the estate, offering a granular view of each instance to support licensing and compliance validation.
Each row represents a unique installation, with attributes such as device name, software name and version, publisher, operating system, and (where available) install and usage dates. The presence of JDKs is flagged, helping differentiate between development tools and runtime environments.
The availability of runtime insights such as Process Path, Command Line, and Process Running depends on the data source ingested. These fields are specifically enriched when Licenseware’s Oracle Java Discovery Module (OJDM) is used for collection. This data enables identification of running Java instances and their invocation paths—crucial for determining licensability under Oracle’s policies. You can read more about this enrichment approach here.
Non-Oracle Java Installations
This section provides visibility into Java distributions deployed in the environment that are not published by Oracle. It includes platforms such as Azul Zulu, IBM Java SDK, SAP Java, Amazon Corretto, and others.
Identifying and understanding these non-Oracle deployments can help accelerate decision-making when considering a support model shift or cost-avoidance strategy related to Oracle Java licensing.
Infrastructure Reconciliation
This section aligns Java software installations with the physical or virtual infrastructure they run on, providing clarity on how processor-based licensing should be calculated.
Each device is listed alongside its structure type (e.g. Uncapped - Incomplete) and grouped accordingly. This view helps determine the number of licensable processors required for Java, ensuring licensing decisions are based on real hardware usage.
Use this section to:
- Understand the physical layout and grouping of devices.
- Identify uncapped or incomplete infrastructure where licensing risk may exist.
- Confirm how installed Java software maps to devices and affects license counts.
This insight is essential for ensuring compliance when using Oracle’s processor-based licensing metric.
Actionable Insights Details
This section highlights key opportunities for reducing risk and improving compliance across your Java estate. Each task listed is automatically generated based on the licensing position, product version, and usage context.
Common insight types include:
- Version out of support: Devices running outdated Java versions that may require urgent attention for security and licensing.
- Missing hardware data: Systems lacking hardware detail that could affect processor-based license calculations.
- Free usage validation: Products marked as licensable but potentially eligible for free use under the OTN agreement pending verification.
For each insight, a recommended remediation step is provided to guide next actions—such as version upgrades, data completion, or usage verification. These insights help prioritize what matters most in optimizing and securing your Java deployment.