Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:technology:core:online_license_activation [2017/09/15 08:13] 127.0.0.1 external edit |
dev:technology:core:online_license_activation [2026/08/20 13:04] (current) jeroen |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Orbit Online | + | ====== Orbit Product |
| - | ===== Concept | + | This page describes the concepts |
| + | Orbit 3DM Cloud is not licensed via an Activation Key and the Online License Activation service.)). \\ | ||
| - | === Concurrent Use and Online | + | ===== Orbit License |
| - | Licenses for all Orbit products are based on the number of concurrent uses. Any Orbit product must be validated via a License Activation | + | Since version 21.1 the Orbit 3DM products are available for both Orbit License Activation and Bentley' |
| - | Orbit manages all licenses | + | Same software, same functionalities, |
| - | If required setup your firewall to enable outgoing traffic to the given server. Do not use the License Server' | + | |
| - | === Trial and Demonstrator Licenses === | + | {{: |
| + | {{: | ||
| - | Trial and Demonstrator License restrictions are available for Desktop Standalone products only, see [[technology: | + | === Trial and Demo Licenses === |
| - | ===== Products ===== | + | Trial and Demo Licenses are available for Desktop products. Both are subject to license restrictions. \\ |
| + | More information, | ||
| - | Depending the type of Orbit Product, a slightly different validation check is applied. | + | ===== Bentley CONNECT Edition ===== |
| - | === Orbit Desktop Standalone === | + | For documentation on product download and activation for Bentley Connect Edition, see https:// |
| - | From version 11.2, released November 2015. | + | === Bentley CONNECTION Client - Offline Activation === |
| - | Orbit Desktop Standalone products connect to Orbit Online License Service every time you start and stop the application. By closing the application properly, the license use is released immediately allowing you or any co-worker to start Orbit right away on a different machine using the same license. | + | * [[https:// |
| + | * [[https:// | ||
| + | ===== Orbit License Activation ===== | ||
| - | Online connectivity is required to start the application and to release your license use at closing the application. \\ | + | ==== Concepts ==== |
| - | If you successfully started the application the license use is valid for 1 hour. When your license lease is about to expire the application reconnects automatically to the online license service to extend its license lease lifetime with another hour. | + | |
| - | After 3 failed attempts to automatically extend a valid license lease the application shutdown timer is displayed. Once you confirm acknowledge, | + | === Activation Key & Concurrent Use === |
| - | In case (1) the application is not closed properly or (2) no successful connection to the online | + | * An Activation Key defines a product, features & capabilities, |
| + | * Activation Keys are managed | ||
| + | * Product use requires an Activation Key and online validation via the Orbit License Service. | ||
| - | If the Orbit desktop can't be started due to an invalid license the License | + | === Online |
| - | === Orbit Desktop Clients === | + | Online license validation requires outbound connectivity to the Orbit License Service < |
| + | If a firewall exception needs to be set, then use the Server Name and not its IP. The License Service is a scaled Cloud Service and has no fixed IP. | ||
| - | From version 1.0, released late nineties. | + | === Offline License Activation === |
| - | Orbit Desktop Clients | + | Orbit provides an alternative dongle-based |
| - | By closing | + | The installation procedure |
| + | An Offline License Activation replaces | ||
| + | Specific terms and conditions for offline license activation are applicable, see [[dev: | ||
| - | If you successfully started the application the license use is valid for 30 minutes. When your license lease is about to expire the application reconnects automatically to its Orbit Server to extend its license lease lifetime with another 30 minutes. | + | ==== My Orbit GT ==== |
| - | After 2 failed attempts | + | Customers are able to consult and manage their Activation Keys and Concurrent Uses via [[https:// |
| - | In case (1) the client isn't closed properly or (2) no successful connection to the Orbit Server could be established when stopping the application, | + | === Concurrent Use = License Lease === |
| - | === Orbit Server === | + | A successful activation validates the product to use for a well-defined period, the so-called " |
| + | By closing the application properly, the license lease is released immediately. This allows restarting the application right away on any hardware using the same license. Beware of the exception for the Orbit WebClient SDK (see below). \\ | ||
| - | From version 11.2, released November 2015. | + | Via this portal, specific individuals can manually end a license lease. This is required when the application is stopped in an irregular way (e.g. rebooting the server without stopping the Orbit Publisher Service prior). In such a case, technically, |
| - | An Orbit Server operates the same as the above described Orbit Desktop Standalone, differences : | + | === Get Access |
| - | * The license lease lifetime is 24 hours. | + | |
| - | * No acknowledge and shutdown timer can be used. If the license lease expires the Orbit Server license will become invalid. | + | |
| - | Orbit Servers connects | + | Access |
| - | A valid Orbit Server | + | |
| - | === Orbit Publisher === | + | You don't know if you have an Orbit GT Account or forgot your password, try to login here https:// |
| + | You don't have an Orbit GT Account, register here https:// | ||
| + | You have an Orbit GT Account but you don't have permissions to access this portal, request permission via orbit.sales@bentley.com. \\ | ||
| - | From version 11.2, released November 2015. | + | ==== Product Activation ==== |
| - | An Orbit Publisher operates the same as the above described | + | Depending on the type of Orbit Product, a slightly different validation check is applied. |
| - | === Orbit WebClient SDK === | + | === Orbit Desktop |
| - | From version 11.0 | + | Orbit Desktop Standalone products connect to Orbit Online License Service every time you start and stop the application. By closing the application properly, the license use is released immediately allowing you or any co-worker to start Orbit right away on a different machine using the same license. |
| - | The Orbit WebClient SDK integrated by any Plugin connects | + | Online connectivity is required |
| - | If you successfully started the application the license use is valid and assigned to the requested seat for 1 or 24 hours, depending | + | If you successfully started the application the license use is valid for 1 hour. When your license |
| - | Note your license | + | After 3 failed attempts to automatically extend a valid license |
| - | The Orbit WebClient SDK does not end the lease when it is closed. To reuse a license | + | In case (1) the application |
| + | |||
| + | If the Orbit desktop can't be started due to an invalid license | ||
| + | |||
| + | === Orbit 3DM Publisher Server === | ||
| + | |||
| + | An Orbit Server operates the same as the above described Orbit Desktop Standalone, differences : | ||
| + | * The license lease lifetime is 24 hours. | ||
| + | * No acknowledge and shutdown timer can be used. If the license lease expires the Orbit Server license will become invalid. | ||
| - | The Orbit WebClient Activation Key can be entered manually or requested from the Publisher it is connecting | + | Orbit Servers connects |
| - | If you request the Activation Key from Publisher, you need to ensure the Publisher | + | A valid Orbit Server |
| - | ===== Manage License Leases ===== | + | === Orbit 3DM Viewer and Plugins |
| - | A successful activation validates product use for a well defined period, so called " | + | The Html5-based 3DM Viewer SDK and any Plugins provided by Orbit GT developed Plugins |
| - | By closing the application properly, the license lease is released immediately. This allows to restart the application right away on any hardware | + | |
| - | Customers are able to consult and manage their licenses and license leases via the http:// | + | From version 18.0 Plugins provided by Orbit GT using the Flash-based Mobile Mapping or Oblique Viewer SDK are free of charge. \\ |
| - | Via this portal, specific individuals can manually end a license lease. This is required when the application is stopped in an irregular way. In such case, technically, | + | The Orbit 3DM Publisher version 18.0 or higher includes unlimited Activation Keys for all Plugins developed by Orbit GT that use the Flash-based Viewer SDK. \\ |
| + | Contact Sales at Orbit GT to obtain | ||
| + | More information about the Activation | ||
| - | Access to the my.orbitgt.com portal is granted to defined Primary Company Contacts, being those individuals within the company that are responsible for the use of the Orbit products and licenses. \\ | ||
| - | Your Orbit GT Account((Orbit GT Account : Orbit GT Website login credentials, | ||
| - | If you require access to this portal and you can't login, request permission via sales@orbitgt.com. \\ | ||
Last modified:: 2018/06/21 08:13