Developer Guide > Operational Data Store Dashboard and Reports > Dashboard and Reports Structure in Logi Info Studio
  

Dashboard and Reports Structure in Logi Info Studio

This section applies only if you use the Dashboard using operational data store. The Dashboard displays event information based on aggregated data that it retrieves from the operational data store. Use Logi Info Studio to view the default Dashboard panels and create custom Dashboard panels based on default KPIs and custom KPIs that you retrieve from the operational data store.
The default Dashboard in Logi Info Studio includes the following global elements:

Operational Data Store Dashboard Filters

This section applies only if you use the Dashboard using operational data store. The Dashboard uses filters for each report that you generate in Logi Info Studio. The filters correspond the global filters in the Dahsboard page of the Operation Console.
The following table describes the default Dashboard filters:
Filter
Description
@Request.idBegin~
Start date of the date/time filter, in the format yyyy-mm-dd.
@Request.itBegin~
Start time of the date/time filter, in the format hh:mm.
@Request.idEnd~
End date of the date/time filter, in the format yyyy-mm-dd.
@Request.itEnd~
End time of the date/time filter, in the format hh:mm.
@Request.iPartnerId~
Partner database identifier for the selected partner.
@Request.iAccountId~
Account database identifier of the selected account.
@Request.eventTypeId~
Event type database identifier of the selected event type.
@Request.eventStatusId~
Event status database identifier of the selected event status.

Operational Data Store Dashboard SQL Query Elements

This section applies only if you use the Dashboard using operational data store. Each report in the default Dashboard using operational data store uses SQL constants for common queries to the operational data store and query parameters. You can reuse these SQL constants when you create custom Dashboard panels based on KPIs that you load to the operational data store.
Note: For the SQL server, use the same constants with the addition of the suffix _SQLSERVER. For example, DX_ODS_FILTER_ACCOUNT would be DX_ODS_FILTER_ACCOUNT_SQLSERVER.
Note: You cannot create reports in Logi Info Studio with SQL queries to the run-time Data Integration Hub repository.
The following table describes the default Dashboard SQL constants:
SQL Constant Name
Description
DX_ODS_FILTER_ACCOUNT
Filters the database rows according to the related account.
Includes the following query parameters:
  • - requestAccountId
DX_ODS_FILTER_ERROR_STATE
Filters the database rows to display only error events.
DX_ODS_FILTER_EVENT_STATUS
Filters the database rows according to the event status.
Includes the following query parameters:
  • - requestEventStatusId
DX_ODS_FILTER_EVENT_STATUS_STATE
Filters the database rows according to the event state. The following values are available:
  • - 1. Show error events with a final state.
  • - 2. Show non-error events with a final state.
  • - -1. Show all events with a final state.
Includes the following query parameters:
  • - requestEventStatusState
DX_ODS_FILTER_EVENT_TYPE
Filters the database rows according to the event type.
Includes the following query parameters:
  • - requestEventTypeId
DX_ODS_FILTER_PARTNER
Filters the database rows according to the related partner.
Includes the following query parameters:
  • - requestPartnerId
DX_ODS_FILTER_TIME_ORACLE
Filters the database rows according to a selected time frame.
Includes the following query parameters:
  • - requestDateBegin
  • - requestTimeBegin
  • - requestDateEnd
  • - requestTimeEnd
DX_ODS_USER_RESTRICTION_BY_ACCESS_ID
Filters the database rows according to the related user access identifier.
Note: To maximize user access control, use DX_ODS_USER_RESTRICTION_BY_ACCESS_ID, DX_ODS_USER_RESTRICTION_BY_EVENT_TYPE, and DX_ODS_USER_RESTRICTION_BY_PARTNER in your custom Dashboard panels.
Includes the following query parameters:
  • - requestUserId
DX_ODS_USER_RESTRICTION_BY_EVENT_TYPE
Filters the database rows to display only event types for which the user has viewing privileges.
Note: To maximize user access control, use DX_ODS_USER_RESTRICTION_BY_ACCESS_ID, DX_ODS_USER_RESTRICTION_BY_EVENT_TYPE, and DX_ODS_USER_RESTRICTION_BY_PARTNER in your custom Dashboard panels.
Includes the following query parameters:
  • - requestUserId
DX_ODS_USER_RESTRICTION_BY_PARTNER
Filters the database rows to display only related partners for which the user has viewing privileges.
Note: To maximize user access control, use DX_ODS_USER_RESTRICTION_BY_ACCESS_ID, DX_ODS_USER_RESTRICTION_BY_EVENT_TYPE, and DX_ODS_USER_RESTRICTION_BY_PARTNER in your custom Dashboard panels.
Includes the following query parameters:
  • - requestUserId

Operational Data Store Dashboard JavaScript Support Files

This section applies only if you use the Dashboard using operational data store. Data Integration Hub uses JavaScript files and jQuery files to process event information when you view the Dashboard in the Operation Console.
The files are located in the following location:
<DIHInstallationDir>\DataIntegrationHub\tomcat\webapps\dih-dashboard\_SupportFiles
The following table describes the JavaScript files and jQuery files that the default Dashboard uses:
File
Description
dx.js
Functions that the Data Integration Hub server uses when it processes reports with the LogiXML engine.
dxbrowser.js
Functions that the browser client uses when you view the Dashboard in the Operation Console.
jquery-*.*
Collection of jQuery files that enable dynamically-populating drop down lists in the global filter section, such as partner or account.

Operational Data Store Dashboard Theme Modifier

This section applies only if you use the Dashboard using operational data store The theme modifier controls the appearance of the Dashboard panels. Data Integration Hub applies the style and appearance settings in the theme modifier to any custom Dashboard panel that you create.
The theme modifier files are located in the following location:
<DIHInstallationDir>\DataIntegrationHub\tomcat\webapps\dih-dashboard\_Themes\DIHDashboard\Informatica
The following table describes the theme modifier components for the default dashboard:
File
Description
Theme.css
Cascading style sheet that determines the graphical and textual formatting of the Dashboard panels.
ThemeModifier.xml
Global settings for the Dashboard panels behavior and the single sign-on mechanism that Data Integration Hub uses when you log on to the Operation Console.

Custom Dashboard Settings

This section applies only if you use the Dashboard using operational data store. You modify certain properties in the LogiXML _Settings.lgx file when you create a custom Dashboard for Data Integration Hub.
The following table describes the properties to modify:
Property
Description
DX_CONSOLE_URL
Location of the Operation Console, in the following format:
http://<DIH host>:<DIH port>/DIH-console
DASHBOARD_SAVEFOLDER
Location to store the personalized layout settings for each Dashboard user.
Default is: @Function.AppPhysicalPath~\dx\saved_dashboards
DX_ODS_ORACLE_CONNECTION
Connection string for the operational data store.
DX_ORACLE_CONNECTION
Connection string for the main Data Integration Hub repository.
LogonFailPage
URL to display after the user logs out of the Operation Console.
The default URL is the Data Integration Hub Logout page: http://<DIH host>:<DIH port>/DIH-console/logout.jsp
AuthenticationClientAddresses
IP addresses for servers that can request authentication tokens from the LogiXML server, separated by semicolons. For each server, set IP4 and IP6 addresses.
caption
Description of the custom Dashboard.
COOKIE_PATH
Path to the cookie file for the custom Dashboard. Must match the value in the Cookie Path property.
WEBAPP_NAME
Name of the folder which contains the custom Dashboard.
Default is: dxdashboard
Redirect Error URL
Link for the page to display if the Dashboard encounters an error.