VIMON

The VIMON module is used to display Virtimo monitoring within BPC.

Configuration

Important configurations are listed below:

Vimon_ProxyID*(proxyId)*
(string) ID of the BackendConnection, which establishes the connection to the VIMON server.
Params_InitialDashboardPath (initialDashboardPath)
(string)
The path to a dashboard that is to be displayed initially.
Params_InitialFilter (initialFilters)
(array)
A list of filters that are to be set initially.
Example configuration:
```
{
    "param1": ["value11", "value12", "value13"],
    "param2": "value21",
    "param3": 0
}
```

The data is transformed into URL parameters as follows: param1=value11&param1=value12&param1=value13&param2=value21&param3=0

Params_InitialLowerDate (initialLowerDate)
(string)
If it is set, initial data is loaded from the date. Relative time specification is also valid, e.g.: now-7d.
Params_InitialUpperDate (initialUpperDate)
(string)
If it is set, data is initially loaded up to the date. Relative time specification is also valid, e.g.: now-7d.
Params_KioskMode (kioskMode)
(boolean)
Enables the display of the VIMON in kiosk mode, whereby only the selected dashboard is displayed. The navigation bar or filter field, for example, are not displayed in kiosk mode.
Params_OrganizationId (orgId)
(string) ID of the organization

Widget

It is possible to display a configured VIMON instance in the dashboard.

Customization of the content security policy

Some content security policies are set as default in the BPC to protect against attacks. During integration, VIMON brings along Javascript code with script evaluations (i.e. eval()) and inline scripts. These are prevented by the BPC in the content security policy.
In order to integrate VIMON in the BPC, these policies should be adapted.

The adaptation takes place in the file [karaf_folder]/etc/jetty.xml.

The value of header-csp should contain the following: script-src 'self' 'unsafe-eval' 'unsafe-inline'

Keywords: