Skip to content
  • There are no suggestions because the search field is empty.

Oracle Weblogic Deployment

This article provides an overview of Oracle WebLogic Server deployments and domain configurations, including edition usage and licensing eligibility. It also identifies running applications to distinguish between standard and custom components across environments.

Graphical Overview

This section provides a graphical overview of WebLogic Server deployments across the environment, focusing on edition distribution and associated processor consumption.

Key Elements:

  • Device Count and Coverage: Displays the total number of devices identified and the subset running WebLogic, helping establish deployment scale.

  • Edition Distribution: Highlights the breakdown of WebLogic editions in use—including WebLogic Server Standard, Enterprise, and Suite—providing insight into the types of deployments present and their respective licensing requirements.

  • Processor Utilization by Edition: Maps Oracle processor usage to each WebLogic edition, offering a clear view of licensing impact and potential consolidation opportunities.

  • Licensing Insight: Supports rapid assessment of edition-specific licensing needs, especially in mixed-edition environments where entitlements vary significantly.

 

WebLogic Basic Eligibility

This section determines whether WebLogic Server Standard deployments are eligible for the use of the free "Basic" license, based on deployment and operational criteria.

Key Elements:

  • Eligibility Status: Each WebLogic device is evaluated and marked as Yes, No, or Unclear depending on the completeness and accuracy of the deployment data.

  • Eligibility Criteria: Eligibility for the WebLogic Basic license is typically based on limited feature usage, lack of clustering, and specific domain configurations. Devices that meet these conditions are flagged as eligible.

  • Error Detection: Devices that cannot be verified due to data gaps (e.g. missing deployment details) or technical errors (e.g. failure to connect to the WebLogic server) are marked as Unclear or No, with detailed diagnostic reasons provided.

  • Licensing Relevance: Proper identification of eligible devices can significantly reduce licensing exposure by applying the free Basic license where applicable, especially in environments with mixed deployments.

This section helps ensure accurate license classification and prevents unnecessary licensing of WebLogic Server Standard where the Basic edition can be legitimately applied.

 

Coherence Usage

This section reviews the deployment environment for evidence of Oracle Coherence usage, which is subject to separate licensing when enabled or clustered.

Key Elements:

  • Coherence Detection: The section checks all WebLogic environments for active Coherence configurations, including whether Coherence clustering is enabled or referenced within domains.

  • Blank Output Significance: An empty table, as shown in this case, confirms there is no Coherence usage across any scanned devices or domains. This simplifies the license position by eliminating Coherence from consideration.

This section helps verify that no inadvertent or legacy Coherence configurations are present that could result in unnecessary licensing exposure.

 

WebLogic Domain Configuration

This section captures detailed configuration data from WebLogic domains, helping to assess deployment complexity, clustering, and server roles—critical for understanding license applicability and usage scenarios.

Key Elements:

  • Domain Detection: Lists all detected WebLogic domains along with their names and version numbers, offering a comprehensive view of middleware environments across devices.

  • Active Domain Identification: Highlights which domains are active versus inactive, supporting efforts to scope licensing only to currently operational environments.

  • Cluster Awareness: Displays whether clustering is configured or in use. Even if clustering is configured but not active, it can impact licensing requirements for WebLogic Suite.

  • Machine and Server Mapping: Identifies which machines and WebLogic server instances are linked to each domain, providing insight into application distribution and usage across infrastructure.

  • Configuration Tracking: Includes the full config path source for each domain, useful for auditing and verifying data origin in compliance checks.

This data is instrumental in validating WebLogic license requirements, particularly where clustering, multiple server instances, or complex domain setups are in play.

 

Apps Running on WebLogic Domain

This section focuses on identifying all applications deployed across WebLogic domains, providing clarity on the nature of these applications—whether standard Oracle components or custom-built deployments—supporting accurate license scoping.

Key Elements:

  • Custom vs. Standard Applications: Each deployed module is assessed to determine whether it aligns with standard Oracle-delivered applications or represents a custom-developed component. This distinction is critical when validating licensing requirements, particularly for environments claiming limited or non-commercial use.

  • Domain-Level Visibility: Applications are linked to their respective WebLogic domains and devices, providing a detailed view of where each application is installed and whether it is deployed in active configurations.

  • Module and Archive Type: The report includes technical indicators such as module type (.ear, .rar) and source paths, which help identify non-standard deployments or integrations often found in custom development.

  • Version Mapping: Applications are tied to specific domain versions, ensuring compatibility insights and supporting version-specific licensing rule evaluations.

This application-level mapping allows organizations to differentiate Oracle-native functionality from bespoke solutions, ensuring license assessments reflect actual usage and development footprint.