You create the SOA Security Manager schema so that the MySQL database can store policy, key, and audit logging information.
To create SOA Security Manager schema in a MySQL database
Specifies the path to the schema files extracted from the tier 2 directory zip.
sm_mysql_ps.sql
DROP FUNCTION IF EXISTS `databaseName`.`getdate` $$ CREATE FUNCTION `databaseName`.`getdate` () RETURNS DATE
Example: If the name of the database is smpolicystore, the required update appears as follows:
DROP FUNCTION IF EXISTS `smpolicystore`.`getdate` $$ CREATE FUNCTION `smpolicystore`.`getdate` () RETURNS DATE
Note: You can also use this schema file to create a stand–alone key store.
Note: You can use a separate database to function as this type of SOA Security Manager data store.
sm_mysql_logs.sql
DROP FUNCTION IF EXISTS `databaseName`.`getdate` $$ CREATE FUNCTION `databaseName`.`getdate` () RETURNS DATE
The audit store schema is created.
Note: You can use a separate database to function as this type of SOA Security Manager data store.
smsampleusers_mysql.sql
DROP FUNCTION IF EXISTS `databaseName`.`getdate` $$ CREATE FUNCTION `databaseName`.`getdate` () RETURNS DATE
The SOA Security Manager sample user store schema is created.
Specifies the path to the schema files extracted from the tier 2 directory zip.
MySQL.sql
The policy store schema is created.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |