Oracle Fusion Middleware Deployment

Oracle Fusion Middleware Deployment is the middleware estate: what is installed, what was recognized as a licensable product, and how many processors that product needs. An unrecognized component still has to be read. It is often noise, or a piece already inside a parent product.

Open it from Apps, then Oracle Middleware Manager, on the Reports tab, or from Reports.

• Overview is Number of Devices and Number of WebLogic Devices.
• Devices by Operating System places them.
• Component Recognition Coverage splits Recognized and Unrecognized. An unrecognized component is usually noise, or a component already matched to a parent. It is not automatically a second product to buy.
• Verification Tasks is a metric, the items it affects, and a recommendation.
• Devices by Product Family and Oracle Processors by Product show where the processors sit.

Processor counts need the hardware upload as well as the middleware file. Without the cores, the capping and the virtualization, the processor requirement is not finished. That context is Infrastructure Overview.

Components are grouped under the licensable parent so a bundled item is not counted again. Installed Products and Bundling shows the parent product, the inclusion type, the final bundled product, and the evidence for that grouping.

Product type is full or embedded. An embedded component follows the parent.

Orphan components are licensable items with no parent. They may need their own entitlement. In an audit they are the rows that do not disappear into a bundle.

Licensing Summary is the product family, product name, processors required, and product type. Download that table for one row per device, with the user. See Using reports.

Actionable Insights is the device, the task, and the detail.

WebLogic edition and Basic eligibility are on Oracle WebLogic Server Deployment. The products this app knows are on Which middleware products OMWM covers.