iDashboards can be accessed through a Desktop Application, which requires an installation on each client computer.
After installing the application, it is required to configure a server. While this process is not difficult, it may be desirable to manage the deployment of the iDashboards Desktop Application for mass-distribution. In this event, consider bundling a server configuration file to auto-populate the Desktop Application with pre-configured servers, URLs and even usernames!
A minimum version of iDashboards is v9.5d
A minimum version of the iDashboards Desktop Application is v1.2
- First, it is necessary to have a file called "idashboards-desktop-servers.xml". Attached to this post is an example file or below is the content of the example file. Review the property definitions as described below. Everything is case-sensitive.
- Next, place this file into the user's home directory. On a Windows computer, open File Explorer and enter %HOMEPATH% into the address bar. On my computer it was simply "C:\Users\krose". Other Operating Systems can use their own directories.
- Lastly, open (or close and reopen) the iDashboards Desktop Application (which will now import the configuration from the file). For this to work, the exact file name, in the exact folder location, using the exact syntax, will be required.
It's fairly easy, although it can get complicated if you need to repeatedly test or update this process. Read the rules surrounding the <fileId> element if you don't think your desktop application is correctly reading the values. Usually you'll have to increase the <fileId> number by at least '1' for each launch. Once you get your configuration file dialed in, it is not necessary to keep the file in the home directory...that's why there's an option to <deleteOnLoad>.
|<?xml version="1.0" encoding="UTF-8"?>
<displayName>iDashboards Cloud Evaluation</displayName>
- Cannot be empty or contain spaces
- This element accepts any characters, but best practices encourages numeric values
- This field is similar in concept to a version number. Enter a random number, like "3", and iDashboards will identify the 1st launch of the Desktop Application as the value "3". The next launch of the Desktop Application (#2) will check the <fileId> value:
- If "3", do not read anything else in the configuration file
- If "4", import the new configuration settings
- If the 'current' value is the same as a 'previous' value, the entire file will be ignored
- This element is option (default/empty value is 'false')
- This element, when set to "true" will delete the XML file and retain an encrypted version on each local machine. This will result in the file only being used once.
- Use this to define one or more <server> elements (see item below)
- Repeat each <server> element to configure multiple servers
- Add/Remove server configurations here. The sub-fields <url> and <displayName> are minimum requirements for each configured server
- This is the URL for the User Application, originally used with a browser and Adobe Flash player plugin
- If a URL in the configuration file is already configured in the Desktop Application, no import will be taken on that server item
- This element will display the friendly name used to identify each server
- This field can be empty
- Must be used in conjunction with the <password> field
- This field can be empty
- Must be used in conjunction with the <username> field
- This element will control whether or not to connect to the server when the Desktop Application is opened. When set to "true" the server connection will immediately open after the Desktop Application is opened.