A practical guide for SAM managers to interpret LMS script output for WebLogic Server, SOA Suite, BI Publisher, and other Fusion Middleware components. Step-by-step analysis, red flag identification, and compliance documentation best practices.
Oracle's LMS scripts cover various product families, including Oracle Fusion Middleware. The middleware components typically inventoried by the LMS tool span the full Fusion Middleware portfolio. For a comprehensive overview of the licensing models for all these products, read our Oracle Fusion Middleware licensing guide.
| Product | Description | Licence Implication |
|---|---|---|
| Oracle WebLogic Server | Core Java EE application server (Basic, Standard, Enterprise, Suite editions) | Edition determines features allowed; clustering = Enterprise+ |
| Oracle SOA Suite | Service-Oriented Architecture platform: BPEL, Oracle Service Bus, BPM | Separate licence required; runs on WebLogic Suite |
| Oracle Business Intelligence | OBIEE / Oracle Analytics Server, BI Publisher | Separate licence; check if covered by bundled product |
| Oracle WebCenter | Portal and content management middleware | Separately licensable product |
| Oracle Forms & Reports | Legacy middleware for forms-based applications | Includes restricted-use WebLogic Basic |
| Oracle Internet Application Server (iAS) | Legacy app server (now realised through WebLogic) | Often bundled with EBS; restricted-use terms |
| Oracle Tuxedo | Middleware for COBOL/C/C++ applications | Separate licence if present |
| Java SE | Java runtime usage on servers | Requires subscription for commercial use since 2019 |
These products fall under Oracle's Fusion Middleware portfolio and are within the "radar" of LMS and GLAS audits. The LMS tool's middleware module gathers data about application server domains and deployed components, much like the database module gathers info on DB options. If it is installed or configured, the script will find it.
The LMS Collection Tool combines scripts and utilities to extract configuration and usage data from middleware installations. Understanding the collection mechanism helps you interpret the output accurately. For general guidance on Oracle licence compliance scripts, read our comprehensive guide.
Oracle provides middleware LMS scripts (often in a ZIP file) to run on each relevant server. A master script (shell or batch) must be run with admin privileges. This master script calls product-specific subscripts for WebLogic and other components. The scripts are designed not to modify the environment. They are read-only and have minimal performance impact. Oracle often assures customers of this, though it is wise to run them in a maintenance window.
The tool leverages the WebLogic Scripting Tool (WLST), a Jython-based interface, to query WebLogic domain information. A WLST script (often run offline) reads each WebLogic domain's configuration to list the domain name, servers, clusters, deployments, and services. By automating WLST commands, the LMS script captures a complete snapshot of your middleware setup without requiring manual input.
In addition to WLST, the tool directly collects important config files from middleware homes: domain-registry.xml (lists all WebLogic domains registered on that installation with file system paths), config.xml per domain (main configuration with servers, clusters, JMS, deployed applications), registry.xml (Oracle Universal Installer inventory listing all installed middleware products), and product-specific configs if present (e.g., opmn.xml for Oracle HTTP Server). The LMS script copies these because they reveal which components and features are in use. For example, registry.xml shows if SOA Suite or WebCenter binaries are installed, even if not actively running.
The script may also scan the file system and running processes: file scans search for known middleware installation directories; process scans check running processes for Oracle middleware (e.g., Java processes running WebLogic). This differentiates between installed-but-unused software and actively running servers. The output files (consolidated into a ZIP archive) may include raw text, CSV, or XML files with the collected data. All are packaged for analysis by Oracle's auditors, or by you proactively.
After running the LMS collection tool, you will have a set of output files. Understanding each file is the first step in analysis. Read our companion guide on interpreting Oracle LMS database script output for the database equivalent.
| Output File | What It Contains | Licence Implication |
|---|---|---|
registry.xml | All Oracle Fusion Middleware components installed: product names, internal codes, versions | Reveals installed products. If SOA Suite or BI Publisher appears without a licence, investigate immediately. |
domain-registry.xml | All WebLogic domains registered with the installation (with file system paths) | Ensures no WebLogic domain is overlooked. Each domain path should have a corresponding config analysis. |
config.xml (per domain) | Core domain configuration: domain name, version, servers (Admin + Managed), clusters, JMS, data sources, deployed applications | Shows how WebLogic is being used. Primary file for edition determination. |
| WLST Output Reports | Pre-formatted text/CSV: each domain, server instances, clustering status, JMS, version, deployed apps | Simplified analysis view. May show: "Domain ProdDomain has 1 AdminServer and 4 Managed Servers in cluster ProdCluster." |
| Other Config Files | SOA composite info, httpd.conf / opmn.xml, BI config files, FMW Control deployment data | Confirms active use of SOA Suite, OHS, BI Publisher. Not just installation but actual deployment. |
The LMS output is very detailed. It captures not only what is installed, but how it is configured and what is running. As a SAM manager, focus on the parts that have licence implications: features and components in use, clustering status, deployed Oracle applications, and server counts. Cross-reference against your licence types and NUP vs Processor entitlements.
One of the most important tasks is determining which WebLogic edition is in use and which features are enabled. Oracle does not explicitly label "This is Standard Edition" in the config. You infer it from features.
| Feature / Indicator | Standard | Enterprise | Suite | How to Detect in LMS Output |
|---|---|---|---|---|
| Single-server domain (no cluster) | ✅ | ✅ | ✅ | No <cluster> entries in config.xml |
| Clustering enabled | ❌ | ✅ | ✅ | <cluster name="..."> in config.xml or Managed Servers with cluster references |
| Distributed JMS | ❌ | ✅ | ✅ | <distributed-topic> or <distributed-queue> spanning servers |
| Whole Server Migration | ❌ | ✅ | ✅ | Migration configuration for migratable targets in domain config |
| Production Redeployment | ❌ | ✅ | ✅ | Two versions of an app deployed for zero-downtime updates |
| Oracle Coherence | ❌ | ❌ | ✅ | Coherence cluster config or Coherence library deployed in domain/inventory |
| Basic JMS (single server) | ✅ | ✅ | ✅ | JMS on single server. Not a differentiator. |
If the domain config shows a cluster (multiple WebLogic instances clustered together), Enterprise Edition features are in use. WebLogic Standard Edition does not support clustering. If LMS shows clustering and your records show only Standard Edition licences purchased, you have a compliance gap. This is the single most common middleware compliance issue. Understand Oracle core factor and licence minimums and counting rules for calculating exposure.
Beyond edition detection, identify whether the WebLogic domain is hosting Oracle middleware suites or products:
A domain containing SOA Suite components will show deployments or services like soa-infra, BAM, or OracleServiceBus. This means Oracle SOA Suite is installed on top of WebLogic, a separate licensable product. Verify you have SOA Suite licences for the corresponding processor count. SOA Suite also requires WebLogic Suite as the underlying platform.
A BI domain might show deployments like analytics, BI_Publisher, or BI-specific JMS and data sources. BI Publisher may be included with certain products (e.g., EBS includes a restricted-use XML Publisher). If standalone, verify you have BI licences.
Identified by applications like formsapp or configurations for Forms. The Forms licence includes a restricted-use WebLogic Basic. Ensure the WebLogic domain is used only for Forms/Reports. Any custom applications deployed alongside violate the restricted-use terms.
The OEM WebLogic domain is often named GCDomain and runs the EMGC (Enterprise Manager Grid Control) application. This includes a restricted-use WebLogic licence. No separate WebLogic licence is required as long as it is only used for OEM. Even clustering OEM is permitted under that restricted licence for high availability.
The LMS script output shows: "Domain ProdDomain: WebLogic Server 12.2.1, 1 admin + 4 managed servers in cluster ProdCluster". This tells us the domain is clustered, hence not Basic or Standard. Oracle would consider this an Enterprise Edition deployment. If your records show only WebLogic Standard licences purchased, you have a compliance gap. Use the core factor table to calculate the processor licence count.
Our independent advisers specialise in LMS output analysis and audit defence. We review your data, identify compliance gaps, and build a defensible position before Oracle does.
Audit Defence → Audit Risk AssessmentOracle often bundles "restricted-use" WebLogic licences with other products (Oracle Database, E-Business Suite, etc.). It is critical to distinguish these from full-use WebLogic installations in the LMS findings. For broader context on restricted-use rights, read Oracle partitioning policy vs contract terms.
| Bundled Product | WebLogic Included | How to Identify in LMS | Restrictions |
|---|---|---|---|
| Oracle E-Business Suite | WebLogic Basic (via iAS EE) | Domain name like EBS_domain; EBS-specific apps | Only for EBS. No custom apps. No advanced features. |
| Oracle Enterprise Manager | Restricted-use WebLogic | Domain named GCDomain; EMGC app | Only for OEM. Clustering for HA permitted. |
| PeopleSoft | Restricted WebLogic / Tuxedo | PeopleSoft-specific domain and apps | Only for PeopleSoft app server components. |
| Hyperion / EPM | Restricted WebLogic | Hyperion services (Essbase, etc.) | Only for Hyperion. Cannot be used beyond EPM. |
| OBIEE / OAS | Restricted WebLogic for BI | BI-specific deployments and configs | Only for hosting the BI system. |
| Oracle Forms & Reports | WebLogic Basic | Forms-specific apps and config | Only for Forms/Reports. No custom Java apps. |
Oracle's restricted licence terms explicitly state that WebLogic Basic can only be used for running the components of the product it came with. Deploying a custom Java application on an EBS WebLogic domain, or running non-OEM apps on a GCDomain, violates the licence and creates compliance exposure. Read Fusion Middleware installer and licensing pitfalls for how installer choices create unexpected exposure.
When reviewing LMS data, watch for these compliance red flags. Oracle uses these scripts specifically to identify usage beyond what you have licensed. Spotting them yourself lets you address issues proactively. For broader audit awareness, read Oracle audit trends and key focus areas and hidden Oracle audit risks.
Clustering, distributed JMS, Whole Server Migration, or production redeployment features detected but only Standard Edition licensed. This is the most common and most expensive red flag. A single clustered domain on 8 Intel cores could mean 4 Enterprise Edition processor licences (at 0.5 core factor) that you do not own.
SOA Suite, Oracle Service Bus, BPM, or WebCenter components active in registry.xml or domain config without corresponding licences. Even "installed but unused" binaries are a flag. Oracle's position is that installed software requires licensing.
WebLogic instances running on servers or cores beyond your licensed processor count. An extra environment spun up for testing without licences creates exposure. Use NUP vs Processor analysis to find the most cost-effective metric.
Non-EBS applications deployed on an EBS WebLogic domain, or any similar cross-usage of restricted-use WebLogic for custom applications. This is a clear licence violation.
Coherence data grid deployed or configured in a WebLogic domain. Coherence is included only with WebLogic Suite. Enterprise Edition does not grant Coherence usage beyond basic internal cache.
Oracle JDK on servers with no Java subscription. Since 2019, Oracle Java SE requires a commercial subscription. LMS often flags Java installations alongside middleware. Read our Java audit guide and how to prepare for a Java audit.
Even if a feature was enabled unknowingly (an admin turned on clustering or SOA Suite for testing), the script records it and Oracle will consider it a licensing requirement. "We only tested it" is rarely accepted as a defence. Read how to fight an Oracle audit claim for strategies to counter such findings.
Once you have extracted key information from the LMS output, cross-check against your organisation's licence entitlements. For guidance on the broader reconciliation process, read conducting internal Oracle licence audits.
List Oracle middleware licences you own: product name, edition, version, quantity (processors or NUP), and any restrictions. Include bundled/restricted-use rights from other Oracle products. Check your licence types and ordering documents.
Take each component from LMS data and map it. WebLogic domain with clustering maps to WebLogic Enterprise Edition. SOA Suite components map to Oracle SOA Suite licences. OHS installation maps to iAS licence (or covered by EBS/WebLogic Suite). Use the Oracle-verified SAM tools to automate this mapping.
If usage exceeds entitlements (e.g., 8 cores in use but only 4 licensed), mark as compliance issue. If covered under a restricted licence, ensure restrictions are met.
Cross-verify hardware details (CPUs, cores) with Oracle's core factor table and counting rules. For example, 16 Intel cores x 0.5 core factor = 8 processor licences required. For virtualised environments, read Oracle licensing in virtualised environments.
If you assume a WebLogic domain is covered by a restricted licence (like OEM or EBS), document the basis. This is critical if Oracle or an auditor questions it later. Keep copies of relevant agreements and ordering documents.
The LMS output is essentially Oracle's view of your usage. Oracle expects matching licences for everything reported. Any discrepancy is where they will press during an audit. Doing this cross-check internally means you can address issues or prepare explanations before sending data to Oracle. It is far better that you find these than Oracle finds them first. Read our audit negotiation guide for defensive strategies.
Handling LMS script output can be complex, but a methodical approach makes it manageable and provides defensible records. For a complete audit defence framework, read Oracle audit response playbook.
Engage middleware administrators early. They can confirm whether a domain is exclusively for EBS, whether a cluster was used only for testing, etc. Also involve your Oracle licensing specialist or procurement team.
Ensure the output is complete (all servers/domains included), no sensitive passwords are logged, and you can reproduce findings. If something looks incorrect (e.g., a decommissioned domain still showing config), note it. Read what to do when you receive an Oracle audit letter.
Create a spreadsheet listing each Middleware instance: Server, Domain, Product/Component, Version, Key Features (cluster Y/N), Licence Required, Licence Owned. Group domains by product type and environment.
Write a short note on each potential compliance issue. Example: "Found WebLogic cluster in DeptX. Currently licensed as Standard Edition. Action: Investigate purchasing Enterprise licences or removing the cluster."
Keep copies of relevant Oracle agreements. Your ordering document might state "Includes restricted use WebLogic Basic for EBS only." Quote that if needed. Read Oracle support policy vs contract rights for understanding what Oracle can and cannot enforce.
Discover unused middleware installations (opportunity to uninstall and reduce risk), consolidation opportunities (fewer servers = fewer licences), and historic configurations that need cleanup.
For any red-flag item, have an explanation or remediation ready. Example: "We configured a cluster for a one-time test, but it is not used in production. We have now disabled clustering." Accompany with evidence.
Our team of former Oracle insiders can review your LMS output, identify compliance gaps, and build a defensible position. We have helped clients reduce Oracle audit claims by 60-90%.
Oracle Advisory Services → Licence ManagementNo. The LMS scripts are designed to be read-only. They read configurations and output data without modifying the environment. Oracle assures customers they have minimal performance impact, though it is wise to run them in a maintenance window as a precaution.
Check the domain's config.xml for clustering, distributed JMS, Whole Server Migration, or production redeployment. Any of these features require Enterprise Edition or higher. If the domain has a single server with no clusters or enterprise-only features, it can run on Standard Edition. Note that Standard Edition is licensed per physical socket, while Enterprise is licensed per core (with core factor).
No. EBS includes a "restricted-use" WebLogic Basic licence that can only be used for running EBS components. You cannot deploy custom applications on this WebLogic instance. If you need WebLogic for anything beyond EBS, you must purchase a separate full-use WebLogic licence and deploy on a separate domain.
Oracle's position is typically that installed software requires licensing, regardless of active use. However, if you can demonstrate that SOA Suite binaries were installed but never configured, deployed, or used, you may have a defensible position. The safest approach is to uninstall unused components before an audit. If they appear in LMS output, be prepared to explain and provide evidence. Read how to fight an Oracle audit claim.
Absolutely. Always review and verify LMS script outputs internally before sharing. This ensures completeness, allows proactive remediation, and lets you prepare explanations. You will be in a much stronger negotiating position if you have already identified and addressed compliance gaps. Read our audit response playbook.
Running WebLogic on AWS requires careful attention to Oracle's cloud licensing policies. The WebLogic licensing on AWS guide covers how to count vCPUs for licence calculations, BYOL rights, and common pitfalls. Read Oracle licensing on AWS for broader context.
Yes. Third-party support for middleware and applications can save 50%+ on annual support fees. This also reduces Oracle's leverage in audits, since you are no longer dependent on Oracle for patches and updates. Read third-party support comparison 2026.