Updating the Entitlement Key

APOD/SOD requires a valid license entitlement key to use its features. If your APOD/SOD includes either IBM Aspera Console or IBM Aspera Shares, you can enter your entitlement key through the web UI.
Note: Entitlements are enabled per machine instance, not per app. For APOD/SOD licenses that allow access to both Console and Shares features, the entitlement portion of the procedure is slightly different. However, completing it for one enables the entitlement for both. Once the entitlement has been enabled from either app, it may take a few minutes for the other app to recognize the change. For more information about entitling Shares, see the IBM Aspera Shares On Demand Admin Guide.
  1. If this is your first time entering your entitlement key, first log in to Console. You are prompted to update Console with your entitlement key. Enter your customer ID and entitlement key, and click Save.
    Until you provide a valid license, you cannot use Console or Shares. If you need to review or update the entitlement information at a later time, go to Configuration > License.
  2. Back up and restore the On Demand server configuration.

    The image instance does not store data when terminated; therefore,we advise that you back up the configuration before shutting down.

    Note: A full backup of the On Demand server configuration requires backing up the Shares configuration as well as the Console configuraiton. For information on backing up Shares, see the IBM Aspera Shares On Demand Admin Guide.
    For instructions to back up SOD/APOD, see Backing Up the Current Console Configuration.