Installation

Software Requirements

DataStudio is built using Windows Presentation Foundation (WPF) and therefore only runs on Microsoft Windows operating systems with the .NET framework installed.

Table 1. Software Requirements
Operating System Architecture .NET version

Windows Server 2019

X64

4.8

Windows 10

X64

4.8

Windows Server 2016

X64

4.8

Windows Server 2012 R2

X64

4.8

Windows 8.1

X64

4.8

Windows 7

X64

4.8

Although we endeavour to make DataStudio run on any operating system language, we can not assure its operation on all languages and language settings. Typically the software is tested on English and German language operating systems.

Please visit the dedicated system requirements page for a more detailed description of required minimum hardware and operating system to install and run system:inmation.

Hardware Requirements

DataStudio is a WPF thick client application and therefore benefits considerably from good client hardware, especially a high performance graphic card. However, we recommend using DataStudio on physical hardware rather than virtual machines, with at least: 4 GB RAM Intel I5 Core class processor (or similarly capable one) 1 GB GPU RAM

Generally, DataStudio can also be run on less powerful hardware as long as the minimum software requirements are met. However, significant slow downs may also be encountered.

System Setup

DataStudio is installed as part of the installation of system:inmation. Please refer to the system documentation for more information about the installation and setup of system:inmation.

XCOPY Deployment

The XCOPY command can also be used to deploy DataStudio to a Windows host with necessary software requirements, without requiring the system:inmation installation on the host. For XCOPY deployment, copy the DataStudio folder from the installation media to your local drive.

In locked down desktop environments it may be necessary to grant .NET applications the right to start from the selected target path.

Starting DataStudio

If DataStudio was installed from the system:inmation setup procedure then it can be started from the desktop shortcut item that is automatically created. Otherwise the InDatastudio.exe file can be found in the datastudio folder within the inmation.root installation folder. In the case of XCOPY deployment, just run the InDatastudio.exe file from the target folder.

DataStudio executable file
Figure 1. DataStudio executable file

Login

When DataStudio starts, the Login Dialog is displayed and gives you options of how to connect to system:inmation. Before using DataStudio, you must first login to system:inmation.

Login Dialog
Figure 2. Login Dialog

Workspace

The Workspace dropdown menu contains a list of all the available workspaces. The Login dialog requests that a workspace is selected to load after login, however, there is also the option to create a new workspace (this will be the only selectable option if this is the first running of DataStudio). If other workspaces are available, the last one used is automatically selected.

Core Server

The name of the Core server you wish to connect to can be entered into the Core server field (to connect to the Core server on the same machine enter 'localhost'). If the name of the Core server is not known then the IP address of the server can be entered directly. If a Core has been connected before, it will show up automatically in the dropdown menu. The TCP communication port can also be specified in the Port field.

The default port used by for communication with the Core is 6512. This can be configured during installation or reconfigured by changing the Server Port property on the Core object later in DataStudio.

The last used Core server and port combination will be automatically selected when the DataStudio Login dialog is opened.

Authentication

system:inmation supports two different methods of authentication: Windows Authentication and Profile Credentials.

When Windows Authentication is used, the information of the currently logged in Windows user account will be transmitted with the login request to the Core. In this case there is no need (or possibility) to pass username or password with the request.

When Profile Credentials are used, a User Name and Password must be specified. The User Name must correspond to a Profile object in the Access Model. To create a Profile you must first log on as a system administrator using the "so" (system owner) profile specified during the initial installation. Profiles and access privileges can then be configured for other users.

Login Failure

Login failure can occur in certain circumstances, normally related to connectivity or incorrect authentication credentials. When this happens, the login dialog will display an error message providing more information.

Examples:

Establishing connection to <host name>:<port number> failed

No TCP connection could be established to the given Core host and port. This could be because the hostname/port number have been entered incorrectly or there is a problem connecting to the specified Core service.

Solutions: - Check the Core host name and port number. - Check to see if the Core service is running on the specified host machine by checking Task Manager or Services application - Check that the specified host name/IP address is resolvable by the DNS - Check to see if a firewall is blocking communication between the Core and DataStudio

The connection could not be Established. Client authorization failed. Please use valid credentials and try again. Contact a system administrator to configure your privileges

The credentials entered are not correct.

Solutions: - Check that the user name and password have been entered correctly. - Check that the user name corresponds to a Profile in the Access Model (requires system administrator access) - Check that the User Name/Profile has sufficient privileges to log on to DataStudio (requires system administrator access)

Login Failure error messages. No connection could be established and Authentication Failure.
Figure 3. Login Failure error messages. No connection could be established and Authentication Failure.