SAS Event Stream Processing: Renewal Instructions

• Overview
• Apply a License Manually
• Apply a License Using Ansible

Overview

A valid license file is required to run any applications that use SAS Event Stream Processing. Your Software License Renewal Confirmation message contains a license file. You must place that license file in the license location.

Apply a License Manually

To manually apply a new license:

1. On the command line, verify the installation directory.

   UNIX: echo $DFESP_HOME

   Windows: echo %DFESP_HOME%

   In a UNIX environment, the default installation directory is /opt/sas/viya/home/SASEventStreamProcessingEngine.

   In a Windows environment, the default installation directory is C:\Program Files\SAS\Viya\SASEventStreamProcessingEngine

2. Copy the license file to the license location:

   UNIX: $DFESP_HOME/etc/license

   Windows: %DFESP_HOME%\etc\license

3. If an application has changed the license location (for example, through the C++ Modeling API dfESPlibrary::Initializeutility), copy the license file to the changed location.

Apply a License Using Ansible

If your deployment was performed using Ansible, you can use Ansible to apply a new license. Ansible applies your new license to the CAS controllers—primary and backup—and also to SAS Foundation.

To apply a license using Ansible:

1. Log on to your Ansible controller machine with a user that meets the requirements in “Set Up the User Account that Deploys the Software” in SAS Viya for Linux: Deployment Guide.
2. Move the current license files into a backup location.

   Copies of your current license files should reside in your Ansible playbook directory (sas_viya_playbook/, by default).

   The license files are named SASViyaV0300_order-number_site-number_Linux_x86-64.jwt and SASViyaV0300_order-number_Linux_x86-64.txt.

3. SAS distributes renewal licenses to customers as file attachments in a renewal order email (ROE). Make sure that your new license files (a .txt file and a .jwt file) reside in your Ansible playbook directory.
4. Modify your Ansible playbook to point to the new license files. Open sas_viya_playbook/vars.yml, locate LICENSE_FILENAME and LICENSE_COMPOSITE_FILENAME, and replace the current license file name with the corresponding new license file name.
   Note: The JSON web token license file (.jwt) is also referred to as a composite license.

   Here is an example:

   # The name of the license file on the Ansible machine. LICENSE_FILENAME: "SASViyaV0300_09MMMV_Linux_x86-64.txt" # The name of the composite license file on the Ansible machine. # If both files are present, the playbook will use the # composite license file. LICENSE_COMPOSITE_FILENAME: "SASViyaV0300_09MMMV_70180938_Linux_x86-64.jwt"

   # The name of the license file on the Ansible machine.
   LICENSE_FILENAME: "SASViyaV0300_09MMMV_Linux_x86-64.txt" 
   
   # The name of the composite license file on the Ansible machine.
   # If both files are present, the playbook will use the
   # composite license file.
   LICENSE_COMPOSITE_FILENAME: "SASViyaV0300_09MMMV_70180938_Linux_x86-64.jwt"

5. Run the following Ansible command for the default inventory file:

   ansible-playbook apply-license.yml