Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › Configure a SQL Server Policy Store › How to Configure the Policy Store › Create the SiteMinder Schema

Create the SiteMinder Schema

You create the SiteMinder schema so that SQL Server database can store policy, key, and audit logging information.

The following warnings are displayed when running the policy store and audit logging schema files and do not affect the policy store configuration:

• Warning: The table 'smvariable5' has been created but its maximum row size (8746) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
• Warning: The table 'smodbcquery4' has been created but its maximum row size (64635) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
• Warning: The table 'smaccesslog4' has been created but its maximum row size (9668) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

To create the SiteMinder schema

1. Start the Query Analyzer and log in as the person who administers the Policy Server database.
2. Select the database instance from the database list.
3. Open sm_mssql_ps.sql in a text editor and copy the contents of the entire file.
4. Paste the schema from sm_mssql_ps.sql into the query and execute the query.

   The policy and key store schema is added to the database.

5. Open SQLServer.sql in a text editor and copy the contents of the entire file.
6. Paste the schema from SQLServer.sql into the query, and execute the query.

   The policy store schema is extended.

7. Repeat steps three and four to use the policy store as an audit logging database. Use the following schema file:

   sm_mssql_logs.sql

   Note: You are not required to configure the policy store to store additional SiteMinder data. You can configure individual databases to function as a separate audit log database, key store, and session store.

   The database can store SiteMinder data.

Configure a SQL Server Data Source for SiteMinder

If you are using ODBC, you need to configure a data source to let SiteMinder communicate with the SiteMinder data store.

More information:

SQL Server Authentication Mode Considerations

SQL Server Authentication Mode Considerations

SiteMinder data sources do not support Windows authentication. Configure the SiteMinder data source with the credentials of a user that is stored in the database.

Note: For more information about SQL Server authentication modes, see the vendor−specific documentation.

Create a SQL Server Data Source on Windows

ODBC requires that you configure a data source for the SQL Server wire protocol.

Note: This procedure only applies if the Policy Server is installed on a Windows System.

Follow these steps:

1. Complete one of the following steps:
   • If you are using a supported 32–bit Windows operating system, click Start and select Programs, Administrative Tools, ODBC Data Sources.
   • If you are using a supported 64–bit Windows operating system:
     1. Navigate to C:\Windows\SysWOW64.
     2. Double–click odbcad32.exe.

   The ODBC Data Source Administrator appears.

2. Click the System DSN tab.

   System data source settings appear.

3. Click Add.

   The Create New Data Source dialog appears.

4. Select SiteMinder SQL Server Wire Protocol and click Finish.

   The ODBC SQL Server Wire Protocol Driver Setup dialog appears.

5. Enter the data source name in the Data Source Name field.

   Example: SiteMinder Data Source.

   Note: Take note of your data source name. This information is required as you configure your database as a policy store.

6. Enter the name of the SQL Server host system in the Server field.
7. Enter the database name in the Database Name field.
8. Click Test.

   The connection settings are tested and a prompt appears specifying that the connection is successful.

9. Click OK.

   The SQL Server data source is configured and appears in the System Data Sources list.

Create a SQL Server Data Sources on UNIX Systems

The SiteMinder ODBC data sources are configured using a system_odbc.ini file, which you create by renaming sqlserverwire.ini, located in policy_server_installation/db, to system_odbc.ini. This system_odbc.ini file contains all of the names of the available ODBC data sources as well as the attributes that are associated with these data sources. This file must be customized to work for each site. Also, you can add additional data sources to this file, such as defining additional ODBC user directories for SiteMinder.

The first section of the system_odbc.ini file, [ODBC Data Sources], contains a list of all of the currently available data sources. The name before the “=” refers to a subsequent section of the file describing each individual data source. After the “=” is a comment field.

Note: If you modify of the first line of data source entry, which is [SiteMinder Data Source], take note of the change because you will need this value when configure your ODBC database as a policy store.

Each data source has a section in the system_odbc.ini file describing its attributes. The first attribute is the ODBC driver to be loaded when this data source is used by SiteMinder. The remaining attributes are specific to the driver.

Adding a MS SQL Server Data source involves adding a new data source name in the [ODBC Data Sources] section of the file, and adding a section that describes the data source using the same name as the data source. You need to change the system_odbc.ini file if you create a new service name or want to use a different driver. You should have entries for the Oracle or SQL drivers under [SiteMinder Data Source].

Again, to configure a MS SQL Server data source, you must first create a system_odbc.ini file in the policy_server_installation/db directory. To do this, you need to rename sqlserverwire.ini, located in policy_server_installation/db, to system_odbc.ini.