An flrclient_template.xml file is provided in the “licenses” folder as part of the NiagaraAX Supervisor default installation. In order to retrieve
a license, you need to rename this template file to flrclient.xml and edit the <flr> and <packmap> attributes as described below. The flrclient.xml file provides the information that the NRE license manager requires to locate the FLR and a set of application-to-license-pack
mappings that the NRE uses to determine which license it should lease from the FLR.
When starting up an NRE application, the NRE license manager looks for a valid flrclient.xml file. If a valid file is not found, the license manager looks next for a standard node-locked license.
The following list includes brief descriptions of the required elements in the flrclient.xml file:
-
<flrclient>
This top level element contains all other elements in the file.
-
<flr>
Use this element’s attributes to define the FLR server address and port, as described below:
The flrclient.xmlfile may contain multiple FLR configurations (specified by multiple <flr> elements) so that you can distribute license request loads, if desired. Also, you can edit the flrclient.xml file at any time to add, remove, or update flr configurations.-
host
Type in the ip address of the FLR server (see Figure 4)
-
port
Type in the FLR port number. This number is defined in the FLR server’s license pack file (see Figure 4 and About the license pack file (LPF)).
-
-
<packmap>
Use this element to identify the NRE application and complementary license pack name
-
app
Type in the name of the app (see Figure 4). Note that the app names for Workbench and Station allow a convenience abbreviation “wb” and “station”, respectively. Other applications require the full java class name.
-
pack
Type in the name of the app, as defined in the license pack file. The value for this attribute is specific to your organization.
-