Creating an FNE Server with Extended Host ID
A license server with an extended host ID can be created
|
•
|
at the back office using the FLX_HOSTID_TYPE_EXTENDED hostID type with a capability request, or |
|
•
|
through the FNO user interface by specifying the EXTENDED ID type, if it is made available. |
It is recommended for this deployment model that the FLX_HOSTID_TYPE_EXTENDED hostID type be allowed only for publisher-defined custom host types. This enables easy identification of, and searching for license servers that use the FLX_HOSTID_TYPE_EXTENDED hostID type, and prevents its misuse on typical license servers. FNE license servers must enable the FNE_SERVER_EXTENDED_HOSTID_ENABLED server property and include the publisher-defined custom host type in the capability request to the back office. See About Extended Host IDs for more information about extended host IDs.
There are three ways to configure a license server with an extended host ID; they are not mutually exclusive, and all can be configured. The procedures are arranged from least to most configuration required.
To create a server device with a capability request from the local license server
|
1.
|
On the Administer Operations page of the FNO administrative console, click System Configuration > Embedded Devices. |
|
2.
|
On the Embedded Devices configuration page, select the Allow Adding Unknown Devices check box. |
|
3.
|
Click Save Configs to save the change. |
By default, the EXTENDED ID type is one of the supported FNE ID types excluded from the FNO user interface (in other words, that cannot be assigned to a host type through FNO). Even though it is excluded from the user interface, FNO creates a device with the EXTENDED ID type if the capability request from that device specifies EXTENDED as its ID type. The device is created using the default server host type and EXTENDED ID type. The device hostID is assigned according to the configuration file in the local license server.
To create a server device, before the local license server connects, using the default server host type
|
1.
|
Create or locate the custom directory in the <ops_install_dir> directory. |
|
2.
|
If it does not already exist, create the following directory structure in the custom directory to mimic the properties file path in the site directory: webapps\flexnet\WEB-INF\classes. |
|
3.
|
In the ops_install_dir\site\webapps\flexnet\WEB-INF\classes directory, locate the FLEXnetProdCustomizableText_en.properties file you want to customize. Copy it to the custom\webapps\flexnet\WEB-INF\classes directory. |
|
4.
|
In the ops_install_dir\custom\webapps\flexnet\WEB-INF\classes directory, customize the FLEXnetProdCustomizableText_en.properties file to show the EXTENDED ID type on the FNO user interface: |
|
a.
|
Open the properties file in a text editor. Search for the line that begins with excludedIdTypes= and remove EXTENDED from the comma-separated list of excluded ID types. |
|
b.
|
Save the modified file. |
|
5.
|
In the <ops_install_dir> directory, type flexnet stop to stop FlexNet Operations. |
|
6.
|
In the <ops_install_dir> directory, type flexnet site make to load the customized FLEXnetProdCustomizableText_en.properties file into the site directory. |
|
7.
|
In the <ops_install_dir> directory, type flexnet start to restart FlexNet Operations. The EXTENDED ID type is available on the user interface after FNO is successfully started. |
|
8.
|
Allow the EXTENDED ID type to be assigned to devices with the default server host type through the FNO user interface: |
|
a.
|
On the Administer Operations page of the Administrative Console, click Manage License Technologies to open the License Technologies page, then click FlexNet Licensing. |
|
b.
|
On the Create a License Technology page, click FLX_SERVER to open the Create Host Type pop-up window. |
|
c.
|
In the Create Host Type window, select the Extended check box and click OK. |
It is the user’s responsibility to create the device with the hostID that matches the local license server configuration. If server devices are created only through the FNO user interface, it is not necessary to configure FNO to allow unknown devices to be added.
To create a server device host type exclusively for field engineer use
This is an extension of the previous procedure. A host type with an assigned ID type of EXTENDED is created exclusively for field engineer use.
|
2.
|
Instead of (or in addition to) adding the EXTENDED ID type to an existing host type, create a new host type exclusively for field engineer use and assign the EXTENDED ID type to it. When creating the host type, decide whether to allow devices with this host type to be created in the Self-Service Portal. |
|
a.
|
On the Administer Operations page of the Administrative Console, click Manage License Technologies to open the License Technologies page, then click FlexNet Licensing. |
|
b.
|
On the Create a License Technology page, click the Add Host Type button to open the Create Host Type pop-up window. |
|
c.
|
In the Create Host Type window, enter an appropriate name and optional description for the new field engineer host type, and set the publisher identity. |
|
d.
|
Select the Visible on Self-Service Portal? check box if you want to enable portal users to create devices with this host type. |
|
e.
|
In the Device ID Types table, select the Extended check box, select the Default radio button, and click OK. |
It is possible to search for devices in the FNO user interface by host type (but not currently by ID type). The local license server passes the host type in its capability request. If server devices are created only through the FNO user interface, it is not necessary to configure FNO to allow unknown devices to be added.
See Also
About Extended Host IDs
Restoring a Served Client
Open topic with navigation