DMSContainer is very flexible and generous in terms of licensing. There are 2 kinds of licensing, both works the same and the only differences are the available modules and the number of running instances allowed.
A running instance is an instance which is running using a specific license. If you launch 2 or more DMSContainer instances on the same machine (using different DMS_HOME) these instances are intended as different running instances. So if you run 3 instances using the same license you are running 3 instances.
| Standard License | Professional License |
|---|---|
| Max 10 Instances | Max 20 Instances |
The number of running instances for each kind of license level can change in the future without previous advice from bit Time Professionals.
There are no limit about the number of developers in the company. We don’t want to charge our customers if they are investing hiring new developers. If the business runs well, then you will probably install more DMSContainer instances, then, and only then, you will pay for them. So, long story short, DMSContainer licenses cost are not related to the company developers numbers.
If you need to have a separate license for each customer, then you need to buy it (20 customers -> 20 licenses), otherwise you can buy a common license for a group of 20 (standard) or 40 (professional) customers. Be warned: the licenses are “per-instance”, so if you have a test, staging and production installations for each customer, then it counts for 3 instances. Every reinstallation on a new computer (in a 6 months time span) counts as a new instance. In our experience, if you want a “common shared license” between customers, you should reserve at least 3 instance licenses for each customer. In all cases, if your business is big and you need many licenses, we can arrange a volume-discount offer. In this case your licenses managements can be even simpler (e.g. Our group licenses can expire in 2/3/4 years instead of 1 year). Just to be clear, DMSContainer will never be a big expense for any kind of business, just a big time saver.
DMSContainer default port is 443/HTTPS, check if there’s another service running on the same port. DMS Port number can be changed any time.
Locate dmscontainer.config.json file in <DMS_HOME>\config folder and change value of “ServerPort” with the desired port number.
Yes, it is possible. You need to have the Universal C Runtime updated.
If you get the error above, and if you are using self-signed DMS certificates, you need to enable it . Select “Advanced” button and click on “Proceed to Localhost (unsafe) .
Gmail uses SSL and it must be enabled for the user. Here the configuration:
| Key | Value |
|---|---|
| SMTP Host | smtp.gmail.com |
| Port | 587 |
| SSL | TLSv1 |
| Credential | Your email and password |
If you get this error follow the step here . If you don’t solve the problem, try to enabled third parts application
Libero uses SSL and it must be enable for the user. Here the configuration:
| Key | Value |
|---|---|
| SMTP Host | smtp.libero.it |
| Port | 587 or 465 |
| SSL | TLSv1 |
| Credential | Your email and password |
This error may have many causes. If configuration is ok check if the provider has changed the port number. Recently we have noticed Libero have changed from 465 to 587.
Building class jobs requires using precompiled DMS Packages. If you run into this error you probably have some packages used by the class job somewhere in your files system reachable via windows PATH environment variable or Delphi paths.
dmsRTdmvcframeworkRT.dcploggerproRT.dcpLockBoxDRRemove older if you can otherwise force sdk path in project search path option. SDK path is under DMS installation SDK folder.
If you get this error with some DMS units. You probably have dmsRT.bpl somewhere in your files system. You can run into this error also if you have installed a different version of dmvcframworkRT, for example the IDE extension.
Remove older if you can otherwise force sdk path in project search path option. SDK path is under DMS installation SDK folder.
| DMSContainer Version | Delphi Version |
|---|---|
| 4.1.x | Delphi 11.0.x Alexandria |
| 4.0.x | Delphi 10.3.x Rio |
| 3.1.x | Delphi 10.2.x Tokyo |