1.4 Understanding Site Communication

AppManager manages and monitors the availability, performance, and server health of operating system services, hardware, and applications through jobs. When you run a Knowledge Script on an agent computer and create a job:

  • The Control Center console delivers information about the properties you have set for the Knowledge Script to the QDB.

  • When the management server next checks the QDB, it identifies the new job and collects all of the information about the job to send it to the appropriate agent computers.

    NOTE:In addition to submitting new and changed job information, the management server periodically polls all of the agent computers it is allowed to communicate with to check the health of the agents on each agent computer.

  • The NetIQ AppManager Client Resource Monitor (NetIQmc) service on the agent computer receives the job information from the management server, stores the information in a local repository, then executes the job to begin monitoring.

  • When the job runs, the Knowledge Script invokes program objects that collect performance data or perform tasks by accessing raw system statistics, through APIs, or using other methods.

    The following diagram illustrates the basic flow of job information between the Operator Console or Control Center console and the agent (managed) computer (in this diagram the agent computer and the managed computer are the same).

  • If the job detects an event condition or collects data, the NetIQ AppManager Client Communication Manager (NetIQccm) service or nqmdaemon daemon sends the event information or data point to the management server. If the NetIQccm service or nqmdaemon daemon cannot communicate with the management server, it saves the event information or data point in the agent computer’s local repository until the management server is available.

  • When the management server receives event information or data points from the agent computer, it forwards this information to the repository server to update the QDB.

  • Once the QDB is updated, any new events or data points are sent to Control Center at its next update interval (for example, in the next 30 seconds for an active view or in five minutes for a background view).