CA ehealth. Setting Up Service Availability 2.0. r6.1

Transcription

1 CA ehealth Setting Up Service Availability 2.0 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: Installing Service Availability Service Availability Overview How to Set Up Service Availability Tests SA Setup Prerequisites Test and Agent Setup Prerequisites Types of Tests to Run Agent Sets Test Sets Test Profiles Platform Dependencies How to Set Up Service Availability Install Service Availability Chapter 2: Upgrading Service Availability Guidelines for Upgrading Service Availability Service Availability Upgrade Process Migrate Existing SA Paths Upgrade Service Availability Chapter 3: Managing SA Agents and Tests Discover SA Agents SA Workflow Overview View Agents Create Tests Create Test Sets Create Agent Sets Create Test Profiles Guidelines for Using Commit to Propagate Tests to Agents Types of Commits Commit Changes View Commit Log Files Monitor Agents and Test Profiles Modify the Test Monitor page Guidelines for Changing Configuration Settings Edit the SA Configuration File Run Historical Reports for Your Paths Supported Platforms for SA Contents 5

6

7 Chapter 1: Installing Service Availability This document explains how to install or upgrade Service Availability by using the ehealth Web interface. It also describes the SA workflow for creating tests or sets of tests, associating them with one or more agents in a test profile, and distributing those tests to SA agents. This chapter contains the following topics: Service Availability Overview How to Set Up Service Availability Tests SA Setup Prerequisites Test and Agent Setup Prerequisites How to Set Up Service Availability Install Service Availability Service Availability Overview ehealth and Service Availability (SA) 2.0 help you create, manage, and monitor a variety of tests for measuring the performance of key business applications. These tests let you evaluate the availability and response times of those business services and help ensure their reliability. The following diagram illustrates the SA workflow. Installing Service Availability 7

8 How to Set Up Service Availability Tests ehealth System View ehealth reports SNMP Commit Tests to Agents SA test system runs on a SystemEDGE agent to test business services continuously. Database Servers SQL Query Test Set SA Web interface Create tests & test profiles. Deploy and manage tests. Monitor tests & evaluate test performance. Virtual User Test Set HTTP Test Set Use the ehealth Web interface to view the available SystemEDGE agents where Service Availability tests will run. How to Set Up Service Availability Tests Complete the following tasks to set up SA tests: 1. Plan and organize how and where to set up your tests and test systems. 2. Create tests to measure the performance of your business services, including Web services, network services, database services, , file transfer services, custom tests, and robotic scripts for testing user services. 3. Group logically related tests into test sets and logically related SystemEDGE test systems into agent sets. 4. Create test profiles and populate them with associated sets of agents and tests for easy management of related testing and monitoring. 5. Deploy the test profiles to one or more test systems with the SA Commit operation. This step creates paths between each test source and destination. 6. Use SA to monitor the SA tests that are running and evaluate their performance. Go to the SA Monitor page to see the status and performance of any SA test. 7. View At-a-Glance reports for the paths that ehealth creates to get current and historical data for those paths. 8 Setting Up Service Availability 2.0

9 SA Setup Prerequisites SA Setup Prerequisites You must do the following before installing SA: Install ehealth Release 5.7 or later. Note: For more information, see the ehealth Installation Guide. Install SystemEDGE Release 4.2 or later second. Note: For more information, see the ehealth SystemEDGE User Guide. Install the SystemEDGE JRE Software Package for Version 2 next. The JRE package is available from the SystemEDGE section of the ehealth Support Website: Make sure that a minimum of 20 MB of disk space is available for SA 2.0. Migrate your existing SA test paths before installing SA 2.0 if you are upgrading from a previous version of SA. Make sure that the SNMP community string for SystemEDGE is set to read-write. SA writes tests to agents and requires write permission to do so. Test and Agent Setup Prerequisites Before installing Service Availability, determine the number of test systems and agents that you intend to set up and where to install them. The recommended practice is to set up SA test systems in each of the key locations and business groups throughout your enterprise. This approach lets you simulate and monitor user activity for each of your critical business applications. As part of your planning, consider the number, capacity and location of your SA est systems from the standpoint of being able to produce consistent test results. Types of Tests to Run If you have Web servers in your environment, you can use HTTP, HTTPS, and ping tests to test your Web servers. If you have DNS and DHCP servers, create DNS and DHCP tests. If you have special applications that you want to test, create Custom or Virtual User tests. Over 20 tests are available, as shown in the following table. Active Directory DHCP File I/O HTTP Custom DNS FTTP HTTPS Installing Service Availability 9

10 Test and Agent Setup Prerequisites IMAP MAPI NTTP POP3 SMTP SQL Query TFTP LDAP NIS Ping Round Trip SNMP TCP Connect Virtual User Agent Sets SA 2.0 lets you group agents into agent sets so that you can manage them more easily and logically. An agent set is a collection of one or more SA agents that you can manage together. For example, you can create an agent set that includes all SA agents in a particular location or business organization like sales or manufacturing. Test Sets You can group tests into test sets. For example, you may want to create a test set that includes all your ping tests or a test set that includes all the tests you want to run from a specific SA test system for example, a ping test, DNS test, TCP Connect test, and HTTP test. Grouping test resources logically (for specific business groups, key locations, or business applications) lets you monitor the performance and health of those related resources. You create groups of tests and agents based on the type of information reporting you want. For example, you can create a set of tests to monitor the performance and availability of important Web resources or critical business applications for your entire enterprise or just one location. You can then view ehealth reports (directly from SA) to see if those important business resources have been performing as expected. Test Profiles A test profile is a logical association of tests or test sets with agents or agent sets. This dimension of SA makes managing and deploying tests to agents very easy. It lets you distribute a common set of SA tests to multiple SA agents and manage all of them together. 10 Setting Up Service Availability 2.0

11 How to Set Up Service Availability Platform Dependencies When planning your SA tests, be sure to consider system platform dependencies that might influence the success of deploying groups of tests to multiple agents. For example, tests that require pathnames are not interchangeable between UNIX and Windows because the pathname conventions are different (for example, backslashes in UNIX pathnames versus forward slashes in Windows). Note: On AIX systems, you cannot install Service Availability on the same system where with the Oracle AIM is installed. How to Set Up Service Availability The process for setting up SA is summarized as follows: 1. Make sure that ehealth Release 5.7 or later is installed and running on the system from which you intend to manage your agents and tests. ehealth must be installed and running before you install Service Availability. 2. Install SystemEDGE Release 4.2 or later on all systems from which you want to run SA tests. SystemEDGE must be installed before you install Service Availability. Standardizing the location in which you install SystemEDGE agents makes deployment and ongoing management simpler. To configure SystemEDGE log file monitoring of SA test systems, CA recommends that you install the SystemEDGE agent in the default location. Otherwise, modify the AdvantEDGE View templates to include the correct path to the log files. Note: For more information about log file monitoring, see the SystemEDGE User Guide. 3. Install the SystemEDGE JRE Software Package for Version 2 on all systems from which you want to run SA tests. SystemEDGE JRE must be installed before you install Service Availability. The JRE package is available from the SystemEDGE Downloads page of the ehealth Support Website: 4. Install SA 2.0 on all SystemEDGE agents from which you want to run SA tests. 5. Use ehealth to run the discover process for System and Response Elements modes to discover the SystemEDGE agents that you have installed. Create your tests, test sets, agents sets, and test profiles as necessary. Note: You must use a read-write SNMP community string for Commit to succeed. Without it, your SA tests will not run. 6. Use Commit to update the agents. 7. View historical ehealth reports for your paths. More information: Commit Changes on page 30 Installing Service Availability 11

12 Install Service Availability Install Service Availability Follow the instructions in this section if you are installing Service Availability for the first time. To Install SA on a UNIX System 1. Verify that ehealth, SystemEDGE, and the SystemEDGE JRE package are installed, as described in the How to Set Up Service Availability on page Log in as the root user on the system(s) from which you want SA tests to originate. 3. Verify that /plugins exists in the SystemEDGE agent installation directory. The recommended directory is /opt/empsysedge/plugins. If that directory does not exist, verify that you have SystemEDGE Release 4.2 or later installed and then create the directory manually. 4. Insert the AdvantEDGE CD into the CD-ROM drive and mount it on the partition /cdrom. For mounting instuctions, see your system documentation. For Solaris systems, execute the following command: mount -r -t hsfs /dev/sr0 /cdrom 5. Change to the SystemEDGE agent installation directory and load the files from the CD-ROM by executing the following commands (for Solaris): cd /opt/empsysedge tar xvof /SvcRspFilepath/svcrsp.tar 6. Run the install script by executing the following commands (for Solaris): cd /opt/empsysedge/plugins/svcrsp/./install Note: For AIX systems, the installation directory is as follows: /usr/lpp/empsysedge (not /opt/empsysedge) Similarly the install script for SA is in the following directory: /usr/lpp/empsysedge/plugins/svcrsp/install Please pay particular attention to these sections of the SystemEDGE installation: Managing Community Strings: The installer shows your current SNMP community string setting(s). You need at least one read-only and one read-write community string. Without a read-write community string set, you cannot run SA tests. Trap Destinations: The ehealth server must be one of your trap destinations to support monitoring. The installer shows your current trap destination settings and lets you create new ones. 12 Setting Up Service Availability 2.0

13 Install Service Availability Installing and Licensing JDBC drivers: You have two options: install a JDBC driver to support Microsoft SQL tests in SA and install a JDBC driver to support Oracle tests in SA. If you choose to install either or both drivers, you must accept the associated licensing agreement(s). Finally, the installer takes you through the SystemEDGE licensing procedure. 7. Complete the agent licensing and then complete the procedures in the chapter about managing SA agents and tests. Note: If the installation process does not succeed, read the install log to see if you have entered information incorrectly. This file is in the following location: /tmp/svcrsp.install.log To Install SA on Windows Systems 1. Verify that ehealth, SystemEDGE, and the SystemEDGE JRE package are installed, as described in How to Set Up Service Availability on page Log on to the Windows system as the administrator. 3. Insert the AdvantEDGE CD-ROM into the drive. 4. Double-click svcrsp.exe to launch the InstallShield installer. The Service Availability Module Installation dialog appears. 5. Click Next. An informational screen appears. 6. Click Next. InstallShield installs the module on your system. 7. Click Finish. 8. Click Yes in the dialog to enable Service Availability monitoring in SystemEDGE. 9. Specify the number of threads you want Service Availability to run simultaneously and then click Next. The default value is 10. If, however, you intend to run Virtual User tests (or run SA tests sequentially), specify 1. A dialog asks if you want Service Availability to execute Custom (and Virtual User) scripts, File I/O tests, and allow Untrusted SSL Certificates. 10. Click the boxes next to the options that you want to enable and then click Next. A dialog informs you that a TOS (Type of Service) registry entry has been created and set to enabled. (This change takes effect after you reboot.) If your routers are configured to use TOS, you can set TOS values with Service Availability. 11. Click Next. A dialog informs you of the current SNMP read-write community string(s) and asks if you want to add new ones. Installing Service Availability 13

14 Install Service Availability 12. Add any new strings, separated by spaces, and then click Next. A dialog informs you of the current SNMP read-only community string(s) and asks if you want to add new ones. 13. Add any new strings, separated by spaces, and then click Next. A dialog informs you of the current SNMP trap community:destination pairs and asks if you want to add new ones. 14. Add any new pairs, separated by spaces, and then click Next. A dialog asks if you want to download the JDBC drivers for Microsoft SQL Server, Oracle, or both. 15. Click the boxes for the databases against which you intend to run SQL tests and then click Next. 16. Click Yes to proceed with the database driver downloads. 17. Click Yes in the subsequent window to accept the license agreement for each driver. The installation starts the SystemEDGE agent, and a dialog asks whether you want to license Service Availability now. 18. Click Yes. The License Type dialog appears. 19. Accept the default of permanent or specify usage or partner. A dialog asks if you are using a Web proxy. 20. Do one of the following: If you are using a proxy server, click Yes and then specify a hostname, user name, and password for the proxy in the subsequent dialogs. If you are not using a proxy server, click No. The Web Licensing Account Information dialog appears. 21. Specify your licensing account user name and password and click Next. A dialog informs you that license data will be sent to productlicensing@ca.com and asks for confirmation. 22. Click OK. The installer adds a licensing string for your Service Availability module to the drive:\winnt\system32\sysedge.lic file and the InstallShield Wizard Complete dialog appears. 23. Click Finish and then complete the procedures in the chapter about managing SA agents and tests. Note: For a complete list and description of the installed files, see the ehealth Help. 14 Setting Up Service Availability 2.0

15 Chapter 2: Upgrading Service Availability This chapter contains the following topics: Guidelines for Upgrading Service Availability Service Availability Upgrade Process Migrate Existing SA Paths Upgrade Service Availability Guidelines for Upgrading Service Availability Before upgrading SA, pay close attention to the following: Users upgrading from a previous version of Service Availability can still view, delete, and retire SA 2.0 paths in the ehealth Path Manager. You can no longer use Path Manager, however, to create new SA paths (tests). With ehealth 5.7 or later, you create and manage all SA tests from the SA Web interface. Once you have upgraded your ehealth system and have migrated your SA paths, you can start using the SA 2.0 web console to make changes to existing SA tests and create new ones. CA recommends that you upgrading your ehealth server before upgrading your SA agents to SA 2.0. Although ehealth versions prior to 5.7 can poll and report on SA agents that have been upgraded to SA 2.0, the new test format used by the SA 2.0 agent is not backward compatible with previous versions of ehealth. Any attempts made to create or modify SA tests on an upgraded SA 2.0 agent by previous versions of ehealth may cause erroneously formatted SA tests and will result in ehealth polling errors. Before installing SA 2.0, you must install the SystemEDGE JRE Software Package for Version 2. This package was previously installed with SA, but now must be installed separately. Upgrading Service Availability 15

16 Service Availability Upgrade Process If you have more than one ehealth system running SA tests on a common agent, contact your ehealth Technical Support representative for assistance in upgrading ehealth. If you are currently using Service Availability tests created with the ehealth Path Manager, you must migrate those test paths before you can use them in ehealth 5.7 or later. Service Availability Upgrade Process To upgrade SA, you must complete the follow tasks: 1. Upgrade ehealth to Release 5.7 or later first. Note: For more information, see the ehealth Installation Guide. 2. Verify that polling is turned on for existing SA paths that need to be migrated. 3. Let the ehealth poller run for at least one complete polling interval (about five minutes). 4. Migrate your existing SA paths with the nhmigratesapaths utility. 5. Make a backup copy of the current SA installation directory on each SA test system and keep a copy of the configuration file, svcrsp.cf, for use later in the process. 6. Upgrade SystemEDGE to Release 4.2 or later for each SA test system. 7. Install the SystemEDGE JRE Software Package for Version 2 on each SA test system. The JRE package is available from the SystemEDGE Downloads page of the ehealth Support Website: 8. Upgrade to SA 2.0 On each SA test system. 9. Use ehealth to run the discover process in System and Response Elements modes to rediscover all of the SystemEDGE agents. 10. Commit the agent updates to synchronize the agents with ehealth. 11. Create new tests, test sets, agents sets, and test profiles as necessary. 12. Monitor your agents and test profiles. 13. View historical ehealth and Live Health reports. More information: Guidelines for Upgrading Service Availability on page 15 Commit Changes on page 30 Monitor Agents and Test Profiles on page Setting Up Service Availability 2.0

17 Migrate Existing SA Paths Migrate Existing SA Paths The nhmigratesapaths utility migrates only those response paths that are currently in the ehealth database. If your current SA configuration file has Service Availability tests that do not exist as paths in ehealth, those paths are not in the current ehealth database and will not migrate successfully. To manage them through the SA 2.0 Web interface, you must create them again as new tests by using the Service Availability page of the Systems & Apps tab after upgrading ehealth and your SA agents. Note: nhmigratesapaths is a run once tool. After this migration program has run successfully, the SA test configuration can be managed only from the new SA web interface. Any SA path modifications made from Path Manager after you migrate your SA paths are temporary and will be overwritten by SA once the SA agent has been upgraded to SA 2.0. Run nhmigratesapaths once, as soon as possible, after upgrading to ehealth Release 5.7 or later and before upgrading your agents to SA 2.0. ehealth does not overwrite existing SA test paths (agent-test pairs) that exist in the current configuration file, whether or not those tests were created originally in ehealth. At startup, SA 2.0 updates the existing configuration file in the SA installation directory with any new configuration options. It does not change the settings for other (previous) configuration options. To Migrate Existing SA Paths 1. Make sure that the ehealth system has been upgraded to Release 5.7 or later and that you have not created any SA 2.0 tests, test sets, or agent sets by using the Service Availability page of the Web interface. Note: nhmigratesapaths will not run if there are pre-existing SA 2.0 paths. If any exist, you must use nhmigratesapaths -deleteconfig to remove those paths before you begin path migration. 2. Verify the following: Your ehealth system is not the front end system in an ehealth cluster. In a Distributed ehealth environment, run nhmigratesapaths on all of the back-end systems that have Service Availability paths or elements configured. ehealth is running. Polling is turned on for all paths that you want to migrate. Note: The nhmigratesapaths utility does not migrate paths that have polling turned off or paths that are polled remotely. 3. Open a command window on the ehealth system and execute one of the following commands. On UNIX, the command format is: NH_HOME/bin/nhMigrateSaPaths Upgrading Service Availability 17

18 Upgrade Service Availability NH_HOME Represents the ehealth home directory. On Windows, the command format is: nhmigratesapaths nhmigratesapaths verifies the following: You have not run the utility previously on this system. Service Availability paths exist in the ehealth Path Manager. No duplicate paths exist in the ehealth Path Manager. If they do, nhmigratesapaths displays a list of the duplicates and exits. You must clean up the duplicates before running the utility again. nhmigratesapaths checks for the following: Any existing paths that have polling turned off or are retired. Whether any paths are dynamic. If so, nhmigratesapaths lists the dynamic paths to let you delete or retire them before rerunning the utility. Finally, nhmigratesapaths migrates any known paths and displays the number of paths migrated successfully. Upgrade Service Availability Standardizing the location in which you install SystemEDGE agents makes deployment and ongoing management simpler. If you want to configure SystemEDGE log file monitoring of SA test systems, CA recommends that you install the SystemEDGE agent in default locations. Otherwise, you must modify the AdvantEDGE View templates to include the correct path to the log files. To Upgrade to SA 2.0 on UNIX Systems 1. Verify that ehealth Release 5.7 or later, SystemEDGE Release 4.2 or later, and the SystemEDGE JRE software package are installed, as described in the Service Availability Upgrade Process on page Log in as the root user on the SA system(s). 3. Verify that /plugins exists in the SystemEDGE agent installation directory. The recommended directory is /opt/empsysedge/plugins. If that directory does not exist, verify that you have SystemEDGE Release 4.2 or later installed and then create the directory manually. 4. Stop the SystemEDGE agent by executing the stop command for the SystemEDGE startup script. For Solaris, execute the following command: /etc/rc2.d/s99sysedge stop 18 Setting Up Service Availability 2.0

19 Upgrade Service Availability Note: The location and name of the startup script varies by operating system. For information about the name and location of the SystemEDGE startup script for your operating system, refer to the ehealth SystemEDGE User Guide. 5. Make a copy of the current svcrsp.cf configuration file on each SA agent system (after migrating paths) for use later. 6. Insert the AdvantEDGE CD into the CD-ROM drive and mount it on the partition /cdrom. Note: For mounting instuctions, see your system documentation. For Solaris systems, execute the following command: mount -r -t hsfs /dev/sr0 /cdrom 7. Change to the SystemEDGE agent installation directory and load the files from the CD-ROM by executing the following commands (for Solaris): cd /opt/empsysedge tar xvof /SvcRspFilepath/svcrsp_full.tar Note: For AIX systems, the installation directory is: /usr/lpp/empsysedge (not /opt/empsysedge) Service Availability is now installed. Note: If you installed Service Availability in a location other than the default location, specify the correct install path for your installation. If you do not include the correct path, the SystemEDGE agent cannot load the module and Service Availability cannot collect data. 8. Put a copy of your backup SA configuration file into the current SA 2.0 install directory. When SA starts, ehealth will update it with any new configuration options while maintaining your current configuration. 9. Configure SystemEDGE to load SA by opening the /etc/sysedge.cf file in a text editor. Add the sysedge_plugin keyword and the path to the shared library for SA and then save the file. For example, you would add the following text for a 64-bit Solaris system (on one line): sysedge_plugin /opt/empsysedge /plugins/svcrsp/svcrsp-sparcv9.so 10. Restart the SystemEDGE agent by executing the following command from the /opt/empsysedge directory (for Solaris): /etc/rc2.d/s99sysedge start You can now complete the procedures for managing SA agents and tests. Note: For a complete list and description of the installed files, see the ehealth Help. Upgrading Service Availability 19

20 Upgrade Service Availability To Upgrade to SA 2.0 on Windows Systems 1. Verify that ehealth Release 5.7 or later, SystemEDGE Release 4.2 or later, and the SystemEDGE JRE software package are installed, as described in the Service Availability Upgrade Process on page Log on to the Windows system as administrator. 3. Insert the AdvantEDGE CD-ROM into the CD-ROM drive. 4. Double-click svcrsp.exe to execute the InstallShield installer. The Service Availability Module Installation dialog appears. 5. Click Next. An informational screen appears. 6. Click Next. InstallShield installs the module on your system. 7. Click Finish. 8. Click Yes to enable Service Availability monitoring in SystemEDGE. 9. Specify the number of threads that you want Service Availability to run simultaneously and then click Next. The default value is 10. If, however, you intend to run Virtual User tests (or run SA tests sequentially), specify 1. Note: To change configuration settings, edit this file: \sysedge\plugins\svcrsp\svcrsp.cf A dialog asks if you want Service Availability to execute Custom (and Virtual User) scripts, File I/O tests, and allow Untrusted SSL Certificates. 10. Click the boxes next to the options you want to enable and then click Next. A dialog informs you that a TOS (Type of Service) registry entry has been created and set to enabled. (This change takes effect after you reboot.) If your routers are configured to use TOS, you can set TOS values with Service Availability. 11. Click Next. A dialog informs you of the current SNMP read-write community string(s) and asks if you want to add new ones. 12. Add any new strings, separated by spaces, then click Next. A dialog informs you of the current SNMP read-only community string(s) and asks if you want to add new ones. 13. Add any new strings, separated by spaces, then click Next. A dialog informs you of the current SNMP trap community:destination pairs and asks if you want to add new ones. 14. Add any new pairs, separated by spaces, then click Next. A dialog asks if you want to download the JDBC drivers for Microsoft SQL Server, for Oracle, or both. 15. Click the boxes for the databases against which you intend to run SQL tests and then click Next. 20 Setting Up Service Availability 2.0

21 Upgrade Service Availability 16. Click Yes to proceed with the database driver downloads. 17. Click Yes in the subsequent window to accept the license agreement for the driver. 18. Click OK. The installation starts the SystemEDGE agent. 19. Click Finish. You can now complete the procedures for managing SA agents and tests. Note: For a complete list and description of the installed files, see the ehealth Help. Upgrading Service Availability 21

22

23 Chapter 3: Managing SA Agents and Tests This chapter contains the following topics: Discover SA Agents SA Workflow Overview Guidelines for Changing Configuration Settings Edit the SA Configuration File Run Historical Reports for Your Paths Supported Platforms for SA Discover SA Agents The ehealth discover process finds elements in your IT infrastructure and stores information about them in the ehealth database and poller configuration. After you install your SA agents, you must use your ehealth system to discover them. Note: To upgrade SystemEDGE agents by using a push deployment from the ehealth web console, see the ehealth Help. You must be an ehealth administrator to run the discover process. To run the discover process 1. Select Setup, Discover from the ehealth console. The Discover dialog appears. 2. Select System and Response Elements under Mode. 3. Specify the read and write community strings to use to discover the agents in the Community Strings field. You need a write community string for SA to write tests to agents. 4. Locate Discover Using and specify the IP addresses of the systems on which you installed the SA agents. 5. Click Discover. 6. Click Save in the Discovering dialog. Managing SA Agents and Tests 23

24 SA Workflow Overview The elements that ehealth discovered are saved, and these agents are now displayed on the Agent Management page of the SA Web interface. Note: For more information about running the discover process, click Help in the Discover dialog. SA Workflow Overview The SA Web interface provides a central management console for your SA agents. You can use this interface to do the following: 1. View the list of available agents. 2. Create tests. 3. Group them into test sets (optional). 4. Group the agents into agent sets (optional). 5. Associate the agents and agent sets with tests and test sets by creating test profiles. 6. Use commit to propagate your tests to the agents. 7. Monitor the performance of tests, based on agents or test profiles. View Agents Before creating any tests, be sure that ehealth knows about your agents. You cannot write tests to agents until ehealth has discovered them. To view the known agents 1. Go to the Service Availability page of the ehealth Web interface. 2. Click Agents. The Agent Management page appears and lists each agent known to ehealth. In SA 2.0, you associate agents with tests in a test profile and then deploy (by using Commit) the profile to the agents in the list. SA uses that information to create test paths automatically. If agents do not appear in the list, ehealth has not discovered any agents. Verify the following: The SystemEDGE agent and Service Availability module are installed on your systems. The discover process was run for those systems using the System and Response Elements modes. 24 Setting Up Service Availability 2.0

25 SA Workflow Overview Create Tests SA provides over 20 types of tests for evaluating the availability and performance of key business applications. SA 2.0 lets you create tests independently of agents and create sets of tests and associate them with an agent or a set of agents when you create a test profile. You can also deploy one or more tests to one or more agents by using test profiles. To create a test 1. Go to the Systems & Apps page from the ehealth Web interface. 2. Select Service Availability and then click Tests. The Test Management page appears. 3. Click Add. The Create a New Test page appears. 4. Select the type of test to create from the Test Type list and complete the fields for name, description, and the test-specific options. The online help from that page provides details and examples to help you complete the page for each type of test. Note: When specifying pathnames for new tests that you create, be sure to use the correct formats for the operating system on which the test runs. Use forward slashes (/) for UNIX systems and backslashes (\) for Windows systems. 5. (Optional) Select Advanced to view and modify advanced options for the test. 6. Click Save when you have finished specifying options for the test. To create a test that is very similar to a test you have already created 1. Select the test on the Test Management page. 2. Click Modify and specify a new test name. 3. Modify any options and then click Save As. The new test is created. Create Test Sets You can group your SA tests logically by creating test sets. For example, one test set may contain a variety of tests whose purpose is to monitor the availability and performance of important Web sites. Another test set may focus on or database performance. Your test sets may apply to the entire enterprise, to specific locations in the company, or to specific business units or organizations. To create a test set 1. Go the Service Availability page from the ehealth Web interface and click Test Sets. Managing SA Agents and Tests 25

26 SA Workflow Overview The Test Set Management page appears. If tests do not appear on this page, you have not created them. 2. Click Add. The Create a new Test Set page, shown in the following graphic, appears. 3. Specify a name and (optional) description for the test set. 4. Select the tests that you want to add to the test set from the Available Tests list and then click Add. To select multiple tests, press Ctrl and select the tests that you want to add. 5. (Optional) Select any test in the Member Tests list that you want to remove from the set and click Remove. 6. Click Save to create the test set. The Test Set Management page appears. Create Agent Sets You can group your agents logically by creating agent sets. An agent set makes it possible to deploy the same test or test sets to a range of agents to set up uniform testing for various business organizations or locations. Agent sets enhance the flexibility of deploying tests and serve as a means of organizing the type of targets for which you produce ehealth reports. 26 Setting Up Service Availability 2.0

27 SA Workflow Overview To create an agent set 1. Go the Service Availability page from the ehealth Web interface and click Agent Sets. The Agent Set Management page appears. 2. Click Add. The Create a new Agent Set page appears. 3. Specify a name and (optional) description for the agent set. 4. Select the agents that you want to add to the agent set From the Available Agents list and then click Add. To select multiple agents, press Ctrl and select the agents you want to add. 5. (Optional) the Member Agents list, select any agents in that you want to remove from the set, and click Remove. 6. Click Save to create the agent set. The Agent Set Management page, shown in the following graphic, appears. 7. Finish creating agent sets and commit your changes as described in Commit Changes on page 30. Managing SA Agents and Tests 27

28 SA Workflow Overview Create Test Profiles Test profiles associate the tests and test sets that you create with agents and agent sets. You can add the same tests, test sets, agents, or agent sets to multiple profiles. When you create a test profile and commit changes, ehealth adds each test to the associated agent and creates a response path element for each agent-test association in the profile. Even if the same agent-test association exists in multiple profiles, ehealth creates only one path and adds it to the agent only once. To create a test profile 1. Go to the Service Availability page from the ehealth Web interface and click Test Profiles. The Test Profile Management page appears. 2. Click Add. The Create a new Test Profile page appears. 3. Specify a name and (optional) description for the test profile. 4. Select Agent Sets or Single Agents and then select the agent sets or agents that you want to add to the profile. 5. Select Test Sets or Single Tests and then select the test sets or tests that you want to associate with the agent or agent set that you selected. 6. Click Add. The association that you created appears. 28 Setting Up Service Availability 2.0

29 SA Workflow Overview 7. Repeat steps 5 and 6 until you have finished associating agents and tests for this profile. Note: SA does not distinguish between Windows and UNIX systems when deploying tests. When you associate tests with agents in the test profile, be sure not to associate a Windows-specific test with an agent on a UNIX system. For example, the MAPI and Virtual User tests can run only on Windows systems. If you create a test profile in which you apply those types of tests to agents on UNIX systems, SA creates the test profile but the tests will fail when the agent attempts to run them. 8. (Optional) Remove associations from the test profile by selecting the association and clicking Remove. 9. Click Save to create the test profile. The Test Profile Management page appears. 10. Finish creating test profiles and commit your changes. ehealth creates paths for each agent-test association in the profile and pushes the tests to the specified agents. Guidelines for Using Commit to Propagate Tests to Agents When you make changes through the Service Availability Web interface, the changes are saved in the ehealth database but are not transferred immediately to the ehealth poller configuration or the Service Availability agents. To create or modify ehealth paths and push changes to the SA agents, you must commit the changes. You can commit changes by clicking Commit from the Service Availability page. The recommended practice is to commit changes all at once when you have completed the process of creating or modifying your tests, test sets, agent sets, or test profiles. The Test Profile Management page includes a Changes Committed column to indicate whether changes have occurred to any tests, test sets, or agent sets in the profile. If that column has a value of No, the information in the ehealth database is not up to date with the information that exists on the agent and in the poller configuration and, thus, requires a commit. Types of Commits You can select two types of commit: An incremental commit updates the agents and the ehealth poller configuration with only those additions or modifications that occurred since the last commit (or with changes that were not pushed to an agent because the agent was inaccessible at that time.) An incremental commit is the default type of commit. A full commit rebuilds the entire configuration on the selected agents and rebuilds the paths, synchronizing the agents with what is current in the ehealth database. A full commit takes longer than an incremental commit because it transfers more data. Managing SA Agents and Tests 29

30 SA Workflow Overview Note: Use the full commit only if the information on the agent and in the ehealth database are not the same. For example, if you perform a commit and some agents do not get updated, the commit log file may recommend that you perform a full commit. If your svcrsp.cf file on the agent system includes entries that do not exist within the ehealth database (any entries that you did not create through the SA Web interface), a full commit does not delete that information. A full commit deploys the information from the ehealth database to the agents by adding missing information and updating all entries that were added, modified, or deleted through the SA Web interface. Commit Changes You must commit changes made through the Service Availability Web interface to transfer them to SA agents and create or modify ehealth paths. To commit changes 1. Click Commit Changes from the Service Availability page of the Systems & Apps tab. The Commit Changes page appears. 2. Do one of the following: For an Incremental commit (the default), click Commit. For a Full Commit, select Rebuild Full Configuration near the bottom of the Commit screen and click Commit. 30 Setting Up Service Availability 2.0

31 SA Workflow Overview To stop the commit process, click Stop. ehealth completes the updates process for the agent currently being addressed and then completes the commit process for just those agents that were contacted. If an agent is unavailable when ehealth attempts to contact it, the Commit Changes Status page informs you that it could not update that agent. ehealth does not attempt to contact the agent again until the next time that you commit changes. The Committed Changes column on the Test Profile Management page continues to display No for any profiles to which that agent belonged until the agent is updated by a subsequent commit. To exclude one or more agents from a commit operation, deselect that agent name. View Commit Log Files You can view log files for commit operations on the Commit Changes page. The logs provide detailed information about the changes, including which tests were added to, updated on, or deleted from each agent, and any agents that ehealth could not contact. To view a log file 1. Select the log you want to view from the Log files available to view list on the Commit screen. 2. Click Open. The log file appears in a new window. Monitor Agents and Test Profiles You can monitor all of the tests running on an agent by clicking the Monitor button at the bottom of the left panel. To monitor agents from the Monitor Setup screen 1. Select either Monitor by Agent or Monitor by Profile. 2. Select one agent or profile to monitor. The Test Monitor page appears, listing all tests on the selected agents or test profiles. Managing SA Agents and Tests 31

32 SA Workflow Overview Modify the Test Monitor page When you are monitoring agents or test profiles, you can alter the information that displays on this page. You can view relevant information and hide the information that is not relevant. To change the columns that you want to display in the table 1. Select Show Column Config. 2. Select the columns that you want to display or deselect any columns that you do not want to display. 3. Click Update Page. Note: For more information about columns, access the Web Help from this page. You can filter the information on the page by hostname, test type, or row status. This features lets you narrow down the amount of information for snapshots of particular systems or problem areas. To filter the information on the page 1. Select Show Filter Options. 2. Select a hostname from the Agent list, a test type from the Test Type list, or a row status from the Row Status list. 3. Click Update Page. You can refresh the page, set a refresh interval, or reset the display defaults. 32 Setting Up Service Availability 2.0

33 Guidelines for Changing Configuration Settings To refresh the page, click Force Refresh. To enable the page to refresh every 60 seconds, click Enable Refresh. You can configure a different refresh interval from the AdvantEDGE View Preferences page. To reset the display with the default options, click the Default Columns button at the bottom of the screen. Guidelines for Changing Configuration Settings Follow these guidlines when editing the SA configuration file: On UNIX systems, you must make any configuration file modifications after installing or upgrading SA. On Windows systems, you can specify some configuration parameters during installation. You can also edit the configuration file afterward. If you deploy sets of tests from the ehealth server, set up the configuration file before deployment. In this way, you can push a common SA configuration to multiple systems where SystemEDGE agents and SA tests run. You must edit the javabin field if your SystemEDGE agent is installed in a directory other than the default (/opt/empsysedge). You can modify configuration settings any time after installing SA. Whenever you make such changes, you must stop and restart the SystemEDGE agents affected by those changes. Edit the SA Configuration File Some configuration options, such as security privileges, the maximum number of threads, or the location of Java Runtime Environment (JRE) files, are set by default. Others are disabled by default. To change SA configuration settings 1. Stop the SA agent(s) whose configuration file you intend to change. 2. Open the svcrsp.cf file with an editor. 3. Review the settings for SA operating parameters that affect performance and security. These parameters include the maximum number of threads, an alternate location for the JRE, or whether to allow SSL tests to work with sites that do not have trusted certificates. 4. Make any necessary changes and then save the file. Managing SA Agents and Tests 33

34 Run Historical Reports for Your Paths 5. Restart the SA agent(s). Note: With security settings enabled, some operations such as File I/O and Custom tests may not run. Run Historical Reports for Your Paths You can link directly to the ehealth Run Reports page. After Service Availability has been running tests for at least one polling cycle (about five minutes), you can obtain historical data for the paths in a test profile. To run an At-a-Glance report for a path in your test profile 1. Go to either the Modify Test Profile page or the Test Profile Monitor page and select Run-At-Glance at the bottom of the page. 2. Click the name of a path to link to the Run an At-a-Glance report page for that path. 3. Click Generate Report. (Optional) You can specify a different Sample Size and Report time. Note: For more information about running the report, click the Help icon. An At-a-Glance report appears. Note: A complete At-a-Glance report for the response path also includes charts for Attempts, Total Bytes, Total Throughput, and Total Errors. You can also run At-a-Glance reports for your response paths and response endpoints directly from the Run Reports tab of the ehealth Web interface. To run additional ehealth reports, do one of the following: Click on one of the charts to drill down to a Trend report for the path. Return to the Run Reports tab to run Top N, Health, or Service Level reports for the path. Supported Platforms for SA Service Availability runs on the following platforms: Sun Solaris SPARC Releases 2.6 through 2.10 Sun Solaris x86 Releases 2.6 through 2.9 (32-bit) Microsoft Windows NT 4.0 (Service Pack 6a or later), Windows 2000, Windows XP, and Windows 2003 (32-bit only) HP-UX /PA-RISC 11.0, 11i AIX Releases and 5.1 through 5.3 (32- and 64-bit). 34 Setting Up Service Availability 2.0