Does the OBIEE License Include WebLogic Server or Other Components
Oracle Business Intelligence Enterprise Edition (OBIEE) licensing includes certain bundled software components, though restrictions and conditions apply. Understanding what’s included or requires additional licensing helps avoid unexpected compliance costs.
What Components Are Included with OBIEE?
OBIEE comes with two main bundled components at no extra licensing cost:
1. WebLogic Server (Restricted Use)
- OBIEE licensing includes a restricted-use license for Oracle WebLogic Server Standard Edition.
- This allows deploying OBIEE applications without purchasing a separate WebLogic license.
- Important limitation: This included WebLogic Server can only be used for OBIEE and related BI components (e.g., BI Publisher).
- You cannot use the included WebLogic Server to run custom Java EE applications unrelated to OBIEE.
2. Oracle BI Publisher
- OBIEE license includes full usage rights to Oracle BI Publisher.
- BI Publisher provides advanced reporting and document-generation capabilities, such as formatted reports (PDF, Excel, HTML).
- If OBIEE is licensed, no additional BI Publisher licenses are required when used on the same server as OBIEE.
Practical Example:
- Installing OBIEE 12c automatically includes BI Publisher. You can immediately start creating and publishing formatted enterprise reports without extra costs.
Limitations of the Included WebLogic Server
The bundled WebLogic Server Standard Edition included with OBIEE is suitable for basic deployments but has critical limitations:
WebLogic Clustering Requires Additional Licensing
- WebLogic clustering (needed for high availability or scaling out OBIEE servers with session replication) requires WebLogic Server Enterprise Edition.
- OBIEE’s included WebLogic Standard Edition does not allow clustering.
- If your OBIEE deployment must scale or provide clustering, you must license WebLogic Server Enterprise Edition separately for those clustered OBIEE nodes.
Practical Example:
- Suppose you deploy OBIEE on two servers and want an active-active configuration with session replication. In this scenario, you cannot rely on the bundled WLS Standard Edition. You must purchase separate WebLogic Server EE licenses to legally cluster the OBIEE nodes.
Read Practical Best Practices to Stay Compliant with Oracle Middleware Licensing.
Database Licensing and OBIEE
OBIEE requires an underlying database to host its metadata repository schemas. However, the OBIEE license generally does not include a free full-use Oracle Database license. Consider the following carefully:
OBIEE Metadata Repository
- OBIEE needs a database repository created by the Repository Creation Utility (RCU).
- Historically, Oracle sometimes allowed restricted use of the Oracle Database, specifically for metadata schemas for some products. However, in modern OBIEE licensing, no general provision for a free Oracle Database exists for production metadata storage.
- Recommended practice: Assume you must separately license the database used by OBIEE’s repository schemas unless Oracle documentation explicitly grants restricted-use licenses.
Options for Database Licensing
- Use your existing licensed Oracle Database if available.
- License an Oracle Database Standard Edition if your OBIEE metadata repository workload fits the SE2 limitations.
- Use Oracle Database Express Edition (XE) as a repository (free but limited in size and resources—suitable only for small-scale test environments).
Practical Example:
- You install OBIEE 12c for your business analytics. You already have an Enterprise Edition Oracle Database licensed for other purposes—use that database for OBIEE’s repository schemas at no additional database licensing cost. If no existing database is licensed, budget for at least a small Oracle Standard Edition database.
Real-World Licensing Scenarios
Here are common scenarios illustrating how the OBIEE licensing works practically:
Scenario 1: Single-Server OBIEE (No Extra Licensing Required)
- Single OBIEE server installation
- WebLogic Standard Edition (included)
- BI Publisher installed and used for formatted reporting (included)
- Database repository on an existing licensed Oracle DB
- Result: No extra licensing costs beyond OBIEE itself.
Scenario 2: High Availability Cluster (Additional WebLogic Licenses Needed)
- OBIEE deployed in a two-server clustered setup for high availability
- Requires WebLogic Server clustering (Enterprise Edition needed)
- Database repository licensed separately
- Result: Must buy additional WebLogic Server Enterprise Edition licenses for both nodes.
Scenario 3: OBIEE with Dedicated Database (Database Licensing Needed)
- OBIEE installed standalone
- No existing database licensed
- Need a dedicated database repository
- Result: Must separately license an Oracle Database Standard Edition or use Express Edition (free but limited).
Compliance Risks and Best Practices
Understanding bundled components and licensing limitations is critical to maintaining Oracle license compliance. Avoid the following common pitfalls:
- Mistake: Using the included WebLogic for unrelated applications.
- Mistake: Enabling WebLogic clustering without Enterprise Edition licenses.
- Mistake: Assuming a free full-use Oracle Database license is bundled.
To stay compliant:
- Document all OBIEE deployments, noting explicitly what’s bundled.
- Educate administrators clearly about licensing restrictions.
- Regularly review your OBIEE setups to ensure no unexpected features are activated.
Read if Oracle SOA Suite includes WebLogic Server or other prerequisites.
Summary of Key Points:
- OBIEE licenses include:
- WebLogic Server Standard Edition (restricted use) – No extra licensing is needed unless clustering is required.
- Oracle BI Publisher – Fully included; no separate licenses required.
- OBIEE does not automatically include Oracle Database licenses.
- Purchase separate WebLogic Server Enterprise Edition licenses for clustering or advanced WebLogic functionality.
Careful planning and understanding of bundled components with OBIEE licensing can help avoid costly compliance mistakes and ensure efficient and legal use of Oracle’s BI suite.
