Oracle HTTP Server Licensing

What is Oracle HTTP Server licensing?

Oracle HTTP Server licensing governs OHS, Oracle's Apache based web server, which sits in front of Oracle Fusion Middleware and Database deployments as the web tier handling static content, routing, and SSL termination. The defining feature of OHS licensing is that it is usually not a separate cost: OHS is generally provided under a restricted use entitlement when it serves as the web tier for another licensed Oracle product, which means most OHS deployments carry no incremental charge. The licensing question arises only when OHS is used beyond that restricted grant.

Understanding OHS licensing is therefore mostly about understanding the boundary of the restricted use entitlement, because crossing it converts a free component into a licensable one. OHS sits within the broader Oracle middleware estate and is tightly bound to WebLogic Server, with which it ships as part of the Fusion Middleware web tier.

The restricted use grant

OHS is included with Oracle Fusion Middleware products and with the Oracle Database under a restricted use right that permits OHS to operate as the web tier for those licensed products. In this role, fronting a licensed WebLogic application, a Forms and Reports deployment, a Database, or another Fusion Middleware product, OHS requires no separate licence. This is why the great majority of OHS deployments in Oracle estates are correctly free, and why OHS rarely appears as a line item.

The grant is precise about purpose. It covers OHS used to serve and route to the licensed Oracle product it supports, and it is documented in the product licensing information. Reading that document, rather than assuming OHS is universally free, is what establishes whether a given deployment sits inside the grant. The restricted right is generous in its intended use but does not extend to arbitrary web serving unrelated to a licensed Oracle product.

When does OHS become licensable?

OHS steps outside the restricted grant when it is used as a standalone, general purpose web server divorced from any licensed Oracle product, or when it serves content and applications that are not the licensed Oracle product the grant supports. An organisation that deploys OHS purely to host an unrelated website, or to front a non Oracle application stack, is using OHS beyond the restricted use right and needs to establish the correct licensing basis for that use.

In practice this is an uncommon but real finding, because OHS is a capable web server and teams occasionally repurpose an installed instance for general web serving. The control is the same as for restricted use WebLogic: classify each OHS instance by what it actually fronts, and confirm that every instance is serving a licensed Oracle product within the grant rather than acting as a standalone server. Where an instance has strayed, the remedy is to bring it back within the grant, retire it, or license it appropriately.

The WebLogic and Web Tier relationship

OHS ships as part of the Oracle Fusion Middleware web tier, closely associated with WebLogic Server, and the two are usually deployed together with OHS routing requests to WebLogic managed servers. The licensing implication runs the other way from OHS: it is the WebLogic behind OHS that carries the substantial licence, not the OHS in front. A correctly licensed WebLogic estate with OHS as its web tier has its OHS covered by the restricted grant, so the focus of any review is the WebLogic edition and core count, with OHS confirmed as restricted use.

This relationship is why OHS licensing questions almost always resolve into WebLogic and Fusion Middleware licensing questions. The genuine OHS specific risk, standalone general purpose use, is narrow; the broader risk is misreading a Fusion Middleware web tier deployment and missing the WebLogic edition obligation underneath, which is where the cost actually sits.

Is Oracle HTTP Server free?

Oracle HTTP Server is free in its intended role, as the web tier for a licensed Oracle Fusion Middleware or Database product, under the restricted use entitlement that comes with those products. It is not a universally free, unrestricted web server. The accurate statement is that OHS carries no separate charge when it serves the licensed Oracle product it ships with, and it requires a licensing assessment only when used beyond that purpose.

This nuance matters because the common shorthand that OHS is free can lead a team to repurpose it as a general web server believing no licence is implicated. The correct mental model is conditional: free for its designed job, a question outside it. Treating OHS instances as deliberately classified, each confirmed to be fronting a licensed Oracle product, is the discipline that keeps the shorthand from becoming a finding, the kind of classification the middleware licensing practice applies across the web tier.

OHS in the cloud

On OCI and other authorized cloud environments, OHS carries the same restricted use logic: deployed as the web tier for a licensed Oracle product running under BYOL or a marketplace image, it remains within the grant. The cloud does not change the boundary; an OHS instance fronting a licensed WebLogic deployment on OCI is restricted use exactly as on premise, while an OHS repurposed as a standalone web server on cloud compute would step outside the grant just as it would on premise.

The practical cloud point is that the substantive licensing attention belongs to the WebLogic and Fusion Middleware products OHS fronts, which are counted on OCPUs with the core factor suspended. OHS itself rarely moves the cloud licensing total; the WebLogic behind it does.

Where OHS audits find money

OHS specific findings are uncommon and narrow: standalone OHS instances used as general purpose web servers, or OHS fronting non Oracle stacks, outside the restricted grant. These are real but rare, because OHS is usually deployed exactly as intended. The far larger risk associated with OHS deployments is indirect: a Fusion Middleware web tier whose WebLogic edition or core count was not fully licensed, where the auditor's attention to the web tier surfaces the WebLogic obligation underneath.

The defence is an inventory of OHS instances classified by what each fronts, confirming restricted use, paired with the WebLogic and Fusion Middleware licensing map beneath them. With that map the rare standalone OHS use is visible, and more importantly the WebLogic obligation the web tier implies is accounted for, before an audit. The audit defence practice reconstructs both under pressure, but the inventory is cheap to maintain in advance.

The buyer side view

Oracle HTTP Server is governable once you hold the conditional model: free as the web tier for a licensed Oracle product, a question outside that role. Classify every OHS instance by what it fronts, confirm each sits within the restricted grant, and bring back, retire, or license any instance repurposed as a standalone web server. Above all, recognise that the real cost behind an OHS deployment is the WebLogic and Fusion Middleware it fronts, and license that edition and core count deliberately. Do this and OHS is correctly free; assume it is universally free and a repurposed instance becomes the rare finding. To classify your web tier and the WebLogic beneath it, request a consultation.