Acquire licenses for backend applications

Acquiring licenses for backend applications including the terminal services could be challenging due to several reasons, such as:

• Not possible to reserve licenses in terminal services session

• Unable to acquire a specific part number as multiple part numbers can exist for the same product

• No support for user-based reservations in InTouch

You can mitigate these challenges by creating the .avevalic configuration file and specifying the preferred part number to be acquired.

Create the .avevalic configuration file in the specific folders, and update the part numbers details. These part numbers will be automatically considered for license acquisition.

Note: License acquisition by specifying the part number details in the .avevalic configuration file is valid for terminal servers only at the time of this release.

Create the .avevalic configuration file

You can create the .avevalic configuration file locally at your own %USERPROFILE% directory. Alternatively, you can create a global.avevalic configuration file at C:\Program Data\AVEVA\Licensing.

1. Navigate to the location depending on the type of configuration file you want to create.

   • For a local configuration file, navigate to the %USERPROFILE% directory.

   • For a global configuration file, navigate to C:\Program Data\AVEVA\Licensing\.

2. Right-select anywhere in the folder and select New > Text Document.

3. Rename the new text document to .avevalic

   In some cases, if you are not able to save the file name as '.avevalic' (dot avevalic), you can name the file as '.avevalic.' (dot avevalic dot).

   Note: The .avevalic file available in %USERPROFILE% has precedence over the global .avevalic file located under Program Data.

Update the .avevalic file

To update the .avevalic configuration file with the details of the part numbers, follow the rules below:

• In the case of multiple part numbers, update the part numbers in the First-In-First-Out (FIFO) order.

• Separate multiple part numbers using a comma (,).

• Part Numbers entry can contain an asterisk ‘*’, but it should not be used in the first or second part of the part number.

  • When ‘*’ is used, the characters preceding the '*' are considered for matching, and the characters succeeding '*' are ignored.

  • If Part Numbers do not contain '*', then the whole part number is considered for matching

• Specify a user for each part number. Part numbers specified without a user will be applied for all the users.

• If a Part Number is invalid, it is logged as invalid and the next part number is considered for matching.

If any process is running as a service without an interactive user, the global configuration file and the part numbers available without a user map will be considered.

Sample .avevalic file

A sample.avevalic file can have the data as below:

Global .avevalic file

A sample global .avevalic file contains the part numbers as follows:

wwuser=Itch-05-n-17,Itch-10-n-17

wwuser2=Itch-04-U*

Itch-04-S-20, Itch-05-S-*

Hist-05-N-20

Itch-07-*-20

Local .avevalic file

The local .avevalic file contains the part numbers as follows:

Itch-30-*

Itch-04-S-20, Itch-05-*-20

Itch-10-*

Itch-04-N*