License Checks

#### Search Results

Search

# License Checks

The following describes the license check support.

- License Check during Deployment

- License Check for Deployed Applications

## License Check during Deployment

When you deploy a Natural for Ajax web application into an Application Server or a Web Container, license checks are done. In case of an invalid license, you’ll find an error in the Natural for Ajax server log file or the log file of your Application Server/Web Container, depending on the configuration. Each access to the deployed web application shows a corresponding license error page in the browser.

## License Check for Deployed Applications

Whenever a new session is started in the browser, the license is checked.

- License Errors Before Expiration Date

- License Errors After Expiration Date

### License Errors Before Expiration Date

Starting 40 days before the license expires, corresponding warnings are written to the Natural for Ajax server log file or the log file of your Application Server/Web Container, depending on the configuration. Additionally, you will see a corresponding warning text when opening the Monitoring Tool.

Optionally, in the cisconfig.xml file, you can define a list of hostnames. When the web application is called with an URL containing this hostname, an alert box with a license warning is shown once per day.

#### Example:

    <cisconfig licwarningsfor=”localhost” ...>

This will show an alert box for the URL http(s)://localhost:<port>/mywebapp/*. It will not show any alert boxes when the web application is accessed from outside, for example using the URL http(s)://myhost:<port>/mywebapp/*.

### License Errors After Expiration Date

When the license expires, an error page shows when trying to start a new browser session. Sessions that are already running do not have any impacts. The Configuration Tool can still be used without any constraints.

### On this page

- License Check during Deployment
- License Check for Deployed Applications