The next two sections explain how to create an ODA data source to connect to Stardust Process Model and Runtime Data. After having created Stardust ODA data sources, you may specify arbitrary Runtime Views and Model Views on these data sources as primary sources for your reports. For basic information on connecting data sources please refer to the BIRT Help.
This chapter describes the configuration for the following data source types:
An Stardust Process Database ODA Datasource is a connection to a Stardust Audit Trail Database.
To create a data source:
Now you may specify the connection parameters in the following dialog:
Hereby, Driver Class Path, Database URL, Database User and Database Password are the JDBC Connection parameters to a local JDBC-connected database. Datasource JNDI Name is the name of a database in a managed environment, e.g. a Web application server or an application server.
The JDBC connection parameters are used to connect to the database during report design time for preview purposes, the data source JNDI name is used at runtime, when the carnot-reporting.war is deployed to an application server.
In case you enter a JNDI name, the driver class is looked up via JNDI. If you do not provide the data source JNDI name, the JDBC connection parameters are also used at runtime. In this case, you cannot use the pooling or transaction synchronization mechanisms of the application server environment.
There are some predefined driver class paths provided, which you can select via the drop-down arrow on the right side of the Driver Class Path entry. To extend or modify this list, select the button Manage Drivers... to open the Manage JDBC Drivers dialog:
In the JAR Files tab you can add, delete or restore a new database driver jar. If you click the Add button, a file browser opens to browse for a driver jar:
To edit the default settings for a driver, like the name displayed or a URL template:
Now you can select the defined driver class in the Driver Class Path list:
The entry for the Database URL will be filled with the URL template defined for the selected database driver, e.g.:
If this field is left empty, the audit trail will be checked for partitions. In case exactly one partition exists, its ID will be used. In case there are more than one partitions an exception will be thrown with the message that the partition needs to be specified.
In case you specify a partition ID in this field, its existence in the audit trail will be checked. If a partition with this ID exists, it will be used, otherwise an exception is thrown.
The Worktime Calculator selects the plug-in containing the worktime calculation business logic. For more information on this issue please refer to chapter Calculating Worktime.
You may use an arbitrary number of different Stardust Process Database data sources per report.
Once you filled out all the necessary entries, you can test the connection by clicking Test Connection.
If you are not able to create a DataSource please check in the Error Log view (Window > Show View > Error Log) of the Java perspective, if your license might not be valid.
This section describes how to connect to the embedded derby database that is used within the RAD (Rapid Application Development) environment.
Now this driver is provided in the Driver Class Path list, where you can select it:
Enter the following Database URL:
Choose a JNDI name:
Now start the server and test your connection.
a Stardust Process Model ODA Datasource is a connection to a Stardust Process Model. To select it:
Provide the file path to the process model in File Path Process Model, e.g.:
You may use an arbitrary number of different Stardust Process Model data sources per report.
Stardust provides predefined parameters to be evaluated by the data source. Please refer to the section Stardust Parameters of the chapter Sample Reports and Library for detailed information.
To create a data source with predefined Stardust Parameters: