Self Service Licensing Guide
- 11 Oct 2022
- 3 Minutes to read
-
Print
-
DarkLight
Self Service Licensing Guide
- Updated on 11 Oct 2022
- 3 Minutes to read
-
Print
-
DarkLight
This article covers the features of self-service licensing. Self Service Licensing needs to be enabled through the settings. Once enabled, a thread job in Decisions is run, which collects information and applies a license for the environment. This thread job is run every hour and when Decisions is started.
The information gathered to apply for the license will be the customerID, customer name, contact email, and environment type, defined under the License Service Setting section. Other information gathered will be the usage data of the environment, such as the Machine name, the number of cores, memory size, IP Address, and Instance name of the environment.
Self-Service Licensing Guide
After signing up to license Decisions, Decisions sends a welcoming email with the Customer Id and Name.
- Sign in to Decisions and navigate to System > Settings > Licensing Setting.
- Within the Licensing Settings action menu, select Display License Data.
License Setting Actions
After the settings are done, the server will initiate a license request. From the Licensing Settings action menu, there are a set of actions.
| Action Name | Function |
|---|---|
| Check For License | Sends a license request to the Decisions licensing server. Used to manually request a license. |
| Display License Data | It Opens information about the server's current license, including its license type, when it was issued, and when it will expire. |
| Edit License Server Settings | Opens the Edit Licensing Settings window. |
| Force Request Now | Shows information about the current license installed on the Decisions instance. |
| Edit Licensing Settings | This shows a dialog with the licensing settings like Customer Id, Customer Name, etc. |
Check For License
Selecting Check for License will display a pop-up notification that the request has started and then a reply which indicates the state of the request.
| State Name | Description |
|---|---|
| Starting License Check | This message indicates that a license request has been started. |
| License Received and Installed | This message indicates that a license was received for this server and has been installed. To determine the details of the license, use the 'Display License Data' action. |
| License Already Installed | The license found is already installed. Please contact support for more help. |
| Skipping License Check | A license request is already pending. |
| Invalid or Unknown Company Id | A pop-up will show if the settings have an invalid or an unknown company id and a license is requested. An email will also be sent. |
License Server Type
There are six types of licenses for a server:
| License Type | Description |
|---|---|
| Trial | Enterprise-level license for temporary use only |
| StandardNonProduction | Non-prod licenses cannot be used to serve production transaction levels or concurrent users. |
| StandardProduction | This is for any production server. |
| Repository | Used for licensing a Decisions Repository environment |
| Disaster Recovery | Used for licensing DR environments |
| EnterpriseProduction | Enables the enterprise module for production environments. The enterprise module includes features such as clustering, multi-tenancy, and HL7. |
| EnterpriseNonProduction | Enables the enterprise module for development/QA environments. |
License Server Settings
- Select Edit Licensing Setting in the action menu.
- Select Allow License Requests.This checkbox enables the system to request licenses. The method cannot be followed if the server configured does not have internet access. Navigate to Licensing a Server.
Multi-Tenant License
Set this to true if the Server being configured needs a Multi-Tenant License. For multi-tenancy, tenants and control instances will use the same licensing information.
Licensed Company Id
The licensed company id is a globally unique id sent from the customer onboarding manager when the license agreement is initiated.
Licensed Company Name
The company name must match the ID provided in the email. If these two values are out of sync, the requests will be routed to the sales team.
Email Contact for License
This email address will receive notifications about license updates and progress for license requests submitted to Decisions. It is okay if this email address is not the same address to which the onboarding emails are sent.
License Contact Phone
Phone number is optional but will allow Support to contact the user if there is a problem with their license requests.
Licensing a Container
License info is specified in the following environment variables:
- DECISIONS_LICENSECOMPANYID
- DECISIONS_LICENSECOMPANYNAME
- DECISIONS_LICENSECONTACTEMAIL
- DECISIONS_ENVIRONMENTNAME
- DECISIONS_LICENSETYPE
These environment variables can also be used for licensing a VM. If environment variables are found, they will be over the values in the License Server Settings. Once a VM with licensing variables starts, licenses for the VM and any containerized instances will be retrieved.
Licensing a Multitenant environment
The licensing information is expected for tenants and control instances when licensing a multitenant environment. This information gathered will be can be found under License Server settings.
Multiple Requests
If several requests are submitted back to back, a notification will show that a request 'in process' prevents another request from running.
If there is no customer account, and one has been requested. It comes to the Decisions team to approve; then, an email will be sent. Change the license server settings to match this email. After changing the server settings to match, a string of emails will be sent about the licensing process.
For further information on Installation, visit the Decisions Forum.
Was this article helpful?
