Configuring SQL Accounting

You must configure both Steel-Belted Radius Carrier and the SQL database to support SQL accounting. The configuration procedure must be tailored to the database that you use. However, all procedures must give the following results:

• The SQL server must be configured to be listening for client requests. For SQL purposes, the Steel-Belted Radius Carrier server must be a client of the SQL server.

• The Steel-Belted Radius Carrier server must know the machine where the SQL server software runs, and it must know the protocol and port used in communicating with that machine.

• The required transport must be in place between SQL client and server.

Files

Files

The files listed in Table 50 establish settings for configuring SQL accounting in Steel-Belted Radius Carrier. For more information about these files, refer to the SBR Carrier Reference Guide.

Using the SQL Accounting Configuration File

Using the SQL Accounting Configuration File

To configure SQL accounting, you must edit the accounting configuration file (radsql.acc (Solaris and Oracle) or radsqljdbc.acc (Solaris and JDBC)), located in the same directory that contains the Steel-Belted Radius Carrier daemon.

You must modify certain options in the accounting configuration file to accommodate your own database. After you update your accounting configuration file and restart Steel-Belted Radius Carrier, accounting proceeds as you have configured it.

Using Multiple SQL Databases

Using Multiple SQL Databases

You can configure Steel-Belted Radius Carrier to log accounting transactions against more than one SQL database.

To add an additional database, create a new configuration file with extension .acc in the same directory as radsql.acc (Solaris and Oracle) or radsqljdbc.acc (Solaris and JDBC). You can give this file any name you like, provided its extension is .acc. At startup, Steel-Belted Radius Carrier enumerates all .acc files to create its list of accounting modules.