License
In the License tab, you can manage your license in the License Configuration wizard.
| With Neptune DXP 24 we introduced a new licensing mechanism. The binary no longer contains a default trial license for two End Users. |
If you have a customer license, the validity is calculated based on your existing Subscription Period and payment terms plus 30 days. The validity is automatically updated when the next Subscription Period starts. A trial license is valid for 30 days. The trial license for two End Users comes with no restrictions and gives you full access to the feature functionality of Neptune DXP - SAP Edition.
Online versus offline licenses
In general, you can configure two license types: online licenses and offline licenses. Online licenses are the default license type and are intended for systems with internet access. If your system has no internet access, you need to configure an offline license.
During the license configuration, you can either configure an online license or an offline license.
| Before you activate a license, set the system role under System Settings → General so that it matches the intended license configuration. The SAP Client classification reflects the role of Neptune DXP - SAP Edition. |
Configuring an offline license requires different steps. On request, you will be provided a license file by Neptune Software that is customized to your respective system.
License entitlements
Your Platform License covers a number of Runtime Instances across Production and Non-Production Environments as specified here, and a number of End Users as set out in your Quotation.
Runtime Instances and environments
Each environment uses one Runtime Instance. In the system, a Runtime Instance is shown as a license token, so one environment consumes one token.
For each Runtime Instance used by a Production Environment, five Runtime Instances are available for Non-Production Environments. This does not apply to enterprise agreements. A standard deployment with one Production Environment therefore provides six Runtime Instances in total.
| License | Runtime Instances |
|---|---|
Free trial |
One Runtime Instance, for a single environment |
Standard customer license |
Six: one Production Environment and five Non-Production Environments |
Enterprise agreement |
As defined in the end-user license agreement |
If you need environments beyond this allocation, additional Runtime Instances are required. Adding Runtime Instances or End Users requires a new or amended Quotation signed by both parties before the additional capacity is used.
End Users
The number of End Users is set out in your Quotation. Non-Production Environments are licensed for a reduced number of End Users, calculated as 30 percent of the End Users in the Production Environment, with a minimum of 50. If the Production Environment has fewer than 50 End Users, the Non-Production figure matches it.
| Production End Users | Non-Production End Users | Rule applied |
|---|---|---|
1000 |
300 |
30 percent of production |
100 |
50 |
30 percent would be 30, raised to the 50-user minimum |
10 |
10 |
Production is already below 50, so Non-Production equals Production |
Example: a typical customer setup
Company Ltd.'s Quotation covers 200 End Users, and their standard allocation provides six Runtime Instances.
One Runtime Instance runs their Production Environment, the live system where employees do their everyday work, covering their 200 End Users.
The other five Runtime Instances run Non-Production Environments, which Company Ltd. uses to build and test changes before those changes reach employees, for example development, testing, and training.
Company Ltd.'s Non-Production Environments are licensed for 60 End Users, which is 30 percent of their 200 production End Users, above the 50-user minimum.
If Company Ltd. needs environments beyond these six Runtime Instances, or more End Users, an amended Quotation signed by both parties is required before the extra capacity is used.