Dashborad Tables

Dashboard

Repository

BC_REPOSITORIES (MNG DB)

This table contains data for each Dashboard repository configurations such as Rules Context Menus Tooltip etc.

All data stored by Customer ID , Repository Type  and version of BAC when these entities were included and start using.

BRE_ID - contains the unique ID for customer data in this table

BRE_CUSTOMER_ID    - the customer ID who has settings which defined in in BRE_XML_DATA column

BRE_REPOSITORY_TYPE     - context/type of xml data:

(PropofationRules, contextMenu, flowmapMapping, tooltips, bundles, assignmentRules, entities, dimensions, rulemap ) each of this types corresponds to relevant data in BAC.

BRE_XML_DATA - the XML data - general data of

BRE_VER_NUM - the version of BAC. This column contains information regarding from each version of the BAC some settings were added to BAC DB.

For example: the settings regarding to some type menus which was added / predefined for some view and special customer.

SELECT BRE_XML_DATA FROM BC_REPOSITORIES
WHERE (BRE_CUSTOMER_ID =<Customer_ID>  OR BRE_CUSTOMER_ID = 0)
AND BRE_REPOSITORY_TYPE = <REPOSITORY_TYPE>
GO

 

 

We added BRE_CUSTOMER_ID = 0 because a general data which related to each customer storage in record with BRE_CUSTOMER_ID   = 0

For example for default customer (ID=1) and context menu context

SELECT BRE_XML_DATA FROM [dbo].[BC_REPOSITORIES]
WHERE (BRE_CUSTOMER_ID = 1 OR BRE_CUSTOMER_ID = 0)
       AND BRE_REPOSITORY_TYPE = 'contextMenu'
GO

 

 

We will see two record - one for all customers (global settings - BRE_CUSTOMER_ID =0) and special settings (BRE_CUSTOMER_ID   = 1).

NODE: All data stored in XML format.

Custom MAP

DASH_CUSTOM_IMAGE_VIEW (MNG DB)

Contains the data about a custom map for view

DASH_CUSTOM_IMAGE_NODE (MNG DB)

Contains the data regarding to CI on the custom map for view

These two tables contain all data regarding to Custom map for view and CIs in this view.

DASH_CUSTOM_IMAGE_VIEW (MNG DB)

DCIV_ID - unique ID of record - if will change the image for view - previous report was deleted and one new record was added to table with auto increment  of this field (last record in table + 1) and DCIV_IMAGE_VERSION was changed to (last value + 1)

DCIV_CUSTOMER_ID - the customer ID who has custom map.

DCIV_VIEW_ID - UCDB   ID of view for each the custom map was defined

DCIV_IMAGE_URL  - the relevant url  for image.  On this path the image storage in BAC system as a graphic-file

DCIV_DIMENSION_ID - not relevant

DCIV_LAST_UPDATE - the time when this custom map was updated in Dashboard

DCIV_IMAGE_DATA - the downloaded image-data from specified url.

DCIV_IMAGE_VERSION - the number of changes of the image for the same view (changes + 1. For example if we changed the image two times the value will be 3 (two changes and 3-th  version of image)

DASH_CUSTOM_IMAGE_NODE (MNG DB)

DCIN_ID  - unique ID of CIs on the maps

DCIN_CUSTOMER_ID - the ID customer who has a custom map

DCIN_VIEW_ID -  UCDB ID of View with custom map

DCIN_NODE_ID - UCMDB CI ID which locates on custom map

DCIN_DIMENSION_ID - not relevant

DCIN_XPOS - X coordinate of CI on the Map

DCIN_YPOS - Y coordinate of CI on the Map

MNG DB

Session

HA_ACTIVE_SESS (MNG DB)

The Table contains the data about session and user with access/connect information to Dashboard.

HA_ID - internal Dashboard BAC session ID

HA_HOST - the IP address of host which are connecting to BAC

HA_SESSION_ID  - general  session ID

HA_USER_ID  - the user ID of connection (see USERS table)

HA_CUSTOMER_ID - customer ID of connection

HA_TIMESTAMP - the time of login in the number format.

HA_LOGIN_CTX - a cache of login.

Report

Two tables correspond to this area.

M_KE01F1_F (PRF DB)

This table contains the data about status changing of KPI

M_KT01F1_F (PRF DB)

This table contains the data about KPI status in time

M_KE01F1_F (PRF DB)

SAMPLETIME - time in a sample in the number format. This sample was sent from trinity (not from Data Collectors)

TUID - TUID

DBDATE - time when the data were publish to DB

LOOK001 - the type of sample according to published record in DB.

LOOK002 - Customer ID

LOOK003 - KPI ID

BNRY004 - Entity ID

NUMB005 - Type of the KPI

NUMB006 - Status of the KPI

NUMB007 - not relevant

M_KT01F1_F (PRF DB)

SAMPLETIME - time in a sample in the number format. This sample was sent from trinity (not from Data Collectors)

TUID - TUID

DBDATE - time when the data were publish to DB

LOOK001 - the type of sample according to published record in DB

LOOK002 - Customer ID

LOOK003 - KPI ID

BNRY004 - Entity ID

NUMB005 - Type of the KPI

NUMB006 - Status of the KPI

 Other areas

Regarding to

• Filters
• Geographical map
• Console

Configuration of these pages and areas in Dashboard locate Setting_Parameters

Because the all confoguration data correspond to Ifrastucture Settings parameters. Threfore this data storage in this table.

SETTING_PARAMETERS (MNG DB)

This table contain the data regarding to changes in the Infrastructure Settings.

SP_ID - The ID of the setting

SP_CONTEXT - (!) - Context of the settings (in Dashboard Case is: BACAppSettings)

SP_SUB_CONTEXT - Not relevant

SP_NAME -

• Console - business.console*

• Top View Properties - tp*
• Topology Map - topology.map*
• Sound Notification - dashboard.beep*
• Service Impact - service.impact*
• Maps Management Properties - maps*

 * - can be any text
SP_VERSION - version of the settings

SP_HOST_ID - Not relevant

SP_VALUE - Value of a setting

SP_VALUE_CLOB - Not relevant

SP_CUSTOMER_ID - The Customer ID

Example:

How to collect information regarding Dashboard Applicaton setting

SELECT * FROM SETTING_PARAMETERS
where SP_CONTEXT = 'BACAppSettings'
go

 

KES

You can find all KPI Assignments of KES in BC_REPOSITORIES (MNG DB) table. You should use only rows with BRE_VER_NUM = 6.x. All the details about this table can be found at the beginning of this page.
We also saving all the assignments under:
<BAC Data Processing Server>\HPBAC\AppServer\webapps\site.war\bam\conf\repositories . if you want to compare between defaults assignments and custom assignment, you can use:
\assignmentRules\def.xml contains OOTB KES Factory assignments
\assignmentRules\1.def.db.xml contains current assignments definitions

For Propagation assignments, which locate at the same place as KES assignments, look at:
\propagationRules\def.xml contains OOTB KES Factory propagations
\propagationRules\1.def.db.xml contains current propagations definitions

Filters

Using table BC_APP_PERSISTENCY in MNG DB

Filters with BAP_FILTER_ID < 0 are global (default) and the rest are per customer