Setting up the connection configuration file
In a BIRT report design, the configuration key that specifies a data source is the concatenation of the ODA plug-in’s data source extension ID and the data source design name separated by an underscore (_) character.
The connection property names are the connection properties defined for your data source. To find the correct names for the connection properties, check the data source definition in the XML source of the BIRT report design file. You can view the report’s XML source by selecting the XML Source tab in the report editor.
The code example in Listing 27-3 shows the XML definition of a MySQL Enterprise database in a report design. Using this data source, the report developer can test the report in development. This XML data source definition specifies the connection properties, odaDriverClass, odaURL, odaUser, and odaPassword, for the data source, ClassicModels.
Listing 27-3  
  <oda-data-source extensionID="" name="Customers" id="4">
    <property name="odaDriverClass">
    <property name="odaURL">
    <property name="odaUser">root</property>
    <property name="odaPassword">pwd</property>
At run time, the report uploaded to iServer connects to a production database that resides on a different database server. The connection properties specify a machine IP address,, and a different username and password. To externalize the database connection information, create the configuration property file, DBConfig.xml, with the settings shown in Listing 27-4.
Listing 27-4  
<ConnectOptions Type="">
  <Property PropName="odaDriverClass">
  <Property PropName="odaURL">
  <Property PropName="odaUser">operator</Property>
  <Property PropName="odaPassword">pwd</Property>

Additional Links:

Copyright Actuate Corporation 2012