Skip Headers
Oracle® Audit Vault Server Installation Guide
10g Release 2 (10.2.2) for Solaris Operating System (SPARC 64-Bit)

Part Number B32388-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

1 Oracle Audit Vault Server Installation Overview

Oracle Audit Vault is a powerful enterprisewide audit solution that efficiently consolidates, detects, monitors, alerts, and reports on audit data for security auditing and compliance. Oracle Audit Vault provides the ability to consolidate audit data and critical events into a centralized and secure audit warehouse.

This chapter provides an overview of the Oracle Audit Vault Server installation process. This chapter includes the following sections:

1.1 Audit Vault Installation Components

Oracle Audit Vault software installation consists of two parts:

1.2 Audit Vault Installation Methods

You can choose different installation methods to install Oracle Audit Vault Server, as follows:

1.2.1 Interactive Installation Methods

When you use the interactive method to install Oracle Audit Vault, Oracle Universal Installer displays a series of screens that enable you to specify all of the required information to install the Oracle Audit Vault software.

1.2.2 Automated Installation Methods Using Response Files

Oracle Audit Vault provides a response file template for Audit Vault Server (av.rsp). The response template file can be found in the AV installer location/response directory on the Audit Vault Server installation media.

When you start Oracle Universal Installer and specify a response file, you can automate all of the Oracle Audit Vault Server installation. These automated installation methods are useful if you need to perform multiple installations on similarly configured systems or if the system where you want to install the software does not have X Window system software installed.

For Audit Vault Server, Oracle Universal Installer can run in silent (noninteractive) mode. For silent mode, specify both the -silent and -responseFile options followed by the path of the response file on the command line when you invoke Oracle Universal Installer. For example:

./runInstaller -silent -responseFile Path of response file

Oracle Universal Installer runs in silent mode if you use a response file that specifies all required information. None of the Oracle Universal Installer screens are displayed, and all interaction (standard output and error messages) and installation logs appear on the command line.

Prepare the response file by entering values for all parameters that are missing in the first part of the response file, then save the file. Do not edit any values in the second part of either response file.

See Section 3.6 for information about performing an Audit Vault Server silent installation:


The basic installation is not supported in silent mode. Silent installation is only supported for the advanced installation.

1.3 Audit Vault Server Installation

The Audit Vault server installation consists of two options:

The Audit Vault Console uses a wallet in the $ORACLE_HOME/network/admin/avwallet directory. An Oracle wallet is a password-protected container that stores credentials, such as certificates, authentication credentials, and private keys, all of which are used by Secure Sockets Layer (SSL) for strong authentication. Oracle wallets are managed through Oracle Wallet Manager. Oracle Wallet Manager can perform tasks such as creating wallets, requesting certificate generation, and importing certificates into the wallet.

The wallet is used to store the user name and password of the user granted the AV_ADMIN role. This user name is used by the Audit Vault Console to allow communication with Oracle Audit Vault. The Audit Vault Console provides the management service that initiates the communication with agents using HTTP. The Audit Vault Configuration Assistant (AVCA) modifies the Oracle Enterprise Manager Database Control console server.xml file and other related files to enable Audit Vault management through the Audit Vault Console.

If certificate-based authentication is used for communication with any agent, the Audit Vault administrator must acquire the necessary server-side certificates and set up Oracle Wallet for storing the certificates on the server. This server-side certificate is used for authenticating the Audit Vault Server to the agent. Similarly, agents must each have a certificate to authenticate each agent to the Audit Vault Server.

Communication at the management level between the Audit Vault Server and the Audit Vault Agent can be secured after the installation is complete. This is done as part of the postinstallation configuration, in which SSL is configured for the mutual authentication between the Audit Vault management service on the server side and each agent over HTTPS.

After you check the requirements described in Section 1.4, the general steps to install Oracle Audit Vault Server include these tasks:

  1. Run Oracle Universal Installer to perform Audit Vault Server installation.

  2. Run postinstallation and configuration tasks using AVCA.

1.4 Installation Considerations

This section contains information that you should consider before deciding how to install this product. It includes contains the following topics:

1.4.1 Hardware and Software Considerations

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system versions might be certified after this guide is published, review the certification matrix on the OracleMetaLink Web site for the most up-to-date list of certified hardware platforms and operating system versions. The OracleMetaLink Web site is available at

If you do not have a current Oracle Support Services contract, then you can access the same information at

1.4.2 Multiple Oracle Homes

This product supports multiple Oracle homes. This means that you can install this release of the software more than once on the same system, in different Oracle home directories. See Section 2.5.3 for more information.