5.2 Configurations Available in Settings Window.
In this section, we describe the configurations available in (Server) Settings window. It opens when you click on the settings button on the global menu.
5.2.1 Setting the Data Retention policy
netLD stores all configuration data unless specified. However, it causes the size of the database to increase in the long run. You can set an expiration period of the data to avoid this problem. The configuration is available in Data Retention menu.
In Delete expired data weekly at this time, you can configure which timing you want to remove the old data. The rest determines just as it says:
• Duration to keep configuration history
• Duration to keep terminal proxy history
• Duration to keep job execution history
5.2.2 System Backup and Restoration
All netLD internal data are saved in derby and lucene sub directories (and also pgsql after version 14.06) under the netLD installation directory. netLD provides a convenient backup & restoration feature for those configurations. System backups can be scheduled and runs automatically.
In System Backup settings, you can modify the following contents:
Menu Items Description
Enable daily system backup Enable this checkbox to enable daily system backup.
Perform the system backup at Specify the time to perform the system backup.
this time Number of backups Specify the number of backups (7, 14, and 30)
to keep Backup directory to keep in the local server
Specify a name of the directory that the back up
files should be saved.
Perform System Backup Now Click on this button to execute a system backup.
Backup data will be saved in a directory named backup yyyy-mm-dd,where yyyy,mm,dd corresponds to year, month and date, respectively. The default directory is <installdir>/backups,but you can also save the backup into the other path (e.g. D:ˇbackups).Backup data can be saved only in the local disks.
2 These settings are independent of the backup schedule for the device configuration.
Figure 5.2.1: Data Retention settings menu
Restoring the Backup Data
Note that there is no compatibility of the saved data between the different versions of netLD. This is usually not a problem because, when netLD is upgraded to a new version and it has some backup data, they are automatically migrated to the new version.
The problem occurs when you move or store the saved data manually. One such situation is when you want to migrate the settings to the new machine. In this case, you should be careful about the compatibility.
To migrate the setting data manually, follow the instruction below:
1. Stop the running netLD service in the new and the old servers.
2. Copy derby and lucene (and pgsql after version 14.06) sub directories (cf. Sec. 7.2, p.231) from the old server and save them into the netLD install directory of the new server.
3. Start netLD service in the new server.
5.2.3 Mail Server
You can set an SMTP server to allow netLD to send E-mails. Following configurations are available.
Figure 5.2.3: Mail Server section in settings window
Menu Items Description
Mail server host name or IP address The mail server by host name or IP address.
From email address The sender email address.
From name The sender name.
Server requires authentication Enables the server authentication.
Mail server username Mail server username for the authentication.
Mail server password Mail server password for the authentication.
5.2.4 Changing the Data Directory in Operation
You can customize not only the backup directory but also the current setting directories, while it requires some amount of operations.
1. Stop the running netLD service (via CLI, Service Manager or Task Tray. see
Sec. 2.6)
2. Copy derby and lucene subdirectories (cf. Sec. 7.2, p.231) to the destination directory, E://nlddata for example.
3. Open Net LineDancerˇosgi-configˇconfig.iniand find the following line:
netld.datadir=
Append the destination directory path to the line:
netld.datadir=E://nlddata
4. Start netLD service in CLI. (e.g., net start netld)
5.2.5 netLD RADIUS External Authentication
netLD provides the ability for users to be authenticated using an external Remote Access Dial In User Service (RADIUS) server. This guide will explain how to configure netLD to enable this integration.
Requirements
In order to run the RADIUS integration you must have a RADIUS capable server like Microsoft Active Directory or FreeRADIUS. The netLD server and RADIUS server must also be able to communicate using UDP on port 1812.
Configuring RADIUS
In order for netLD to be able to authenticate, the RADIUS server only needs to be configured to handle Access-Request packets. After sending an Access-Request to the RADIUS server, netLD will listen for an Access-Accept response. The response should contain one or more Filter-Id attributes.
Here is an example configuration for a user named ”jdoe” in FreeRADIUS. . .
jdoe Cleartext-Password := "password"
Filter-Id += "role:Administrator",
Filter-Id += "networks:*",
Filter-Id += "customFields:1,2,3,4,5"
This configuration tells FreeRADIUS that for an Access-Request for a user named ”jdoe” to match the password ”password”. If the password matches an Access-Accept response will be sent with three Filter-Id attributes set. These three Filter-Id attributes control the access the user is granted.
Name Required Description
role Yes The name of the netLD role to assign to this user.
networks No A comma separated list of the managed networks
visible to the user. (Use ”*” to grant access to all networks)
custom Fields No A comma separated list of the custom fields
that should be visible to the user.
Configuring Net LineDancer
To configure RADIUS authentication you must tell netLD the hostname and shared secret for communicating with your RADIUS server. The RADIUS config- uration settings can be found in the Server Settings window.
Here you can enter the hostname or IP address of the RADIUS server and the shared secret to use when making requests. You can test if the settings are correct by entering a test username and password into the Test Authentication area. Clicking the Test button will cause netLD to attempt an Access-Request against the specified server.
To enable the RADIUS integration check Allow authentication using an exter- nal RADIUS server and click on OK.
5.2.6 Changing the Column Names of Custom Device Fields
You can add arbitrary texts in the custom fields of the devices. In order to modify the value of custom field in each device, see Sec. 3.3.4. In this setting section, you can customize the titles of Custom Device Fields.
5.2.7 Launchers (URL Launchers)
In this setting section, you can create shortcuts to access certain URLs defined by the device in the right-click menu which appears in the inventory.
If you set a URL Launcher template (IP Address for example), an IP Address button appears in the right-click menu in Device View. When you click on it, the template is instantiated with the device information, and the browser opens the result URL.
To add such a launcher, click on 
to insert the entry to the list. The URL may contain some specific patterns surrounded with braces {} which are substituted with the actual value of each device.
Figure 5.2.4: External Authentication section in Server Settings window.
{device.ipAddress} in the URL of that entry is substituted with an actual IP address 10.0.0.1.
Those patterns are added via ← buttons in URL Variables.
5.2.8 Network Servers
In Network Servers, you can modify the settings for Login Idle Timeout and Server Primary IP Address.
Login Idle Timeout
Login idle timeout for netLD console is set to 30 minutes by default. You can change it in the Network Servers. Follow the instruction below.
Disabling this feature is not available because it is a bad practice with regard to the security. If someone get the configuration data while an administrator is leaving his desk for a while, it causes a serious system abuse. However, if you really want to do it, you are still able to achieve virtually the same results by setting the maximum value (526,000).
To change the value, change the number of minutes in User login idle timeout (minutes) dial box. Click on the OK button to save the value.
Figure 5.2.6: URL Launchers
Figure 5.2.7: Network Servers
netLD primary server IP address will be automatically detected when the program is launched. To change the value, use Server Primary IP Address pull down list to change the IP address and click on the OK button.
Restart Required dialog will show up. Click on the Yes button to restart the server and apply changes in the settings.
Changing the HTTPS port (Windows version only)
Enable Host the HTTPS web client on a non-standard port checkbox and change the port number, and click on the OK button.
Click on the Yes button in Restart Required dialog to restart netLD server. Reference: Sec. 7.1, p.230
5.2.9 Software Update
netLD automatically checks for updates and notifies if any updates are available, including adapter or manual updates. Automatic update notification needs an Internet connection.
Usually you will find the update notified on the top of the screen.
1. Click on the Install Update button to update. Click on the Yes button to confirm starting the update.
2. Download starts automatically. When the update is complete, netLD service restarts, and then the new login screen appears.
Downloading the updates.
