1 Workflow
Licensed Features like Multichannelling Content.Repositories and the Template/Tagtype Migration Tool must be activated. First the feature needs to be added to the license key. This can be done by sending a license activation request to license@gentics.com. The license key file needs to be updated after the license request has been granted. Remove the activation information from the keyfile.
- license.key:
1234-5678-9123-4567-8912-3456-7890-1234 6314E8EE755209DD58ADB65A018DD81C 302C02141FC3E44CEE28EEE83EABBAFF376BC77E1CE02C5C02147E773456A1F93F1B3C4A09C928E96C1EAF4EFC89 CN
- Change to:
1234-5678-9123-4567-8912-3456-7890-1234
After this step the Gentics Content.Node Tomcat Server needs to be restarted. The restart will invoke a reactivation of the license key. After the activation has been completed the license key file should look similar to this:
1234-5678-9123-4567-8912-3456-7890-1234 6314E8EE755209DD58ADB65A018DD81C 302C02141FC3E44CEE28EEE83EABBAFF376BC77E1CE02C5C02147E773456A1F93F1B3C4A09C928E96C1EAF4EFC89 CN, TTM, MCCR
The last line of the license key should now contain the licensed feature information.
Please note that earlier versions of Gentics Content.Node don’t support license keys that have licensed features. This means that a Gentics Content.Node installation may fail activation when the a feature was added to the license key. This applies for Gentics Content.Node Version 5.12.4 and earlier versions.