License upload

This page describes the handling of licenses. The link that is defined in the item menu goes directly to the licence upload function (a working copy is created).

Principles of Licensing

Sage and its partners can issue licenses for parts of the Sage X3 program. A license is necessary to start the application because most of the program code is encrypted, and decryption is possible only when there is a valid license.

The licenses are digitally signed.

For each license, there is a digitally signed policy that contains the total set of modules, activity codes, and so forth, which are under license control. The user can only use the modules that are unlocked by the license. The policy file for Sage is part of the installation, and the policy file for partners can be uploaded together with the corresponding license files. A license file without the corresponding policy file is invalid.

A license can be concurrent. For key functions, a user can use them only if they are unlocked by the license and contained in a badge which has been assigned to the user's role. The total number of badges is also restricted by the license.

Enter license data

During the Syracuse installation, you can enter a license file which will be used for the first start of the application. If you have to start the application and no license has been installed, you can also copy a license file manually to the bin/temp directory of the Syracuse installation. It must be accessible by the operating system user under which the Syracuse service runs. It must have the name license.json. When the program starts, it will read this file and rename it to license.bbb.

When you want to update or add a license, you can enter the data in this screen. You may paste the license content into the field Content and click on the Upload license link. You may upload an arbitrary number of partner and policy files in a single step.