ehealth Administration Overview Guide

Transcription

1 ehealth Administration Overview Guide MN-EHADMOV-001 October 2006

2 This documentation (the "Documentation") and related computer software program (the "Software") (hereinafter collectively referred to as the "Product") is for the end user's informational purposes only and is subject to change or withdrawal by CA at any time. This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Software are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the Software is limited to the period during which the license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS PRODUCT, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of this Product and any product referenced in the Documentation is governed by the end user's applicable license agreement. The manufacturer of this Product is CA. This Product is provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (c)(1)(ii), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2006 CA. All rights reserved.

3 Table of Contents Preface 5 Audience About This Guide Reading Path Revision Information Documentation Conventions Technical Support Chapter 1 ehealth Administration Roadmap 9 Discovering Your Resources Creating Elements Maintaining Your Data Collection Managing Discovered Elements and the ehealth Poller Maintaining Your Poller Configuration Managing Reports Understanding ehealth Data Analysis Managing Scheduled System Jobs Where to Go for More Information Managing ehealth System Processes Where to Go for More Information Managing the Database Data Storage Where to Go for More Information

4 4 Table of Contents Types of ehealth Systems Standalone ehealth Distributed ehealth Remote Polling Traffic Accountant Chapter 2 ehealth User Interfaces 19 Administrator Roles ehealth Console Administrative Options Command Line Interface Web User Interface Administrative Options OneClick for ehealth Administrative Options Chapter 3 Maintaining Your ehealth System 25 Using Advanced Logging to Troubleshoot Problems Upgrading to New Releases Installing Service Packs Index 27

5 Preface Audience The ehealth network management software locates devices, agents, and management systems within your infrastructure and collects data on them. This guide provides an overview of ehealth administration important ehealth concepts, the methods that ehealth uses to collect data on your resources, the various user interfaces available, and the primary tasks required of an ehealth administrator. This guide supports ehealth Release 6.0 and later. This guide is intended for anyone who must perform any of the following ehealth administration tasks: Resource discovery Element, poller, and groups management Report generation and customization Job scheduling ehealth system and process management Database management To use this guide, you should know how to use windows-based applications and have some understanding of the operating system. You should also be familiar with basic network terminology. 5

6 6 Preface About This Guide This section describes the reading path that you should follow, as well as the revision history of this guide. It also includes the documentation conventions used in this guide. Reading Path Prior to reading this guide, you should become familiar with ehealth technology concepts as described in the Introduction to ehealth guide. After reading this guide, you can refer to these ehealth documents for detailed information regarding administration tasks: ehealth Resource Discovery Guide ehealth Element and Poller Management Guide ehealth Report Management Guide ehealth Scheduled Job Management Guide ehealth System Management Guide ehealth Database Management Guide All of these documents are available in PDF format in the Administration area of the ehealth Web Help and on the Support Web site. Revision Information This is the first release of this guide. Documentation Conventions Table 1 lists the conventions used in this document. Table 1. Documentation Conventions (Page 1 of 2) Convention File or Directory Name code emphasis Description Text that refers to file or directory names. Text that refers to system, code, or operating system command lines. Text that refers to guide titles or text that is emphasized.

7 Technical Support 7 Table 1. Documentation Conventions (Page 2 of 2) Convention Description enter Text that you must type exactly as shown. 1 Name New Term Variable NOTE Text that refers to menus, fields in dialog boxes, or keyboard keys. Text that refers to a new term, that is, one that is being introduced. Text that refers to variable values that you substitute. A sequence of menus or menu options. For example, File Exit means Choose Exit from the File menu. Important information, tips, or other noteworthy details. CAUTION WARNING Information that helps you avoid data corruption or system failures. Information that helps you avoid personal physical danger. Technical Support If you have a Support Contract ID and password, you can access our Support Express knowledgebase at the following URL: If you have a software maintenance contract, you can obtain assistance with ehealth. For online technical assistance and a complete list of primary service hours and telephone numbers, contact Technical Support at

8

9 1 ehealth Administration Roadmap As an ehealth administrator, you use the ehealth Suite of software applications to report on the performance, capacity, availability, and response time of your network, systems, and applications. The standard ehealth product includes an integrated database and four user interfaces that you can use to collect historical data on your resources and generate reports. This chapter describes the task path, or administration roadmap, that you need to follow to successfully administer your ehealth software. It also provides an overview of the most important concepts relating to ehealth administration such as resource discovery, element and poller management, group management, report generation, and scheduled job management. Although you may not hold responsibility for performing all ehealth administrative functions for your organization, it is important to understand all of the primary tasks. Throughout this chapter, you are directed to other guides for detailed information. Each one of these documents is available in PDF format in the Administration section of the ehealth Web Help. They are also available on the Support page of the product Web site at Discovering Your Resources To monitor and manage the performance of networks, systems, and applications, the ehealth software locates resources, or elements, within your infrastructure and collects data on them. ehealth monitors two types of elements: statistics elements, which are devices and interfaces within the network; and conversation elements, which monitor traffic flow among nodes and applications using the network. 9

10 10 Chapter 1 ehealth Administration Roadmap Statistics elements include the following: Local area network (LAN) and wide area network (WAN) interfaces Quality of Service (QoS) Routers, their central processing units (CPUs), and interfaces Mobile wireless and wireless interfaces Systems, their disks, interfaces, partitions, CPUs, and process sets Remote access server (RAS) devices, modem pools, modems, and Integrated Services Digital Network (ISDN) interfaces Application services and their process sets Response sources, destinations, and paths Synchronous Optical Network (SONET) interfaces Storage area networks (SANs) Digital subscriber line (DSL) interfaces and cable modems Voice over IP (VoIP) features such as call managers, voice line quality, and services Conversations elements include devices that use Remote Network Monitoring version 2 (RMON2) or similar agents to monitor traffic, and Cisco NetFlow collectors. Creating Elements The process of locating your resources and creating elements for them is referred to as discovery. To find the resources, ehealth uses Simple Network Management Protocol (SNMP) agents to search for the IP addresses that you specify. It then obtains information from the management information base (MIB) of each device and creates elements based on that information. When you save the discover process results, ehealth stores the element information in its database and its poller configuration. Importing Element Information Using DataSync If you have a network management system (NMS) or other source at your site that collects configuration information and data for your resources, you can use the ehealth DataSync application programming interface to import your element information. To use DataSync successfully, however, you must be comfortable creating programs, scripts, and files that use complex syntax and have a working knowledge of ehealth. For detailed instructions, refer to the ehealth Integration Guide.

11 Discovering Your Resources 11 Using Integration Modules ehealth provides a set of integration modules that enable you to use ehealth to report on the data that various NMSs collect. When you add licenses for these integration modules, you can access a script (installed with ehealth) to install them. They can then input bulk performance and configuration data into ehealth, providing critical data quickly and eliminating the need for duplicate polling. For more information, refer to the appropriate user guide for the integration module. 1 Maintaining Your Data Collection Resource discovery is a critical step in ehealth administration, so it is important to understand the various ways that your element configuration can change and the steps that you can take to maintain it effectively and ensure data continuity. After every discover, it is good practice to do the following: Review your discover logs carefully and review changes that have occurred. Retire or delete elements that you no longer want to monitor. Resolve resource changes that discover was unable to resolve. For future discoveries, it is important to use a filtering method to find only the elements that you want to monitor. Rediscovering often, as changes occur, can ensure that data collection remains continuous and can significantly reduce the number of resource changes that discover is unable to resolve. Where to Go for More Information You can run the discover process interactively or schedule it to run at regular times to maintain your element information and the poller configuration. The ehealth Resource Discovery Guide includes a detailed discussion of the following: Understanding how ehealth identifies infrastructure changes Performing a discover for the first time Interpreting your discover results and resolving the problems identified Determining when you should rediscover to maintain your poller configuration Improving the discovery of your infrastructure changes Filtering your resource search effectively Running a scheduled discover job Troubleshooting common problems

12 12 Chapter 1 ehealth Administration Roadmap Managing Discovered Elements and the ehealth Poller ehealth collects performance and availability data from your discovered elements by polling them. Polling is the process of collecting statistics on network, system, and applications data directly from elements. The ehealth poller automatically collects data for any element in the ehealth poller configuration. The poller configuration defines the information for each element such as the name, a polling rate (the frequency with which ehealth polls the element), and the agent type (the type of element that ehealth discovered). Maintaining Your Poller Configuration While discover can keep your poller configuration up-to-date, it works most effectively when you maintain your configuration by correcting problems with resources that you are monitoring, adding new resources, and deleting those that have been removed from the infrastructure. ehealth provides you with the tools that you need to proactively manage your poller configuration to ensure that ehealth successfully collects data regularly on your resources. Organizing Your Elements by Grouping By grouping related elements, you can simplify reporting for your users and ensure that the data is organized effectively. Because you could discover thousands of elements, ehealth provides a grouping capability. You can organize elements based on geographic location or function by creating groups, organize those groups into group lists, and then run reports on them. For example, if you wanted to monitor all systems supporting your business within Europe, you could create a group for each country and include systems that support offices in that country. You could then add the groups to a group list called Europe and generate data on the group list. Where to Go for More Information For complete instructions on managing your elements and the polling process, refer to the ehealth Element and Poller Management Guide. This guide includes a detailed discussion of the following: Managing the data collection process and resource changes Resolving polling problems Modifying element information, and adding new elements to your configuration Organizing your elements into groups and group lists for easier reporting

13 Managing Reports 13 Managing Reports As ehealth identifies and collects data from existing devices, agents, and management systems in your infrastructure, you can generate reports on this data to manage your resources. With appropriate permissions, you can generate ehealth reports on elements, groups, and group lists. An ehealth report presents data in a particular format, which typically includes one or more charts. A chart is a graphical or tabular representation of data within the report. Different charts are available for each type of technology. As an ehealth administrator, you can generate reports from the ehealth console and output them to the screen, the Web, or a printer, or save them as files. You can also reports to ehealth users. To enable ehealth users to generate and view reports from the Web interface, you can set the appropriate permissions on their Web user accounts. Most Web reports have drilldown capabilities, which allow Web users to view additional reports and obtain more information about the elements. To meet the specific needs of a user or organization, you can customize reports in various ways, as well as control access to particular report types and drilldown report features. You can run reports on demand (ad hoc), or schedule them to run on a regular basis. 1 Understanding ehealth Data Analysis When you run a Health or Service Level report on demand, ehealth analyzes the data while the report runs, which can be a time-consuming process. When you schedule Health and Service Level reports to run on a regular basis using the job scheduler, ehealth preprocesses the data to reduce the amount of time required to generate the report. Each night, before running these scheduled reports, ehealth runs a special data analysis job to analyze the previous day s as-polled data. It uses this data to calculate averages, analyze trends based on trend thresholds, and calculate a health index for each element. A trend threshold is an upper limit on performance factors such as utilization and errors. When an element reaches that limit, a performance problem has developed. The health index is a measurement of the performance of each element based on various criteria. It appears in certain reports to indicate the health of resources. A high health index indicates problems, while a low one indicates a healthy element.

14 14 Chapter 1 ehealth Administration Roadmap Using Service Profiles ehealth uses the health index and trend thresholds to evaluate the current status of your resources. As an ehealth administrator, you can control the thresholds that ehealth uses for analysis by using a service profile to define trend thresholds and the performance ranges used for health indexes. Many ehealth reports compare current performance to a baseline, which is the typical or historical behavior for that element, group, or group list based on the past several weeks of performance data. The baseline period projects back from the day on which the report is run. ehealth reports compare hourly information to the same hour of the day, and daily information to the same day of the week in the baseline period. Where to Go for More Information For a detailed discussion of ehealth data analysis and complete instructions on managing reports, refer to the ehealth Report Management Guide. This guide covers the following: Understanding the value of each report type Running ehealth reports and setting the report output Setting permissions for users to run and view reports Viewing reports from the Report List and Organization pages of the Web interface Deleting reports Collecting historical data on your resources and managing service profiles Customizing reports Managing Scheduled System Jobs To facilitate the administration of your ehealth system, ehealth runs many processes on a regular basis. These automated processes are referred to as scheduled jobs. As an administrator, you can modify the job schedule to suit the particular needs of your ehealth site. ehealth runs several scheduled jobs to manage your database size by deleting old reports, cleaning up temporary files, and summarizing data. You can also schedule jobs to automate your resource discovery and report generation processes, as well as create new job types to run commands automatically.

15 Managing ehealth System Processes 15 Where to Go for More Information For instructions on using the ehealth job scheduler, refer to the ehealth Scheduled Job Management Guide. This guide includes a detailed discussion of the following: The purpose of the ehealth job scheduler Types of default ehealth jobs Viewing jobs and job history Managing multiple jobs Scheduling new jobs Creating new job types to automate tasks 1 Managing ehealth System Processes A critical task of ehealth administration is monitoring the ehealth system and its critical processes to ensure that everything is functioning properly. To monitor ehealth processes, you can use the ehealth History and System Information features of the OneClick for ehealth (OneClickEH) console to quickly view all historical activity that has occurred on your system. To determine whether critical processes are running or certain events have occurred on the ehealth system, you can place a management agent on the ehealth system. Where to Go for More Information For instructions on managing your system processes, refer to the ehealth System Management Guide. This guide includes a detailed discussion of the following: Using a management agent to monitor ehealth logs and processes Using OneClickEH to obtain the history and status of ehealth logs, files, and processes Managing the Database ehealth includes a fully-integrated database that does not require a dedicated database administrator to operate it. As an ehealth administrator, you may be responsible for managing the ehealth database to ensure that critical resource information is saved and is always available for reporting and management. You need to ensure that the database software is running smoothly, and that the data is backed up regularly. In addition, you need to manage the growth of the database so that it does not run out of disk space.

16 16 Chapter 1 ehealth Administration Roadmap Data Storage As the poller collects data from your elements, ehealth stores the detailed performance data as-polled data in its database. Since ehealth collects data every five minutes for each element, the as-polled data can quickly grow. To keep the database size manageable, ehealth aggregates the raw five-minute samples into hourly average samples and daily average samples. ehealth performs the aggregation process, referred to as database rollup, on a regular schedule. Typically, the ehealth system keeps three days of as-polled data samples, six weeks of hourly average samples, and 70 weeks of daily average samples. To meet the reporting needs of your organization, you can customize the rollup schedule and the length of time that ehealth keeps data. Where to Go for More Information For a description of the tools that you can use to automate database management, refer to the ehealth Database Management Guide. This guide describes the following: The contents of the database Factors that can have the greatest impact on the rate of growth Methods for managing database growth and changes Procedures for backing up your ehealth system Strategies for troubleshooting database problems Types of ehealth Systems To manage the resources within your infrastructure, you can install the ehealth software on a standalone system. If your network is large, you may need to install it on multiple systems. In addition to standalone systems, several other types of ehealth systems are available: Distributed Remote Poller Traffic Accountant

17 Types of ehealth Systems 17 Standalone ehealth A standalone ehealth system is a single workstation on which you have installed the ehealth software. Standalone ehealth systems typically support up to 50,000 elements. Depending on the size of your infrastructure, you may only need to install a single ehealth system to manage your resources. If your organization is extensive, but you do not need to report on all elements together in one report, you can install multiple standalone ehealth systems throughout your organization, each administered by a different person. Standalone systems are not connected in any way, and each one must collect and process the data for the resources that it monitors. 1 Distributed ehealth If you have a large infrastructure, you could deploy multiple Distributed ehealth Systems across large geographic ranges or locate them centrally to gather data and manage various segments of your network. This configuration is referred to as a cluster. The cluster contains several ehealth systems that manage specific sets of resources, and share the information with each other. By using Distributed ehealth, you can distribute the workload of collecting and processing data across multiple ehealth systems that work in parallel. Report users can access reports for any element or groups in the cluster from Distributed ehealth Consoles, which are reporting front-ends to the cluster. Clusters can support up to one million elements. For complete instructions on administering a cluster, refer to the Distributed ehealth Administration Guide. Remote Polling If you are administering a large-scale or wide-area environment, one ehealth system may not be enough to monitor all of your resources. As an alternative to a Distributed system, you can use a remote polling environment. With remote polling, you install ehealth on remote systems (called remote sites) and configure each site to poll a set of elements. The database at each remote ehealth site contains the data for the elements that it is polling, and you can use ehealth at each site to manage those elements. A central ehealth system retrieves element information and performance data periodically from the remote ehealth systems and merges the data into one central ehealth database. From this central database, you can run reports for all elements. The central site can support up to 50,000 elements, depending on the system configuration and the reports that you run. For complete instructions on administering a remote poller system, refer to the Using the ehealth Remote Poller guide.

18 18 Chapter 1 ehealth Administration Roadmap Traffic Accountant Traffic Accountant is a specialized network and application monitoring capability. Rather than collect data on statistics from network resources like routers/switches, interfaces, and systems, it collects traffic flow information from RMON2 probes and traffic sources such as Cisco NetFlow. It provides network traffic analysis and reporting that enables you to track the individual users, applications, and departments who are consuming most of your network resources. Because the volume of Traffic Accountant data can become quite large and consumes a large amount of data storage capacity, you must install the application on a separate system that is dedicated to ehealth Traffic Accountant. CA does not support the installation of ehealth statistics monitoring and Traffic Accountant on a single system. For instructions on administering a Traffic Accountant system, refer to the ehealth Traffic Accountant Administration Guide.

19 2 ehealth User Interfaces The ehealth software offers four user interfaces (UIs), all of which are available to ehealth administrators: ehealth console ehealth command line interface (CLI) ehealth Web user interface OneClick for ehealth (OneClickEH) Not all functions are available through every ehealth interface, and some are available in more than one. ehealth documentation provides guidelines for selecting the most efficient and practical method to perform a particular task. Choose the method with which you are most comfortable as an administrator. For example, of those functions that are available through the CLI and a graphical UI, you may feel more comfortable using the CLI, while another administrator would prefer to use a graphical UI. This chapter describes the roles and privileges of the ehealth administrator, and outlines the functionality available with each interface. Administrator Roles For most ehealth sites, the ehealth administrator who manages the ehealth console is also the administrator of the ehealth Web interface and OneClickEH. However, in larger sites, these responsibilities might be shared by different people. Administering the ehealth Console and CLI To administer the ehealth console and the CLI, you must be able to log in to the ehealth system using an operating system account that has ehealth administration privileges. 19

20 20 Chapter 2 ehealth User Interfaces Administering OneClickEH and the Web User Interface To administer the OneClickEH console and the Web user interface, you must log in to the ehealth system using a special ehealth Web user account named admin. This account allows you to configure these interfaces, control user access to them, and assign limited administrative privileges to other Web users. By default, the ehealth web user account does not have permission to log in to OneClickEH. As a best practice, multiple administrators should use the OneClickEH Statistics Polling Management interface to resolve polling problems. You can also use multiple ehealth consoles to perform administrative tasks; however, secondary consoles consume system resources and can impact system performance. The primary ehealth console and any of the secondary consoles can run at local or remote workstations. Through the primary console, administrators can perform all administrative- and user-level ehealth tasks. Administrators can use secondary consoles to perform a subset of the tasks that can be performed from the primary console. For guidelines and best practices for operating multiple ehealth consoles, refer to the Using Secondary ehealth Consoles focus topic. ehealth Console The ehealth console is a graphical UI that provides menus and icons for performing key administration tasks such as managing resources, scheduled jobs, and the database. Figure 1. ehealth Console When your ehealth console opens, it displays as many as three additional windows that provide you with ehealth polling status. However, to obtain detailed information about polling activity, you should use the OneClickEH console. The OneClickEH Status Summary window shows the time of the next scheduled poll, the number of good and bad polls that have occurred, the duration of each poll, and the average normal and fast poll rates over the last 24 hours.

21 Command Line Interface 21 Administrative Options The following table describes the administrative options that you can access through the ehealth console menus: Menu Name Administration Tasks 1 2 Console View the polling status windows. Start and stop the ehealth server, and quit the console. Setup Perform an interactive discovery, and discover NetFlow probe elements. Manage and configure poll rates and the poller configuration. Schedule automatic system jobs. Change global console settings. Manage ehealth licenses. Reports Run and customize reports. Create and edit Traffic Accountant views. Database View the status of your ehealth database. Change the number of weeks of analyzed data that you keep in the database. Load a new database, and save (back up) your database. Save system messages to a log file. Command Line Interface ehealth contains a directory of commands that you can run from a console or terminal window. While some of the command functions are also available through one of the administrative interfaces, many advanced functions are only available through the CLI. For example, while you can use the job scheduler UI to modify the time at which a schedule job runs, you must use the nhschedule command to create new job types. You can also use the CLI to automate tasks by using scripts. Most ehealth commands are quite powerful; therefore, you should use them with caution or under the direction of Support. Before running a command for the first time, review the Web Help to learn about the purpose of the command and its potential impact to your system.

22 22 Chapter 2 ehealth User Interfaces Web User Interface ehealth installs a Web server to enable users to view ehealth reports and other features from a remote system using a Web browser. Figure 2. Web Interface Tabs Administrative Options From the various tabs of the Web interface, you can perform administrative functions, manage ehealth reporting, and access numerous ehealth products. The following table describes the tasks that users can perform using the Web interface and the functions that you can perform as an administrator: Interface Tab User Tasks Administrator Functions Gateway Link to product Web site and Help. Design a gateway page as a portal to your site. Report Center Create custom reports and queries on ehealth resources (available only if Report Center is installed). Control access to the Report Center, Query Studio, and Report Studio applications. Organization View groups and elements. Control user access to elements and groups. Report List View Web-based reports. Control user access to generated reports. Run Reports Run standard ehealth reports. Allow users to run reports, as well as permit some basic customization of those reports. MyHealth Create custom reports using panel types. Design MyHealth report pages, or allow users to do so. Live Health Monitor elements in real time. Control user access to the Live Health applications and the BSC. Systems & Apps Deploy and manage agents to collect data. Control user access to these product areas and assign user privileges to access particular features.

23 OneClick for ehealth 23 Interface Tab User Tasks Administrator Functions Admin Change to a different Web account and change passwords. Access OneClickEH to manage user accounts, customize the ehealth Web site, and create Service Note rules. 1 2 OneClick for ehealth OneClick for ehealth (OneClickEH) is an additional administrative interface to the ehealth system. From this interface, you can monitor and manage your ehealth systems, view your element hierarchy, and perform many administrative functions. You can launch this application from any Web browser and work simultaneously with other administrators to manage all of your ehealth systems. NOTE OneClickEH supports ehealth Releases 5.6.5, 5.7, and later, running on Sun, HP-UX, and Windows operating systems. The OneClickEH interface runs on Windows 2000, 2003 and XP operating systems; it is not supported on Windows NT and UNIX operating systems. To access the complete range of features available with OneClickEH, you must upgrade to ehealth Release 6.0. A single OneClickEH interface can manage multiple ehealth systems, even if they are mixed versions. As shown in Figure 3, OneClick EH displays a tree structure on the left with access to the administrative functions. On the right, it displays a high-level status summary. From this window, you can access more information by drilling down to various functions.

24 24 Chapter 2 ehealth User Interfaces Figure 3. OneClick for ehealth Administrative Options You can perform the following administrative functions using OneClickEH: Manage statistics polling by identifying and resolving polling errors, and managing ehealth licenses. Review ehealth history by accessing historical logs to track changes and problems. Access the job scheduler to monitor scheduled system jobs and the job history. Administer Web user accounts to enable users to view and run reports, and manage groups. Manage the ehealth system by monitoring server processes and files, and troubleshooting configuration problems. Manage your ehealth resources by organizing them into groups and group lists.

25 3 Maintaining Your ehealth System This chapter describes some important steps that you should take to proactively maintain your ehealth system: Use advanced logging to troubleshoot problems. Upgrade to new releases. Install patches. Using Advanced Logging to Troubleshoot Problems Through the OneClickEH console or the ehealth Web interface, you can access two types of advanced logging tools to troubleshoot problems that you might encounter with ehealth. Some of these options can interfere with your system performance, and most of the log files consume a significant amount of disk space. Therefore, do not enable advanced logging unless you are troubleshooting a specific problem under the direction of Support or your Sales Engineer. To use advanced logging through the OneClickEH console, select Setup Advanced Logging, and select the tasks for which you want to access ehealth log files. Click Apply and View Advanced Logs. OneClickEH automatically opens the Server Files folder and displays the log files pertaining to the tasks. Press the F5 key to refresh the directory listing. To access this feature, the User can manage ehealth configuration option must be enabled on your Web user account under the OneClickEH tab. To use advanced logging through the Web interface, you must log in as the administrator, select the Admin tab, and select Site Management Advanced Logging. Specify the Web user for whom you want to generate logs, the Web pages, and the time range. ehealth stores the log files in the /ehealth/log/advanced directory. 25

26 26 Chapter 3 Maintaining Your ehealth System Upgrading to New Releases When a new release of ehealth is available, you should upgrade to obtain the latest features and software fixes. For example, to access all of the latest features available with OneClickEH, you need to upgrade to Release 6.0. The InstallPlus program allows you to reduce downtime by installing the very latest fixes, certifications, and support as part of your upgrade. The InstallPlus program is the standard ehealth installation program it is updated for every patch and certification release. It ensures that you install the very latest available software when you install or upgrade to an ehealth release. Use the InstallPlus program only when you install an ehealth release for the first time, or when you first upgrade from a previous ehealth release. For instructions on using InstallPlus, refer to the ehealth installation and upgrade guides for your platform. All ehealth user documentation is available on the product Web site. Installing Service Packs InstallPlus does not replace the standard service pack (patch) installation program. After you have installed an ehealth release, continue to use the service pack installation program to install fixes and patches for your release.

27 Index A administration concepts baseline 14 baseline period 14 cluster 17 data analysis 13 data storage 16 discovery 10 elements 9 Health Index 13 report generation 13 types of ehealth systems 16 administrator roles 19 tasks database management 15 report management 13 resource discovery 9 resource management 12 scheduled job management 14 system process management 15 advanced logging for troubleshooting 25 D data analysis 13 data storage 16 discovery 10 E ehealth database 16 elements 9 maintenance installing service packs 26 upgrading 26 polling 12 systems distributed 17 remote polling 17 standalone 17 Traffic Accountant 18 ehealth interfaces command line interface (CLI) description 21 ehealth console administrative options 21 description 20 27

28 28 Index OneClick for ehealth administrative options 24 description 23 Web interface administrative options 22 description 22 elements 9 L logging troubleshooting information 25 R remote polling 17 report generation 13 S service packs, installing 26 T Traffic Accountant 18