Oracle Licensing in ServiceNow SAM - 7 Activities customers should complete

RyanShamirA
ServiceNow Employee

on ‎05-05-2026 01:46 AM

Oracle is consistently one of the most complex and audit-heavy publishers in any organization's software portfolio. Getting your ServiceNow SAM environment correctly configured for Oracle isn't just a technical task — it's a compliance risk mitigation exercise.

 

Having worked closely with customers and partners on Oracle licensing scenarios in SAM, I've put together a practical checklist of the seven key activities you should work through to ensure your Oracle environment is accurately tracked, reconciled, and audit-ready.

 

Here's what's covered:

  1. Plugin setup — what to install and where to find it
  2. Discovery — native patterns vs. Oracle GLAS, and when to use both
  3. License configuration — entitlements, software models, partitioning (hard/soft/cloud), BYOL vs. License Included
  4. VMware aggregation — host affinity and aggregation level settings for Oracle on VMware
  5. SAM Health Checks — identifying any configuration issues 
  6. Reconciliation & reporting — Publisher Overview and Oracle Infrastructure Report
  7. Java SE licensing — employee metric, tier pricing, and override cost configuration

Each part includes direct links to the relevant ServiceNow documentation.

📌 Bookmark this article to get notified of any updates.

1. Setup & Prerequisites

  • Verify plugin availability: Log in to your ServiceNow instance and navigate to System Applications > All Available Applications > All. Search for the Software Asset Management Professional for Oracle plugin (Plugin ID: con.snc.samp.oracle) and submit a plugin request if it is not already installed.

 

 

2. Discovery

 

 

3. License Configuration

 

4. Validation & Health Checks

 

5. Reconciliation & Reporting

 

6. Java SE Licensing (If Applicable)

The following steps apply if your organization is using Oracle Java SE Universal under an employee-based license metric.

 

 

 

7. Additional Resources




  • 701 Views
Comments
JoostHofstede
Tera Contributor
Monday

Hi @Ryan ,

 

Thanks for this article. Great summary of all steps!

I have a question regarding step 3.1: Ensure entitlements and software models are set up for supported Oracle products.

 

Our Oracle products are licensed with perpetual licenses with yearly support (as in most cases if not all). 

The support is required to install patches, get updates and support. We will not run Oracle products without this support.

A couple of years ago we reduced our Oracle install base and along with it also the support licenses.

 

I have tried in many ways to configure this in Sam Pro to determine if we are compliant (perpetual licenses + support) for the current usage.

I have tried the following scenarios:

1. Enter perpetual licenses and support separately. The support is linked to the perpetual licenses. The number of support licenses are reduced a couple of years ago.

2. Enter the licenses as if it were subscription based. More in the past and less in the last couple of years.

 

As a test, I have entered too little support or subscriptions for the last couple of years.

In both cases Sam Pro does not give me the right results.

 

In the first scenario it completely ignores the support and since we have lots of perpetual licenses, we are shown to be compliant even though we do not have enough support licenses for the current setup.

In the second scenario it simply consolidates current usage against past (and expired) subscriptions resulting in us showing as compliant.

 

What is the trick I need to apply to have SAM Pro show me that we are not compliant in this scenario?

 

If it helps, consider this random example of quantities:

8 Processor perpetual licenses.

8 Processor support licenses for 2010-2023

4 Processor support licenses for 2023-2026

2 DB servers with each 4 Processors (license requirement=8) that are continuously being patched.

First usage in 2010. Last usage in 2026

0 Helpfuls
Version history
Last update:
‎05-05-2026 01:46 AM
Updated by:
ServiceNow Employee
Contributors