Visual KPI Configuration
Visual KPI Instance
In Server Manager, select Default Web Site in the explorer panel. Right click on Default Web Site and select Install New Visual KPI Instance from the context menu.
In the Setup Wizard click Next.
Accept the license agreement and click Next.
Leave the Trial License license key in place, or enter your license key in the License Key field. Then click Next.
Enter a name for your Visual KPI instance in the Visual KPI Instance Name field. Leave the Regional Settings as default, which is the detected server language. Click Next.
Leave the installation path as default, and click Next.
Enter the credentials for the database connection of Visual KPI. Note that these credentials need to be allowed to create and delete databases on the selected SQL server instance. Click Next. Setup will only continue, if the connection could be established.
Enter the site administrator credentials (Name and Email). Change the Notification Protocol to None, and click Next.
Select the No option to not install the sample data and click Next.
On the installation summary page, click Next.
Once the installation has been successfully completed, click Finish.
Visual KPI Interface
Go to the Server Manager and select the Interfaces node below the installed instance. Right click the Interfaces node and select from the context menu.
Click Next to begin the interface installation.
Accept the license agreement and click Next.
Enter a Name for the inmation Interface of the selected Visual KPI instance and click Next.
Leave the installation path default, and click Next.
Enter the Base Address to the inmation Web API providing data to the interface. This follows the syntax:http://[hostname]:[listening] of the Web API server. The default port is 8002.
In this example the Web API service is running on the same host as the Visual KPI server so we can use 'localhost'. The base address would therefore be:
If the Web API service is running on a different host to the Visual KPI Server (often the same host where the Core service of system:inmation is installed), then enter that host name instead.
Also enter the inmation authentication credentials (Profile and Password) that have access rights to system:inmation. Here we use the credentials assigned to the ‘so’ system owner profile in system:inmation.
On the installation summary page, click Next.
Once the installation has been successfully completed, click Finish.
After the interface configuration you can change the settings in the Server Manager if needed.
Visual KPI Remote Context Server
Go to the Server Manager and select the Remote Context Services node below the installed instance. Right click the Remote Context Services node and select from the context menu.
Click Next to begin the installation procedure.
Accept the license agreement and click Next.
Enter a Name for the Remote Context service, and click Next
Leave the installation path as default, and click Next.
On the installation summary page, click Next.
Once the installation has been successfully completed, click Finish.
In the Server Manager enter the inmation authentication credentials (Profile and Password) that have access rights to system:inmation. Here we use the credentials of the "so" system owner profile in system:inmation. Also, if the Visual KPI server is on a different host machine to the inCommunication service, the inmation Server name (under "inmation Remote Context Service Configuration") should be changed to the hostname (or IP address) of the machine where the inCommunication service is running.
| The "inmation Remote Context Service Configuration" settings above the security settings should be automatically completed similar to as seen above. If your System object has a custom name, you may need to alter the _inmation RCS Script Node Path to match the name. The inmation Instance Path setting is needed if you are creating KPI Server and KPI Instance objects in the Server Model. |
Right click the inmation RC Server node and Start from the context menu to start the service.
