TUFLOW Licensing: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
Line 41:
=== Cloud vs. non-Cloud ===
The advantage of a Cloud licence is that you can set it up on as many machines as you like, and reuse it on future machines, for as long as the licence is valid. This gives you a similar advantage to using a Network Licence, without the complexity of network connectivity. Another benefit of this is that you can put the licence on computers that are not connected to your local network. A potential disadvantage of a Cloud licence can be the requirement that the computer it is installed on has https (web) internet access to `wibu.cloud`. It is worth noting that currently the monitoring of Cloud licence usage is not as mature as the monitoring of network licences.
=== Cloud Direct vs. Cloud Server ===
Cloud Direct requires container files be imported to all modelling computers. In this form it is recommended that all install activities are completed by an organisation's IT department, so container files aren't distributed beyond the said organisation. One limitation of the Cloud Direct option is client licence monitoring ability. No Wibu tools exist to enable client licence use monitoring. The most common Cloud Direct use is within smaller organisations who do not own network infrastructure to enable a traditional network configuration, or in cloud simulations where licenses need to be deployed to numerous virtual machines. Cloud Server offers additional security compared to Cloud Direct. There is only a single connection between a server/servers and the WIBU cloud. As such container file are not broadly distributed within an organisation. Client licence monitoring can be enabled on the client server to monitor usage by all client connections.
{{Tips Navigation
| |||