New License Model - FAQ

As of 9.4, Dynamicweb includes a new licensing model which helps us keep better track of the various Dynamicweb solutions out there. This will, in time, help us deliver better service and support to customers and partners alike, by allowing us to see key solution data such as application versions, module configurations, and so on.

It also ensures that your license is automatically synchronized with our business.

Licenses are tied to an installation – each installation has to have its own license (or copy of a license) applied.

Each installation or copy of an installation is required to apply a license. If a solution is installed on one machine and later copied to another machine, the license file is invalidated and has to be re-applied to the new copy.

Simply run through the license setup again, and apply the right license. Each installation of a solution will have its own /Files/*.license file.

Please make sure the license file is not set to read only.

Azure and Load Balancing setups

As of this version, we do not recommend you upgrade solutions hosted on Azure to 9.4. Azure may periodically change the physical server for the solution, which will invalidate your license, and require you to apply it again. The license is tied to an "Installation ID" that Dynamicweb calculates, and part of that ID is the machine name. In Azure you will in some occassions see that webapps changes from one machine to another causing the license to invalidate. The frontend will continue to run though. We are currently working on a way to handle this and expect support in the beginning of March. 

In a similar vein, if you run a Load Balancing setup behind a DMZ, your NLB nodes will not be able to connect to the license service, and therefore can't revalidate a stale license. We therefore do not recommend you upgrade such a setup to 9.4 at this time.

After upgrading a solution to 9.4 or later, you will be prompted to install a license.

This requires you to login twice:

  • To the backend in a normal fashion, using the administrator credentials for the solution
  • To the license service using your Dynamicweb ID - the username and password you also use to log in to the docsite, where you are currently reading this.

After you login to the backend, you will be guided through a license setup wizard (Figure 3.1).

 

Figure 3.1 Install a trial license or a customer license

This wizard will ask you to choose between :

  • Installing a trial license
    A trial license is valid for 30 days, and can be extended indefinitely – although we will of course be notified when this happens, as you’re not supposed to run forever on a trial license. For now, a trial license has access to all Dynamicweb features, but we plan to create trial versions which match the actual license configurations we offer.
  • Installing a customer license
    If you choose to install a customer license, you will be asked to log in to the license service using your Dynamicweb ID (engage/docsite login) and shown a list of the customers registered to the partner account you are associated with in our CRM (Figure 3.2).
Figure 3.2 Select one of the customers registered to your account

Here you must:

  • Select the appropriate customer from the list
    When you login with your Dynamicweb ID, you are mapped to a partner account. The list shown here is a list of all customers with active subscriptions in our system related to that partner account. If customers are missing or wrong, it indicates flawed data in our CRM or NAV. Apply a trial license instead and contact us to correct the issue.
  • Select the appropriate license (Figure 3.3)
    The list shown here is a list of all valid subscriptions for that customer. A valid subscription is one which includes a license currently sold by Dynamicweb (Web & Ecommerce and All-in-One editions). Old license types - e.g. a Business or Corporate license - will not be shown. Contact your Partner Account Manager to get a valid license added to the subscription.
Figure 3.3 Select one of the licenses associated with the customer account
  • Select a license type for the solution (Figure 4.1):
    • Development
      Use this license type for copies of your customers solution in development environment. You can have as many as you like as long as they are not live.
    • Staging
      Use this license type for installations on staging servers for customer approvals. This type requires a valid staging license on your subscription
    • NLB-node
      Use this license type for installations on nlb nodes. In a setup with i.e. 3 servers, one will have the live license, 2 will have the NLB license types
    • Live
      Use this license type for the installation running the public site. Only one is permitted per subscription
    • Other
      Should not be used
  • Click Register

Once you’ve applied the correct license for a solution, you should be able to work with the solution as usual. If you experience any difficulties or changes, see below.

Figure 4.1 Select a license type and click Register

The new license model should have no negative impact on your business, unless you run a pirated version of the software, or you have manually enabled access to moduled which are not a part of your license.

On the positive side, when a solution has a customer license applied, administrator accounts will be able to upgrade licenses and order add-ons directly from the administration interfaceSettings > System > License configuration

The new license/add-on is added immediately - though you must login/logoff - and you will be billed accordingly on your next invoice.

If your customer does not have a valid license, apply a trial license, then contact your Partner Account Manager to get a license added to the subscription.

A Dynamicweb 9.4+ license will be marked stale after 14 days. The solution will then try to connect to our license service, to confirm that it is still valid. If the solution cannot reach our license service, it will keep trying until it does.

If it is unable to connect for 30 days, you will be warned when logging in – and after 45 days, your backend access will be disabled. The frontend will still be accessible.

To avoid this make sure your firewall allows access to licens.dynamicweb-cms.com

A common development scenario involves two or more developers working on the same solution using GIT, TFS, etc.

Sharing a trial license
The developer who first installs the solution, adds a trial license. At this stage a /Files/{InstallationID}.license file is created. Now the solution files are committed to CVS.

Developer 2 then gets the solution files including the {InstallationID}.license file. But on this installation the installation id is different, and license is not valid. Therefore developer 2 has to create his own Trial license which results in a second {InstallationID}.license file. Both can be committed to CVS. Same approach for developer 3 and more.

Sharing a real license
If you are not developing on a trial license, the approach is almost the same.

The developer who installs the solution, will apply the license by logging in, choose the customer, then the subscription and finally set the license type to "Developer". The solution is checked in to CVS and checked out by developer 2. Again the {InstallationID}.license does not match the 2nd developers machine, so he will just apply the license again like developer 1 did, resulting in 2 *.license files of type developer using the same license subscription.

Figure 8.1 Sharing a license

If your problems are related to customers not appearing when applying a license, or to not being able to select the correct license for a customer, this may be related to bad or outdated data on our end. Please contact your Partner Account Manager to correct the issue.

If you have access to more or less than you pay for, please contact support(at)dynamicweb.dk or call +45 70252092.