Activating InRule

Overview

InRule can be activated via the Installer or Activation Utility.

Depending on the product component and license key type, an InRule license may be either be licensed by machine or by cores. If you want to remove the software from one computer and install it onto another, it will first have to be deactivated, and then installed and activated on the new computer. You can deactivate the software via the Activation Utility or via the Installer during the uninstall process. If you increase the number of cores on a computer that is running InRule, you will need to reactivate the software so that the updated core count is recorded in InRule's Licensing System.

If you will be decommissioning or rebuilding a machine which has InRule installed on it, please first deactivate all InRule licenses on that machine.

Licensable Product Components

• irServer/irSDK 
  • “irServer” is the type of engine license to be used for running rules on a server. Running rules on a server is licensed by cores. “irServer” should not be confused with out of the box rule engine service called “irServer - Rule Execution Service”. An irServer license should be used to run rules on a server, regardless of if the out of the box service is being used, or if a custom service wrapper is written around the engine. Running rules on a server means you need an irServer license. A separate irServer license key is typically provided for each environment (Development, Production, Disaster Recovery).
  • irSDK is the group of assemblies used for developers to integrate the rules engine with their application. These assemblies can also be used to write irAuthorextensions, etc. These same assemblies are used to run rules. irSDK is both a product name, and also a type of engine license for a developer machine. irSDK license types are licensed by machine rather than by cores.
• irAuthor - This license is required to run irAuthor and irWord.
• irCatalog - An irCatalog license is required on the machine where the irCatalog service is installed. irCatalog is licensed by cores. This license type works very similarly to irServer - a license key is typically provided for each environment (Development, Production, Disaster Recovery).  
• irX for MicrosoftDynamics365 - The irX for MicrosoftDynamics365 authoring extension requires this license.
• irX for Salesforce- The irX for Salesforce authoring extension requires this license.

Installer Activation

Installer - GUI

Use this screen in the installer to enter your license key(s) and activate the product.

Enter your name, organization, license key(s) and then click Next to activate.

Select the "I don't have an internet connection" if you need to activate InRule on a computer that cannot connect to the InRule Licensing Service.

If you don't have a license key, click "What if I don't have a license key?" for more options. These may include:

• Contacting your local administrator to obtain your organization's key
• Contacting InRule Support to obtain a key

Installer - Command Line

In addition to the Windows user interface, the Installer also supports a command line interface so that it can be invoked from scripts or code.

Please see details about this process in the Automated Installation - Command Line Options topic.

Activation Utility Activation

Activation Utility - GUI

InRule supports a License Activation Utility that allows a user to activate and deactivate licenses and/or register the Event Log Source without running the installer. The Activation Utility is a WPF application with a full Windows UI, but it will run silently if started with command line arguments (see below). The InRule License Activation Utility ships with versions 4.1.3 and later.

After installation of any product components via the InRule Installer, the ActivationUtility.exe file will be available in the <InRule installation directory>\ActivationUtility folder. This folder can be XCOPY deployed to machines that require deployment, license activation and/or Event Log Source registration without running the InRule MSI installer.

A sample screen shot of the utility is below. A given machine only requires activation one time, and then InRule DLLs may be deployed to any location on that machine.

To activate a license key for an InRule product or feature:

• If your computer is not connected to the internet or otherwise cannot access the InRule license server, check the "I don't have an internet connection" box near the top of the form.
• In the "Activate Licenses" section, enter your name and organization.
• Enter your license key in the space provided. You may enter more than one key, one per line.
• Click Activate.

You may also use the Activation Utility to manage existing licenses on the machine. See the  InRule SDK Developer's Guide for details.

You may use the Activation Utility to install or uninstall the InRule Event Log source. Unlike the InRule Installer, the Activation Utility does not automatically attempt to create an InRule-specific Event Log Source/section. In order to perform this recommended function, you will need to run the utility by right-clicking and selecting "Run as administrator". Installation and un-installation of the InRule Event Log Source is then accomplished using the button at the bottom of the Activation utility's GUI. The action is independent of activating/deactivating licenses but can be performed in the same session.

Activation Utility - Command Line interface

In addition to the Windows user interface, the License Activation Utility also supports a command line interface so that it can be invoked from scripts or code. If a given operation is successful, the process will exit a code of zero. If the operation fails, then a non-zero exit code will be returned. During execution, all output is written to the Windows Standard Output Stream as well as a log file.

The following command line arguments are supported:

For more information on the Activation Utility, see the irSDK Developer's Guide "License Activation Utility" topic.