Future Directions of EM

Transcription

1 Future Directions of EM

2 Oracle Enterprise Manager 101 This appendix provides a look towards future releases of EM. First, we mention some of the new features planned for the release of EM that ships after the database release. Oracle will provide a new HTML interface for the management tools provided within Enterprise Manager. Mozart is the code name for the set of these new features that will be provided in EM during the next few releases. Mozart will be visible initially with the release of Oracle s Application Server ias release 2, which can be administered with the new Web-based EM, taking advantage of some featuresofthemozartarchitecture.thefullversionofmozartwillinitiallybedeployed internally, and is currently planned to be made available to customers in the post-9i Release 2 timeframe. Mozart features not only ias and database management, but also client-side monitoring of Web applications, and asoftware management solution. Note that all features and timelines mentioned in this chapter are subject to change. EM9i Release 2 New Features The Oracle9i database Release 2 is available with a new release of the Java-based Enterprise Manager, which is also called EM9i release 2. This release has some new features focusing on database management: Support for Oracle Streams, which is a new database technology intended to be used for replicating data in distributed environments. The advanced database management categories in the console navigator tree will be rearranged into two folders called Distributed and Warehouse for abetter overview. Distributed will contain in-doubt transactions, database links, streams, advanced queues, and advanced replication. Warehouse will contain OLAP and Summary Management. In addition, you can optionally arrangetheschemaobjectsinacategorizedwaytomakethemeasiertoview. Oracle 9i introduces the XML database, which is a system designed to store and retrieve XML documents both via relational and hierarchical access APIs. EM helps to configure and manage this XML database. That includes configuration and protocol management and XML schema definition, as well as managing access to and manipulation of resources. Enhancements in the field of backup and recovery, such as automatic management of previous backups and support of individual block recovery. Similar to the buffer cache advisor currently deployed in EM, EM Release 2 is planned to have similar advisors for the Program Global Area (PGA), the Mean Time to Recover (MTTR), and the Shared Pool.

3 Future Directions of EM Support of new features in Resource Manager such as automated consumer group switching, operation queuing, maximum estimated execution time, undo quota, and statistics on consumed resources. Schema management features including simultaneous action for multiple objectssuchasrecompilingallinvalidobjectsorchangingstorageparameters, enablingordisablingallconstraintsonatable,listoffunctionsandprocedures in a package, the schema tree simplifications mentioned previously, support for Java classes and resources, and support for rename constraint and rename column commands. SQL Scratchpad is the name of a new interface for SQL and PL/SQL editing and development and database querying. Features include SQL editing, including color coding of SQL, tabular formatted results window, both graphical and tabular execution plan access, execution time and rows returned for individual statements, and a history of all run SQL commands. EM enables you to switch automatic segment management for tablespaces on or off. With automatic segment management, objects automatically manage their free space, whereas with manual segment management, objects manage their free space using free lists. EM helps to map database files to devices along with device statistics to identify I/O performance. Files can be mapped to intermediate layers of logical volumes, which can be mapped to actual physical devices. EM displays these file mappings, their logical grouping, and the properties of the storage device. The file topology is displayed graphically. Support for optional deletion of datafiles when dropping a tablespace. Enhancements for Data Guard management regarding logical standby, multiple standby sites, and failover/switchover functionality. EM will offer the same functionality for Real Application Clusters (RAC) Cluster Databases and Cluster Database Instances as it does for singleinstance databases. LogMiner enhancements include integration with Recovery Manager, session filtering by System Change Number (SCN) range, access to various LogMiner session options flags, access to the LogMiner MINE_VALUE function, and support for any V$LOGMNR_CONTENTS columns. OLAP enhancements include providing default values for the Dimension Wizard, support for analytic workspaces, support for additional dimensions, and fact table styles and time dimensions that generate the lookup table.

4 Oracle Enterprise Manager 101 Spatial data management enhancements: geometry type constraints to index createstatements,changeprobequeriestoonlyqueryall_sdo_geom_metadata, function-based index support, and new layers in different coordinate systems. The Change Management Pack will include afeature enabling you to clone an existing schema with asubset of production data for testing or development purposes. TheDiagnosticsPackwillincludeanewRAC-Overviewchartandwilldisplay datadeterminedbythedatabaseastopsegments. Project Mozart Project Mozart is the internal code name for a new set of EM features that are based on Internet-technologies such as HTML and XML. These new features are the logical consequence of Oracle s manageability strategy outlined in Chapter 1. EM version 9i has brought a massive move towards Internet-based technology, through making all Java-based tools available to be run as an applet in Windows-based browsers, and offering real-time monitoring data through EM s Reporting Website as pure HTML charts on any platform. The new HTML-based EM is a new feature enhancing the Java-based EM. Mozart combines performance monitoring, administration, and software management. Architecture The new EM naturally has agui that is HTML-based. Because EM features a monitoring mechanism, it stores data in a repository, which consists of a set of tables that can be stored in any existing database account, just like the repository used by the Java-based EM. Because the console consists of a number of viewlets, servlets, and so on, which are stored on the node containing the repository, the console can be customized or built into a portal very easily. In combination with its security model, you can customize access to certain features or data for specific user groups or DBAs. This architecture also eliminates the need for an OMS as we know it today. What still exists is a monitoring daemon on the target nodes, which provides overall performance data and gives operating system insights in the most effective way. Mozart offers asoftware development kit (SDK), and all components are built on open standards, enabling users and integrators to extend its monitoring capabilities to even non-oracle components like routers, storage devices, or others. The new architecture is based on standard APIs and languages like HTML, XML, SNMP, and WBEM.

5 Future Directions of EM Performance Monitoring With applications moving to use Internet technology, administrators need the ability tomonitortheoverallhealthofanapplication.oneofthemostimportantkeyindicators for how well systems are running is the performance from the end-user perspective, in other words, the Web client response time. Mozart enables DBAs to monitor this response time in real time and split it up into components like network transmission or system transaction time. DBAs can monitor the application itself, determining user connection abandonment rates, or the slowest response times by visitor or domain, in addition to typical metrics like overall application availability and performance. In addition, the systems can be monitored too, because they are a vital component of the overall Web application: routers, operating systems, databases, Web servers, and more. The goal is to have a complete monitoring solution for all components involved in delivering aweb application to the end-user: client response, application performance, and system performance. Administration Whereas the current version of EM s reporting framework offers information about systems through the Web in read-only mode, Mozart s HTML interface enables DBAs to actively administer systems. You can create database users, increase storage space, modify Web server configuration parameters, and examine database objects through the Web. The interface also includes state-of-the-art wizards and advisors. Managing 9iAS release 2 Release 2of the Oracle Application Server features an HTML GUI that includes some of the functionality defined in Mozart. It consists of two components: The Oracle9iAS Administration Service and the Oracle9iAS Homepage, which is provided by the Oracle9iAS Administration Service. Web-based EM can be used with or without the EM three-tier architecture. If the three-tier architecture is installed, the administration service provides the OMS with the ias services it is managing, which are displayed in the Java console, allowing you to launch the 9iAS homepage directly from there. You can then use the agent to monitor the HTTP Server and Oracle Containers for J2EE (OC4J) components. 9iAS Administration Service The Administration Service is capable of discovering and managing all application server instances on a single host node. Note that a 9iAS instance can consist of multiple ias components like Oracle HTTP Server (OHS), Oracle Containers for

6 Oracle Enterprise Manager 101 J2EE (OC4J), Oracle Web Cache, Oracle Portal, Oracle Forms, Oracle Reports, and Oracle Discoverer. In addition to discovering, the administration service includes numerous administration features like single sign-on, 9iAS cluster management, configuration, deploying J2EE (Java 2 Platform, Enterprise Edition) applications to OC4J containers or automatic monitoring of status, and usage and performance of both host and ias components. 9iAS Homepage Most features are accessible through the 9iAS Homepage, which displays instance availability, CPU and memory consumption, and uptime. It also offers links to manage of the other components of a9ias mentioned previously, which are managed through their own respective Homepages. The OHS Homepage, for example, displays availability, user volumes, used system resources, server load, responsiveness, and percentage of requests encountering errors. In addition, it enables you to configure listening addresses and ports, log files, monitor the HTTP Server, or add multiple virtual hosts easily. Similarly, you can administer J2EE containers through the OC4J Homepage.ThisHomepageoffersfunctionalityreachingfrommonitoringperformance or status to deploying a new OC4J application to the J2EE container using a wizard. Software Management The expressions Software Management and Change Management are often used synonymously, meaning the changing, upgrading, or patching of the operating system or installed software. The Change Management Pack that manages changes in object definitions inside a database is often confused with this area. In EM, you use the term Software Management to describe managing software installations, which is one of the new areas to be covered by future versions of EM. In general, EM is meant to make software management easier. That means that EM identifies the current patch level of currently installed Oracle software, and the operating system, and also keeps track of all changes made to an installation over time. DBAs can then establish a baseline that defines a software installation level. As DBAs can compare schemas in the Change Management Pack, DBAs can compare software installations between systems, or between systems and baselines with EM s Software Management to easily identify differences. EM can frequently check whether there are new patches available from Oracle that should be applied, and collect them in a central inventory. The goal is to free the DBA from having to check for new patches frequently. Through the central repository, each patch only has to be downloaded once. The patches in the Patch Depot can then be applied to selected systems with the help of an integrated wizard.