Installation and Upgrade Guides › Policy Server Installation Guide › Configuring SiteMinder Data Stores in a Relational Database › Configure Oracle Data Stores › How to Store Audit Logs in Oracle › Import the Policy Store Data Definitions › Configure the Oracle RAC Wire Protocol Driver

Configure the Oracle RAC Wire Protocol Driver

You configure the wire protocol driver to specify the settings SiteMinder uses to connect to the database.

Note: This procedure only applies if the Policy Server is installed on a UNIX system. If you have not already done so, copy one of the following files and rename it system_odbc.ini. The file you rename depends on the database vendor you are configuring as a SiteMinder data store.

• sqlserverwire.ini
• oraclewire.ini
• mysqlwire.ini

These files are located in siteminder_home/db

The system_odbc.ini file contains the following sections. The data source that you are configuring determine the section or sections that you edit:

[SiteMinder Data Source]

Specifies the settings SiteMinder is to use to connect to the database functioning as the policy store.

[SiteMinder Logs Data Source]

Specifies the settings SiteMinder is to use to connect to the database functioning as the audit log database.

[SiteMinder Keys Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the key store.

[SiteMinder Session Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the session store.

[SmSampleUsers Data Source]

Specifies the settings SiteMinder is to connect to the database functioning as the sample user data store.

Follow these steps:

1. Open the system_odbc.ini file.
2. Depending on the data source you are configuring, edit the applicable data source sections with the following information:
   • Add ServiceName=nete_servicename
   • Add AlternateServers=
   • Add Loadbalancing=1
   • Remove or comment SID=nete_serverid

   The modified text for the data source should appear as follows:

   Driver=nete_ps_root/odbc/lib/NSora24.so
   Description=DataDirect 6 Oracle Wire Protocol
   Logon=uid
   Password=pwd
   HostName=nete_servername1
   PortNumber=1521
   ServiceName=nete_servicename
   CatalogOptions=0
   ProcedureRetResults=0
   EnableDescribeParam=0
   EnableStaticCursorsForLongData=0
   ApplicationUsingThreads=1
   AlternateServers=
   LoadBalancing=1
   

   Note: When editing data source information, do not use the pound sign (#). Entering a pound sign comments the information, which truncates the value. The truncated value may cause ODBC connections to fail.

   nete_ps_root

   Specifies an explicit path to the directory where Policy Server is installed.

   uid

   Specifies the user name of the database account that has full access rights to the database.

   pwd

   Specifies the password for the database account that has full access rights to the database.

   nete_servicename1

   Specifies the IP Address of the first Oracle RAC node.

   (Oracle 10g) Specifies the virtual IP Address of the first Oracle RAC node.

   nete_servicename

   Specifies the service name for the entire Oracle RAC system.

   AlternateServers

   Specifies the connection failover to the other Oracle nodes, if the primary server is not accepting connections.

   Example: (HostName=nete_servername2:PortNumber=1521:ServiceName=nete_servicename[,...])

   LoadBalancing=1

   Turns on client load balancing, which helps to distribute new connections to keep RAC nodes from being overwhelmed with connection requests. When enabled, the order in which primary and alternate database servers are accessed is random.

3. Save the file.

   The Oracle wire protocol driver is configured.

Point the Policy Server to the Database

You point the Policy Server to the database so the Policy Server can read and store audit logs.

To point the Policy Server to the data store

1. Open the Policy Server Management Console, and click the Data tab.

   Database settings appear.

2. Select ODBC from the Storage list.

   ODBC settings appear.

3. Select Audit Logs from the Database list.
4. Select ODBC from the Storage list.

   Data source settings become active.

5. Enter the name of the data source in the Data Source Information field.
   • (Windows) this entry must match the name you entered in the Data Source Name field when you created the data source.
   • (UNIX) this entry must match the first line of the data source entry in the system_odbc.ini file. By default, the first line in the file is [SiteMinder Data Sources]. If you modified the first entry, be sure that you enter the correct value.
6. Enter and confirm the user name and password of the database account that has full access rights to the database instance in the respective fields.
7. Specify the maximum number of database connections allocated to SiteMinder.

   Note: We recommend retaining the default for best performance.

8. Click Apply.

   The settings are saved.

9. Click Test Connection.

   SiteMinder returns a confirmation that the Policy Server can access the data store.

10. Click OK.

    The Policy Server is configured to use the database as an audit logging database.

Restart the Policy Server

You restart the Policy Server for certain settings to take effect.

Follow these steps:

1. Open the Policy Server Management Console.
2. Click the Status tab, and click Stop in the Policy Server group box.

   The Policy Server stops as indicated by the red stoplight.

3. Click Start.

   The Policy Server starts as indicated by the green stoplight.

   Note: On UNIX or Linux operating environments, you can also execute the stop-all command followed by the start-all command to restart the Policy Server. These commands provide an alternative to the Policy Server Management Console.