CA ehealth. Setting Up Live Monitoring of Your Service Availability Tests. r6.1

Transcription

1 CA ehealth Setting Up Live Monitoring of Your Service Availability Tests r6.1

2 This documentation and any related computer software help programs (hereinafter referred to as the Documentation ) is for the end user s informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation 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 related 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 product are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the related software is limited to the period during which the applicable 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 Documentation 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 DOCUMENTATION 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 DOCUMENTATION, 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 any product referenced in the Documentation is governed by the end user s applicable license agreement. The manufacturer of this Documentation is CA. 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 (b)(3), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2008 CA. All rights reserved.

3 CA Product References CA Product References This document references the following CA product: CA ehealth (ehealth) CA AdvantEDGE View (AdvantEDGE View) CA ehealth SystemEDGE (SystemEDGE) CA ehealth Live Health Application (Live Health) Contact Technical Support For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at 3

4

5 Contents Chapter 1: Detecting Application Problems Types of Application problems The ehealth Solution Setup Overview Chapter 2: Enabling Live Monitoring of Your SA Test Configuration Setup Prerequisites How to Enable Live Monitoring Create Groups and Group Lists of Service Availability Components Configure Log File Monitoring by SystemEDGE Agents Create Web Accounts for Monitoring Service Availability Install Live Health Apply Live Health Profiles Create the Live Status Diagram Contents 5

6

7 Chapter 1: Detecting Application Problems Using both Live Health and Service Availability (SA) to monitor your critical business applications can help you to detect and diagnose application issues that affect your users. With SA, you configure tests to monitor the applications that are critical to your business. Live Health monitors the tests and notifies you of application problems and possible causes. This chapter contains the following topics: Types of Application problems The ehealth Solution Setup Overview Types of Application problems Application problems typically fall into two categories: Response time degradations Application tasks are taking more time to complete. This impacts productivity because less transactions complete in the same amount of time. When the delay becomes noticeable to users, it results in complaints and customer dissatisfaction. Availability The application is not responding and users are blocked from their ability to do their work. Application outages can severely impact the business in loss of revenue, loss of productivity, and loss of credibility with users. Availability problems occur when an application is stopped or its supporting system hardware is offline. Problems also occur when applications change in such a way that tasks or transactions no longer work. For example, Web page URLs could change as a result of a site redesign or a software update. Login accounts can expire or be accidentally deleted. System names or IP addresses could change as a result of network reconfiguration or system upgrades. Detecting Application Problems 7

8 The ehealth Solution These changes might seem transparent to users, but they impact usability. For instance, users or applications that rely upon static URLs break (become unavailable) if the URL changes. Users who must access specific systems for their work are blocked when the system name is no longer found. In addition, network conditions and resource limitations could cause problems that force transactions to time out and fail. Live Health and Service Availability (SA) can detect and report these problem cases so that you can solve the real cause of the trouble. The ehealth Solution ehealth provides more Service Availability test capabilities and strong integration with Live Health. When the problem is availability, ehealth can provide more information to help you determine the problem that caused the application to be unavailable. Whether you are using the Business Service Console, Live Status, or Live Exceptions, Service Availability test monitoring is the key to accelerated identification and resolution of application problems. Setup Overview Setting up and using Live Health to monitor your Service Availability test environment consists of the following: Creating groups and a group list for your SA test system Applying profiles to that group list Using that group list to create a Live Status view of your SA test systems Using tools such as Live Status and the Business Service Console to see application problems and determine whether they are response time degradation or availability problems Using SA alarms to identify the possible cause of the problem so that IT staff can quickly take action 8 Setting Up Live Monitoring of Your Service Availability Tests

9 Chapter 2: Enabling Live Monitoring of Your SA Test Configuration This chapter contains the following topics: Setup Prerequisites How to Enable Live Monitoring Setup Prerequisites Before you begin the setup process, you must do the following: Install ehealth 5.7 or later. Deploy SA agents. Set up your SA tests. Note: For more information about setting up SA tests, see Setting Up Service Availability 2.0. How to Enable Live Monitoring To enable live monitoring of your SA test configuration, you must complete the following tasks: 1. Create groups and a group list of Service Availability elements in ehealth. 2. Configure SystemEDGE agents for SA log file monitoring on all SA test systems. 3. Create ehealth Web accounts for SA test administrators or other staff responsible for monitoring SA, if needed. 4. Install Live Health on client systems as needed. 5. Apply Live Health profiles to the SA group list and SA system group. 6. Create a Live Status diagram. Enabling Live Monitoring of Your SA Test Configuration 9

10 How to Enable Live Monitoring Create Groups and Group Lists of Service Availability Components Organize the components of your SA test configuration into groups and group lists. CA recommends that you create the following groups and group list: A response group named All_SA containing the Service Availability response source (-RS) elements A system group named All_SA containing all the SA test system (-SH) elements This two-branch structure lets you monitor your SA test configuration as it increases in size. After you create additional test agents and tests, ehealth automatically adds them to these groups and group lists when you specify the group list name, All_SA, in the Save to field under Groups during element discovery. Note: For more information about creating groups and group lists, see the ehealth Administration Guide. Configure Log File Monitoring by SystemEDGE Agents New AdvantEDGE View templates enable the SystemEDGE agent to monitor the SA agent log file (jcollector.log) and the operational health of the SA test system. You must configure the SystemEDGE agent installed on each SA test system. The template that you apply must match the operating system of the SA test system. For example, if you have three SA test systems with Windows XP, Windows 2003, and HP-UX 11.0 operating systems, respectively, you can do either of the following: Apply the templates individually: 1. Apply the Service Availability Windows XP /2003 template to the Windows XP system. 2. Apply the Service Availability Windows XP /2003 template to the Windows 2003 system. 3. Apply the Service Availability HP template to the HP-UX 11.0 system. Apply one of the templates to a group: 1. Create a group of the two Windows systems. 2. Apply the Service Availability Windows XP /2003 template to the group. 3. Apply the Service Availability HP template to the HP-UX 11.0 system To configure SystemEDGE log file monitoring 1. (Optional) Create a group of SA test systems that have the same operating system so that you can apply the appropriate template. 2. Locate the AdvantEDGE View page of the ehealth Web interface and select an SA test system from the System list or a group of SA test systems from the Group list. 10 Setting Up Live Monitoring of Your Service Availability Tests

11 How to Enable Live Monitoring 3. Select Template Configuration from the Configuration list. 4. Click the Configuration icon. AdvantEDGE View displays the templates available for installation. 5. Select one of the following, depending on the operating system of the SA test system (selected in Step 2): Service Availability - Linux Service Availability - HP-UX Service Availability - Windows NT 4.0/2000 Service Availability - Windows XP /2003 Service Availability - Solaris 6. Click Apply Selected Templates. Note: If you installed the SystemEDGE agent in a non-default location, you must modify the templates to include the correct path. The default templates are stored on the ehealth system in the following directory: ehealth/web/aview/var/templates/sys ehealth Specifies the full path to the location in which you installed ehealth. 7. Configure the SA test system to send traps to the ehealth system. (If you already did this during SA agent installation, go to Create Web Accounts for Monitoring Service Availability on page 12.) Stop the SystemEDGE agent by doing one of the following: On Windows systems, open the Control Panel dialog and double-click ehealth SystemEDGE. The SystemEDGE Control Panel appears. Click Stop Agent. On UNIX systems, log in as root and enter the path to the SystemEDGE startup script followed by stop. For Solaris systems, execute the following command: /etc/rc2.d/s99sysedge stop 8. Edit the SystemEDGE configuration file, sysedge.cf, by adding a line similar to the following: trap_community private ipaddress private Defines a read-write community string. ipaddress Defines the IP address of the ehealth system. 9. Save your changes. 10. Restart SystemEDGE to apply the changes by doing one of the following: On Windows systems, open the Control Panel dialog and double-click ehealth SystemEDGE. The SystemEDGE Control Panel appears. Click Start Agent. Enabling Live Monitoring of Your SA Test Configuration 11

12 How to Enable Live Monitoring On Solaris systems, log in as root and execute the following command: /opt/empsysedge/bin/sysedge -b -p port port Defines the port number that the SystemEDGE agent is using. Create Web Accounts for Monitoring Service Availability Depending on your environment, the responsibility for monitoring SA test systems, administering Live Health, and administering ehealth can be divided among various individuals. If you plan to make Live Status and Live Exceptions part of their toolset, you may need to create new user accounts. Note the following guidelines: If visibility of specific groups and group lists must be restricted to specific users, the ehealth Web administrator should create or modify Web accounts and grant this access. Note: For more information, see the ehealth Help. All SA tests must have LE Monitor selected in the Advanced Options area of the Modify Test page in Service Availability. Each element monitored by Live Health must have a Live Health license. Note: For more information about creating Web accounts, see the ehealth Administration Guide. Install Live Health Install the Live Health client software on systems from which you plan to view the alarms resulting from Live Health monitoring of SA tests and test systems. To download the Live Health client 1. Open a Web browser and log in to the ehealth Web server. 2. Select the Live Health tab. 3. Read the instructions on the Live Health page and click the link to download the software. 4. Specify the destination directory for the installation program and download the file. Note: For platform-specific installation instructions, see the ehealth Help. 12 Setting Up Live Monitoring of Your Service Availability Tests

13 How to Enable Live Monitoring Apply Live Health Profiles After you have created the recommended groups, you must apply the new Live Health profiles for Service Availability to the All_SA group list so that Live Health monitors the SA tests. You must also associate the default profiles for systems to the All_SA system group so that Live Health monitors the test systems for unusual workload, insufficient disk space, and other operational problems. To create associations between Live Health profiles and the All_SA group list and All_SA system group 1. Log in to the Live Exceptions Browser and connect to the ehealth system on which the SA test agents have been discovered. 2. Select Setup, Subjects to Monitor. The Setup Subjects dialog appears. 3. Click New in the Setup Subjects dialog. The Setup Subjects Editor dialog box appears. 4. Select Group Lists under Subject Type. 5. Select All_SA under Subjects. 6. Select the following profiles under Profiles: Response Failure Service Availability Failure Service Availability Polling To select more than one profile, hold down the Control key as you select. 7. Click Apply. 8. Select Groups under Subject Type. 9. Select All_SA under Subjects. 10. Press and hold the Control key as you select the following profiles under Profiles: System Delay System Failure System Generic System Licensing System Security System Unusual Workload 11. Click Apply. 12. Click OK. The Setup Subjects dialog that appears should be similar to the following graphic: Enabling Live Monitoring of Your SA Test Configuration 13

14 How to Enable Live Monitoring Create the Live Status Diagram Now that Live Exceptions profiles are monitoring your SA tests and test systems, create a Live Status diagram that provides a real-time, panoramic view of the status of your SA test configuration. To create the Live Status diagram for your SA test configuration: 1. Log in to Live Status and connect to the ehealth system that is managing the SA test systems. 2. Select File, New Diagram. The New Diagram dialog appears. 3. Specify SA Test Configuration or another name for your Live Status diagram in the Title field. 4. Select the All_SA group list from the Group List list. 5. Click OK. The Live Status diagram, shown in the following graphic, is composed of two branches. The All_SA (System) branch has icons representing the status of your SA test systems. The All_SA (Response) branch has icons representing the status of your SA test agents. The response branch icons initially appear as Unused (gray). Once response paths are associated with them, the icons appear as Normal (dark green). 14 Setting Up Live Monitoring of Your Service Availability Tests

15 How to Enable Live Monitoring To view each application as a branch 1. Select File, Edit Diagram. 2. Select Response Display Options. 3. Locate the Applications to include area and select the applications that you are monitoring with Service Availability. 4. Make sure that Display Response by Application is selected. 5. Click OK to close the Response Display Options dialog box. 6. Click OK to close the Edit Diagram dialog box. Enabling Live Monitoring of Your SA Test Configuration 15

16 How to Enable Live Monitoring Example: Corporate Web site Users Getting File Not Found Errors SA test administrators have configured HTTP tests that request information from the corporate Web site that is vital to investor and customer relations. The tests have run without problems for three weeks. Suddenly, the Live Status diagram shows major alarms on several HTTP tests. Because Live Health is set up to monitor the SA test systems, the workflow shown in the following graphic is possible. After two clicks, a Live Status user has the information necessary for resolving the problem. No ambiguity existed to cause the user to run down the wrong path investigating possible causes such as network or Web server problems. 16 Setting Up Live Monitoring of Your Service Availability Tests