Graphical Overview
This section provides a visual summary of your Oracle Middleware environment. It includes total device counts, operating system distribution, component recognition coverage, and product family breakdown.
It also highlights verification tasks such as missing hardware details or unrecognized components, which may impact license accuracy and should be resolved before proceeding with compliance assessments.
Additionally, the Oracle Processors by Product chart shows how processor usage is distributed across identified Oracle Middleware products. This is especially important for environments licensed on a processor basis, helping to highlight which products contribute most to licensing requirements and where consolidation or further analysis may be needed.
Together, these visuals offer a quick, comprehensive view of your deployment and its licensing impact.
Actionable Insights
This section lists specific tasks that can be performed to improve data quality and completeness. Each row is tied to a device and highlights a required action, such as missing hardware details or unrecognized components.
Unrecognized components often stem from either noise in the data or components already recognized through other matching signatures. While these typically don’t affect accuracy, this view is useful for spotting any obvious gaps or missing key products.
Common tasks include:
- Reviewing components that couldn’t be matched
- Uploading hardware details to complete infrastructure context
This section acts as a final validation step before moving forward with licensing analysis or reporting.
Licensing Summary
This section outlines the estimated license requirements for each Oracle Middleware product or component identified in the environment.
Each entry includes:
- Product Family and Product Name
- Processors Required — the calculated licensing need based on deployment
- Product Type — classified as either a full product or an embedded component
The processor requirements reflect all relevant hardware and virtualization data, ensuring alignment with Oracle’s licensing policies. These calculations also account for any automated product bundling, where middleware components are grouped under parent products as per Oracle’s published bundling rules. This ensures a realistic view of what requires licensing and helps avoid overstatement.
This section supports license planning and entitlement reconciliation by showing the effective licensing footprint for each middleware product.
Licensing Requirement Details
This section provides a detailed breakdown of license requirements per product and per device. It shows how many processors are required on each host, taking into account the actual deployment context.
Each row includes:
- Device name, product, and product family
- Whether the product is licensable
- The hardware configuration (cores, processors, capped status)
- Virtualization structure and type
- Additional metadata such as operating system and evidence references
This view is where all component recognition, hardware, virtualization, and bundling logic comes together. It reflects the processor-based licensing requirement on a per-device basis, ensuring accuracy aligned with Oracle's licensing rules.
This section supports final reconciliation and validation during compliance assessments or internal audits.
Bundling Overview
This section provides a detailed view of Oracle product bundling applied during the licensing analysis. It shows how individual components detected across devices are grouped under parent products according to Oracle’s published bundling rules.
Each row includes:
- Device name, product, and product family
- The included components and included licenses
- Reasons for bundling (e.g. suite relationships, embedded usage)
- Supporting evidence
This logic ensures that only licensable parent products are counted, avoiding overstatement by excluding separately listed but bundled components. It also feeds directly into the processor calculations shown in the licensing summary and device-level licensing sections.
Bundling helps clarify what actually needs licensing, supports accurate entitlement mapping, and aligns the report with how Oracle products are commonly sold and deployed, and are often considerably cheaper when purchased as a bundle.
Installed Products and Bundling Details
This section lists all detected Oracle Middleware products and components, along with their bundling relationships.
It shows:
- Device-level product installations
- Whether the product is a standalone item or part of another suite
- Parent product, inclusion type, and final bundled product
- Justification and supporting evidence for bundling decisions
This view provides full traceability from raw installation data to the final licensed product. It’s useful for validating component mapping logic, especially where products may appear standalone but are actually embedded within suites (e.g. Java SE bundled under WebLogic Suite).
This section ensures transparency in how bundling was applied and supports internal audit preparation, entitlement validation, and licensing discussions with Oracle.
Orphan Components
This section lists licensable components that could not be logically bundled into a parent product.
These are typically standalone installations that:
- Do not match any defined Oracle bundling rules
- Appear isolated without supporting components or suite context
Each orphan component is displayed with its device name, product name, product family, and licensing status.
These components require individual attention, as they may represent overlooked installations or require separate entitlements. They are especially important during audit preparation, where standalone usage can introduce unexpected licensing obligations.