Adding Hierarchical Data Sources to a Catalog

This topic introduces the two methods for adding hierarchical data sources to a catalog according to how you implement the HDS API: adding general hierarchical data sources and importing hierarchical data sources from an XML file.

This topic contains the following sections:

Adding a General HDS to a Catalog
- Example of Adding a General HDS
Importing an HDS from an XML File to a Catalog
- The XSD File Used for HDS

Adding a General HDS to a Catalog

Create a catalog or open a catalog.
In the Catalog Manager, right-click the node of a data source and choose New General Hierarchical Data Source from the shortcut menu.
If you want to add the HDS to a new data source in the catalog, select any of the existing catalog data source, select New Data Source on the Catalog Manager toolbar, then in the New Data source dialog box, specify the name of the data source, select the Hierarchical connection type and select OK.
In the New General Hierarchical Data Source dialog box, select Browse to specify the HDS class name.
In the Parameter box, type a number or parameter string. The parameter string must match the format defined in the HDS class.
You can reference parameters and constant level formulas predefined in the current catalog data source in the format @FieldName, and the special field "User Name" as @username in the PARAMETER string.
Select Load Tree. Designer then parses the data source tree. Modify the column properties in the Columns box.
Select OK to add the HDS.

Example of Adding a General HDS

There are three classes used in this example. Their source code files are HierarchicalDataSource.java, HierarchicalDatasetMetaData.java, and HierarchicalDataset.java, which are available in <install_root>\help\samples\APIUDS\hierarchicalUDS. In this example, the HierarchicalDataSource.java returns the result set from the demo HSQL DB.

Copy the above three files to <install_root>\help. Modify the demo HSQL DB path in both HierarchicalDatasetMetaData.java and HierarchicalDataset.java.
Compile the Java files to generate HierarchicalDataSource.class, HierarchicalDatasetMetaData.class, and HierarchicalDataset.class.
Append the path <install_root>\help into the ADDCLASSPATH variable of the batch file setenv.bat in <install_root>\bin, so that at runtime HierarchicalDataSource can be found.
Start Designer with the batch file you just modified and open an existing catalog.
In the Catalog Manager, right-click the data source to which to add the HDS, then select New General Hierarchical Data Source from the shortcut menu.
In the New General Hierarchical Data Source dialog box, select Browse to find the class HierarchicalDataSource.class.
In the Parameter box, type a number. Designer only fetches the records whose employee ID is less than this number.
Select Load Tree. Designer then loads the data source tree.
In the Columns box, modify the column properties.
Select OK to add the HDS.

Importing an HDS from an XML File to a Catalog

Create a catalog or open a catalog.
In the Catalog Manager, right-click the node of a data source and choose New XML Hierarchical Data Source from the shortcut menu.
If you want to add the HDS to a new data source in the catalog, select any of the existing catalog data source, select New Data Source on the Catalog Manager toolbar, then in the New Data source dialog box, specify the name of the data source, select the XML connection type, select Hierarchical Data Source and select OK.
In the New XML Hierarchical Data Source dialog box, select Browse to specify the XML URI and XSD URI as required. Select Load Tree to load the structure of the XML file. Designer then lists the root of the file in the Root Name text box.
Designer supports all kinds of URI as the XML data source.
- If you want to specify a schema file for the XML data source file, you must first make sure that the schema file path specified in the XML data source file is consistent with the path you specified in the XSD URI field, and that this file actually exists. Select Load Tree to load the structure of the XML file. Designer then lists the root of the file in the Root Name text box. Modify the column properties in the Columns box as required.
- Designer supports static string inline with multiple parameters, for example:
  http://localhost:8888/jrserver%2fSampleReports%2fSampleReports.cat/Key Performance Indicators Report.cls?jrs.cmd=jrs.try_vw&jrs.result_type=7&jrs.param$p_Year=2016&jrs.param$p_Month=2&jrs.param$p_Region=APAC
  It is the URL used to run the sample report "Key Performance Indicators Report.cls" in XML on Server. Type the URL into the XML URI text box, and select Load Tree. Designer then loads the structure of the returned XML stream in the Structure box (before doing so, make sure that Server is started). Modify the column properties in the Columns box as required.
  You can use the colon ":" and At "@" symbols to identify Logi Report parameter names. If you use these symbols in your XML URI but you do not want Logi Report to parse them as parameters, you must add quotation marks to them. For example, when you browse to d:\test\employee.xml, you can quote it either as "d:\test\employee.xml" or d":"\test\employee.xml.
  The Server administrator must select the No Security Checking option in the Administration > Configuration > Advanced page of the Server Console, so that Server can parse the URL successfully. In addition, you can reference the Logi Report parameters in the URL for setting different values dynamically at runtime.
In the Columns box, modify the column properties.
When importing the XML file, you have to define the types of some data in the Format column. For example, if it is Date type, such as 1978-03-12, in the corresponding Format column, type in "yyyy-MM-dd". If the data is $12,345.32, in the corresponding Format column, type in "$##,###.##". By default, the value of the Scale column is 0, therefore, for decimal type data, you need to specify the scale value in its corresponding Scale column, that is, modify this value to the number of digits that you want to appear to the right of the decimal point, for example, if the data is 123.23, then in the Scale column, modify this value to 2. For the Currency and Array columns, select them.
Select OK to import the HDS into the catalog.

The XSD File Used for HDS

When you import an XML HDS with an XSD file, the XML file only provides the data to the Designer reports, while the structure, data type, and so on of the data from the XML file is defined in the XSD file. That is, the XSD file determines the structure of the HDS. You should be aware of the following points about the XSD file in order to generate a correct report based on an XML HDS with an XSD file.

Data type conversion

Before the data type defined in the XSD file can function with Designer, Designer should at first convert the data type into a corresponding data type when you import the XML hierarchical data source based on the rules in the following conversion table.

XML Data Type	Logi Report Data Type
SchemaSymbols.ATTVAL_BOOLEAN	java.sql.Types.BIT
SchemaSymbols.ATTVAL_INT	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_SHORT	java.sql.Types.SMALLINT
SchemaSymbols.ATTVAL_BYTE	java.sql.Types.TINYINT
SchemaSymbols.ATTVAL_INTEGER	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_NONPOSITIVEINTEGER	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_NEGATIVEINTEGER	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_NONNEGATIVEINTEGER	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_UNSIGNEDLONG	java.sql.Types.BIGINT
SchemaSymbols.ATTVAL_LONG	java.sql.Types.BIGINT
SchemaSymbols.ATTVAL_UNSIGNEDINT, //4294967295	java.sql.Types.BIGINT
SchemaSymbols.ATTVAL_UNSIGNEDSHORT, //65535	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_UNSIGNEDBYTE, //255	java.sql.Types.SMALLINT
SchemaSymbols.ATTVAL_POSITIVEINTEGER	java.sql.Types.INTEGER
SchemaSymbols.ATTVAL_FLOAT	java.sql.Types.FLOAT
SchemaSymbols.ATTVAL_DOUBLE	java.sql.Types.DOUBLE
SchemaSymbols.ATTVAL_DECIMAL	java.sql.Types.DECIMAL
SchemaSymbols.ATTVAL_STRING	java.sql.Types.VARCHAR
SchemaSymbols.ATTVAL_DATE	java.sql.Types.DATE
SchemaSymbols.ATTVAL_TIME	java.sql.Types.TIME
SchemaSymbols.ATTVAL_DATETIME	java.sql.Types.TIMESTAMP
SchemaSymbols.ATTVAL_HEXBINARY	java.sql.Types.LONGVARBINARY

The XSD structure Designer supports

Designer does not support all XSD structures in HDS. The following diagrams show the supported structures.

The ComplexType

The Element type in the diagram can be of simpleType, ref, or complexType (it is different from the ComplexType in the root of this diagram. It can be global complexType but cannot be the anonymous one. If you have defined a complexType named "A", and in this complexType A redefined an element as complexType named "B", then the elements belong to complexType B must be of the simpleType).

The Attribute type in the diagram should be of the anonymous type or of the schema built-in type, such as xs:string.
The SimpleType

SimpleType here should be of the schema built-in type, such as xs:string. List type here cannot support some functions, such as minLength and maxLength.

The Element

Element diagram

ComplexType here can include both global and anonymous complexType. The anonymous type means you do not give a name to the type, for example:

<xs:element name="aa">
 
    <xs:simpleType>
 
        <xs:restriction base="xs:string">
 
            <xs:enumeration value="Julie P. Adams"/>
 
        </xs:restriction>
 
    </xs:simpleType>
 
</xs:element>

From the code above, you can see that the simpleType in the element aa has no name specified.

Note icon

Designer does not allow an XML data source file without any schema file. That is, you can leave the XSD URI entry empty. However, Designer uses the data type VARCHAR for all the columns in the data source.
When you import data of List type from an XSD file, you can define the delimiter via the property List Delimiter in the Report Inspector.
Designer also supports dynamic XML URI. The XSD file defines the structure of the XML HDS. The XML file in fact only provides the data, so one XSD file can match more than one XML file. That enables you to develop reports with dynamic XML URI. For more information, see Example 1: Developing a Report from an HDS with Dynamic XML URI.
When you specify a schema file for the XML data source file, due to the schema file being complex, there are some limitations:
- Namespace: Designer supports the default namespace (3w) and target namespace. You can define a prefix for the default namespace, such as xs or xsd, but the value of elementFormDefault must be qualified. The value of attributeFormDefault should be unqualified, but Designer does not allow you to add prefixes before the attributes of the elements.
- Type: If you want to use a customized complexType or simpleType, do not add the prefix to the value of the type, while if you use the built-in simpleType or complexType, you must add the prefix.

Previous Topic Next Topic