SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere Nutzervereinbarung und die Datenschutzrichtlinie.
SlideShare verwendet Cookies, um die Funktionalität und Leistungsfähigkeit der Webseite zu verbessern und Ihnen relevante Werbung bereitzustellen. Wenn Sie diese Webseite weiter besuchen, erklären Sie sich mit der Verwendung von Cookies auf dieser Seite einverstanden. Lesen Sie bitte unsere unsere Datenschutzrichtlinie und die Nutzervereinbarung.
The initial version that was released in the mid 1990sand was a simple and limited GUI interface used for some aspects of databaseadministration only (along with a command-line interface, server manager linemode, or svrmgrl).The DBAs at that time saw it as a novelty and used it very sparingly. They laughedat it. But it was the first attempt by Oracle at a GUI management tool.This was followed by Oracle Enterprise Manager, called OEM initially. First OEMVersion 1 was released, followed by OEM Version 2.2, which could be used withOracle Database 8i. The next version, OEM 9i could be used with Oracle Database9i and this was a much better-looking Java console that had to be installed on yourWindows PC or workstation. Even though there were Java-related memory andperformance issues with this version, it had increased acceptance among DBAs,who started using it in greater numbers.The next version, Enterprise Manager (EM) 10g was introduced in the first decadeof this century. It used the N-tier architecture, using Oracle Application Server asthe backend application server for the actual Enterprise Manager Java application.This was an OC4J application, that is, Oracle Containers For J2EE (OC4J) 10g,which was compliant with Java 2 Enterprise Edition (J2EE) 1.4. The EnterpriseManager application was installed centrally as one or more Management Servicesusing the same Central Repository, with Management Agents installed on multipleTargets that communicated with the Management Service. This type of centralizedinstallation of Enterprise Manager was called Grid Control.The backend application server OC4J application was replaced by Oracle WebLogicServer in Enterprise Manager 11g, released in April 2010. This version, for thefirst time, required the WebLogic Server software to be installed first, before theEnterprise Manager 11g Grid Control software was installed.Enterprise Manager Grid Control 10g could manage 8i, 9i, 10g, as well as 11.1databases, and other products such as Oracle Application Server. EnterpriseManager Grid Control 11g was able to manage 11.2 databases as well, althoughsupport for 8i databases was dropped.And in October 2011, during Oracle OpenWorld, the latest Enterprise Manager 12c,renamed Cloud Control instead of Grid Control, was announced with great fanfare.
Oracle Enterprise 12c is rich in GUI as well. The new user interface in Enterprise Manager Cloud Control 12c was developed using the ADF.Enterprise Manager – a section titled New in this Release and a Did you know... section. Every time you go to this consolelogin, some new information is displayed. You can also expand any of the pointsto show more information.
In this new version, you can select your own home page—the page you see when you log in to Cloud Control. Suppose you have just installed Cloud Control and are logging in for the very first time, you will immediately be presented with a collection of home pages, one of which can be chosen as the preferred home page. This is seen in the above screenshot. As we can see here, there are a number of home pages available for DBAs, middleware administrators, level 1 support staff and even Siebel administrators.There is a Summary page that EM Administrators can select; this is closest to the Enterprise Manager home page we used to see in versions 10g and 11g. This shows at a glance the availability and other details of all the Targets where there is an EM Agent talking to this Enterprise Manager system.There is a Databases home page for DBAs. There are also Middleware, Fusion Applications, and SOA home pages, a Service Dashboard page, an Incidents page, and even a Cloud Infrastructure page for monitoring and managing the Cloud infrastructure. Any of these pages can be selected as the home page at this stage, when first logging on. In the future, it is possible to select any other page as the home page by going to Setup | My preferences | Select My Home from the Cloud Control menu.
Let's say we have selected the Summary page as the home page. The page that appears is shown in the above screenshot. As we can see from this page, the Cloud Control Summary page displays the overall availability of all the Targets managed by the Enterprise Manager. You can see which Targets are down, and drill down immediately to find the issue. You can see the critical and warning Incidents that have been raised by the Targets, any Problems,or any Jobs that have failed. You can also drill down to the Patch Recommendations from here—Enterprise Manager Cloud Control 12c connects to My Oracle Support (MOS) and gets a list of all available patches for the Targets, and displays them here. On the second half of the page we can see the inventory at a glance: what type of Hosts, what type of databases, and so on, are present in the enterprise. We can also see the Compliance Summary and the Least Compliant Targets sections, and finally the Service Requests section, which shows the service requests that have been opened. And all this just on the Summary page.
Enterprise Manager Cloud Control 12c is a huge release with a plethora of new features. Here I will discussing/talking about the outstanding features.
Overview of enterprise manager 12c
Overview of Enterprise Manager 12c
Oracle Apps DBA
Introduction to OEM
Introduction to OEM 12c
New features of 12c