About the data source connection configuration file
You can use the iHub data source connection configuration file to externalize data source connection property values. This file is also used by BIRT report designs. A set of connection property values appears in a ConnectOptions element in the configuration file’s Runtime element, for example:
<Runtime>
…
<ConnectOptions Type="My_DB2_Connection">
<Property PropName="server">My_DB2_Server</Property>
<Property PropName="database">My_DB2_Database</Property>
<Property PropName="username">My_DB2_User</Property>
<Property PropName="password">My_DB2_Password</Property>
<Property PropName="port">50000</Property>
<Property PropName="appcodepage">3</Property>
</ConnectOptions>
…
</Runtime>
The password is not encrypted.
You can create an entry for a new set of connection property values or add connection property values to an existing entry. For information about creating a ConnectOptions element, see one of the following topics:
*Externalizing connection property values for a preconfigured connection type
*Externalizing connection property values for a configurable connection type
*Externalizing connection property values for an ODA connection type
In each case, you must first locate the file in which the connection properties
are specified. To locate the data source connection configuration file, check the value of the ConnConfigFile attribute of the appropriate Template element in the shared configuration file, acserverconfig.xml. ConnConfigFile specifies the path of the data source connection configuration file. For more information on ConnConfigFile and the connection configuration file, see BIRT iHub System Administration Guide.
The configuration key specified in the .dcd file must match the Type attribute
for the ConnectOptions element. In Figure 2‑25, the configuration key matches the Type attribute in the ConnectOptions element above. For more information about connection properties, see About connection properties.
Figure 2‑25 Specifying a configuration key