beautypg.com

Reports and event (error) handling, Preparing to use rdbms synchronization – Cisco 3.3 User Manual

Page 361

background image

9-33

User Guide for Cisco Secure ACS for Windows Server

78-16592-01

Chapter 9 System Configuration: Advanced

RDBMS Synchronization

Replaying transaction logs that slightly predate the checkpoint does not damage
the CiscoSecure user database, although some transactions might be invalid and
reported as errors. As long as the entire transaction log is replayed, the
CiscoSecure user database is consistent with the database of the external RDBMS
application.

Reports and Event (Error) Handling

The CSDBSync service provides event and error logging. For more information
about the RDBMS Synchronization log, see

Cisco Secure ACS System Logs,

page 11-13

. For more information about the CSDBSync service log, see

Service

Logs, page 11-31

.

During manual synchronizations, Cisco Secure ACS provides visual alerts to
notify you of problems that occurred during synchronization.

Preparing to Use RDBMS Synchronization

Synchronizing the CiscoSecure user database using data from the accountActions
table requires that you complete several steps external to Cisco Secure ACS
before you configure the RDBMS Synchronization feature within Cisco Secure
ACS. If you are planning to use a CSV file as your accountActions table, also see

Considerations for Using CSV-Based Synchronization, page 9-35

.

To prepare to use RDBMS Synchronization, follow these steps:

Step 1

Determine where you want to create the accountActions table and in what format.
For more information about the accountActions table, see

About the

accountActions Table, page 9-31

. For details on the format and content of the

accountActions table, see

Appendix F, “RDBMS Synchronization Import

Definitions”

.

Step 2

Create your accountActions table.

Step 3

Configure your third-party system to generate records and update the
accountActions table with them. This will most likely involve creating stored
procedures that write to the accountActions table at a triggered event; however,
the mechanism for maintaining your accountActions table is unique to your