ACI API 25.3
ACI API Programming Guide

# Overview

The OEM licensing scheme restricts access to ACI API by applying ACI encryption to all requests, so that only the OEM application, which knows the encryption keys, can communicate with ACI API. This enables OpenText to provide a single license with no host or port restrictions that the OEM can distribute with all copies of their software. Even though the OEM license can be used to start ACI API on any machine, end users (customers of the OEM) cannot abuse this license because they do not have the encryption keys required to communicate with ACI API.

You can use OEM licensing with ACI API ACI servers, and with NiFi Ingest.

NOTE: You can also operate ACI servers with an Enterprise OEM license. The Enterprise OEM license uses License Server to provide a standard license, and also includes an embedded OEM encryption key that allows optional ACI request encryption, without any additional configuration in your ACI components. When you use encryption for a request, it acts like OEM encryption (with an encrypted request and unencrypted response).

This option provides a way for you to migrate an OEM system to the standard licensing model without requiring you to immediately change existing applications that use OEM encryption.

Copyright 2025 Open Text
Version 25.3 | Last updated July 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery ACI API 25.3

Topic Title: Overview