Understanding externalization precedence
Data source properties in a report design can be externalized to the connection profile and to the iServer connection configuration file. In addition the Connection Profile Store URL itself can be externalized. The following precedence rules explain how iServer determines the final list of data source properties for report execution.
Data source properties in the iHub connection configuration file override the data source in the connection profile that overrides the data source connection properties in the report. The ascending order of precedence for iServer looks like this:
Data source properties in the report design
Data source properties in the connection profile
Data source properties in the iHub connection configuration file
The following sample connection configuration file externalizes the file path to the connection profile and shows the required structure:
<Config>
<Runtime>
<ConnectOptions Type="org.eclipse.birt.report.data.oda.jdbc_SQL Server Data Source">
<Property PropName="OdaConnProfileStorePath">
C:\SqlServer.profile
</Property>
</ConnectOptions>
</Runtime>
</Config>
The connection profile referenced by the BIRT report design is read when the report is executed in iServer. The path to the connection profile in the design has to be visible to iServer.