Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › Configure a MySQL Policy Store

Configure a MySQL Policy Store

A MySQL policy store can also function as:

• A key store
• An audit logging database

  Note: Session information is stored in a separate database. Do not use the policy store to store session information.

Using a single database simplifies administration tasks. The following sections provide instruction on how to configure a single database server.

Gather Database Information

Gather the following information before configuring the policy store or any other type of SiteMinder data store:

• Database host—Identify the name of the database host system.
• Database name—Identify the name of the database instance that is to function as the policy store or data store.
• Database port—Identify the port on which the database is listening.
• Administrator account—Identify the login ID of an administrator account with permission to manage objects in the database.
• Administrator password —Identify the password for the administrator account.

How to Configure the Policy Store

Complete the following procedures to configure MySQL Server as a policy store.

Note: Be sure that you have gathered the required database information before beginning. Some of the following procedures require this information.

1. Be sure that MySQL is installed using the default character set (Latin1). If MySQL was not installed using the default character set, reinstall MySQL before configuring the SiteMinder data store.
2. Be sure that the MySQL database that is to function as the policy store is accessible from the Policy Server host system.
3. Use the vendor–specific user interface to create the database instance for the SiteMinder data store.
4. Create the SiteMinder schema.
5. Configure a MySQL data source for SiteMinder.
   • (Windows) Create a MySQL data source.
   • (UNIX) Create a MySQL data source on UNIX systems.
   • (UNIX) Configure the MySQL wire protocol driver.
6. Point the Policy Server to the database.
7. Set the SiteMinder superuser password.
8. Import the policy store data definitions.
9. Import the default policy store objects.
10. Restart the Policy Server.
11. Prepare for the Administrative UI registration.

Create the SiteMinder Schema

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

Follow these steps:

1. Start the Query Browser and log in as the person who administers the Policy Server database.
2. Select the database instance from the database list.
3. Navigate to the following location:

   siteminder_home\db\tier2\MySQL.
   

   siteminder_home

   Specifies the Policy Server installation path.

4. Open sm_mysql_ps.sql in a text editor and copy the contents of the entire file.
5. Locate the following lines:

   DROP FUNCTION IF EXISTS `databaseName`.`getdate` $$
   CREATE FUNCTION `databaseName`.`getdate` () RETURNS DATE
   

6. Replace each instance of 'databaseName' with the name of the database functioning as the policy store.
7. Copy the contents of the entire file.
8. Paste the file contents into a query and execute the query.

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

9. Navigate to the following location:

   siteminder_home\xps\db\Tier2DirSupport\MySQL 
   

10. Open the following file in a text editor and copy the contents of the entire file:

    MySQL.sql
    

11. Paste the schema from MySQL.sql into the query, and execute the query.

    The policy store schema is extended.

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

    sm_mysql_logs.sql
    

    The database can store SiteMinder data.

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