06.05.2013 Views

User Guide for Cisco Secure Access Control Server - Stewing Home

User Guide for Cisco Secure Access Control Server - Stewing Home

User Guide for Cisco Secure Access Control Server - Stewing Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RDBMS Synchronization<br />

8-32<br />

<strong>User</strong> <strong>Guide</strong> <strong>for</strong> <strong>Cisco</strong> <strong>Secure</strong> <strong>Access</strong> <strong>Control</strong> <strong>Server</strong> 4.2<br />

Chapter 8 System Configuration: Advanced<br />

Step 7 (ACS <strong>for</strong> Windows) Set up a system DSN on the senior synchronization partner (the ACS that will<br />

communicate with the third-party system). For steps, see Configuring a System DSN <strong>for</strong> RDBMS<br />

Synchronization (ACS <strong>for</strong> Windows), page 8-32.<br />

Step 8 Schedule RDBMS synchronization on the senior synchronization partner. For steps, see Scheduling<br />

RDBMS Synchronization, page 8-36.<br />

Step 9 Configure your third-party system to begin updating the accountActions table with in<strong>for</strong>mation that will<br />

be imported into the ACS internal database.<br />

(ACS SE) If needed, activate the mechanism that is to copy the accountActions file to the applicable<br />

directory on the FTP server.<br />

Step 10 Confirm that RDBMS synchronization is operating properly by monitoring the RDBMS<br />

Synchronization report in the Reports and Activity section. For more in<strong>for</strong>mation about the RDBMS<br />

Synchronization log, see ACS Audit Logs, page 10-5.<br />

Also, monitor the CSDBSync service log. For more in<strong>for</strong>mation about the CSDBSync service log, see<br />

Service Logs, page 10-12.<br />

Configuring a System DSN <strong>for</strong> RDBMS Synchronization (ACS <strong>for</strong> Windows)<br />

On the ACS, a system DSN must exist <strong>for</strong> ACS to access the accountActions table. You can use a local<br />

AccountActions CSV file to obtain a DSN <strong>for</strong> RDBMS Synchronization. ACS creates a default DSN<br />

<strong>Cisco</strong><strong>Secure</strong> DBSync using a Microsoft Text Driver to process the local CSV files. ACS extracts the<br />

contents from the CSV file at the specified location, process the contents and renames the file with .done<br />

extension. If the Use local CSV file option is disabled, ACS per<strong>for</strong>ms RDBMS Synchronization as usual.<br />

Tip Everything ACS does with ODBC requires System DSNs. <strong>User</strong> DSNs will not work. Confusing the two<br />

DSNs is an easy mistake to make when configuring the datasources in the ODBC control panel applet.<br />

Ensure your System DSN is set properly.<br />

For more in<strong>for</strong>mation about the <strong>Cisco</strong><strong>Secure</strong> Transactions.mdb file, see Preparing to Use RDBMS<br />

Synchronization, page 8-30.<br />

To create a system DSN <strong>for</strong> use with RDBMS synchronization:<br />

Step 1 From Windows <strong>Control</strong> Panel, open the ODBC Data Source Administrator window.<br />

Tip In Windows 2000 and new Microsoft operating systems, the ODBC Data Sources icon is located<br />

in the Administrative Tools folder.<br />

Step 2 In the ODBC Data Source Administrator window, click the System DSN tab.<br />

Step 3 Click Add.<br />

Step 4 Select the driver to use with your new DSN, and then click Finish.<br />

A dialog box displays fields requiring in<strong>for</strong>mation that is specific to the selected ODBC driver.<br />

Step 5 In the Data Source Name box, enter a descriptive name <strong>for</strong> the DSN.<br />

Step 6 Complete the other fields that the selected ODBC. These fields may include in<strong>for</strong>mation such as the IP<br />

address of the server on which the ODBC-compliant database runs.<br />

OL-14386-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!