Flexera

Prerequisites

For Flexera One:

• Flexera One SaaS address or fully qualified domain name (FQDN) and Organization ID

• OAuth API refresh token created in Flexera One for Turbonomic use

For FlexNet Manager:

• FlexNet Manager Suite 2023 R2 or above

• Address or fully qualified domain name (FQDN) of FlexNet Manager Suite instance

• Local Windows Server username and password of an account Turbonomic can use

Turbonomic policies for Flexera licenses

Turbonomic generates policies to comply with the following types of Flexera licenses, where Usage Rights lists the configurations Turbonomic considers when creating policies:

"coverInstallsOnVirtualMachines": true,
"limitNumberOfVirtualInstalls": false,
"limitVirtualInstallsIncludesHost": true,
"numberOfAllowedVirtualInstalls": 1

"coverInstallsOnVirtualMachines": true,
"limitNumberOfVirtualInstalls": true,
"limitVirtualInstallsIncludesHost": false,
"numberOfAllowedVirtualInstalls": 1

"coverInstallsOnVirtualMachines": true,
"limitNumberOfVirtualInstalls": false,
"limitVirtualInstallsIncludesHost": false

"coverInstallsOnVirtualMachines": true,
"limitNumberOfVirtualInstalls": true,
"limitVirtualInstallsIncludesHost": false,
"minimumNumberOfProcessors": 2

"coverInstallsOnVirtualMachines": false,
"limitNumberOfVirtualInstalls": false,
"limitVirtualInstallsIncludesHost": true,
"minimumNumberOfThreadsPerVM": 4

"rules": {
  "virtualization": {
    "calculationType": "limitedVMs",
    "hosts": {
      "virtualMachines": {
        "coverage": {
          "count": 20,
              "includeHost": false
          }
        },
        "cores": {
          "minCount": 16,
          "minCountPerProcessor": 8
        }
      }
    }
  }
}

Flexera permissions

The account that Turbonomic uses to connect with a Flexera target must be a Read-Only account with the following roles:

• View IT assets

• call APIs

Adding Flexera targets

1. Click Settings > Target Configuration.

2. On the Target configuration page, click Add Target.

3. On the Select target page, click FlexNet Manager or FlexeraONE.

4. In the side panel, review the connection requirements and then click Connect Target.

5. Configure the following settings:

   For Flexera One:

   • Display name

     Specify a name that uniquely identifies this connection.

     This name is for display purposes only and does not need to match any name in Flexera One.

   • Address

     Specify the fully qualified domain name or IP address of the Flexera One platform.

   • Organization ID

     Specify the unique identifier that defines your organization within Flexera One.

   • Refresh token

     Specify the API refresh token that Turbonomic uses to generate access tokens for OAuth authentication. Learn more

   • Connect using HTTPS

     If you select this option, Turbonomic connects to the target servers using HTTPS. Make sure that the required certificate is configured for use on the host.

     HTTPS is enabled by default and cannot be modified.

   • Proxy configuration

     Specify proxy information only if you connect through a proxy.

     • Proxy hostname or IP address

       Specify the address of the proxy used for this target.

     • Proxy port

       Specify the port to use with the proxy used for this target. By default, the port is 8080.

     • Proxy username

       Specify the username to use with the proxy.

     • Proxy password

       Specify the password to use with the proxy.

     • Connect using HTTPS

       Select this option if Turbonomic will connect to the proxy through HTTPS.

   For FlexNet Manager:

   • Display name

     Specify a name that uniquely identifies this connection.

     This name is for display purposes only and does not need to match any name in FlexNet Manager.

   • Address

     Specify the fully qualified domain name or IP address of the FlexNet Manager Suite platform.

   • Username

     Specify the local Windows Server username. For example, domain\user.name.

   • Password

     Specify the password of the account Turbonomic uses to connect to the target.

   • Connect using HTTPS

     If you select this option, Turbonomic connects to the target servers using HTTPS. Make sure that the required certificate is configured for use on the host.

     This option is selected by default.

   • Validate server certificates

     If you select this option, Turbonomic verifies the target certificate and proxy, if in use.

     This option is selected by default.

Actions

Turbonomic does not generate unique actions for entities it discovers through a Flexera target. Instead, it uses the license specifications it discovers in Flexera to prevent actions that do not comply with license restrictions. It can also modify or generate actions to ensure license compliance.

When Turbonomic generates an action, the action details include a list of policies that constrain the action recommendation. In this list, policy names that begin with Flexera: indicate policies that implement the license constraints Turbonomic has discovered for Flexera. You can click to navigate to the policy definition. Note that you can see the policy definition, and you can only enable and disable it. The status remains the same across target and policy rediscoveries, and disabled policies do not affect actions.

The policies that Turbonomic generates affect Turbonomic actions in the following ways: