Are there any components of Oracle Middleware that need separate licenses
Oracle Middleware includes core products like WebLogic Server, SOA Suite, WebCenter, and Identity Management. While these base products provide extensive functionality, certain advanced features, add-ons, and management tools require additional licenses.
Many organizations mistakenly assume all middleware features are bundled, leading to compliance problems during audits.
Below, we break down which middleware components require separate licensing, including common examples and licensing scenarios.
Management Packs for WebLogic Server
Oracle offers specific management packs for WebLogic Server within Oracle Enterprise Manager (OEM). These packs provide advanced capabilities for monitoring, diagnostics, and configuration management.
Important: The WebLogic Management Pack is not included with the standard WebLogic Server Enterprise Edition license.
What’s Included vs. Separate License Required
- WebLogic Server Enterprise Edition includes basic administrative tools and built-in management capabilities via WebLogic Console and WLST scripting.
- WebLogic Suite (higher-end edition) does include the WebLogic Management Pack for OEM.
- You must buy the OEM WebLogic Management Pack license separately if you’re using just WebLogic EE (Enterprise Edition) and activating OEM advanced monitoring or diagnostics features.
Example Scenario:
Suppose your administrator starts using the OEM WebLogic Management Pack dashboards (e.g., advanced diagnostics). If your organization owns only WebLogic EE, enabling this triggers a license requirement. An audit would flag this usage, requiring you to either disable the functionality or buy licenses.
Oracle Coherence (Data Grid)
Oracle Coherence is an advanced distributed caching and data-grid solution. While some Oracle middleware editions include restricted Coherence usage, general-purpose use requires additional licensing.
Licensing Details for Coherence:
- WebLogic Suite includes full Oracle Coherence Enterprise Edition.
- WebLogic Server Standard or Enterprise Edition does not include full-use Coherence. Only limited embedded caching is permitted.
- Oracle Coherence standalone is licensed separately by Processor or Named User Plus in Standard Edition One, Enterprise Edition, or Grid Edition.
Example Scenario:
A company using WebLogic Server EE decides to implement Coherence for application caching to boost performance. However, WebLogic EE does not include Coherence for general-purpose caching. They must either upgrade to WebLogic Suite or buy separate Coherence licenses.
Oracle SOA Suite Optional Components
Oracle SOA Suite includes extensive functionality but historically featured optional components that required separate licenses.
Included Components:
- Oracle BPEL Process Manager
- Oracle Service Bus (OSB)
- Oracle Mediator
- Oracle Web Services Manager (OWSM)
- Oracle Business Rules
- Oracle Human Workflow
- Oracle Business Activity Monitor (BAM)
- Technology adapters (e.g., JMS, database adapters)
Components Requiring Separate Licenses:
- Oracle API Gateway / API Management
- Oracle Event Processing (historically licensed separately)
- Historically, Oracle B2B Integration was licensed separately (though in newer versions, it is usually bundled).
Example Scenario:
If your SOA Suite implementation requires advanced API Management (Oracle API Gateway), this product is not included in the SOA Suite license and must be licensed separately.
Oracle Service Bus (OSB) Standalone Licensing
Oracle Service Bus is usually included within the SOA Suite license. However, standalone licensing is available separately.
- If you have already licensed Oracle SOA Suite, you have full rights to OSB.
- You must license OSB separately if you license only WebLogic Suite (without SOA Suite) and require OSB functionality.
Example Scenario:
An organization not using SOA Suite wants to deploy OSB standalone for service integration. They either need SOA Suite or must license OSB separately as an option to WebLogic Suite.
Identity and Access Management Additional Modules
Oracle’s Identity and Access Management suite is extensive. Standard licenses provide significant functionality, but some specific features need separate licenses:
Common Separate Licenses:
- Oracle Identity Federation (included with OAM Suite, but separate if you license OAM basic)
- OAuth & Social Login capabilities (available in Oracle Access Management with Mobile and Social module, not standard OAM)
- Oracle Identity Cloud Service (OICS) subscriptions if integrating cloud-based identities.
Example Scenario:
Suppose you have basic Oracle Access Manager (OAM) licenses but require federation or OAuth integration for mobile/social login. In that case, you must upgrade or separately license OAM’s additional modules.
Oracle HTTP Server (OHS)
Oracle HTTP Server is typically bundled with WebLogic or Internet Application Server licenses. Standalone usage, however, requires a specific Web Tier license (which is rarely needed but important to note).
- Included are WebLogic Server, SOA Suite, and Internet Application Server licenses.
- Separate: If deployed standalone without any underlying Oracle Middleware license.
Read Practical Best Practices to Stay Compliant with Oracle Middleware Licensing.
Database Options and Middleware Schemas
Oracle Middleware products typically require an Oracle Database to store metadata and runtime data. Middleware licenses do not include database licenses or database options.
- Middleware schemas can run on Standard Edition 2 or Enterprise Edition databases.
- If you activate database options (Advanced Security encryption, Advanced Compression) for middleware schemas, these database options require separate database option licenses.
Example Scenario:
You deploy Oracle SOA Suite schemas in Oracle Database EE and enable Transparent Data Encryption (TDE). Middleware licenses do not cover TDE. You must purchase Advanced Security licenses separately.
Common Compliance Pitfalls with Middleware Licensing
Activating Features Without License
- Administrators may inadvertently activate management pack features in OEM for middleware, triggering licensing requirements.
Misunderstanding Coherence Inclusion
- Using general-purpose Coherence grid capabilities without WebLogic Suite or standalone licenses.
SOA and API Licensing
- Mistakenly believing SOA Suite includes Oracle API Gateway, leading to accidental unlicensed API gateway usage.
Recommendations to Stay Compliant:
- Regular Licensing Reviews: Routinely audit middleware configurations for enabled features.
- Staff Education: Ensure administrators understand licensing impacts of turning on optional middleware features.
- Clear Documentation: Reference Oracle’s official Licensing Information documentation for each product to confirm included and separately licensed features.
Read Can I Use Oracle Middleware Licenses Interchangeably On-Premises and in the Cloud.
Example Licensing Gotchas (Real-World Situations)
Scenario 1: Unintentional WebLogic Management Pack Usage
A DBA enabled advanced OEM management dashboards for WebLogic EE. Oracle auditors identified this, and the company had to either disable the feature or purchase licenses immediately.
Scenario 2: Misuse of Coherence with WebLogic EE
An IT team enabled general caching via Oracle Coherence on WebLogic EE. An audit uncovered this. They had to either disable Coherence caching or buy separate licenses (or upgrade to WebLogic Suite).
Summary: Oracle Middleware – Included vs. Separately Licensed Components
Oracle Middleware products offer robust out-of-the-box features but contain optional advanced capabilities requiring separate licensing. Always:
- Verify product licensing information for included features and options.
- Conduct internal license reviews regularly.
- Ensure that all activated features have appropriate license coverage to avoid compliance risks.
By proactively managing middleware licensing, your organization can utilize Oracle middleware solutions effectively while avoiding audit surprises.
