Knowledge Discovery 25.1
Knowledge Discovery Expert

# Licenses

This section describes licensing for Knowledge Discovery products and components.

## Standard License Model

The standard licensing model in Knowledge Discovery uses a License Server module, which provides licenses to all the other modules that make up the Knowledge Discovery deployment. The License Server itself uses an encrypted license file, given at point of sale, which specifies:

- the number of permitted instances of each module type

- the number of permitted users, document sections and query rates

- the licensed module actions and features

- the license expiry date

- license information, such as the MAC address of the License Server

As well as the license file (`licensekey.dat`), License Server requires a version key (`versionkey.dat`), which contains information about the versions of components that you can use. You must download a new version key when you upgrade your components. You can obtain the `versionkey.dat` from the Software Licenses and Downloads portal (SLD), in the License Server package or as a standalone download package.

Other modules obtain their license from the License Server, and renew it periodically (typically every 2 hours) to continue operating.

## OEM License Model

An alternative licensing model allows you to distribute Knowledge Discovery as part of an OEM application. In this case, the application has a single license without host or port restrictions. This license typically still includes an expiry date and version number. You also require a version key, which you deploy alongside the license key.

For OEM licensing, you do not require a License Server installation. To prevent OEM customers from abusing the license, all requests to Knowledge Discovery are encrypted in the application.

For more information about OEM encryption, see Encryption in Knowledge Discovery.

## Enterprise OEM License Model

The Enterprise OEM License Model uses License Server to provide a standard license, and also includes an OEM encryption key that allows optional ACI request encryption.

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

## Security in Licenses

Licenses are strongly encrypted, as are the requests and responses that issue them. To configure these requests to also use SSL, you can use the `SSLConfig` configuration parameter. For more information, refer to the License Server Reference.

Related Topics

- Troubleshoot License Issues

Copyright 2024 Open Text
Version 25.1 | Last updated January 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 25.1

Topic Title: Licenses