The administration tab is divided into multiple sections covering a variety of administrative actions, as detailed below.
In this section, a new license file can be uploaded when provided by Heimdall, and the current settings and license use can be observed. In Demo mode, up to 4 LB servers can be used, and up to four VDBs with rules (optimizations) can be enabled for 30 days. The used count is only based on VDBs that have received traffic in the last 30 seconds, so will dynamically account for activity. If the used values surpass the allowed values, then a warning will be displayed on the console, but no restriction in features will be enforced. License handling is strictly advisory, i.e. while the system may complain about a license being invalid, it will not restrict what is done, to insure no outages occur as a result of licensing.
Note: When using an AWS paid-for instance, the proxy use on the instance will not count toward license use. Additionally, added paid-for instances can be reconfigured to be a pure proxy instance and will also not count to license use on another management server.
Log File Management
This section is provided to assist in managing log files, and the options should be self explanatory.
The first component of this is a drop-down list of update paths that an update can be triggered for. LTS is the Long-term support release build set, Latest release is the latest full feature release, and test is a test version which may format your HD, causing data corruption or loss, and possible changes in marital status. You are warned.
The second is the shutdown/restart Heimdall button, which will not explicitly trigger a restart, but will rely on any restart mechanisms on the server to trigger the actual execution of the server after it terminates.
The third is the release notes link, for the most current release notes, and finally, an option to download the Heimdall driver.
Note, for command line manual update, please do the following:
1) copy the file into the install directory as heimdall-new.zip 2) cd to install directory 3) execute the following commands:
* sed -i "s/\s*\"modules\/.*\",*//g" config/heimdall.conf * unzip -j heimdall-new.zip * unzip -j heimdall-new.zip
4) kill and restart the heimdallserver.jar process: ps auxw | grep heimdallserver.jar root 4198 0.0 0.0 6100 624 pts/0 S+ 18:03 0:00 grep --color=auto heimdallserver.jar root 26005 30.8 4.0 9679444 638504 ? Sl 17:58 1:25 java -server -XX:+HeapDumpOnOutOfMemoryError -jar /opt/heimdall/heimdallserver.jar
This section provides a list of any alerts that have been dismissed with the check. Any alerts in this list will not be shown in the top of the GUI until cleared.
This provides the login times, account ID and source IP of the recentally recorded GUI logins.
This section allows a cache driver (specifically Hazelcast) to be uploaded for use by Heimdall instead of the built-in driver. This allows the driver to match what may exist in a customer's environment if our version causes a conflict.
These are properties that can control overall Management server behavior, and will be added to over time. Current properties supported.
- Disable Google Analytics: This will disable the external calling to Google analytics to provide metrics on server usage. All such data is anonymous.
- Max Log Age: Sets the maximum age in days of log files and log records
- Reserved Disk Space: Sets the amount of FREE memory to maintain on the log filesystem
- Verbose Debug Mode: On the server, enable verbose debug mode
- Proxy Host: If a proxy is needed to access the Internet for code update notifications and downloads, the host to use for this
- Proxy Port, Proxy User & Proxy Password: Settings to configure the proxy behavior. The port defaults to 3128, no default for the others.
- Minimum free disk space %: configured how much space needs to be free for any configuration saves to occur. Defaults to 1 for 1%. This helps prevent configuration loss if not enough space is available to successfully save the full configuration.
This section allows configuration management filters to be created, which can then be used optionally by users, or enforced on them in the user's tab. The filters insure they can not access or create configuration objects with names that do not meet the specified regular expression. This applies to VDBs, Data Sources, Rules, and Drivers. Analytics and Logs will also be filtered based on the resources they are relevant to by the filters, to prevent data leakage. The dashboard will also be filtered based on this. The two primary use cases are:
- forced segregation of resources on particular users;
- optional enforcement to allow grouping of resources, simplifying the display for groups of resources. This can also be used to help ensure that newly created objects meet naming guidelines implemented by an organization.
When a user is not forced to use a particular filter, then the filters will be available in the upper right-hand corner of each page to allow them to be changed on the fly:
Allows modules to be added or removed as needed. The fewer the modules, the faster a Heimdall node can startup. In particular cache modules that are unused should be deleted as some can add significant load time.