What I ran into
I needed to quickly check license entitlements and expiration for a Connect CDC setup, and I realized the OmniLicense file itself already contains most of the information. It is not obvious at first, but once you know where to look, it is very straightforward.
Where the expiration date is hidden
The simplest way I found is this:
- The last 6 digits of the OmniLicense file represent the expiration date
- The format is YYMMDD
Example:
...150630
This translates to June 30, 2015
What else the file tells you
The OmniLicense file also includes entitlement counts.
It shows how many licenses are assigned for each OS, both for source and target:
- Windows
- Unix
- Linux
- z/OS
- AS/400
Example interpretation:
- Source: Windows 3, Unix 7, Linux 3, z/OS 0, AS/400 2
- Target: Windows 3, Unix 7, Linux 3, z/OS 0, AS/400 2
This is useful when validating cross-platform replication setups.
How to confirm inside the UI
If the license is already installed, I usually double check it in Director:
- Open the model
- Go to Help → License Information
- Look for the ValidTo value
That field gives the expiration date clearly, without manual decoding.
You can also access the same information from the server level in Director under Help → License Information.
Why this matters
I’ve seen cases where replication issues were actually tied to license limits or expiration, not configuration.
Knowing how to read the OmniLicense file helps with:
- Quick validation during troubleshooting
- Verifying entitlements across environments
- Avoiding surprises when licenses expire
Takeaway
The OmniLicense file is not just a key. It is a compact summary of your license scope and validity.
Once I knew how to read it, I stopped guessing and started verifying instantly.
Have you used the OmniLicense file directly for troubleshooting, or do you usually check everything through Director?
------------------------------
Adhitya Maya
*Precisely Software Inc.
------------------------------