This is documentation of a bèta release.
For documentation on the current version, please check Knowledge Base.

This is an old revision of the document!


Orbit Online License Activation

Concept and Requirements

Concurrent Use and Online Activation

Licenses for all Orbit products are based on the number of concurrent uses. Any Orbit product must be validated via a License Activation Key.
Orbit manages all licenses and its concurrent uses via the central Orbit Online License Service. Outbound connectivity to the Orbit License Service https://activation.orbitgt.com/service on port 443 is required.
If required setup your firewall to enable outgoing traffic to the given server. Do not use the License Server's IP. It isn't a fix IP and vary as this is a scaled cloud service.

Trial and Demonstrator Licenses

Trial and Demonstrator License restrictions, see license_restrictions.

Products

Depending the type of Orbit Product, a slightly different validation check is applied.

Orbit Desktop Standalone

From version 11.2, released November 2015.

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.

Online connectivity is required to start the application and to release your license use at closing the application.
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, the application will be blocked by the License Manager window in 5 minutes. This give you enough time to save your work or to re-validate your license manually.

In case (1) the application is not closed properly or (2) no successful connection to the online license service could be established when stopping the application, your license will be released once its license lease lifetime expires.

If the Orbit desktop can't be started due to an invalid license the License Manager Window displays the reason of activation failure and how to solve the issue, see License Manager Window.

Orbit Desktop Clients

From version 1.0, released late nineties.

Orbit Desktop Clients connect to their Orbit Server, see below, every time you start and stop the application. No online connectivity is required.
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.

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.

After 2 failed attempts to automatically extend a valid license lease the application shutdown timer is displayed. Once you confirm acknowledge, the application will be closed in 5 minutes. This give you enough time to save your work locally.

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, your license use will be released once its license lease lifetime expires.

Orbit Server

From version 11.2, released November 2015.

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.

Orbit Servers connects to the Orbit Online License Service every time you start and stop the Orbit EOS Service correctly, see Orbit Enterprise Service.
A valid Orbit Server is able to activate a well defined number of concurrent Orbit Desktop Clients. The Orbit Server is not connecting to the Online License Service to validate a connecting Orbit Desktop Client.

Orbit Publisher

From version 11.2, released November 2015.

An Orbit Publisher operates the same as the above described Orbit Server.

Orbit WebClient SDK

From version 11.0

The Orbit WebClient SDK integrated by any Plugin connects to the Orbit Online License Service every time you load the Orbit WebClient. If you successfully started the application the license use is valid and assigned to the requested seat for 1 or 24 hours, depending your license configuration. Your license use will be released once its license lease lifetime expires.

Note your license use is assigned for 1 or 24 hours to the requested seat. Cleaning your cache or cookies removes your Activation Key. Restarting the plugin afterwards initiates an additional concurrent license use.

The Orbit WebClient SDK does not end the lease when it is closed. To reuse a license lease on a different hardware, you require to wait until the license lease lifetime is over or use a second concurrent seat.

The Orbit WebClient Activation Key can be entered manually or requested from the Publisher it is connecting to.
If you request the Activation Key from Publisher, you need to ensure the Publisher is configured to distribute a valid Activation Key for the plugin you are using.

Manage License Leases

A successful activation validates product use for a well defined period, so called “license lease lifetime”. Depending the product type (see above), a certain license lease lifetime is applicable.
By closing the application properly, the license lease is released immediately. This allows to restart the application right away on any hardware using the same license. Beware of the exception for the Orbit WebClient SDK (see above).

Customers are able to consult and manage their licenses and license leases via the http://my.orbitgt.com portal.
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 application was not able to successfully communicate the end-of-lease to the Orbit Online License Service. Any abuse is reported as license violation.

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. If you require access to this portal, request permission via sales@orbitgt.com. Your login credentials are identical to your orbitgt.com website login.

 
Last modified:: 2018/06/21 08:13