Generate Trial License

Trial License Properties

Depending on the system configuration and environment there are multiple selection options available for a trial license:

Single Server License

Both, the Single Server License, as well as the Plus Single Server License rely on IP addresses of the system. The IP addresses are returned by the Java VM as the available IP addresses of the server. Only IP addresses eligible for licensing will be display in the selection box.

For evaluation purposes we recommend to use INETAPP Plus, so that you can try all features, like report repository and task planner. More information about the differences of INETAPP Plus and INETAPP you can find on our website: i-net Clear Reports Feature Matrix.

If the server running INETAPP does not have an internet connection then you can request the trial license key for its IP address on our website: http://www.inetsoftware.de/products/clear-reports/trial-license-request. Set this trial license key in the configuration manager dialog "License".

Technical Requirements

  • the server must be a physical server
  • the server must not be located in the cloud (AWS/EC2, Azure ...)
  • the server must have a static, physically attached IP address that will not change
  • the server's static IP address must not be provided using a WiFi adapter
  • the software must not be run in a containerized environment (Docker, Kubernetes ...)

Site License

The Site License allows an unlimited usage of INETAPP within one site (one location) of a company/organisation. A license of this type is at least required to run INETAPP with the Docker Container.

A Site Licenses requires a static and verifiable hostname. For this Trial License type it is therefore required to have a Domain Naming Service (DNS) available in the same network. The final license may also be bound to an external internet address (see below).

Technical Requirements

  • the server must have a static hostname, verifiable by DNS (no internet required)
  • OR
  • the server must have a verifiable external internet address (reverse DNS lookup, e.g. by the companies internet connection)

Private Cloud License

The Private Cloud License allows an unlimited usage of INETAPP in a private cloud environment, such as Amazon AWS, Azure or GCE. It is possible to license a certain number of nodes, which requires the nodes to be interconnected using a Mongo or Azure CosmosDB persistence store.

The Private Cloud License requires a verifiable domain name (FQDN). For verification the FQDN of the license must match the FQDN of the external visible URL. The INETAPP server will then be asked via the external visible URL to return verification information. With the external visible URL it is possible to vary protocol, port and context of the connected servers behind a proxy using the same license. Access to the internet is not required for this license.

Note: Please make sure to manually set the external visible URL to the FQDN of the license. Otherwise it will automatically be generated form the dynamic hostname of the node. This usually results in an invalid license error. The FQDN can be checked by entering it in a browser which results in the start page of the INETAPP

Technical Requirements

  • the server must be an actual installation or docker container
  • the server must not be an application server or be run using the libraries only
  • the server must have an accessible, verifiable external internet address / FQDN set as visible URL in the configuration
FQDN Sample
  • node 1: x21.cloudprovider.com
  • node 2: x42.cloudprovider.com
  • External visible URL: https://myservice.vpc.company.com/inet
  • Then the FQDN for the license is myservice.vpc.company.com

Public Cloud License

The Cloud License allows the usage of INETAPP in a public cloud environment, such as Amazon AWS, Azure or GCE. It is possible to license a certain number of nodes, but requires the nodes to be interconnected using Mongo or Azure CosmosDB persistence stores.

The Cloud License requires an externally verifiable domain name (FQDN) to be entered manually in the configuration. The INETAPP server will then be asked on ports 80 and 443 (HTTP/s) to return verification information.

Note: Please make sure to manually set the external visible URL to the FQDN of the license. Otherwise it will automatically be generated form the dynamic hostname of the node. This usually results in an invalid license error. The FQDN can be checked by entering it in a browser which results in the start page of the INETAPP

Technical Requirements

  • the server must be reachable from the internet using port 80 or 443 (standard HTTP/s Ports)
  • the server must have a verifiable external internet address (DNS lookup)
FQDN Sample
  • node 1: x21.cloudprovider.com
  • node 2: x42.cloudprovider.com
  • External visible URL: https://myservice.company.com/inet
  • Then the FQDN for the license is myservice.company.com