Previous Topic: How to Store Session Information in SQL ServerNext Topic: Configure Oracle Data Stores


Configure the SQL Server Wire Protocol Driver

You configure the wire protocol driver to specify the settings SiteMinder uses to connect to the database.

Note: This procedure only applies if the Policy Server is installed on a UNIX system. If you have not already done so, copy one of the following files and rename it system_odbc.ini. The file you rename depends on the database vendor you are configuring as a SiteMinder data store.

These files are located in siteminder_home/db

The system_odbc.ini file contains the following sections. The data source that you are configuring determine the section or sections that you edit:

[SiteMinder Data Source]

Specifies the settings SiteMinder is to use to connect to the database functioning as the policy store.

[SiteMinder Logs Data Source]

Specifies the settings SiteMinder is to use to connect to the database functioning as the audit log database.

[SiteMinder Keys Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the key store.

[SiteMinder Session Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the session store.

[SmSampleUsers Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the sample user data store.

Follow these steps:

  1. Open the system_odbc.ini file.
  2. Enter the following under [ODBC Data Sources]:
    SiteMinder Data Source=DataDirect 6 SQL Server Wire Protocol.
    
  3. Depending on the data source you are configuring, edit the one or more of the data source sections with the following information:
    Driver=nete_ps_root/odbc/lib/NSmsss24.so
    Description=DataDirect 6 SQL Server Wire Protocol
    Database=SiteMinder Data
    Address=myhost, 1433
    QuotedId=No
    AnsiNPW=No
    

    Note: When editing data source information, do not use the pound sign (#). Entering a pound sign comments the information, which truncates the value. The truncated value may cause ODBC connections to fail.

    nete_ps_root

    Specifies an explicit path to the Policy Server installation directory. This path cannot contain 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.

  4. 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.

  5. Save the file.

    The wire protocol driver is configured.

Point the Policy Server to the Database

You point the Policy Server to the database so the Policy Server can read and store session information.

To point the Policy Server to the data store

  1. Open the Policy Server Management Console, and click the Data tab.

    Database settings appear.

  2. Select Session Server from the Database list.

    Data source settings become active.

  3. Enter the name of the data source in the Data Source Information field.
  4. Enter and confirm the user name and password of the database account that has full access rights to the database instance in the respective fields.
  5. Specify the maximum number of database connections allocated to SiteMinder.

    Note: We recommend retaining the default for best performance.

  6. Click Apply.

    The settings are saved.

  7. Click Test Connection.

    SiteMinder returns a confirmation that the Policy Server can access the data store.

  8. Click OK.

    The Policy Server is configured to use the database as a session store.

Restart the Policy Server

You restart the Policy Server for certain settings to take effect.

Follow these steps:

  1. Open the Policy Server Management Console.
  2. Click the Status tab, and click Stop in the Policy Server group box.

    The Policy Server stops as indicated by the red stoplight.

  3. Click Start.

    The Policy Server starts as indicated by the green stoplight.

    Note: On UNIX or Linux operating environments, you can also execute the stop-all command followed by the start-all command to restart the Policy Server. These commands provide an alternative to the Policy Server Management Console.