OpsMgr Architecture

OpsMgr is primarily composed of five basic components: the operations database, reporting database, Root Management Server, management agents, and Operations Console. These components make up a basic deployment scenario. There are also several optional components that provide functionality for advanced deployment scenarios.

OpsMgr was specifically designed to be scalable and can subsequently be configured to meet the needs of any size company. This flexibility stems from the fact that all OpsMgr components can either reside on one server or can be distributed across multiple servers.

Each of these various components provides specific OpsMgr functionality. OpsMgr design scenarios often involve the separation of parts of these components onto multiple servers. For example, the database components can be delegated to a dedicated server, and the management server can reside on a second server.

The following list describes the different OpsMgr components:

. Operations database—The operations database stores the monitoring rules and the active data collected from monitored systems. This database has a seven-day default retention period.

. Reporting database—The reporting database stores archived data for reporting purposes. This database has a 400-day default retention period.

. Root Management Server—This is the first management server in the management group. This server runs the software development kit (SDK) and Configuration service, and is responsible for handling console communication, calculating the health of the environment, and determining what rules should be applied to each agent.

. Management Server—Optionally, an additional management server can be added for redundancy and scalability. Agents communicate with the management server to deliver operational data and pull down new monitoring rules.

. Management agents—Agents are installed on each managed system to provide efficient monitoring of local components. Almost all communication is initiated from the agent with the exception of the actual agent installation and specific tasks that run from the Operations Console. Agentless monitoring is also available with a reduction of functionality and environmental scalability.

. Operations Console—The Operations Console is used to monitor systems, run tasks, configure environmental settings, set author rules, subscribe to alerts, and generate and subscribe to reports.

. Web Console—The Web Console is an optional component used to monitor systems, run tasks, and manage maintenance mode from a web browser.

. Audit Collection Services—This is an optional component used to collect security events from managed systems; this component is composed of a forwarder on the agent that sends all security events, a collector on the management server that receives events from managed systems, and a special database used to store the collected security data for auditing, reporting, and forensic analysis.

. Gateway Server—This optional component provides mutual authentication through certificates for nontrusted systems in remote domains or workgroups.

. Command shell—This optional component is built on PowerShell and provides full command-line management of the OpsMgr environment.

. Agentless Exception Monitoring—This component can be used to monitor Windows and application crash data throughout the environment and provides insight into the health of the productivity applications across workstations and servers.

. Connector Framework—This optional component provides a bidirectional web service for communicating, extending, and integrating the environment with thirdparty or custom systems.

Source of Information : Pearson-Microsoft Lync Server 2010 Unleashed


Subscribe to Developer Techno ?
Enter your email address:

Delivered by FeedBurner