• Download PDFs
• Configuring a Database to Store Account and Session Data  

• Related Topics
• Overview of the SRC-VTA
• Managing VTA Accounts and Sessions
• Configuring the SRC-VTA to Manage Database Accounts
• Troubleshooting Database Deadlocks
• Using SRC-VTA Keys to Manage Accounts and Sessions
• Deleting Information from the VTA’s Database

Configuring a Database to Store Account and Session Data

The SRC-VTA requires a relational database to store accounts and session data. For information about databases that we have tested for use with the SRC-VTA, see the SRC Application Library Release Notes.

To configure a database:

1. For each VTA, create a database that uses the schema for the SRC-VTA.

   To view the database schemas, see the following files, which are created when you install the Solaris package for the SRC-VTA.

   • /opt/UMC/conf/vta/quota/vtadata.sql
   • /opt/UMC/conf/vta/bucket/vtadata.sql
   • /opt/UMC/conf/vta/quota/vtadata_oracle.sql
   • /opt/UMC/conf/vta/bucket/vtadata_oracle.sql
2. Configure access to the database for an administrator by using the SRC-VTA to monitor and manage subscribers.

   The access parameters that you configure must match the access parameters that you configure for the data sources created in the J2EE application server (see Configuring the J2EE Application Server).