Deploying data objects
There are two types of data objects, and either one can be a data source:
Data object design
A data object design specifies a data source and a data set and data cubes. A report developer or data modeler creates the data object design in BIRT Designer Professional. A data object design has a .datadesign extension.
Data object store
A data object store contains the materialized data generated by a data object design. A volume administrator creates the data object store in Management Console. A data object store has a .data extension.
If the user uses a data object design as a data source, the report retrieves data from databases and other data sources when it runs. The advantage of this approach is that the report retrieves current data. The disadvantage is that it increases the load on production databases.
If the user uses a data object store as a data source, the report retrieves materialized data from the data object store when it runs. The advantage of this approach is that it does not increase the load on production databases. The disadvantage is that the report may not retrieve current data.
A volume administrator controls which users have access to data objects by assigning privileges on the .datadesign and .data files. If the volume administrator does not want to increase the load on production databases, they can give users access to .data files but not .datadesign files.
To deploy a data object, a report developer, data modeler, and volume administrator cooperate in performing the following tasks:
A report developer or data modeler creates a data object design in BIRT Designer Professional. For more information about creating a data object design, see
Using Actuate BIRT Designer Professional.
The report developer or data modeler places the .datadesign file in the BIRT Resource folder.
The report developer or data modeler publishes the .datadesign file to the iHub /Resources folder.
A volume administrator schedules a job for the .datadesign file that generates a .data file. For more information about scheduling a job, see
Managing an Encyclopedia Volume.
A volume administrator assigns privileges for the appropriate users on the .datadesign and .data files. To give a user access to a .datadesign file, assign read and execute privileges. To give a user access to a .data file, assign read privilege.