Skip to end of metadata
Go to start of metadata

Table of Contents

Why are some ADSS Server modules not shown in production while these were shown during the evaluation?

ADSS Server offers multiple features or service modules. Each of these is licensed separately to keep costs down and ensure the clients only needs to license those modules which they require. Any modules that are not licensed are not shown on the operator web-interface. If you need to access other modules on a test basis contact your local re-seller or sales@ascertia.com with full details.

Another reason why a module may not appear or appear disabled is that your operator account has not been assigned suitable access rights. ADSS Server supports a sophisticated Role Based Access Control mechanism.  Consult your ADSS Server administrator about your role and access rights to the system. When a new feature is added to ADSS Server this new feature also needs to be added to the operator role by the administrator - new feature rights are not granted by default during an upgrade. Changes to operator roles can only be made by an administrator.

How to renew an expired ADSS Server license?

If your license has an expiry date that is soon approaching, you can ask for a new one from your local re-seller or via sales@ascertia.com - you should provide information about the license purchase. Generally, there is no need for this since most Ascertia licenses are perpetual. Occasionally a new license file may be required to access a new major version and this is reflected the next time the operator logs on to ADSS Server using that role.

How to replace an existing ADSS Server license with a new one?

For Stand-alone Installation:

  1. Stop ADSS Server Core, Console and Service instances from Windows services panel or UNIX daemon.
  2. Rename the license file to license.xml and place this in the following location (overwrite any previous file of this name): [ADSS Server Installation Directory]\core\license.xml
  3. Start the ADSS Server Core instance from Windows services panel or UNIX daemon in order to take the license file change into effect.

  4. Wait for 2 minutes so that ADSS Server Core instance is fully started.
  5. Start the ADSS Server Console and Service instances subsequently from Windows services panel or UNIX daemon in order to take the license file change into effect.

For Load Balanced Installation:

  1. Stop ADSS Server Core, Console and Service instances of all nodes from Windows services panel or UNIX daemon.
  2. Rename the license file to license.xml and place this in the following location (overwrite any previous file of this name): [Master ADSS Server Installation Directory]\core\license.xml
  3. Start the master ADSS Server Core instance from Windows services panel or UNIX daemon in order to take the license file change into effect.

  4. Wait for 2 minutes so that ADSS Server Core instance is fully started.
  5. Start the master ADSS Server Console and Service instances subsequently from Windows services panel or UNIX daemon in order to take the license file change into effect.
  6. Start the slave ADSS Server Core, Console and Service instances subsequently from Windows services panel or UNIX daemon in order to take the license file change into effect.
Icon

After replacing the license file check the owner / service / license limits on the ADSS Server GUI home page. The ADSS Server license generally assumes that the sample data is not loaded and the target production and test systems contain only the relevant configuration data.

Speak to your sales contact if there are any queries on the license file.

  • No labels