Oracle iAS licensing in 2026. What the old license covers, and where to move it.

Your Oracle iAS license almost certainly still gives you the right to run the software. What it covers, what your support actually delivers, and what it costs to keep or leave are the questions most companies have not checked since the original purchase.

What is Oracle iAS, and which release are you running?

Oracle Internet Application Server (iAS) is the application server family Oracle sold before WebLogic became its strategic platform. The name covers several generations, and the generation matters because the entitlement wording changed between them.

Most surviving deployments run either the Oracle9iAS releases or the Oracle Application Server 10g releases that followed. After the BEA acquisition in 2008, Oracle rebuilt Fusion Middleware on WebLogic Server, and the old stack stopped receiving investment.

What was in the iAS bundle?

• Forms and Reports. The application runtime that keeps most of these installations alive. Its migration cannot be avoided, but it is at least predictable.
• The J2EE container. Oracle Containers for J2EE (OC4J), Oracle's own container for Java applications, which your custom code was written against. TopLink, the object relational mapping library, shipped alongside it.
• Portal and Discoverer. The web portal product and the end user reporting tool, each with its own successor question.
• Single Sign On and Internet Directory. The identity components, and usually the hardest part of any migration to unpick.
• HTTP Server and Web Cache. The web tier, and the easiest layer to replace.

Oracle positions WebLogic Server as the successor platform for all of it. That is a product statement about where Oracle invests. It says nothing about what your old licenses convert into, and buyers routinely confuse the two.

Which iAS edition did you buy, and does it still matter?

It matters more now than it did at purchase. The editions gated which components you could run, and years of configuration changes mean the deployment and the entitlement rarely match any more. Oracle's licensing information for the 10g Release 2 generation sets out four editions.

1. Find the ordering document, not the invoice and not the support renewal quote. The order names the edition, the metric and the quantity.
2. List what is installed and started, component by component, including anything an administrator enabled once for a project.
3. Compare the two lists before an auditor does. Every gap is either something to remove or something to price.

How do you check what is actually installed and running?

Use the tools that shipped with the product. They separate what sits on disk from what runs, and that distinction is what an auditor will test.

• The central inventory. The inventory.xml file under oraInventory lists every Oracle home on the host, including forgotten test and training homes.
• OPatch. Running opatch lsinventory -detail against each Oracle home prints the installed products and patch levels, which gives you the release for the support check.
• OPMN. opmnctl status -l shows which processes are running now, and the opmn.xml file shows every component OPMN is configured to start.
• Application Server Control. The Enterprise Manager console for 10g lists the components deployed in each instance, which helps with edition drift.

What entitlement does a long standing Oracle iAS customer hold?

You hold either a full use license or a grant restricted to one application, and every later decision depends on which. It is the first question we ask, and in most companies it takes a week to answer properly.

Is your iAS license full use, or restricted to one application?

A restricted grant is a narrower license, and it is no weaker for the application it covers. Using it to host a second workload is the most common middleware finding we see in application environments. Our guide to Oracle license types explains how restricted use terms are written.

Which restricted use terms are built into the iAS editions?

Even a full use iAS license carries embedded restrictions, and they generate findings years after installation. The 10g licensing information sets out two that are easy to breach without noticing.

• The infrastructure database. Every edition shipped an Oracle Database for storing the product's own metadata. Storing application data in it requires a full database license.
• Single Sign On and Internet Directory. In Standard Edition and Standard Edition One, Single Sign On was provided only for use with Portal, and Internet Directory only to manage users for the application server components. Running the company's general LDAP service on that directory is outside the grant. Enterprise Edition lists both as full components, so check the edition on the order first.

What does the old iAS entitlement convert toward?

Oracle has run named migration paths from the Application Server editions toward WebLogic editions at various points, and the terms have changed over the years. There is no universal mapping you can rely on from memory.

Ask your account team for the current migration matrix in writing, and read it against the Oracle Technology Price List and your own contract. Buyers with active support routinely discover they hold more toward the target than they assumed.

Is Oracle iAS still supported in 2026?

You can still be paying for support on it, and you are almost certainly not receiving security fixes. Many companies discover the second fact only when a scanner flags a vulnerability and no patch exists.

Oracle's lifetime model runs Premier, then Extended, then Sustaining Support. Oracle's own alert for the 10g 10.1.2 and 10.1.4 releases set the end of Premier Support at December 31, 2011, and Extended Support has since ended too. Sustaining Support has no end date, so a server can look supported on a purchase order and receive nothing that closes a vulnerability.

What does Sustaining Support actually include?

Oracle publishes the dates in its Lifetime Support Policy for Fusion Middleware and describes the tiers on its lifetime support page. Check the dates for your exact release, because they differ within the family.

What does Sustaining Support mean on an internet facing server?

It means an unpatched web tier carrying business traffic. The application server is the component most exposed to the outside world and the least able to hide behind a firewall, which is the wrong risk profile for an unmaintained platform.

• Vulnerability management stops working. Your scanner keeps reporting findings for which no fix will ever be published.
• Certification blocks everything around it. Operating system upgrades, browser changes and database upgrades all stall on the unsupported component.
• Insurance and audit questions get harder. A risk committee will not accept a knowingly unpatched internet facing platform for long, and cyber insurance questionnaires often ask about unsupported software.

Do you need a Java SE subscription to keep iAS or WebLogic running?

Almost certainly not for the Oracle product itself, and in larger companies that answer is worth several hundred thousand a year. Java supplied with an Oracle product remains licensed for use with that product. WebLogic did not lose that entitlement when Oracle moved Java SE to the per employee metric in January 2023.

Oracle sets out the position in My Oracle Support Doc ID 1557737.1, its note on Java SE support entitlement when Java is used as part of another Oracle product. The per employee subscription covers your own general purpose Java: applications your teams wrote, third party software that needs a runtime, and developer machines.

• Test the right question. Ask what the runtime is used for. Which vendor supplied the binary tells you little.
• Refuse to pay twice. Buyers with WebLogic based products have been quoted subscriptions for coverage they were already granted.
• Audit the edges. A standalone runtime installed on the same server for a scheduled script is exactly the general purpose use the subscription targets.

Our page on Oracle Fusion Middleware licensing shows where the included entitlements start and stop across the WebLogic editions. For the Java side, see the restricted use Java entitlements you already have.

What does it cost to stop paying Oracle support on iAS?

It can cost more than it saves. Three policies in Oracle's software technical support policies decide whether cutting iAS support saves anything, and few buyers read them before they cancel.

• Reinstatement. If support lapsed and you later need it back, you pay a reinstatement fee of 150 percent of the last annual support fee, prorated over the lapsed period. You also pay the support fee for the new support period.
• Matching service levels. All licenses in a license set must sit at the same support level, so you cannot support a subset and leave the rest unsupported. Licenses under the same agreement and support identifier are usually treated together in practice.
• Repricing on partial termination. Terminating part of a license order reprices the remaining support at current list minus the standard discount. The new fee cannot fall below what you paid for those licenses, which is how a cancellation meant to save money ends up costing more.

A worked example of reinstatement

Say you hold 4 processor licenses of Internet Application Server Enterprise Edition and paid support at list, $7,700 each, so $30,800 a year. You dropped support 18 months ago and now need it back to claim a migration credit.

The lapse saved $46,200 over 18 months. The reinstatement fee alone is $69,300, half as much again as the saving, and the new year of support comes on top. On iAS the reinstated support still delivers no new fixes. Our note on dropping Oracle support and reinstatement covers the variants, including licenses that never had support.

Is third party support a sensible interim step for iAS?

Sometimes, and it works best as a bridge while you migrate. It can hold the cost down while a migration is scoped and funded. It does not pretend to solve the underlying problem, and you give up the upgrade rights and conversion value that come with Oracle support.

Weigh it against the matching service level rules, because moving one product off Oracle support can affect the products beside it. Our note on Oracle third party support sets out where it works and where it costs more than it saves.

Where should each Oracle iAS component go?

It depends on the workload, and for most companies there are three destinations. Treat the old bundle as a set of separate problems, because that is how it will migrate.

Forms and Reports is the predictable part

Forms migrations are the least risky part of this exercise. Oracle still ships supported releases, currently 14.1.2, documented on the Oracle Forms page, and most application logic carries forward with limited rework.

The timeline goes on everything around the form: printing, file transfer, client side integrations, and screens built for the browser plugin era. Budget for those surroundings first. Our Oracle Forms licensing guide covers what the current Forms and Reports license includes.

Identity decides the schedule

Identity is where these projects slip, because the old Single Sign On layer is usually wired into applications that were never documented. Start here, early in the plan, and treat the corporate identity provider as the default destination.

A like for like Oracle replacement should have to justify itself. Our page on Oracle identity and access management licensing shows what that replacement costs.

Custom Java applications are the real decision

Ask one question about every custom application: how much of it depends on vendor specific container features. If the answer is little, the application does not need WebLogic, and moving it removes Oracle footprint permanently. Our WebLogic to Tomcat feasibility guide lists the features that make a move hard.

Why WebLogic Suite should not be your default destination

The usual advice says the migration path runs to WebLogic Suite, so the exercise is a technical upgrade with a predictable license purchase at the end. We disagree, because that assumption costs more than the migration does.

WebLogic Suite is the top edition, and Oracle's licensing information includes Internet Application Server Enterprise Edition inside it, which is why proposals default to it. For a Forms application the edition you need is often much smaller. Not every workload belongs on Oracle middleware, so split the environment before you price it.

• Forms stays on Oracle, because there is no equivalent runtime anywhere else and the rework would be a rewrite.
• Identity usually leaves, because you already run an identity platform the rest of the business authenticates against.
• Plain Java code often leaves, because it never depended on the container it happened to be deployed into.
• The portal is a rebuild wherever it lands, so pick the destination on merit.

Companies that run this split retire an Oracle line item for good. The ones that migrate wholesale move the same bill to a newer product name and call it modernization. Our comparison of WebLogic Suite and Standard Edition goes further on the edition choice.

What does each option cost at list?

Say the same company runs one Forms application on 2 licensed processors and two custom Java applications on another 2. Processor counts here are after the Oracle core factor. The table uses current list prices for new licenses, before discount and before any migration credit.

The spread between the first and last rows is $134,000 in license fees and $29,480 a year in support.

The last row assumes the Java applications run on an OpenJDK build; putting Oracle's JDK under them brings the per employee Java SE subscription back into scope. A migration credit narrows the gap in every row, but it never turns the top edition into the cheapest one.

Where does a legacy iAS installation create audit exposure?

In four places, and running an old release is not one of them. Findings come from what accumulated around the release while no one was watching.

The four findings we actually see

1. A restricted grant hosting a second application. The grant came with one application, and someone deployed another onto the same server because the capacity was there.
2. Edition drift. Components that belong to a higher edition than the one on the order, usually switched on for a project that ended a decade ago.
3. Virtualization. Middleware running on a virtual cluster where the counting rule reaches wider than the virtual machine, the same argument Oracle makes for the database. See our Oracle virtualization licensing guide.
4. Environments never decommissioned. Test, training and disaster recovery copies still installed and still startable, long after the project they served.

Our page on Oracle middleware audit risk covers the counting arguments in detail, including the virtualization position.

What have we seen in Oracle middleware reviews in 2024 and 2025?

Across roughly 20 to 30 Oracle middleware environments we reviewed in 2024 and 2025, surviving Application Server deployments were kept alive to avoid a migration. In most cases the migration turned out to cost less than the risk being carried.

• Unpatched production. In roughly 7 of every 10 companies with a surviving deployment, at least one production application ran on a release receiving no security fixes of any kind.
• Unknown grant type. No one in the room could say whether the entitlement was full use or restricted to a single application, and the original ordering document had to be recovered from an archive.
• Unneeded Java quotes. Teams had been quoted a per employee Java subscription for a runtime already licensed with the Oracle product it ran.
• Hidden conversion value. Where a conversion toward current middleware had happened, buyers held more entitlement than they knew, which cut the net cost of the migration materially.

Once the environment was split into separate problems, a properly scoped migration took roughly 4 to 9 months. The Forms work was rarely what set that duration.

A surviving Application Server is a deferred decision that accrues interest, on the one platform in your company that faces the internet.

What will Oracle's account team say about iAS, and how should you reply?

Expect a small set of lines, most of them aimed at a larger edition or an extra subscription. Each has a precise reply.

• "WebLogic Suite is the migration path for Application Server Enterprise Edition." Ask for the migration matrix in writing, then price the edition that matches the components you will actually deploy.
• "Your Forms servers need a Java SE subscription." Point to Doc ID 1557737.1 and ask them to name, in writing, the specific use that falls outside the product entitlement.
• "You can drop support on the old middleware and keep everything else as it is." Ask for written confirmation of which license set the iAS licenses belong to and how repricing applies to the remaining lines on that order.
• "Sustaining Support keeps you covered." Ask for the date of the last security fix published for your exact release.
• "The conversion credit is only available this quarter." Ask for the credit calculation per license and let the date follow your migration plan.

Which contract terms should you ask for?

• Conversion credit stated per license. The order should list which old licenses are retired and the credit applied to each, so the value cannot be disputed later.
• Edition defined by components. Name the components you are entitled to run, which closes the edition drift question for the new platform.
• Restricted use scope in plain words. If any grant is application specific, the order should name every application allowed to run on it.
• A price hold for the second phase. If the migration runs in stages, lock the unit price for the licenses you will add later.
• A support repricing statement. Get the support fee for the remaining licenses written into the order, so partial termination cannot raise it.

When should you start an iAS exit before your support renewal?

Start about 12 months before the support renewal date. Entitlement research and identity design take longer than the license negotiation, and a late start leaves you renewing iAS support for another year.

If an audit notice arrives first, the same sequence applies, compressed. The ordering documents and the host inventory become the first deliverables either way.

What to do next

1. Settle the grant type. Recover the original ordering documents and establish whether each grant is full use or restricted to one application. Nothing else can be decided until this is settled.
2. Inventory every host. Record every component and release level, separating installed from configured from actually started.
3. Confirm support status. Check each release against Oracle's published policy, and write down what your current level does and does not include.
4. Check Java quotes. Find out whether anyone has been quoted a Java subscription for a runtime already licensed with the Oracle product it runs.
5. Split and cost. Divide the environment into its five migration problems and cost each one separately.
6. Challenge the edition. Get the current migration matrix in writing before you accept any edition recommendation, and question anything that lands on the top edition by default.
7. Model the support consequences. Work through reinstatement and matching service levels for every option, with independent Oracle advisory reviewing the position.

Frequently asked questions