Embedded Devices Settings
Name
Possible Values
Description
Rqd?
Device Response Lifetime
Value in seconds
Lifetime, in seconds, for device responses generated when a device request is received. If set to zero, responses will never expire.
*
Confirm Add-On Copies Reduction
Checked or unchecked
When checked, this option requires a device to send a confirmation message to verify that returned add-ons have been removed from the device. Without the confirmation message, FlexNet Operations will not mark the add-ons as returned.
Default: Checked.
Request Handler Classname
classname
This is the class that implements the com.flexnet.opsembedded.publicapi.DeviceRequestHandler interface. It will be used to process the vendor dictionary in device requests and fill in any dictionary entries on responses.
Device Handler Classname
classname
This is the class that implements the com.flexnet.opsembedded.publicapi.DeviceHandler interface. It will be used to validate changes to a device’s add-ons and validate and decode device IDs. For more information, see the FlexNet Operations Implementation Guide.
Allow Adding Unknown Devices
Checked or unchecked
When checked, allows unknown devices to be added either via the portal or through device requests, either on- or off-line. If adding unknown devices is permitted, publishers need not prepopulate the devices in FlexNet Operations (from another inventory system, for example).
This setting allows end users to enter a device ID via the self-service portal or capability request file. The system creates the device and calls the device handler class. (You must code the device handler class to configure the device attributes accordingly.)
Note: You must provide a method to set the host type for users to be able to successfully add an unknown device. Some possible methods include:
| • | Enable the Display Host Types configuration setting. |
| • | Define default host types (server and/or client). |
| • | Implement the device handler class to set the host type based on the device ID. |
| • | Configure the device to include a host type in the request. |
Default: Unchecked.
Allow Adding Redundant Server
Checked or unchecked
When checked, allows a redundant server to be added either via the portal or through administrative console. The redundant FlexNet Embedded server provides failover support. The end user can specify two server IDs as valid hosts, and the server will run on both of those hosts.
Default: Unchecked.
Note: Enabling this setting can negatively impact FNE activation performance.
Allow Client Alias Editing
Checked or unchecked
When checked, allows client aliases to be edited in the self-service portal.
Default: Unchecked.
Display Host Types
Checked or unchecked
When checked, causes both the administrative console and the self-service portal to show a list of available host types on the Create a Device page. Users can then select the host type for a new device from a list of host types.
Default: Checked.
Device Usage Summary Job Recurrence
Disabled, Daily, or Hourly
Determines how often (daily or hourly) current license usage is summarized for all served client devices. Setting this option to Disabled prevents the summarization job from running.
Default: Disabled.
Usage Summary Job Hour
0-23
Hour of daily license usage summarization. (Only used if Device Usage Summary Job Recurrence is set to Daily.)
Default: 0.
*
Usage Summary Job Minute
0-59
Minutes after the hour of hourly or daily license usage summarization.
Default: 0.
*
Device Usage History Cleanup Job Recurrence
Disabled, Monthly, or Daily
Determines how often (monthly or daily) the usage history cleanup job runs. When this job runs, it trims the history of the current license usage for all served client devices.
Default: Disabled.
Usage History Cleanup Job Day
1-31
Day of the month for monthly usage history cleanup. (Only used if Device Usage History Cleanup Job Recurrence is set to Monthly.)
*
Usage History Cleanup Job Hour
0-23
Hour of daily usage history cleanup. (Only used if Device Usage History Cleanup Job Recurrence is not disabled.)
Default: 0.
*
Usage History Cleanup Job Minute
0-59
Minutes after the hour of daily usage history cleanup. (Only used if Device Usage History Cleanup Job Recurrence is not disabled.)
Default: 0.
*
Kept Days of Usage History
The number of days usage history information is retained. When the usage history cleanup job runs, events older than the number of days you specify here are deleted from the usage history records.
Default: 31.
*
Server Sync Message Processing Timeout
1-30
The number of minutes FlexNet Operations waits before forcing the processing of queued server sync messages.
Default: 2.
Server sync messages are processed as a batch. As FlexNet Operations receives sync messages, it queues these messages for processing. Sync message processing can be initiated in two ways:
| • | FlexNet Operations receives an empty server sync message from an FNE server (version 4.1 or later). FlexNet Operations interprets the empty message as a request to process all queued server sync messages. |
| • | The number of minutes elapsed since the last (non-empty) server sync message was received equals the Server Sync Message Processing Timeout value. |
*
Include Start Date
Checked or unchecked
Include the Start Date attribute in generated licenses for devices.
Default: Checked.
Include Issued Date
Checked or unchecked
Include the Issued Date attribute in generated licenses for devices.
Default: Checked.
Default Client Host Type
FLX_CLIENT or specify
The default host type FlexNet Operations uses when creating an unknown client device from a request, if the request does not specify a host type. This value is also used when registering a client device from the self-service portal, if not supplied by the request, the portal UI, or a call-out.
Default: FLX_CLIENT.
Default Server Host Type
FLX_SERVER or specify
The default host type FlexNet Operations uses when creating an unknown server device from a request, if the request does not specify a host type. This value is also used when registering a server device from the self-service portal, if not supplied by the request, the portal UI, or a call-out.
Default: FLX_SERVER.
Short Code Request Encoding
Base 10,
Base 16,
Base 34,
Base 36, or
Custom
The type of encoding to use for keyboard activation requests (FNE-based short code requests). If you specify Custom for this setting, you must also specify a value for Short Code Request Character Set.
Short Code Request Checksum Segment Size
numeric, greater than 1
The number of characters per checksum segment (including the checksum character) in the keyboard activation request. If zero, no checksum characters are inserted.
*
Short Code Request Character Set
character set
When the Short Code Request Encoding is set to Custom, this is the character set to use when encoding the request. The characters in the character set can be almost any alphanumeric string of characters—provided there are no duplicate characters present. For example, 0123aBc. The length of the character set determines the base. And the length of the request must be 2000 characters or less.
Short Code Response Encoding
Base 10,
Base 16,
Base 34,
Base 36, or
Custom
The type of encoding to use for keyboard activation responses. If you specify Custom for this setting, you must also specify a value for Short Code Response Character Set.
Short Code Response Character Set
character set
When the Short Code Response Encoding is set to Custom, this is the character set to use when encoding the response. The characters in the character set can be almost any alphanumeric string of characters—provided there are no duplicate characters present. For example, 0123aBc. The length of the character set determines the base. And the length of the response must be 2000 characters or less.
Short Code Response Checksum Segment Size
numeric, greater than 1
The number of characters per checksum segment (including the checksum character) in the keyboard activation response. If zero, no checksum characters are inserted.
*