|Number of votes:||2|
There are some new features in CMS6 regarding license and site handling that I would like to share with you in this post.
In admin mode there is a new option “Site Information” as seen below:
From the list you might already see a new feature, namely that it is possible to have a separate license file for each site in an enterprise scenario.
If you select a site you will be directed to the details page for that site as seen below:
On the “Site Information” tab it is possible to manage which hostnames, ports (and optionally languages) that should be associated with the site. In CMS5 this had to be done directly in the web.config file.
The “License Information” tab lists details about the current license as well as some license management features as seen below:
The “Automatic license management” section gives options for what action the system should do when it detects that a license is about to expire (less than five days left). The different options are:
In the “Download license” section there are some features that involve communications with the EPiServer license service. These features are:
The “Upload license” section lets the user upload a license file from disk and update the site to use it.
The “Restore license” section makes it possible to “rollback” and use a previously backed-up license file (the system will whenever it updates a license file take a backup of the current license file). If you click on the “Restore license” button you will see the page below:
Here you can see all backed up license files. If you click on one of the files you will see details about that license and have the option to restore the license.
In CMS6 we have relocated some parts of the configuration to separate configuration files. There will be a episerver.config file which contains all settings inside the EPiServerSection (episerver configuration element) and a EPiServerFramework.config configuration file that contains all settings for EPiServerFrameworkSection (episerver.framework element). It is still possible to have all configuration in a single file if that is what you prefer. The configuration example below shows the parts of configuration that relate to site and license handling (in the example the configuration section are in same file):
Here you can see that the host mapping configuration has been moved from site element in episerver section to siteHostMapping element in episerver.framework section. You can also see that there is a new attribute licenseFilePath on site element that states where the license file associated with the site should be loaded from. The path can be either relative to the site root or an absolute physical path. The system will by default (e.g. when downloading license files) store them in a sub folder to the site called “Licenses”.