The site administrator, working with an implementation team, senior‑level system administrators, and application experts, is typically responsible for determining site-level policies for managing jobs, events, and data, and for configuring and maintaining AppManager components.
Ideally, you make most, if not all, of these decisions before installing AppManager in a production environment, but often these policies and the implications of the decisions you make are not fully understood until the site is up and running. In most cases, you can make changes and refine policies after installation but it is always best to perform the planning and pre-installation steps described in the Installation Guide for AppManager, available on the AppManager Documentation page, before you install any AppManager components.
The site administrator should actively participate in the following actions during the planning and pilot deployment phases:
Develop a core list of management goals.
Develop a deployment plan that addresses your network and site configuration. For example, which components you should install together and which you should install separately and whether your management site requires a single management server or multiple management servers.
Develop a security plan to determine the level of security to use, the user authentication mode you are using for SQL Server, and the number of users and administrators to be given access.
Verify that pre-installation tasks are complete for the production environment, including a check of network connections, account requirements, and account permissions. For more information about performing pre-installation tasks, see the Installation Guide for AppManager, available on the AppManager Documentation page.
For large and widely distributed organizations, many of the decisions you need to make are relatively complex and require a thorough understanding of your own network requirements and constraints of the AppManager architecture. For these organizations, in particular, NetIQ Corporation recommends that you review all of this guide and the Installation Guide for AppManager.
After you successfully install all of your AppManager components, you typically perform a variety of post-installation tasks to properly configure the environment. These tasks include:
Defining or identifying the SQL Server logins and users who should have access to AppManager.
Changing the account information for the agent or the management server.
Setting event- and data-handling policies and preferences for the site.
Creating core Knowledge Script groups and monitoring policies for the site.
Updating application-specific information.
After you install and configure AppManager, you typically monitor the health of AppManager components, perform periodic database maintenance, optimize communication flow and console performance, maintain user accounts and security profiles, and troubleshoot problems within the environment.
For some of the common activities you perform as the site administrator, you use the Operator Console and Control Center console, but many of the tasks require other tools or programs. For example, setting up AppManager users might require standard Windows administrative tools, SQL Server Management Studio, and AppManager Security Manager. You should be familiar with these administrative tools as well as the basic operation of AppManager.