Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › How to Configure a SiteMinder Data Store in a SQL Server Database › Configure a SQL Server Data Source for SiteMinder › Configure the SQL Server Wire Protocol Driver

Configure the SQL Server Wire Protocol Driver

No client is required for the wire protocol driver.

To configure the SQL Server wire protocol driver

1. Edit the $NETE_PS_ROOT/db/system_odbc.ini file by making the following entries under [ODBC Data Sources] and [SiteMinder Data Source].

   [ODBC Data Sources]
   Siteminder Data Source=DataDirect 6 SP3 SQL Server Wire Protocol
   [SiteMinder Data Source]
   Driver=nete_ps_root/odbc/lib/NSmsss24.so
   Description=DataDirect 6 SP3 SQL Server Wire Protocol
   Database=SiteMinder Data
   Address=myhost, 1433
   QuotedId=No
   AnsiNPW=No
   

   nete_ps_root

   Specifies an explicit path, rather than one with an environment variable.

   Example: export/smuser/siteminder.

   SiteMinder Data

   Specifies the SQL Server database instance name.

   myhost

   Specifies the IP address of the SQL Server database.

   1433

   Represents the default listening port for SQL Server.

   Note: If no system_odbc.ini file exists, copy and rename sqlserverwire.ini to system_odbc.ini. The sqlserverwire.ini file is located in the $NETE_PS_ROOT/db directory.

   You can edit these sections in the same manner to configure data sources for separate logs, keys, session, and sample users databases:

   • [SiteMinder Logs Data Source]
   • [SiteMinder Keys Data Source]
   • [SiteMinder Session Data Source]
   • [SmSampleUsers Data Source]
2. If you are using Microsoft SQL Server 2008 to function as any SiteMinder store, edit the [ODBC] section as follows:

   TraceFile=nete_ps_root/db/odbctrace.out
   TraceDll=nete_ps_root/odbc/lib/odbctrac.so
   InstallDir=nete_ps_root/odbc
   

   nete_ps_root

   Specifies the explicit path to the Policy Server installation directory. This path cannot contain an environment variable.

3. Configure your policy, key, logging, or session data stores.

More Information:

Configure Policy, Key, Logging, or Session Stores