Fallback Project - Intergraph Smart Licensing - Version 1.0 - Updated - Help - Hexagon PPM

Smart Licensing Portal Help

Language
English (United States)
Product
Intergraph Smart Licensing
Search by Category
Help

You can choose to set a fallback project for any configuration. Setting a fallback project is optional.

When an application requests a license, ISL uses the name of the project to identify which keystores should be used to obtain the license. If that project does not exist in the configuration, the license request fails and the user cannot use their PPM software. Choosing a fallback project makes it possible for users to still work, as long as the fallback project includes an available license for the product they are using.

Why would the license request include a project name that does not exist in the configuration?

When a license request includes a project that does not exist in the configuration, it's usually because the project name set for the user in the Smart Licensing Client dialog box has been overridden. The project name can be overridden in two ways:

  • An administrator defined the SLENV_ProjectName environment variable at the user level, system level, or both. If defined at both levels, the project defined at the user level is used in the license request.

    For example, a client configuration has three projects CMI, HSV, and BNA. On your client machine, the SLENV_ProjectName environment variable is set to ATL. When you try to open a PPM application, a license is requested for the ATL project, which does not exist. If a fallback project has not been defined, the license request fails and the application will not open. If a fallback project is defined, the license will be granted from the fallback project, and the application will open.

  • The software that requests the license includes a project name in the license request.

    For example, a client configuration has three projects CMI, HSV, and BNA. When a PPM application runs, the license request includes a different project name, such as HOU. If a fallback project has not been defined, the application will not run because the license request fails. If a fallback project is defined, the license will be granted from the fallback project, and the application will run.

It is also possible, though unusual, for the CCi file on a license client to be out of date, so that the project names available for selection in the License Client no longer match what is in the configuration.

  • When the project name is specified by either an environment variable or the application, that project name will be reported in the license usage report, not the fallback project name.

  • If you do not want to set a fallback project, you can instead add a project with valid keystores to your configuration. The name of the project should match the ProjectName value passed in the license requests, as illustrated in the examples above.

Set the fallback project for a configuration

  1. Click Configure ISL > Configurations.

  2. Highlight the project you want, and click > Set as Fallback.

Clear the fallback project for a configuration

  1. Select Configure ISL > Configurations.

  2. On the top of the Configurations page, click > Clear Fallback Project.