Product specifications

You specify the SBO file name, its directory and the database network layer that is used for the
connection.
2.
Check that the file is valid against the DTD, save and close the file.
3.
Either browse to the sub-directory where you want to store the SBO file or create your own
sub-directory as specified in the setup file.
4.
Create the SBO file with your target database and driver libraries by using an XML editor.
5.
Check that the file is valid against the DTD, save and close the file.
Note:
Apart from customizing the SBO file, you also need to create the COD, PRM and RSS files for each
driver newly installed.
10.1.5 To check connections dynamically
You can customize your driver to make it validate at runtime that a connection of the connection pool
can be used. This validation process consists of executing an SQL query without side effect when the
connection is retrieved from the pool. It means that the connection can be used if the SQL query is
executed without error. If it is not, the connection is discarded.
Remember:
This functionality is available for Generic ODBC, Generic OLE DB and Generic JDBC connections. All
other supported connectivities handle this connection check already, then no customization is required.
1.
Stop Connection Server.
2.
Open the SBO file of your driver.
3.
Locate the DataBase section that is appropriate to your connection.
For example, for a Generic ODBC connection:
<DataBases>
<DataBase Active="Yes" Name="Generic ODBC datasource">
<Libraries>
...
</Libraries>
<Parameter Name="CharSet Table" Platform="Unix">datadirect</Parameter>
</DataBase>
...
4.
Add the following row in the DataBase section:
<Parameter Name="Connection Check">SQL query</Parameter>
where SQL query is the query you use to check the validity.
5.
Save the SBO file.
6.
Restart Connection Server.
Connection Server validates that the connection can be used before executing the data request.
2012-03-15116
Configuring data access driver parameters