Installation and Upgrade Guides › Directory Configuration Guide › MySQL Server › Configure a MySQL Policy Store › How to Configure the Policy Store › Configure a MySQL Data Source for SiteMinder

Configure a MySQL Data Source for SiteMinder

You configure a data source to let the Policy Server communicate with the SiteMinder data store.

More information:

How to Configure a MySQL User Store

Create a MySQL Data Source on Windows

You create a MySQL data source for the MySQL wire protocol driver.

Follow these steps:

1. Log in to the Policy Server host system.
2. Do 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 the install_home\Windows\SysWOW64.
     2. Double–click odbcad32.exe.

   The ODBC Data Source Administrator appears.

3. Click System DSN.

   System Data Sources lists all available data sources.

4. Click Add.

   The Create New Data Source dialog appears.

5. Scroll down and select SiteMinder MySQL Wire Protocol and click Finish.

   The ODBC MySQL Wire Protocol Driver Setup dialog appears.

6. Complete the following steps in the General tab:
   1. Enter a data source name in the Data Source Name field.

      Example:

      SiteMinder MySQL Wire Data Source
      

   2. Enter the name of the MySQL database host system in the Host Name field.
   3. Enter the port on which the MySQL database is listening in the Port Number field.
   4. Enter the name of the MySQL database in the Database Name field.
7. Click Test Connect.

   The connection settings are tested. If the settings are valid, a prompt states that the connection is successful.

8. Click OK.

   The data source is created and appears in the System Data Sources list.

Note: You can now point the Policy Server to the SiteMinder data store.

Create a MySQL Data Source on UNIX Systems

The SiteMinder ODBC data sources are configured using a system_odbc.ini file, which you create by renaming mysqlwire.ini to system_odbc.ini. The mysqlwire.ini file is located in siteminder_home/db.

siteminder_home

Specifies the Policy Server installation path.

This system_odbc.ini file contains all of the names of the available ODBC data sources and 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 value. The value is required when you configure the 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 that is loaded when SiteMinder uses this data source. The remaining attributes are specific to the driver.

Adding a MySQL Server Data source involves:

• Adding a new data source name in the [ODBC Data Sources] section of the file.
• Adding a section that describes the data source using the same name as the data source.

If you create a new service name or want to use a different driver, update the system_odbc.ini file. You should have entries for the MySQL driver under [SiteMinder Data Source].

Again, to configure a MySQL Server data source, you create the system_odbc.ini file by renaming mysqlwire.ini to system_odbc.ini.

Create the MySQL 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.

• sqlserverwire.ini
• oraclewire.ini
• mysqlwire.ini

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.0 MySQL 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/NSmysql24.so
   Description=DataDirect 6.0 MySQL Wire Protocol
   Database=database_name
   HostName=host_name
   LogonID=root_user
   Password=root_user_password
   PortNumber=mysql_port
   

   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 can cause ODBC connections to fail.

   nete_ps_root

   Specifies the Policy Server installation path. Enter this value as an explicit path, rather than one with an environment variable.

   Example: /export/smuser/siteminder

   database_name

   Specifies the name of the MySQL database that is to function as the SiteMinder data store.

   host_name

   Specifies the name of the MySQL database host system.

   root_user

   Specifies the login ID of the MySQL root user.

   root_user_password

   Specifies the password for the MySQL root user.

   mysql_port

   Specifies the port on which the MySQL database is listening.

4. 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 access the SiteMinder data in the policy store.

Follow these steps:

1. Open the Policy Server Management Console and click the Data tab.
2. Select the following value from the Storage list:

   ODBC
   

3. Select the following value from the Database list:

   Policy Store
   

4. Enter the name of the data source in the Data Source Information field.
   • (Windows) The entry must match the name that you entered in the Data Source Name field when you created the data source.
   • (UNIX) The entry must match the first line of the data source entry in the system_odbc.ini file. By default, the first line in the file is [SiteMinder Data Sources]. If you modified the first entry, be sure to enter the correct value.
5. 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.
6. Specify the maximum number of database connections that are allocated to SiteMinder.

   Note: We recommend retaining the 25 connection default for best performance.

7. Click Apply to save the settings.
8. Select the following value from the Database list:

   Key Store
   

9. Select the following value from the Storage list:

   ODBC
   

10. Select the following option:

    Use the Policy Store database
    

11. Select the following value from the Database list:

    Audit Logs
    

12. Select the following value from the Storage list:

    ODBC
    

13. Select the following option:

    Use the Policy Store database
    

14. Click Apply to save the settings.
15. Click Test Connection to verify that the Policy Server can access the policy store.
16. Click OK.

    The Policy Server is configured to use the database as a policy store, key store, and logging database.