Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data in a Relational Database › Configure a SQL Server Policy Store › How to Configure the Policy Store › Create the SOA Security Manager Schema

Create the SOA Security Manager Schema

You create the SOA Security Manager schema so that SQL Server database can store policy, key, token session, 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 SOA Security Manager 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 a logging database, token store, and session store.

   The respective schema files are:

   • sm_mssql_logs.sql
   • sm_mssql_token.sql
   • sm_mssql_ss.sql

   The respective SOA Security Manager schema is added to the database.

   Note: You are not required to configure the policy store to store additional SOA Security Manager data. You can configure individual databases to function as one or more separate logging databases, key stores, token stores, and session stores.

   The database can store SOA Security Manager data.