Installation Guides › Policy Server Installation Guide › Configuring SOA Security Manager Data in a Relational Database › Important Considerations
Important Considerations
Consider the following before configuring a policy store:
- Avoid possible policy store corruptionEnsure that the database server to which the policy store is to be installed is configured to store objects in UTF-8 form:
- (Oracle) Ensure that the database is configured to store objects in UTF-8 form. Oracle supports unicode within many of their character sets. For more information on configuring your database to store objects in UTF-8 form, see your vendor-specific documentation.
- (MS SQL Server) Ensure that the database is configured using the default collation (SQL_Latin1_General_CP1_CI_AS). Using a collation that is case sensitive may result in unexpected behaviors. For more information on configuring your database to store objects using the default collation, refer to your vendor-specific documentation.
- Do not use brackets around the IP address when using IPv6 ODBC data sources or the connection fails.
Example: use fec0::9255:20c:29ff:fe47:8089 instead of [fec0::9255:20c:29ff:fe47:8089]
Note: More information on IPv6-supported databases exist in the SOA Security Manager Platform Support Matrix on the Technical Support site.
To locate the support matrix on the Support site
- Click Technical Support.
- Click Support By Product.
- Select CA SOA Security Manager from the Select a Product Page list.
Scroll to Product Status and click Platform Support Matrices.