6.1 Understanding QDB Installation

Typically, you install the QDB and the management server on different computers. NetIQ Corporation recommends that you also install an agent on the same computer as the QDB to facilitate database management. For more information about installing agents, see Section 8.0, Installing Agent Components.

You can install the QDB to remote SQL Servers. You do not have to run the setup program on the SQL Server.

If you plan to install a report agent and you want the agent to generate Active Directory reports, install the QDB on a member server of the same domain or a trusted domain. For more information about report agents, see Section 8.1.3, Understanding Agent Reporting Capabilities.

You can install the QDB and the CCDB on computers that belong to different domains. For more information about installing the CCDB, see Section 7.0, Installing Control Center Components.

For information about installing the QDB on MSCS, see the Section D.0, Installing on Microsoft Cluster Service.

6.1.1 Understanding Accounts Required for the Installation

During QDB installation, the setup program prompts you for an account that can log in to the SQL Server to create the QDB, and for an account to serve as database owner of the QDB. The database owner account will be used to create tables, users, and stored procedures and manage data in the QDB. For more information about the account requirements, see Section 2.3, Reviewing Required Accounts and Permissions.

6.1.2 Understanding QDB Security Options

During QDB installation, you specify security options for the agent computers that report to the QDB. Depending on your environment, you can configure security for Windows agents only, for UNIX agents only, or for both Windows and UNIX agents.

The security level you select during QDB installation affects all communications between the management servers and agent computers within the management site. AppManager offers the following options for securing communication between agents and management servers:

  • Encrypted communications only

    If you select this option, AppManager encrypts data transmissions between agents and management servers, but does not require agents to authenticate the management servers with which they communicate.

  • Authentication and encrypted communications

    If you select this option, AppManager encrypts data transmissions between agents and management servers and requires agents to authenticate management servers before they transmit data.

If you select either of the secure communication options when you install the QDB, the setup program creates a password-protected encryption key in the QDB and prompts you for a password for agents to use to access their portion of the key. When you install agents, ensure the agents use the same security level and password as the QDB to which they will report.

For more information about security and managing site communications between management servers and agent computers, see the Administrator Guide for AppManager, available on the AppManager Documentation page.

6.1.3 Restricting Knowledge Script Check-in

The setup program checks a copy of every current Knowledge Script into the QDB during installation. To exclude Knowledge Scripts associated with applications you do not use, remove the applicable files from the \Setup\Setup Files folder. For example, to exclude all Knowledge Scripts in the AppManager for BlackBerry and AppManager for BES Knowledge Script categories, delete the following files from the Setup Files folder, where xx is the AppManager or module version:

  • AM xx -BlackBerry- xx .ini

  • AM xx -BlackBerry- xx .msi

  • AM xx -BES- xx .ini

  • AM xx -BES- xx .msi

WARNING:Do not remove any executable files, such as ckBES.exe.