System Settings
This page displays global TagNet settings and the ability to change those settings as shown below:
RFID Version |
|
The installed TagNet version on your Server. Note: the date is important as there can be multiple versions of the same releases (i.e. beta1, beta2, final, etc.) |
|
|
Enable RFID Tracing |
|
Either turned on (*YES) or off (*NO). This setting controls whether low level logging should take place for problem determination. If *YES a number of trace files are created (Service.txt and transport.txt) for each Read Event Cycle as they occur. This is NOT to be confused with EPC Event History or Reader Activity. Note: these trace files are intended to be reviewed by Stratum Global Tech support or an authorized Stratum Global Partner. These are not intended for user interpretation as they are quite complex |
|
|
Enable FTP Tracing |
|
Either turned on (*YES) or off (*NO). This setting controls whether low level FTP logging should take place for problem determination. If *YES a number of Trace files will be generated (Service.txt in addition to files with .FTP extensions). |
|
|
Enable XML Tracing |
|
Either turned on (*YES) or off (*NO). This setting controls whether low level XML logging should take place for problem determination. If *YES a number of Trace files will be generated (Service.txt in addition to files with .XML extensions). |
Network Latency |
|
Introduces a latency factor (in milliseconds) into TagNet RFID event processing. This setting adjusts the speed at which consecutive HTTP requests are sent to the HTTP Server. Some HTTP Server software (such as MS IIS) cannot process repetitive requests quick enough without failing. Note: Shipped default value is 100m. A value of < 20 msec is not recommended as this is simply too quick for most HTTP servers to deal with |
|
|
Sensor Latency |
|
Introduces a latency factor into TagNet reader GPIO polling to lessen the Server overhead when listening on the input stream. Note: Shipped default value is 100ms. A value of < 10 msec is not recommended as it can put a heavy load on the TagNet Server CPU. |
|
|
Response Latency |
|
The time specified that TagNet will wait before polling the reader for a TagList (within the Read Event Cycle). This value has a significant impact on Server performance when managing many readers. Even a value of 10ms will show an improvement in overall server performance. Note: When polling data from the reader and the reader is not ready yet, a delay is made equivalent to the value of the response latency before attempting to poll data again. |
Enables up to ‘x’ number of recovery attempts if a fatal error is detected before shutting down a given Reader schedule. Examples of errors would be a) TagNet cannot see the reader and there is a connection timeout or b) Binding function fails on API call, etc. Note: a value of '999999' indicates that TagNet will continue to attempt recovery until the reader is back online. |
|
|
Maximum Records to Search |
|
This value is used for the Tag Event Viewer to limit the search up to ‘X’ number of records to maintain an acceptable level of performance. |
|
|
Item Search Option |
|
This value is used to condition Product/Asset searches from mobile AssetTrack. When using certain DBMS like MS SQL Express set the value to ‘No Upper Case’ otherwise keep this value set to null. |
|
|
High Volume Data Access |
|
Setting this value to SQL improves overall performance when paging through large Product or Asset Masters (Object Maintenance) and PI Master / Session synchronization |
|
|
Previous Event Cycles for Binding |
|
This value is used when matching tag types during a directional portal binding function. For example; if the user badge tag is seen first, it will look back ‘X’ read event cycles to see if there was a matching asset tag (or visa versa). This is used in function RFDBHLR only. |
|
|
Time Interval for Binding |
|
This value is used for certain binding functions when a matching pair of tags is recycled for another read event cycle |
|
|
Password Include Numbers |
|
Specifies whether the password must include numbers (valid values are none -3) |
|
|
Password Include Symbols |
|
Specifies whether the password must include special characters (valid values are none -3) |
|
|
Use Single Sign-On |
|
Enables the integration with Active directory to automatically logon User to TagNet if that network login is referenced in their user profile |
|
|
Enforces basic referential integrity rules when attempt to add or modify Tag Mapping associations |
|
|
Default Location |
|
Specifies the default location location for certain Bindings (must match the location matrix up to 5 parms) |
|
|
Event Binding Extract Folder |
|
The path used by TagNet schedules to send FTP binding extracts. The shipped default value is C:\TagNet\rfid\binding\ |
|
|
The path used by the Reports function to send generated reports. The shipped default value is C:\TagNet\rfid\reports\ |
|
|
The path used by the Label printing function to retrieve Label formats (.btw & .zpl). The default value is C:\TagNet\rfid\labels\ |
|
|
Image Capture Folder |
|
The path used by the Image capture feature to store images as RFID events occur. The default value is C:\TagNet\rfid\capture\ |
|
|
The path used by TagNet to store Physical Inventory Count sessions that are being saved and restored to different handhelds. The default value is C:\TagNet\rfid\backup\ |
|
|
The path used by TagNet to store repository data during v7to v8 upgrades or to export/import selective data between TagNet instances. The default value is C:\TagNet\rfid\system\ |
|
|
Company Name |
|
Enter the name of your organization. Displays in a number of areas including reports and function titles. |
|
|
Either a *NO or *YES response to enable the automatic notification of TagNet errors via email (see related below). |
|
|
SMTP User Name |
|
Valid email account on the SMTP Server to enable sending of outbound email notifications. This can be a generic email 'Service Account' based on the polices of your organization |
|
|
SMTP From Address |
|
Email address of the ‘sender’ of email notifications. This address should be meaningful as to where the email alert is coming from (e.g. Server name) and can be an email 'Service Account'. Note: Most email servers such as Outlook or SharePoint will not accept an unqualified email address as the sender. |
|
|
SMTP Recipient |
|
The email address to receive the email notifications. Multiple recipients can be specified delimited by a (;) as shown, or it can be a distribution list as setup on your email server. |
|
|
SMTP Encryption |
|
Used in conjunction with the above, specifies the encryption method (*TLS or otherwise leave blank) |
|
|
Copyright © 2024 Stratum Global, Inc.