Installing and Configuring the GUI

The GUI gets installed with the Server using XCOPY of the Server folder from the installation media.

For backward compatibility and for client setups, we provide a MSI installation for the GUI. The GUI reads the global appsettings.json file referenced by the OCTOSAM_CONFIGURATION_FOLDER environment variable. For client deployent scenarios, you need to provide your copy of appsettings.json and install it with the software into the application folder.

License Import

Install your license immediately after configuring the database connection. Do not try to modify the provided license.xml as this will most likely invalidate the encrypted license hash.

You may not install the same license into multiple active databases in parallel. Contact Octosoft if you have specific needs for the setup of multiple databases, for example if you use OctoSAM Inventory in a Windows version migration or company merger scenario.

Query and Reports Definitions

By default, OctoSAM Inventory stores query and report definition in its central database. The definitions are delivered in the Archive QueriesAndReports.zip. This file has to be imported into the database via the GUI (Setup –> Import Queries and Reports).

Custom Reports

OctoSAM Inventory uses Telerik Reporting components for its reports.

Octosoft professional support can assist you with designing custom reports for your specific needs. You can also design your own reports and integrate them into OctoSAM Inventory. More information about Telerik Reports on their website http://www.telerik.com.

Warning!

The OctoSAM Inventory database schema - while fully and openly documented – is internal to OctoSAM Inventory and may change with newer versions of the software. Be prepared to adjust your custom reports with new releases of OctoSAM Inventory.

Custom Queries

OctoSAM Inventory uses its own simple template engine for query definition. See OctoSAM Inventory Query Developer’s Guide for more information. Octosoft professional support is available to write custom queries for your specific needs. A one day training for designing your own custom queries can be also be arranged upon request.

Warning!

The OctoSAM Inventory query engine is internal to OctoSAM Inventory and may change with newer versions of the software. Be prepared to adjust your custom queries with new releases of OctoSAM Inventory.

Queries and Reports Directory Trees

In addition to the central database, Query and Report definitions can be in a directory structure referenced through the appsettings.json settings. See the provided sample appsettings.json file.

Info

Most Queries and Reports are delivered with the Software and loaded into the central database. There is no need to setup these parameters unless you have custom Reports and Queries

Settings for Queries and Reports can be configured with multiple root directories for the Queries and Reports structure. Structures are merged together with the central definitions in the database into the Queries and Reports tree in the GUI. Reports and Queries with the same relative path hide earlier read definitions. This allows you to customize OctoSAM Inventory provided Queries without actually modifying the files that were installed together with OctoSAM Inventory.

You can use file system security to restrict access to Queries and Reports for certain users or groups. File and Directory access errors within the Reports and Queries folder structure are silently ignored.

Warning!

Make sure the Queries and Reports directory trees are read-only for ordinary users. Since these files contain SQL statements, a malicious user could modify them which could lead to security problems if they are later executed in the context of a higher privileged database login

GUI Database Connections

Unlike the other OctoSAM Inventory components, the GUI interactively prompts the user for database connection information and credentials. We highly recommend using Integrated Windows Security for database access.

Login Section in appsettings.json

In case you work with multiple active OctoSAM Inventory Databases in parallel, you can define a list of connections in the appsettings.json file. This will populate a list of pre-configured connection settings.

 "Login": {
    "Environments": [
      {
        "Name": "OctoSAM TEST",
        "Description": "OctoSAM default instance",
        "Server": "localhost",
        "Database": "OctoSAMTEST",
        "Login": "octosam",
        "IntegratedSecurity": true
      },
      {
        "Name": "OctoSAM PROD",
        "Description": "OctoSAM default instance",
        "Server": "localhost",
        "Database": "OctoSAM",
        "Login": "octosam",
        "IntegratedSecurity": true
      }
    ]
  }

The login dialog also lets the user enumerate and select existing SQL Server databases.