Page History
This appendix includes the following topics:• About
...
...
...
| Anchor | ||||
|---|---|---|---|---|
|
An understanding of database mapping and definition files is essential if you want to add internal proprietary information such as, user name and telephone number, to the reports generated by Report Manager.NOTE Entering
| Info |
|---|
Entering invalid strings into these files can cause the customized reporting mechanism to fail. Any modifications made to the xml files falls under the sole responsibility of the customer. Before modifying these files verify that you are experienced with the SQL language, familiar with XML, and that you have fully read and understood this section. |
The database mapping and definitions for customized reports are stored in the following files:
- db.xml.
...
- Describes the database mapping.
- def.
...
- xml. Defines dependency conditions.
- tree.
...
- xml. Defines the hierarchical structure of the Data Tree.
These files are found located in: <precise<precise_root>root>/products/foresight/etc/reports/udr
| Anchor | ||||
|---|---|---|---|---|
|
The db.xml file defines all Database Tables and Join conditions between tables, which are used by the customized reporting mechanism.
...
• About the Related tag
About the Table tag
The Table tag defines the table and its attributes, as described in the following table. The Table tag is a top level element in the db.xml file.
...
INEN_ID = INAP_INEN_ID AND INCE_INAP_ID = INAP_ID
</join>
</table>
The following table describes the Join tag attributes.
...
depend Specifies the dependency condition identifier. This identifier is defined in the def.xml file. If the dependency condition is met, then the table specified in the table attribute is used to retrieve the list of entity identifiers.
| Anchor | ||||
|---|---|---|---|---|
|
The def.xml file is a configuration file that defines dependency conditions using a single tag called dependency. These definitions are used by the depend attribute of the db.xml file.
...
The dependency tag contains a single attribute, called name. The value of this attribute is a character string that identifies the dependency. This character string must be unique in the def.xml file.
The dependency tag format contains dependency conditions, as follows:
...
<dependency name="oa user"><![CDATA[a{2002}]]></dependency>
| Anchor | ||||
|---|---|---|---|---|
|
The tree.xml file defines the hierarchical structure of the Data Tree. Each data field that is a leaf node, includes a unique numeric identifier. The data field identifiers are used in the def.xml file. For this reason you should not modify the existing data field identifiers, but you can add additional data field identifiers to the Data Tree. If you add new data field identifiers to the Data Tree, you must also add new data fields to the def.xml file.
...
<group isApptier="true" tech="ST" installCode="SQ-SQCOL" name="ST" desc="1076" />
The following table describes the Group tag attributes.
...
The meaning of a data field can depend on its context, that is, on the other fields that are selected with it. The Alt tag defines an alternative selection of expression for its data field, based on the other fields selected. When the data field is selected, Report Manager scans the alternatives in the same order as they were listed in the file, and chooses the first alternative whose dependency is met.
Example:
<object id="5050" type="cnt" name="ORInOracleTimeSum" desc="825">
...
If you need to join one table to other tables for this data field only, you can specify its conditions in the alt tag and it is therefore not necessary to define this Join in the db.xml file.
Precise. Performance intelligence from click to storage. Learn more > >
...