outputXmlRepository property

Specifies the database that contains a repository. The repository stores captured SQL data from an application enabled for pureQuery client optimization.

This property can only be specified in the set of properties that is retrieved from a repository. An exception is thrown if the outputXmlRepository property is not retrieved from a repository.

When storing captured SQL data in a repository, the runtime group ID that is used to store the data is the same runtime group ID that is used to retrieve the pureQuery runtime properties from a repository.

If both the outputPureQueryXml and outputXmlRepository properties are set, then an exception is thrown.

Note: Specify the outputXmlRepository property when the repository that stores the SQL data and the repository that holds the pureQuery Runtime properties are different. If you specify the outputXmlRepository property when captured SQL data and pureQuery properties are in the same repository, you duplicate the database connection resources.

This property can take the following values:

ds://DataSource-name
Specifies a database using a JNDI (Java Naming and Directory Interface) data source name. A JNDI Directory Service must be registered such that data sources can be accessed by name. The database must contain a repository and the database user connecting to the repository must have the appropriate database privileges to access the repository.

Most application servers support JNDI Data Source lookup.

The following are examples of a DataSource URL:

ds://AccountsPayableAppl1
ds://jdbc/sample
jdbc:JDBC-URL
Specifies a database using a JDBC URL. The database must contain a repository and the database user connecting to the repository must have the appropriate database privileges to access the repository.
The following example is a JDBC URL:
jdbc:db2://localhost:50000/SAMPLE:user=username;password=passwd;

Feedback