How to Request and Install an Appian Product License

These steps are for acquiring and installing licenses for Appian 17.4.

This document outlines the procedure to request and install a temporary or long-term product license.

License Types and What They Mean

Temporary License

A temporary license is only valid for 7 days and can be used on any server as long as the operating system matches.

This type of license should be requested in one of the following scenarios:

  • A new server is being set up for the first time.
  • A long-term license expired and you want to renew it.

To determine if you need a temporary license, navigate to <APPIAN_HOME>/server/_bin/k/<OS> using the command line and run k.exe in Windows or ./k in Linux. If k3.lic is printed, then you should request a temporary license. Type \\ then Enter/Return to exit.

Long-Term License

A long-term license is valid for an extended period of time and can only be used on the server that it was requested for.

This type of license should be requested in one of the following scenarios:

  • You have already requested a temporary license to set up a new server and you are able to generate the k output.
  • Your existing long-term license is about to expire and you want to proactively request a replacement.

Generating the k Output

In order to generate the k output, navigate to <APPIAN_HOME>/server/_bin/k/<OS>/ and run k.exe in Windows or ./k in Linux. Copy the k output to a text file and save it for future reference. Type \\ then Enter/Return to exit.

Requesting a License

The License Management Application allows registered users on Forum to request a product license to install Appian. Perform the following to request a license:

  1. Navigate to https://forum.appian.com/suite/sites/licenses and log in using your Community credentials.
  2. Fill the form according to your requirements and submit the form.
    • If you are your organization's primary POC (point of contact), then the Appian license administrators will review your request and provide you with the license or the next steps required to generate the long-term license. You will receive these steps in the form of a task on Forum.
    • If you are not your organization's primary POC, then the request will first go to your organization's POC who will have to approve this request. If the POC approves the request, the Appian license administrators will review the request and provide you the license or the next steps required to generate the long-term Product license.
  3. The license will be delivered to you in the form of a task on Forum which allows you to download the license file.

Please note that generating the long-term license can take up to 4-5 business days.

Note: Please request a long-term license as soon as you receive your temporary license.

Installing a License

The steps to install a temporary license and a permanent license are the same. To install a product license, perform the following (Note: Licenses are hot-deployable, so you need not stop the Appian components to install a license):

  1. Copy the k3.lic file into one of the following directories, depending on your operating system:
    • Linux: <APPIAN_HOME>/server/_bin/k/linux64/
    • Windows: <APPIAN_HOME>\server\_bin\k\win64\
  2. Navigate to the directory in which the license was installed and run k.exe in Windows or ./k in Linux.
    • If a valid license cannot be found, the message k3.lic displays.
    • If a valid license is found, the details display in the banner.
  3. Type \\ then Enter/Return to exit.

If k3.lic is printed after installing the new license and running the k script, this is because of one or more of the following:

  • The operating system for which this license was created is different from the operating system on which the license is installed.
  • The CPU count requested for this license is different than the number of CPUs of the machine on which the license is installed.
  • The FQDN requested for this license is different from the FQDN of the machine on which the license is installed.
  • The license was not extracted properly and installed in the correct folder.
FEEDBACK