Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data in a Relational Database › Configure an Oracle 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 a single Oracle database can store policy, key, token, session, and audit logging information.

To create the SOA Security Manager Schema

1. Log into Oracle with sqlplus or some other Oracle utility as the user who administers the Policy Server database information.

   Note: We recommend that you do not create SOA Security Manager schema with the SYS or SYSTEM users. If necessary, create an Oracle user, such as SMOWNER, and create the schema with that user.

2. Import the following script:

   $NETE_PS_ROOT/db/sql/sm_oracle_ps.sql

   Note: Environment variables may not function in Oracle's SQL utility. If you experience problems importing the script using the utility, specify an explicit path.

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

3. Import the following script

   $NETE_PS_ROOT/xps/Oracle.sql

   The policy store schema is extended.

4. Import the following scripts to use the policy store as a logging database, token store, and/or session store.

   The respective schema files are:

   • sm_oracle_logs.sql
   • sm_oracle_token.sql
   • sm_oracle_ss.sql

   The respective SOA Security Manager schema is created in 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.