4.1 Using Tables

The system views and any views you create are based on the following tables:

4.1.1 Agreement Table

The Agreement Table displays a definition of each agreement and objective for every element, starting with the children for which the view was created. Its constraints are:

  • Depth: The number of element levels to traverse.

    Default value is 1. Specify All to traverse all levels.

Table 4-1 explains the Agreement Table’s columns.

Table 4-1 Agreement Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

AGREEMENT

false

true

1024

VARCHAR

CALENDAR

false

true

512

VARCHAR

AGREEMENTDESCRIPTION

false

true

1024

VARCHAR

OBJECTIVE

false

true

1024

VARCHAR

OBJDEFINITION

false

true

1024

VARCHAR

ELEMENT

false

true

1024

VARCHAR

ELEMENT_NAME

false

true

1024

VARCHAR

ELEMENT_ID

false

false

0

INTEGER

4.1.2 Alarms Table

The Alarms Table displays a row for each alarm for the element for which the view was created. It includes default columns and additional columns in semicolon delimited format or XML. You cannot configure the columns. The type of alarm is specified by a constraint. The constraints are:

  • Alarm Type: The alarm type:

  • Alarms: Historical and real-time element alarms.

  • Audit Events: Historical and real-time audit alarms.

  • Outages: Historical element outages. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Service Level Breaches: Historical agreement breaches generated by the real-time BSLM engine. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Service Level Metrics: Real-time agreement metrics. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Change Events: Alarms indicating a change in the element. For more information, see the Operations Center 5.6 Version Tracking Guide.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to define a specific time period for pruning the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

Table 4-2 explains the Alarm Table’s columns.

Table 4-2 Alarms Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

ELEMENT

false

true

1024

VARCHAR

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

ID

false

true

0

INTEGER

SEVERITY

false

true

512

VARCHAR

LASTUPDATE

false

true

0

TIMESTAMP

DATA

false

true

0x1000000

LONGVARCHAR

XMLDATA

false

true

0x1000000

LONGVARCHAR

4.1.3 AlarmsConstructed Table

The AlarmsConstructed Table displays a row for each alarm for the element for which the view was created. You can define a custom set of columns and add EMS (external management system) as a searchable column. For example, to search for alarms generated from an external management system called ALPHA, you would add EMS as a column and ALPHA as a value and then use the following query:

select * from MOSQL.EVE_NAMED_ALARMS where EMS='ALPHA'

The type of alarm is specified by a constraint. A constraint determines which columns display. The constraints are:

  • Columns: The columns to display. The syntax for identifying columns is:

    Name:name, Type:type, Nullable:Yes|No, Size:size_in_bytes

    For example:

    Name:LASTUPDATE,Type:Timestamp, Nullable:false,Size:1024

  • Alarm Type: The alarm type:

  • Alarms: Historical and real-time element alarms.

  • Audit Events: Historical and real-time audit alarms.

  • Outages: Historical element outages.

  • Service Level Breaches: Historical agreement breaches.

  • Service Level Metrics: Real-time agreement metrics.

  • Change Events: Alarms indicating a change in the element. For more information, see the Operations Center 5.6 Version Tracking Guide.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Setting a Report Time Period of None only queries real-time alarms. Setting the Report Time Period to any other value queries the warehouse alarm history and bounds the query according to the configuration of the warehouse alarm history.

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to define a specific time period for pruning the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

Table 4-3 explains the AlarmsConstructed Table’s columns.

Table 4-3 AlarmsConstructed Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

DNAME

false

true

1024

VARCHAR

SEVERITY

false

true

512

VARCHAR

ID

false

true

0

INTEGER

Class

false

true

512

VARCHAR

Specific information is available in Operations Center from external applications via adapters. To include this information, you must add the following columns:

Table 4-4 Information from External Applications via Adapters

Column Name

Name=

nullable=

length

JDBC Type=

NAME

NAME

false

1024

VARCHAR

STATUS

Status

false

1024

VARCHAR

CLASS

Class

false

1024

VARCHAR

DESCRIPTION

Description

false

1024

VARCHAR

NAME corresponds to the element name displayed in the Operations Center console, and STATUS, CLASS, and DESCRIPTION contain values that originate from external applications.

4.1.4 AlarmsNamed Table

The AlarmsNamed Table displays a row for each alarm column for the element for which the view was created. The type of alarm is specified by a constraint. The table contains default columns in addition to NAME and VALUE columns for specifying additional alarm columns. The NAME column is the name of the alarm field. The VALUE column is the value of the alarm field. You cannot configure the columns. The constraints are:

  • Alarm Type: The alarm type:

  • Alarms: Historical and real-time element alarms.

  • Audit Events: Historical and real-time audit alarms.

  • Outages: Historical element outages. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Service Level Breaches: Historical agreement breaches generated by the real-time BSLM engine. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Service Level Metrics: Real-time agreement metrics. For more information, see the Operations Center 5.6 Service Level Agreement Guide.

  • Change Events: Alarms indicating a change in the element. For more information, see the Operations Center 5.6 Version Tracking Guide.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to define a specific time period for pruning the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

Table 4-5 explains the AlarmsNamed Table’s columns.

Table 4-5 AlarmsNamed Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

ELEMENT

false

true

1024

VARCHAR

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

ID

false

true

0

INTEGER

SEVERITY

false

true

512

VARCHAR

LASTUPDATE

false

true

0

TIMESTAMP

NAME

false

true

1024

VARCHAR

VALUE

false

true

1024

VARCHAR

4.1.5 Availability Table

The Availability Table displays a row of data for each time period (such as Minute, Hour, Day, and so on) The row contains historical availability data and outage data. The constraints are:

  • Calendar: The calendar used in determining data relevance. The default is Default calendar, which is On 24x7.

  • Time Categories: The time categories used in determining data relevance. This is a comma-separated list (such as On, Off, or Peak). The default is On. For example, if the specified calendar includes On and Blackout times, then outages that occur in Blackout times are excluded from the results based on the default setting to include On time categories.

  • Time Zone: The time zone used in determining the result set. The default is America/New York.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to define a specific time period for pruning the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Reporting Interval: The interval or level of granularity to display the data. By default this constraint uses the overall report time period. For example, if the report time period is Last Month and days are specified as the reporting interval, a row is generated for each day in the month.

  • Display Sub-Elements Values: Select this option to display a data row for each child element.

Table 4-6 explains the Availability Table’s columns.

Table 4-6 Availability Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

DNAME

false

true

1024

VARCHAR

AVAILABILITY

false

true

0

DOUBLE

DOWNTIME

false

true

0

BIGINT

OUTAGES

false

true

0

INTEGER

OUTAGES_CONTINUING

false

true

0

INTEGER

OUTAGES_INITIATED

false

true

0

INTEGER

RELEVANCE

false

true

0

DOUBLE

DISCONTINUITY

false

true

0

DOUBLE

AGREEMENT

false

true

1024

VARCHAR

OBJECTIVE

false

true

1024

VARCHAR

The following explain the Downtime, Availability, and Discontinuity column values:

  • Downtime and Availability are determined based on element condition data.

  • Downtime is recorded in milliseconds.

  • Availability is calculated based on the total time within the report time period For example, if you request availability for the month of January, the total possible time is the number of milliseconds from Jan 1, 12:00 AM until Feb 1, 12:00 AM. Availability is determined by the formula: (total time in period minus total downtime in period) divide by total time in period. The Availability value is between 0 and 1, where 1 = 100%. By default, an element is available when its state is anything other than CRITICAL. The Calendar and Time Categories specified are used to determine when system outages are relevant to the calculated Availability, Downtime, and Outage results. Only those system outages that occur during time windows of the Calendar that reference the included Time Categories are included in the calculated results. For example, outages that occur during a scheduled maintenance period are not included in the results if the Blackout time category is not specified as included in the view.

    When Agreement and Objective are specified as part of the Where clause in the query, Availability is calculated using the SLA and Objective definitions to determine the total time window.

  • Discontinuity is the time recorded when the system does not record any condition data. This might occur because of manually stopping an adapter, the Operations Center server, or a profile, or if the Operations Center server or a management system feed goes down unexpectedly. It is not known if the element was available during these times. By default, the BSLM engine calculates availability by assuming that there was no outage during these times.

  • Agreement and Objective columns are not saved values, but allow Agreement and Objective definitions to be applied in the Availability calculation. Agreement and Objective are displayed as null unless defined as part of the query. These columns are optional in the SQL query.

For more detailed information, see the Operations Center 5.6 Service Level Agreement Guide.

4.1.6 Breaches Table

The Breaches Table displays a row of data for each breach in the time period (such as Minute, Hour, Day, and so on) The row contains historical breaches. The constraints are:

  • Calendar: The calendar used in determining data relevance. The default is Default calendar.

  • Time Categories: The time categories used in determining data relevance. This is a comma-separated list (such as On, Off, or Peak). The default is On. For example, if the specified calendar includes On and Blackout times, then outages that occur in Blackout times are excluded from the results based on the default setting to include On time categories.

  • Time Zone: The time zone used in determining the result set. The default is America/New York.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to further prune the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Reporting Interval: The interval or level of granularity to display the data. By default this constraint uses the overall report time period. For example, if the report time period is Last Month and days are specified as the reporting interval, a row is generated for each day in the month.

Table 4-7 explains the Breaches Table’s columns.

Table 4-7 Breaches Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

AGREEMENT

true

false

1024

VARCHAR

OBJECTIVE

false

true

1024

VARCHAR

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

DNAME

false

true

1024

VARCHAR

DATE

false

true

0

TIMESTAMP

SEVERITY

false

true

512

VARCHAR

STATUS

false

true

1024

VARCHAR

KEYMETRIC

false

true

0

DOUBLE

APPLIEDAGREEMENT

false

true

1024

VARCHAR

REASON

false

true

1024

VARCHAR

PERSISTENTID

false

true

1024

VARCHAR

This table requires specifying AGREEMENT in the SQL query as part of the where clause. It also optionally accepts OBJECTIVE as part of the where clause.

4.1.7 Condition Table

The Condition Table displays historical condition data. Each row represents the condition of the element at the specified data. The constraints are:

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to further prune the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Display Sub-Elements Values: Select this option to display a data row for each child element.

Table 4-8 explains the Condition Table’s columns.

Table 4-8 Condition Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

DNAME

false

true

1024

VARCHAR

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

TIME

true

true

0

TIMESTAMP

TYPE

false

true

1024

VARCHAR

SVALUE

false

true

1024

VARCHAR

DVALUE

false

true

0

DOUBLE

4.1.8 Elements Table

The Elements Table displays a real-time list of all elements, starting at the children of the element for which the view was created. The constraints are:

  • Depth: The number of element levels to traverse. Default value is 1. Specify All to traverse all levels.

Table 4-9 explains the Elements Table’s columns.

Table 4-9 Elements Table Columns

name=

required In Where=

nullable=

length

JDBC Type=

NAME

true

true

512

VARCHAR

DNAME

false

true

512

VARCHAR

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

CLASSNAME

false

true

512

VARCHAR

CONDITION

false

true

512

VARCHAR

ID

true

true

0

INTEGER

PARENT

false

true

0

INTEGER

LASTUPDATE

false

true

0

TIMESTAMP

4.1.9 Health Table

The Health Table displays a row of data for each time period (such as Minute, Hour, Day, and so on) The row contains historical agreement health data. The constraints are:

  • Calendar: The calendar used in determining data relevance. The default is Default calendar.

  • Time Categories: The time categories used in determining data relevance. This is a comma-separated list (such as On, Off, or Peak). The default is On. For example, if the specified calendar includes On and Blackout times, then outages that occur in Blackout times are excluded from the results based on the default setting to include On time categories.

  • Time Zone: The time zone used in determining the result set. The default is America/New York.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to further prune the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Reporting Interval: The interval or level of granularity to display the data. By default this constraint uses the overall report time period. For example, if the report time period is Last Month and days are specified as the reporting interval, a row is generated for each day in the month.

  • Display Sub-Elements Values: Select this option to display a data row for each child element.

  • Calculate Health Using Objective Interval: Select this option to evaluate health and key metric values based on the time intervals defined by the objective definition, and not those selected in the report settings.

  • Show Key Metric As Percentage: Select this option to display the inverse value of the key metric.

Table 4-10 explains the Health Table’s columns.

Table 4-10 Health Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

AGREEMENT

true

false

1024

VARCHAR

OBJECTIVE

false

true

1024

VARCHAR

DNAME

false

true

1024

VARCHAR

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

HEALTH

false

false

0

DOUBLE

KEYMETRIC

false

true

0

DOUBLE

GRADE

false

false

256

VARCHAR

RELEVANCE

false

false

0

DOUBLE

BREACHES

false

true

0

INTEGER

DISCONTINUITY

false

false

0

DOUBLE

This table requires specifying AGREEMENT in the SQL query as a where clause. It also accepts OBJECTIVE as a where clause.

4.1.10 Outages Table

The Outages Table displays a row of data for outage in each time period (such as Minute, Hour, Day, and so on) The row contains historical outages. The constraints are:

  • Calendar: The calendar used in determining data relevance. The default is Default calendar.

  • Time Categories: The time categories used in determining data relevance. This is a comma-separated list (such as On, Off, or Peak). The default is On. For example, if the specified calendar includes On and Blackout times, then outages that occur in Blackout times are excluded from the results based on the default setting to include On time categories.

  • Time Zone: The time zone used in determining the result set. The default is America/New York.

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no data exists for the time period, no results are returned. Use the Start_Time and End_Time columns to further prune the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Reporting Interval: The interval or level of granularity to display the data. By default this constraint uses the overall report time period. For example, if the report time period is Last Month and days are specified as the reporting interval, a row is generated for each day in the month.

Table 4-11 explains the Outages Table’s columns.

Table 4-11 Outages Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

DNAME

false

true

1024

VARCHAR

START_TIME

false

true

0

TIMESTAMP

END_TIME

false

true

0

TIMESTAMP

OUTAGE_START

false

true

0

TIMESTAMP

OUTAGE_END

false

true

0

TIMESTAMP

DURATION

false

false

0

DOUBLE

DESCRIPTION

false

true

1024

VARCHAR

PERSISTENTID

false

true

1024

VARCHAR

4.1.11 Performance Table

Queries against the Performance table must contain a valid performance Profile name and Expression name defined in the Operations Center server. If the names are not included in the query as part of the where clause, then the query returns an error. For example:

select * from PERFORMANCE_VIEW where Profile = 'Router Performance' and Expression = 'Condition Counts'

The Performance Table displays a list of profile and expression performance data. The constraints are:

  • Report Time Period: For historical tables, enables creating a single view that can be reused on a regular basis to produce a standard interval of data without having to edit the view and specify the start and end dates. The valid values are:

    Last Year, Last Quarter, Last Month, Last Week, Yesterday, Last Hour, This Year, This Quarter, This Month, This Week, Today, This Hour, None

    Ensure that data exists for the time period queried. If no exists for the time period, no results are returned. Use the Start_Time and End_Time columns to further prune the result set. One of the following time formats must be specified:

    yyyy-MM-dd-HH.mm.ss For example: 2012-05-01-00.00.00

    yyyy-MM-dd HH:mm:ss For example: 2012-05-01 00:00:00

    The first format uses periods and hyphens where the other format uses colons and spaces.

  • Display Sub-Elements Values: Select this option to display a data row for each child element.

Table 4-12 explains the Performance Table’s columns.

Table 4-12 Performance Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

DNAME

false

true

1024

VARCHAR

PROFILE

true

false

1024

VARCHAR

EXPRESSION

true

false

1024

VARCHAR

TIME

true

false

0

TIMESTAMP

VALUE

false

false

0

DOUBLE

DISCONTINUITY

false

false

0

BIT

4.1.12 Properties Table

The Properties Table displays a list of real-time properties for all elements, starting with the children of the element for which the view was created. The constraints are:

  • Depth: The number of element levels to traverse. Default value is 1. Specify All to traverse all levels.

Table 4-13 explains the Properties Table’s columns.

Table 4-13 Properties Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

DNAME

false

true

1024

VARCHAR

DATA

false

true

0x1000000

LONGVARCHAR

XMLDATA

false

true

0x1000000

LONGVARCHAR

4.1.13 PropertiesConstructed Table

The PropertiesConstructed Table displays a list of real-time properties for all elements, starting with the children of the element for which the view was created. This table displays columns based on the table constraint. The constraints are:

  • Columns: The columns to display. The syntax for identifying columns is:

    Name:name, Type:type, Nullable:Yes|No, Size:size_in_bytes

    For example:

    Name:LASTUPDATE,Type:Timestamp, Nullable:false,Size:1024

  • Depth: The number of element levels to traverse. Default value is 1. Specify All to traverse all levels.

The PropertiesConstructed Table’s columns are user-defined.

4.1.14 PropertiesNamed Table

The PropertiesNamed Table displays a list of real-time properties for all elements, starting with the children of the element for which the view was created. Each property is specified in a single row. The NAME column specifies the property name. The VALUE column specifies the property value. The constraints are:

  • Depth: The number of element levels to traverse. Default value is 1. Specify All to traverse all levels.

Table 4-14 explains the PropertiesNamed Table’s columns.

Table 4-14 PropertiesNamed Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

ELEMENT_ID

false

false

0

INTEGER

ELEMENT_NAME

false

true

1024

VARCHAR

DNAME

false

true

1024

VARCHAR

NAME

true

true

512

VARCHAR

VALUE

false

true

1024

VARCHAR

4.1.15 Relationships Table

The Relationships Table displays a real-time list of all relationships for every element, starting with the children of the element for which the view was created. The constraints are:

  • Depth: The number of element levels to traverse. Default value is 1. Specify All to traverse all levels.

Table 4-15 explains the Relationships Table’s columns.

Table 4-15 Relationships Table Columns

name=

Required In Where=

nullable=

length

JDBC Type=

LEFTID

false

true

0

INTEGER

RIGHTID

false

true

0

INTEGER

NAME

false

true

512

VARCHAR

LEFTID represents the parent and RIGHTID represents the child in the relationship.