Oracle Enterprise Manager 10g Grid Control Implementation Guide P2

Oracle Enterprise Manager 10g Grid Control Implementation Guideand many other types of targets as well. It is best practice to run either Grid Control or Database Control, but not both, although you can run both concurrently.Grid Control vs. AS ControlHow is Grid Control different from Application Server (AS) Control? In short, as just one of many target types it monitors, Grid Control monitors the Oracle Application Server, whereas AS Control administers the Oracle Application Server.
Nội dung trích xuất từ tài liệu:
Oracle Enterprise Manager 10g Grid Control Implementation Guide P224 Oracle Enterprise Manager 10g Grid Control Implementation Guide and many other types of targets as well. It is best practice to run either Grid Control or Database Control, but not both, although you can run both concurrently. Grid Control vs. AS Control How is Grid Control different from Application Server (AS) Control? In short, as just one of many target types it monitors, Grid Control monitors the Oracle Application Server, whereas AS Control administers the Oracle Application Server. Grid Control Monitors Oracle Application Server While Grid Control administers all Oracle products in your enterprise, it only monitors the Oracle Application Server—both the AS bundled with Grid Control and any separate AS targets that Grid Control monitors. Monitoring AS instances in the Grid Control Console encompasses real-time monitoring, alerting, and historical data collection, just as with any other Grid Control target. For example, the Application Servers tab within the GC Console reveals the status, alerts, policy violations (noncompliance with a desired state for security, configuration, or storage), and resource usage of all Application Servers and their subcomponents, as shown here. Chapter 1: Overview of the Grid Control Architecture 25AS Control Administers Oracle Application ServerBy contrast, use the standalone AS Control Console to administer AS subcomponents. To get abetter understanding of what it means to administer the Application Server, take a look at the ASControl Console home page, accessible directly at http://:1156 on UNIX or http://:18100 on Windows, or through the Grid Control Console on the Application Serverhome page using the Administer link. From the AS Console home page, you can control OMS and non-OMS Application Serversubcomponents—the Oracle HTTP Server, OC4J instances, and Web Cache. This control is fromA to Z; you can stop, start, restart, enable, or disable subcomponents. You can also gatherinformation about the management software itself by clicking the Management link at the bottomof the System Components section on the Application Server home page. The AS Console hasfour other tabs: J2EE Applications (which allow you to view response times for OC4J instances),Ports (which you can change through the UI), Infrastructure (including Identity Management andOracleAS Farm Repository Management), and Backup/Recovery (of AS data and configurationfiles). Without going into more detail, as Application Server Control is beyond the scope of thisbook, I hope I’ve given you just enough information to make the distinction clear between GridControl and Application Server Control.26 Oracle Enterprise Manager 10g Grid Control Implementation Guide Agents for Grid Control, Database Control, and AS Control Now that we are clear that Grid Control, Database Control, and Application Server Control are all distinct, you’re probably not surprised to hear that separate Agents exist for each. The Grid Control central Agent on each managed host (including OMS and OMR hosts) monitors all targets on that host and uploads target information to the SYSMAN schema in the Management Repository. NOTE In this book, Management Agent or Agent refers to the central Grid Control Agent. The Database Control Agent, on the database host, similarly stores data in a SYSMAN schema, but this schema is local to its associated Oracle database. In contrast to both Grid Control and Database Control Agents, the Application Server Control Agent, bundled with the Oracle Application Server, only communicates real-time data internally to the Application Server Control, as there is no Repository for historical data. All three Management Agents are distinct. They run from their respective home directories—the Grid Control Agent from its own Agent home, the Database Control Agent from the database home, and the Application Server Control Agent from the Application Server home including that for the OMS. Grid Control, Database Control, and AS Control: All Together Now Let’s build on the topology of Grid Control core components shown earlier in Figure 1-2 by adding Database Control and Application Server Control to the mix, as represented in Figure 1-4 (I’ve omitted protocols for clarity). I have also included four typical managed targets: a 10g Database Server, a 10g Application Server, an 8i/9i Database Server, and a third-party application. For good measure, the figure illustrates two OMS hosts, with two of the central Agents uploading management data to one of the OMS hosts, and the remaining two Agents uploading to the other OMS host.14 In addition, a Grid Control Console communicates with an OMS, which also receives Agent uploads of target metric data. Although each OMS only receives data from the particular Agents that report to it, each OMS uploads this data to a central Management Repository, which in turn makes information from all Agents available to each OMS. This allows any GC Console to administer or monitor all Grid Control targets. On the other hand, a particular Database Control Console is in contact with just one database, and likewise, a particular AS Control Console connects with just one Oracle Application Server. The Database and AS Consoles are privy only to local database and Application Server data, respectively. All three Consoles can operate concurrently, but (as already stated) it is best to shut down Database Control when using Grid Control, as Grid Control can administer each of the databases to which a particular Database Console ...