Database element definitions tell the deployed adapter definition how and where to create elements that are based on information pulled from a database. Use the DBElement feature to create robust relationship modeling.
Section 5.4.2, Creating an Element for Incoming Database Information
When creating an element definition, the requirements are organized in five main tabs:
Element: Specify basic descriptive information for the element.
Icon: Specify an icon to represent the element. Make a selection from the Operations Center Metamodel icon class browser or specify a custom icon.
For more information, see Section 5.7, Assigning Icons to Groups, Dynamic Groups, and Database Elements.
Query: Define a query to gather and filter database information to create the element and its properties.
For more information, see Section 6.1, Defining a Query and Section 6.9, Testing Queries.
Schedule: Set up scheduling requirements for running the element query and checking for new information at adapter runtime.
For more information, see Section 6.10, Scheduling Queries.
Pages: (Optional) Create custom property pages for the element.
For more information, see Section 5.9, Defining Custom Property Pages.
If multiple element layers are created by different database queries that run on different schedules, the adapter might need to create a temporary parent element for the child information until the query for the parent element runs and updates. This occurs in cases where the database query might be run more frequently for the child elements because information affecting the parents is changed less often.
In thepane, select the parent element of the new element.
Right-click the parent element, then select, or click ( ).
An element is created under the parent element.
To specify basic properties for database elements:
Click the new element in thepane.
In the right pane, theicon is selected by default.
Thepane shows basic properties for the database element:
Specify the Name and Description for the database element.
This information is for definition purposes and is not displayed when the adapter is deployed and created in Operations Center.
To simplify the element distinguished name definition hierarchy, see Section 6.2.5, Using the HierarchyKey Property to Simplify Element Naming.
Enter XML in thefield.
The Hierarchy XML text area provides support for MODL (Managed Objects Definition Language) <param> tags, custom properties, and other tags that are valid with a MODL <generator> tag. You should know the XML syntax for what you want to accomplish.
MODL is an XML-based markup language used to create HierarchyFiles for Operations Center. The HierarchyFile reflects both the nature of information received from a management system and the processing logic of the Operations Center system.
For more information about MODL and the HierarchyFile, see
Using the HierarchyFile in the Operations Center 5.6 Adapter and Integration Guide.
Specify a default algorithm for the group in thefield.
For more information, see the steps below.
To specify a default algorithm in thefield:
In thepane, click to open the Edit Algorithm dialog box.
In the Edit Algorithm dialog box, select theradio button to specify no custom algorithm.
None displays in thefield in the group pane.
To set a custom algorithm, select theradio button, then select an algorithm type from the drop-down list.
Clickto close the Edit Algorithm dialog box.
For information on algorithms, see Using Algorithms to Calculate Element State in the Operations Center 5.6 Server Configuration Guide.
Follow these steps to implement the element definition:
Specify an icon.
For instructions, see Section 4.3, Assigning an Adapter Icon.
Define and test a query.
For instructions, see Section 6.1, Defining a Query and Section 6.9, Testing Queries.
Select a schedule for the query.
For instructions, see Section 6.10, Scheduling Queries.
(Optional) Define property pages for the database element and define the properties they contain at adapter runtime.
For instructions, see Section 5.9, Defining Custom Property Pages.
In the Data Integrator adapter element hierarchy, there is an option to have the child element state propagate up the hierarchy and change the state of its parent, which is the Data Integrator adapter element.
For example, if the adapter element is UNKNOWN, but its child is OK, you might want the OK state to propagate up to the parent adapter element.
To ensure state propagation from child to parent, start the Data Integrator adapter and set the top-most element to the highest algorithm. When the elements are recalculated, the parent element takes the highest child condition.
To set the element to the highest algorithm:
In the Operations Centerpane, under , right-click the adapter root element, then select to open the Status property page:
In the left pane, clickto update the property page.
Select theradio button.
Selectfrom the drop-down list.