Updated: May 29, 2023 |
The task of deploying licenses takes only a few simple steps, even when you are deploying multiple licenses all at once.
In this section, we define package status and discuss how to deploy:
To deploy a named user license to a user:
To deploy multiple named user licenses to a user all at once:
When you deploy a named user product license:
The procedure for deploying a build server license is similar to that for deploying a named user license: click the product’s Users field, click Deploy, and then enter the user’s email address.
Make sure that you deploy the build server license to the same user who will create the build server installation and run the builds.
To write an automated deployment script that creates a build server installation, see the Creating and Deploying Installations of QNX SDP in Large Organizations guide.
To deploy a floating multiuser license to one or more users:
To deploy multiple floating licenses all at once:
When you deploy a floating license:
For more information on administering floating multiuser licenses, see the Floating License Management Guide (http://www.qnx.com/download/group.html?programid=30391). The guide provides an introduction to floating licenses; it also explains how to configure a license server and how to connect development hosts to that server.
The procedure for deploying a project license to multiple users is similar to that for deploying a floating license to multiple users: click the product’s Users field, click Deploy, and then enter the users' email addresses.
You can deploy a project license to all developers working on the project.
The Status (See status) field identifies the maturity of the software at a file level, although it is usually defined at package level so that all included files have the same maturity.
Possible values of this field can include Experimental, Alpha, Beta, Validated, Official, Stable and Experimental-Pending Stable.
The identified software maturity level may have specific meanings and ramifications detailed in the terms and conditions of your software license. For details please consult the license agreement(s) pertaining to your use of the relevant product.
See also Inspect package and file properties and Manifest Reports & File Lookup.Experimental packages can be excluded from the installation or from the calculation of the dependencies by modifying the installation preferences. See Edit installation properties. All packages are considered experimental unless marked Stable, Experimental - Pending Stable, or Official.