Policy Server Guides › Policy Server Administration Guide › Configuring Policy Server Data Storage Options › Configure ODBC Storage Options

Configure ODBC Storage Options

Use the ODBC context–sensitive storage controls to configure an ODBC data source for:

• A policy store
• A key store
• Audit logs
• A session store

Note: For more information about configuring ODBC data sources, see the Policy Server Installation Guide.

Configure an ODBC Data Source

To configure an ODBC data source

1. Specify the name of the ODBC data source in the Data Source Information field. You can enter multiple names in this field to enable ODBC failover.

   Data Source Information

   Indicates the name of the ODBC data source. You can enter multiple names in this field to enable failover.

   User Name

   Indicates the user name of the database account (if required) with full rights to access the database.

   Password

   Contains the password of the database account.

   Confirm Password

   Contains a duplicate of the database account password, for verification.

   Maximum Connections

   Indicates the maximum number of ODBC connections per database allowed at one time.

2. Click Test ODBC Connection to verify that the parameters you entered are correct and that the connection can be made.

Configure ODBC Failover

If you have multiple ODBC data sources and you want to configure failover, list the data source names in the Data Source Information field, separated by commas. For example, entering CA SiteMinder® Data Source1,CA SiteMinder® Data Source2 causes the Policy Server to look at Data Source 1 first. If CA SiteMinder® Data Source1 does not respond, the Policy Server automatically looks for CA SiteMinder® Data Source2.

Note: Using the method described above, you can configure failover for data sources used as policy stores, key stores, session stores, and audit logs.

Configure Limit to Number of Records Returned by a SQL Query

SQL queries that return large numbers of records can cause the Policy Server to hang or crash. To manage this outcome, you can output a warning message to the SMPS logs when the number of records returned exceeds a maximum value that you specify.

To configure the maximum, add the registry key, MaxResults, and set its value to one or more. When the number of records returned by a query equals or exceeds the limit specified by MaxResults, the Policy Server outputs a warning to the SMPS logs. When MaxResults is set to zero or undefined, no warning messages are output.

Adding the registry key, MaxResults, does not change the number of records returned. Adding the key does warn you when the number of results exceeds a limit that you set. You can use this feedback to modify your SQL queries and fine-tune the number of records returned, as needed.

To configure a limit to the number of records returned by a SQL query

1. Manually add the registry key MaxResults:

   Windows

   Add the registry key MaxResults to the following location:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Netegrity\SiteMinder\CurrentVersion\Ds
   \ODBCProvider
   

   Solaris

   Add the following lines to the sm.registry file:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Netegrity\SiteMinder\CurrentVersion\Ds
   \ODBCProvider=35921
   MaxResults=0x1; REG_DWORD
   

2. Assign MaxResults a value greater than or equal to one.

Configure ODBC Registry Settings for Timeout

The parameters listed following control timeout for the connection between and ODBC database and the Policy Server in various situations. The key on Windows and UNIX is available the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Netegrity\SiteMinder\CurrentVersion\Database

"LoginTimeout"

The time that is allowed to connect to the database.

"QueryTimeout"

Allows 30 seconds for the query to complete. When the query does not complete within this time, a cancel request is sent to the database. For an ODBC user directory, the query timeout is overridden with the user directory object Searchtimeout. You set this value using XPSExplorer.

"ConnectionHangWaitTime"

The number of seconds before the Policy Server marks a connection as hung. This value must be larger than twice the value of QueryTimeout or SearchTimeout.

"ConnectionTimeout"

The maximum wait time on a connection. In cases where the query timeout or the log-in timeout apply, those values override the connection timeout.