Axpert Licensing

Axpert Licensing

10.x  (9.8 - 10.8)
Following are different type of license editions available to use for Axpert versions between 9.8 to 10.8.
    1. Evaluation Edition– Allows users to develop and use an app. The app will allow entry of only 500 records in any form in the app. Subsequently, only 10 transactions per session will be allowed. The time starting from the login of a user to the logout of a user is called a session. This will work only for 30 days
    2. Partner Edition– This is intended for partners desiring to develops apps/products for their customers. New apps/products can be developed. The usage restrictions of an evaluation copy are applied. This license needs to be renewed every year. A partner license is tied to the machine. It will get auto validated with Agile server every month
    3. Developer Edition– Intended for end user companies who need customizing capability of their app. This will work only on the app licensed to the customer. It can also connect to the app prefixed with Dev_<AppName> or Test_<AppName>. When connected to this instance, the transaction restriction will be applied to these instances. These are intended to be used as development and test instances. No new application can be developed.
    4. End user Edition– Apps developed on Axpert need end user license to run as a full version. Any one machine in the end user LAN in case of desktop version and the web server in case of web version will be registered with Agile. All machines need not be registered as in the current practice. End users will be licensed based on any one or more of the following
      1. number of users
      2. number of tstructs, iviews
      3. expiry date
      4. number of transactions.
    5. Distributor Edition– There are partners who pay an annual fee and enroll as gold or silver partners. These partners are allowed free distribution of a limited version of Axpert run time. The limited version restricts the number of transactions that may be entered by the end user. The limited version of Axpert is licensed through a distributor license. It is the same as end user license but with a transaction restriction. End users will also have an option to top up once they reach the limit after making a payment. An option to effect the top up will be available to LC and the customer in ALM.
    6. Site Edition– This is a license that is given to remote locations that are connected to a central location through Axpert data router. This is the same as the end user license but is tied to one main instance named the central location. This cannot run without a periodic connection with the central location.
    7. Processor Edition– This is the same as end user license but without any limit on number of transactions or users.
To activate 10.x licenses,
  1. Evaluation & Partner Edition licenses will be tied up with individual system ids and no additional steps are required.
  2. All other type of Axpert License Editions (End User, Developer, Distribution, Site and Processor Editions) would be storing in the concerned Axpert Schemas (table: axliccontrol) and activating in every individual system is not necessary. But  Axpert uses a windows service application "ALM (Axpert License Manager)", which needs to be installed and configured in one of the system (Preferably application server) which is supposed to be ON by 24/7 in the LAN. 
10.9 and Above
The main functional changes in new license model are as follows.
  1. Named users check is removed and concurrent logins check introduced for limited user licenses.
  2. Removed product code checking.
Accordingly, Axpert Desktop, Web and Developer/build license have been categorized as follows.
  1. Evaluation License
  2. Partner License
  3. Desktop  License
  4. Web  License
  5. Site License
To activate 10.9/11 licenses,
  1. Evaluation, Partner License and Site License are same as of previous versions.
  2. Web License: This is an App Server based license. Project/Schema wise license activation not required. 'N' no. of Projects/Axpert web sites can be deployed in server by using this edition. In-Memory DB Redis connectivity is a must in App Server for this Edition. No. of active logins will be restricted across projects/schemas in case of limited user licenses.  To activate, below are the steps..
    1. Add below web.config keys with proper values.
      1. <add key="axpLic_RedisIp" value=""/>           Ex.: 127.0.0.1:6380
      2.  <add key="axpLic_RedisPass" value=""/>      Ex.: agile.01
    2. Setup Redis license service:
      1. Duplicate redis.windows-service.conf file to redis.windows-service-axplic.conf and change following property values
        1. dbfilename (Ex.: axplic_dump.rdb)
        2. port (Ex.: 6380)
        3. requirpass (if required)
      2. Following commands needs to run.
        1. Redis-server --service-install redis.windows-service-axplic.conf --service-name axplic_redis
        2. Redis-server --service-start --service-name axplic_redis
    3. If the web license key is for limited user then following variable should add in system environment variable
      1. Variable name: "axpLic_RedisIp"
      2. Variable value: 127.0.0.1:<portno>          Ex.: 127.0.0.1:6380

      • Related Articles

      • Axpert Generic APIs

        This document is intended for users who want to consume the restful services provided by Axpert for projects that uses the Axpert as back end. Axpert provides the below services. Login GetIView SaveData. Reference document: AxpertGenericAPI

      • Migrating dashboard pages from 10.x to Axpert 11

        Page builder and Widget builder interfaces are no longer available in Axpert 11 and instead Axpert cards are introduced to display them as widgets in application main page.  This article will explain the ways of retaining and maintaining the old ...

      • Error Unable to connect Redis server, when clear In-Memory DB in 11.2.1 Axpert Web

        If you experience the below issue when you clear In-Memory DB. It may be due to redis connection not available in axpert configuration. In web config.file, EnableAxpertConfiguration value as "true" For axpert Configuration setting, in web url change ...

      • Postgres 14 version has an issue in establishing connection from Axpert

        PostgresSQL 14 uses “scram-sha-256” method for authentication by default (as per pg_hba.conf file), which is causing the connectivity issues in Axpert. Solution for the issue : The method “scram-sha-256” needs to be replaced as “trust” in pg_hba.conf ...

      • Test Mail through Axpert Properties over web not displaying any message

        If there is no message or trace, when setting up the office 365 email account through Axpert Properties in web then the following can be tried out. Open the Microsoft 365 admin center and go to Users > Active users. Select the user, and in the flyout ...