CA ehealth CA Performance Center

Transcription

1 CA ehealth CA Performance Center Integration and User Guide CA ehealth r6.2.2/r6.3 / CA Performance Center r

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your 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 may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. 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 YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. 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. Copyright 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA ehealth Release and Release 6.3 CA Performance Center Release Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4

5 Contents Chapter 1: Introduction 9 Before You Begin... 9 Overview Chapter 2: Configuring the Integration 17 Prerequisites Distributed ehealth Clusters How to Configure the Integration Run the Setup Utility on Cluster Members Add CA ehealth as a Data Source Connect to a CA ehealth Data Source Using HTTPS Synchronization of Elements and Groups Set Permissions to Access CA Performance Center Options in CA ehealth Multiple Agents with the Same Port Remote Pollers Delete a Data Source (Optional) Import CA ehealth Certificates from Back-End Systems to the Front-End System Chapter 3: Using CA Performance Center 27 Configuration Items Search for Managed Items Create Groups of Managed Items Manage Groups and Elements in CA Performance Center Types of CA Performance Center Views Edit the Settings for a View CA Performance Center Views That Contain CA ehealth Data View Element-Based Reports View Device-Based Reports View Interface-Based Reports Create and View Group-Based Reports Create and View Custom CA ehealth Element-Based Reports Search for Managed Items from a Report Page Chapter 4: Using CA ehealth 45 CA Performance Center Drill-Down Option Contents 5

6 Log In to the CA ehealth Web User Interface Drill Down from a CA ehealth Element Trend Report Drill Down from a CA ehealth Top N Report Drill Down from a CA ehealth Health Report Drill Down from the Performance Dashboard Drill-Downs to CA Performance Center from Live Health Drill Down from the Live Exceptions Browser Drill Down from the Live Status Window Chapter 5: Configuring TelePresence and Virtualization Overview Reports 55 Cisco TelePresence TelePresence Overview Reports How to Set Up Your System to Run TelePresence Overview Reports Create a TelePresence Overview Report Customization Options Virtualization Overview Reports How to Set Up Your System to Run Virtualization Overview Reports Create a Virtualization Overview Report Customization Options Appendix A: Default Views Provided by the Integration 63 App Service Views Backplane Views CPU Views Disk Partition Views Disk Views DSP Card Views End-to-End Views Environment Component Views Environmental Sensor Views Industrial Component Views Interface Views Internet Appliance Views IP Stats Views LAN/WAN Views Memory Views Mobile Wireless Component Views Mobile Wireless Device Views Mobile Wireless Views Modem Pool Views Modem Views Integration and User Guide

7 Packet Forward Engine Views Power/Energy Component Views Process Set Views Process Views QoS Views Remote Access Server Views Response Client Set Views Response Endpoint Views Response Path Views Router Views Router/Switch Views Server Views System Environmental Sensor Views System Views Appendix B: TelePresence Overview Report Data 93 TelePresence Overview Report Parameters Appendix C: Virtualization Overview Report Data 97 CA ehealth Groups Virtualization Overview Report Parameters VMware Overview Report Parameters HyperV Overview Report Parameters LPAR Overview Report Parameters Solaris Zones Overview Report Parameters Index 111 Contents 7

8

9 Chapter 1: Introduction Before You Begin Before you begin deployment, it is important that you review the following information. Supported environment The following information describes the environment this deployment supports: Operating system: Solaris 2.10 (SPARC) CA ehealth: r6.2.2 and r6.3.0 CA Performance Center: r Additional system requirements have not changed, but can be reviewed in the CA ehealth Release Notes. Package deployment The purpose of this package is to enable CA Performance Center to add CA ehealth as a data source. This package also includes a performance enhancement for the CA Performance Center/CA ehealth synchronization process. Deploy packages based on the version of CA ehealth installed on a system: Deploy EH_622_SP.zip on the systems with CA ehealth r6.2.2 installed. Deploy EH_630_SP.zip on the systems with CA ehealth r6.3.0 installed. The deployment package contains the following files: axis2.war web.war README CA ehealth / CA Performance Center Integration/User Guide (ehealth_pc_integration_enu.pdf) Chapter 1: Introduction 9

10 Before You Begin To deploy this package, follow these steps: 1. Create a directory named $NH_HOME/deploy. mkdir $NH_HOME/deploy 2. Copy the zip file (EH_622_SP.zip or EH_630_SP.zip) to $NH_HOME/deploy. 3. Unzip the file. cd $NH_HOME/deploy $NH_HOME/bin/sys/nhiUnZip EH_622_SP.zip OR cd $NH_HOME/deploy $NH_HOME/bin/sys/nhiUnZip EH_630_SP.zip 4. Create a backup of the existing.war files. mv $NH_HOME/web/tomcat/webapps/axis2.war $NH_HOME/web/tomcat/webapps/axis2.war.bak mv $NH_HOME/web/tomcat/webapps/web.war $NH_HOME/web/tomcat/webapps/web.war.bak 5. Stop CA ehealth web services. nhhttpd stop 6. Clear files and directories and prepare for deployment. rm rf $NH_HOME/web/tomcat/webapps/axis2 rm rf $NH_HOME/web/tomcat/webapps/web 7. Apply the patch. cp -p $NH_HOME/deploy/axis2.war $NH_HOME/web/tomcat/webapps/axis2.war cp -p $NH_HOME/deploy/web.war $NH_HOME/web/tomcat/webapps/web.war 8. Change the directory. cd $NH_HOME/web/tomcat/conf 9. Back up the current server.xml. cp p server.xml server.xml.save 10 Integration and User Guide

11 Before You Begin 10. Edit server.xml and locate the following section (look for axis2): <Context docbase="axis2" path="/axis2" reloadable="true"> <Resource name="jdbc/ehdb" auth="container" type="oracle.jdbc.pool.oracledatasource" driverclassname="oracle.jdbc.driver.oracledriver" factory="oracle.jdbc.pool.oracledatasourcefactory" accesstounderlyingconnectionallowed="true" connectioncachingenabled="true" connectioncacheproperties="{minlimit=10,maxlimit=20}" /> </Context> Note: "KRONE_EHEALTH" is system-specific. Verify that target systems are of similar syntax, such as <hostname>_<oracle_sid>. 11. Change Maxlimit from 20 to 460 in the following line: FROM: connectioncacheproperties="{minlimit=10,maxlimit=20}" /> TO: connectioncacheproperties="{minlimit=10,maxlimit=460}" /> 12. Save server.xml. 13. Restart CA ehealth web services. nhhttpd start Chapter 1: Introduction 11

12 Before You Begin To add performance enhancements for synchronization, follow these steps: 1. Increase the Oracle process limit, based on various factors. Calculate this number as follows: a. Determine the current Oracle processes parameter value, by running the following commands: ksh $NH_HOME/bin/sys/nhisql select value from v\$parameter where name= processes' b. On a Distributed Console, add the number returned by the previous command to the product of: Number of concurrent CA Performance Center users Average number of views in each report Number of ehealth systems in the cluster (or 1, if a standalone server) Example: Number of concurrent CA Performance Center users = 20; Average number of views in each report = 4; Number of ehealth systems in the cluster = 16; Processes = (20 * 4 * 16) + (current Oracle Processes) c. On Distributed Servers or standalone systems, add the current number of Oracle processes to the product of: Number of concurrent CA Performance Center users Average number of views in each report Example: Number of concurrent CA Performance Center users = 20; Average number of views in each report = 4; Processes = (20 * 4) + (current Oracle Processes) 12 Integration and User Guide

13 Before You Begin d. Use the following command to increase the number of processes. For example, if the number of processes obtained from the previous calculation is 750, then use the following command: $NH_HOME/bin/sys/nhisql alter system set processes=750 scope=spfile 2. Increase the value of PGA_AGGREGATE_TARGET. a. On Distributed Servers or standalone systems, add the current PGA_AGGREGATE_TARGET to the product of: Number of concurrent CA Performance Center users Average number of views in each report 1.2 MB b. Use the following command to obtain the current value of PGA_AGGREGATE_TARGET: $NH_HOME/bin/sys/nhisql show parameters PGA_AGGREGATE_TARGET" Example: Number of concurrent CA Performance Center users = 20; Average number of views in each report = 4; Increase in PGA_AGGREGATE_TARGET = (20 * 4 * 1.2 MB) = 96 MB; New value of PGA_AGGREGATE_TARGET = 96 MB + (current value of PGA_AGGREGATE_TARGET) c. Use the following command to increase the size of PGA_AGGREGATE_TARGET. For example, if the new value of PGA_AGGREGATE_TARGET obtained from the previous calculation is 396 MB, then use the following command: $NH_HOME/bin/sys/nhisql alter system set PGA_AGGREGATE_TARGET=396M scope=both 3. Apply changes to the CA ehealth server by restarting CA ehealth and Oracle. a. Shut down CA ehealth services. nhserver stop Chapter 1: Introduction 13

14 Before You Begin b. Shut down and restart the database. nhstopdb immediate nhstartdb c. Restart CA ehealth services. nhserver start Connecting to a CA ehealth data source using HTTPS If you want to use HTTPS for communication between CA Performance Center and a CA ehealth data source, see Connect to a CA ehealth Data Source Using HTTPS (see page 21) for the process to enable this communication. For more information about configuring CA Performance Center properly to use SSL (HTTPS) mode, see the CA Performance Center Single Sign-On User Guide. 14 Integration and User Guide

15 Before You Begin Known Issues The following information describes known issues in the product. Report drilldown to CA Performance Center When you run a CA ehealth report from the OneClickEH console and drill down to CA Performance Center, the following warning message displays: Your web browser is not compatible with this product. You must install a more recent version of this browser to run CA Performance Center. Or if your browser is running in Compatibility Mode, switch it back to normal mode. When this message is encountered, typically you press F12 and then change the browser mode from "IE8 Compatability View" to "IE8" to proceed. However, the F12 button does not work because the report window is not actually a browser window, but a OneClickEH console window. This behavior occurs regardless of what default browser you use, because the OneClickEH console launches the report window using Internet Explorer only. Default CA Performance Center Dashboard reports The default CA Performance Center Dashboard reports do not display data for CA ehealth devices and elements. However, you can create custom CA ehealth dashboards. CA Performance Center integration does not get cleared from a cluster immediately The CA Performance Center/CA ehealth integration is not getting removed immediately when the integration is between a CA ehealth cluster and a CA Performance Center system. To install a new version of CA Performance Center, you first remove the CA Performance Center/CA ehealth integration. After you have removed the CA ehealth data source, you install the new version of CA Performance Center on your CA Performance Center system. Then you run the nhnpcsetup command to configure the integration on the CA ehealth side. However, when you add and then test your CA ehealth data source, you may receive the following error when you attempt to save your configuration: Adding Data Source Failed Data source is already registered to another Performance Center instance You can receive this error even though you verified that the integration was removed by running the nhnpcsetup -list command. After you choose to remove the data source from CA Performance Center, CA Performance Center can take some time deleting the objects that are associated with the data source before it sends the "unregister" request to CA ehealth. The Data Sources page in CA Performance Center does not display whether it is still in the process of removal. You can verify when it has been finally removed by reviewing the Inventory menu in CA Performance Center and verifying that the CA ehealth data source no longer displays inventory items. Chapter 1: Introduction 15

16 Overview Overview The CA ehealth and CA Performance Center integration helps you maintain critical service levels across complex network environments by accessing data about CA ehealth groups and elements from the CA Performance Center interface. This integration lets you: Synchronize data with CA ehealth to keep CA Performance Center up-to-date. View CA ehealth data in the CA Performance Center interface. You can consolidate it with data from other data sources for a comprehensive understanding of your network. Run CA Performance Center reports about CA ehealth groups and elements. Drill down to CA Performance Center from legacy CA ehealth reports and from CA ehealth Performance Dashboard reports. Drill down to CA Performance Center from an alarm in the CA ehealth Live Exceptions Browser to run a CA Performance Center report. 16 Integration and User Guide

17 Chapter 2: Configuring the Integration This section contains the following topics: Prerequisites (see page 17) Distributed ehealth Clusters (see page 17) How to Configure the Integration (see page 17) Multiple Agents with the Same Port (see page 24) Remote Pollers (see page 25) Delete a Data Source (see page 25) (Optional) Import CA ehealth Certificates from Back-End Systems to the Front-End System (see page 25) Prerequisites Before you configure the integration, you must: 1. Install supported releases of CA Performance Center and CA ehealth in your environment. 2. Create CA Performance Center users. Note: For more information about supported releases, see the CA ehealth Release Notes. For more information about installation, see the respective product documentation. For more information about creating CA Performance Center users, see the CA Performance Center User Guide. Distributed ehealth Clusters Distributed ehealth clusters are supported by the integration with CA Performance Center by adding a single cluster front-end system as a data source in CA Performance Center. The cluster front-end system receives, collates, and transforms results from the cluster back-end systems to an appropriate report result, which is then communicated to CA Performance Center. How to Configure the Integration You can configure CA Performance Center with either a Distributed ehealth cluster or a standalone CA ehealth system. For a Distributed ehealth cluster system, complete steps 1 4. For a standalone CA ehealth system, complete steps 2 4. Chapter 2: Configuring the Integration 17

18 How to Configure the Integration 1. (For clusters only) Run the nhnpcsetup utility on one designated CA ehealth front-end system (to add as a data source in CA Performance Center). The designated front end communicates data to CA Performance Center for all back- and front-end systems in the cluster. Specify the credentials for the front- and back-end systems to connect to the designated front-end system. Note: When adding a new member to an existing cluster, run the nhnpcsetup utility on the designated front-end system after adding it to the cluster. 2. Add CA ehealth as a data source for CA Performance Center. For CA ehealth clusters, add only the designated front end as a data source. 3. Verify that synchronization is working by viewing the log files or reviewing the list of devices (Inventory, Device) to verify that the integration is successful. 4. Set permissions for users on the CA ehealth systems to access drill-down reports. More information: Prerequisites (see page 17) Run the Setup Utility on Cluster Members Run the nhnpcsetup utility for all CA ehealth cluster systems to specify credentials to pass from the back-end systems to the designated front-end system. Running this utility is the first, required step in the process of configuring the integration on CA ehealth clusters. Note: Do not run this utility for standalone CA ehealth systems. The first step for configuring a standalone CA ehealth system is Add CA ehealth as a Data Source. You must run this utility for the following scenarios: When you first integrate a CA ehealth cluster with CA Performance Center. After you modify the web user interface, for example, when a password or https is changed, you must rerun this utility. When adding a new member to an existing cluster; run this utility after adding the new member to the cluster. To change the front-end system you are using; you must run this utility on the new front end. The new front end takes over immediately and you are not required to remove the now unused front end. 18 Integration and User Guide

19 How to Configure the Integration 1. Run the following command only from the designated front end system: nhnpcsetup The setup utility prompts you for the values it needs, with default values shown in square brackets. Note: You will run this command several times, targeting each of the other CA ehealth systems in the cluster. 2. Respond to the following prompts as they appear: Enter http port for machine 'test1' [80]: Does machine 'test1' have SSL (https) configured (yes/no)? [no]: Enter web admin user name for machine 'test1' [admin]: Enter web admin user password for machine 'test1': Clearing Errors in Configuration If you complete the configuration, but suspect one or more mistaken entries, run the nhnpcsetup command with the -clear option, as in the following example: nhnpcsetup -clear This clears all of the configuration entries in the cluster. You can then run the nhnpcsetup command again to make the correct entries. The following command line arguments are available for use with this command: -clear -list -h Deletes configuration entries for all cluster members for a given front end server. Displays a list of the existing credentials for all cluster members for a given front end server. Displays the command line help for the utility. Add CA ehealth as a Data Source You must add CA ehealth as a data source in CA Performance Center to make CA ehealth data available in CA Performance Center reports. After you set CA ehealth as the data source, CA Performance Center automatically synchronizes elements and groups with CA ehealth every 5 minutes. Chapter 2: Configuring the Integration 19

20 How to Configure the Integration Completing this procedure is the first, required step in the process of configuring the integration on a standalone CA ehealth system. When configuring a CA ehealth cluster, complete this procedure only on the designated front-end system after running the setup utility on cluster members. Note: The CA ehealth data source can be attached to only one CA Performance Center. To add CA ehealth as the data source 1. Log in to CA Performance Center as a CA Performance Center administrator. 2. Click Admin and select Data Sources from the menu. The Manage Data Sources page appears. 3. Click Add. The Add Data Source page appears. 4. Select ehealth from the Source Type drop-down list, and specify the following: IP address of the CA ehealth server or host name in the Host Name field. Note: For high availability and disaster recovery environments, use the shared host name. Protocol and port in the corresponding fields. Username and password credentials for the CA ehealth admin user. 5. Click Save. CA ehealth is enabled as a data source, and data is exchanged between CA Performance Center and CA ehealth (a process named synchronization). 20 Integration and User Guide

21 How to Configure the Integration Connect to a CA ehealth Data Source Using HTTPS Using HTTPS for communications between CA Performance Center and a CA ehealth data source requires you to complete the following steps: 1. Obtain CA ehealth web server certificates. Note: The required CA ehealth web server certificates are typically one of the following files: $NH_HOME/web/httpd/conf/intermediate.crt $NH_HOME/web/httpd/conf/server.crt Use intermediate.crt if it exists; if it does not exist, use server.crt. The file intermediate.crt may contain several certificates. If this is the case, the key tool does not correctly load all of them. Examine intermediate.crt in any text editor and split individual certificates into separate files using the following marks: "-----BEGIN CERTIFICATE-----" "-----END CERTIFICATE-----" 2. Copy the CA ehealth web server certificates to the directory where you have installed CA Performance Center. Note: This directory location is referenced in the steps that follow as [installationdirectory]. 3. Confirm the TCP port number on which the CA ehealth web server is configured to receive HTTPS traffic. Note: TCP port 443 is used for HTTPS communications by default. Examine the $NH_HOME/web/httpd/conf/httpd.conf configuration file to find the port number that a specific CA ehealth instance uses. Listen Install the CA ehealth server certificates into a CA Performance Center keystore. Use the following commands to add certificates to the keystore: #export PATH=[installationDirectory]/jre/bin:$PATH #export JAVA_HOME=[installationDirectory]/jre #keytool -importcert -trustcacerts -alias cert_alias -file cert_file -keystore [installationdirectory]/jre/lib/security/cacerts Note: cert_alias is a name that is used to identify a particular certificate in the keystore. You can use any name for the alias, such as ehealthservercertificate, as long as it is not already used in the keystore. 5. Repeat the keytool command for each file (cert_file) that you obtained in step 1, using a distinct cert_alias for each file. You are prompted for the keystore password, which is "changeit" by default. 6. Type yes when you are prompted with the message "Trust this certificate? [no]:". 7. Stop and restart the CA Performance Center services. Chapter 2: Configuring the Integration 21

22 How to Configure the Integration 8. Add CA ehealth as a data source using the correct port number as determined in step 3 (443 by default), and use the HTTPS option. Synchronization of Elements and Groups Verify Synchronization Synchronization is the incremental replication of configuration items between CA Performance Center and CA ehealth. The Product Synchronization Web Service provides CA ehealth configuration information to CA Performance Center and allows it to be shared between CA Performance Center and CA ehealth. CA Performance Center imports this information from CA ehealth and renders it in CA Performance Center. Adding CA ehealth as a CA Performance Center data source enables the Product Synchronization Web Service, which triggers the synchronization of configuration information every 5 minutes. Part of the synchronization service allows the replication of CA ehealth group container definitions between the products. Once synchronized, CA ehealth groups are made available within CA Performance Center as system groups, which are read-only and cannot be modified by CA Performance Center users. Any changes to CA ehealth groups are pushed to CA Performance Center during the next synchronization process. Note: CA Performance Center allows different devices to use the same private IP address. In this case, the device name is used to determine whether two devices are actually the same device. You enable this setting in the Admin, System Settings, Global Settings dialog. Synchronization is done automatically, but you can verify the status by viewing the log file in CA Performance Center. To verify synchronization 1. Log in to CA Performance Center as an administrator. 2. Select Admin, Data Sources. The Manage Data Sources page appears. 3. Click Log. The Data Source Log appears and shows the latest log entries. Several entries for the appropriate time period typically indicate that the synchronization was successful. Note: If the log file shows an error, you can resynchronize from the Manage Data Sources page. 22 Integration and User Guide

23 How to Configure the Integration 4. View the information in the entry column. 5. Click Close. You return to the Manage Data Sources page. Set Permissions to Access CA Performance Center Options in CA ehealth Permissions for CA ehealth users to drill down to CA Performance Center are set from the OneClick for ehealth (OneClickEH) console and must be enabled to let you view CA Performance Center reports. Note: For information about setting CA ehealth Web user interface preferences for CA ehealth Performance Dashboard, see the CA ehealth Reports User and Administration Guide. For information about setting CA ehealth Live Health Application or legacy reports privileges, see the CA ehealth online help. To set permissions 1. Select a node from the World View tree in OneClickEH. 2. Select Tasks and Information, User Administration. The User table appears on the right pane. 3. Select a user. The Modify User pane appears. 4. Select the Preferences tab. 5. Select CA NetQoS Performance Center from the drop-down list for the Performance Dashboard Drilldown Target option. This permission provides you with the option to drill down to CA Performance Center reports from the CA ehealth Performance Dashboard. 6. Click Apply. The permissions are set. 7. Select the Reports tab on the Modify User pane. 8. Select Yes from the drop-down list for the Users can run CA NetQoS Performance Center option. 9. Click Apply. The permissions are set. 10. Click OK. Your changes are saved. Chapter 2: Configuring the Integration 23

24 Multiple Agents with the Same Port Multiple Agents with the Same Port There are possible scenarios with multiple agents in CA ehealth: Multiple agents running on different ports of the same device that CA ehealth discovers and polls as separate elements with the same IP address. Multi-function devices; for example, where a device is discovered as both a router and a server in CA ehealth. CA Performance Center considers it an error case where two different ports have the same IP address on the same IP domain and makes one a duplicate of the other. To avoid an error, CA ehealth does not send duplicates of the same CA Performance Center item type over to CA Performance Center. For example, if there are two or more servers with the same IP address (the multiple agent case), one is synchronized as CA Performance Center item type Device / Server and the remaining servers are sent as Item type ehealth subtype server. This prevents the de duplication from occurring. The CA Performance Center item types affected are Device/Server and Device/Router. All CA ehealth elements appear in CA Performance Center, all CA ehealth drill-downs have a corresponding CA Performance Center configuration item without modifications to CA Performance Center, and CA ehealth child elements are correctly parented within CA Performance Center. Note: The best element is synchronized as the CA Performance Center Device item type, which is determined by an algorithm where routers take precedence over servers and higher port numbers take precedence over lower port numbers. However, for devices with multiple agents, CA Performance Center shows multiple configuration items. Example: If you discover an IP address, CA ehealth finds a server with two agents: Euro-1691-SH, a SystemEDGE agent, synchronizes as the CA Performance Center configuration item type Device / Server. Euro-SH, a Sun agent, synchronizes as the CA Performance Center configuration item type ehealth / Server. For a situation where a vendor agent is initially synchronized and then a discover is done on the same IP which finds another agent (such as SystemEDGE agent), an incremental synchronization is performed. The agent added during the initial synchronization is the CA Performance Center Device Item type and the agent discovered later is the ehealth Item type. No designation is made as to which element is best after the synchronization occurs. If a CA ehealth element is retired, it is removed from the CA Performance Center configuration. 24 Integration and User Guide

25 Remote Pollers Remote Pollers CA ehealth remote pollers can be integrated with CA Performance Center. However, the integration does not support multiple remote pollers that are polling the same IP address. Remote pollers are configured using the same procedures to integrate a standalone CA ehealth system. Note: For more information about remote pollers, see the CA ehealth Remote Poller User Guide. Delete a Data Source You can delete a data source from CA Performance Center when you no longer want to integrate with that source. Follow these steps: 1. Log in to CA Performance Center as an administrator. 2. Click Admin and select Data Sources. The Manage Data Sources page appears. 3. Select a data source, and click Remove. The data source is deleted. (Optional) Import CA ehealth Certificates from Back-End Systems to the Front-End System The Distributed ehealth Console (front-end system) designated as a data source makes a web services call to the other cluster members to get data. If the Secure Socket Layer (SSL) protocol is enabled on all systems in a cluster and a firewall is set up between cluster members, the CA Performance Center administrator must do the following: Open the ports on the firewall to allow traffic between cluster members. Obtain copies of all certificates from back-end systems in the cluster. Install a certificate on each cluster web server that uses https (SSL). Note: This procedure is necessary only if the back-end certificate is a self-signed certificate. If the certificate is signed by a third party like Verisign, the import is not needed. Chapter 2: Configuring the Integration 25

26 (Optional) Import CA ehealth Certificates from Back-End Systems to the Front-End System To import CA ehealth certificates from back-end systems to the front-end system 1. Configure CA ehealth to run https on port 443 by executing the following command: nhwebprotocol -mode https-port 443 -hostname <FQDN> 2. Obtain copies of all certificates from $NH_HOME/web/httpd/conf/server.crt. 3. Place these certificates in the $NH_HOME/Jre directory on the front-end system. 4. Open a command shell on the CA ehealth server. 5. Execute the following command: bash' 6. Execute the following command: cd $NH_HOME/Jre 7. Install each certificate by using the following commands: bin/keytool -import -v -keystore lib/security/cacerts -file <certificate_filename> -alias <certificate_alias> -trustcacerts 8. Enter the following password: changeit 9. Restart the entire CA ehealth web server. 26 Integration and User Guide

27 Chapter 3: Using CA Performance Center This section contains the following topics: Configuration Items (see page 27) Types of CA Performance Center Views (see page 31) Edit the Settings for a View (see page 32) CA Performance Center Views That Contain CA ehealth Data (see page 32) Search for Managed Items from a Report Page (see page 43) Configuration Items Configuration items (CIs), also referred to as managed items, are network infrastructure elements monitored by CA ehealth. Synchronization enables CA Performance Center to import CA ehealth data for managed items and render CA ehealth element reports in CA Performance Center. The integration supports these base element types: App Service Backplane CPU DSP Card Disk Disk Partition End-to-end Environment Component Environmental Sensor Facility Devices IP Stats Industrial Component Internet Appliance LAN/WAN Memory Mobile Wireless Mobile Wireless Component Chapter 3: Using CA Performance Center 27

28 Configuration Items Mobile Wireless Device Modem Modem Pool Packet Forward Engine Power/Energy Component Process Process Set QoS Remote Access Server Response Client Set Response Endpoint Response Path Response Path Set Router/Switch System Search for Managed Items CA Performance Center provides the following search options: Search all items Search for specific item types Search for specific items You can search for an item by using the Search field in the CA Performance Center toolbar. Entering partial names or IP addresses opens the Search page filtered to the specified value. You can use the Inventory page when you are not searching for a specific item and want to display a list of managed items. Note: The Inventory tab is visible only if you have administrator rights to data sources and the View Inventory and Search role right. If you do not have administrator rights to a data source, the Inventory tab appears as the Items tab. The Items page does not include data source consoles. 28 Integration and User Guide

29 Configuration Items To search for managed items by using the Search field 1. Enter a search string in the Search field at the top right side of the toolbar. For example, you could type aus to display all configured items and site groups that contain aus. 2. Click the Search icon. 3. Drill down as needed from the higher level views to the detailed views. To search for managed items from the Inventory page 1. Click the Inventory tab. The Inventory page appears. 2. Select one of the following Items: Devices Elements Interfaces The Search page appears. You can set the number of devices, elements, or interfaces to display on each page by selecting a value from the Max Page pull-down list on the bottom right side of the table. 3. Do any of the following: Use the sort function. For Devices, click the column heading Name to alternate between ascending and descending order. For CA ehealth Elements, click the column heading Type to alternate sorting. For Interfaces, click the column heading Interface Name to alternate sorting. Type one of the following in the Search field, and click Search. Name of device, element, or interface The specified device, element, or interface appears. Type of device, element, or interface All devices, elements, or interfaces of the specified type appear. Note: To redisplay all items (per page), delete the value in the Search field and click Search. Chapter 3: Using CA Performance Center 29

30 Configuration Items Create Groups of Managed Items You can create groups of managed items in CA Performance Center to use for organizational purposes. CA Performance Center group-based reports cannot be run on these groups. To run group-based reports in CA Performance Center, you must select a group created and managed in OneClick for ehealth. Note: For more information, see the CA Performance Center documentation. For information about creating groups of elements in CA ehealth before they are synchronized with CA Performance Center, see the CA ehealth Administration Guide or the CA ehealth online help. To create a group in CA Performance Center 1. Click Admin, Groups. The Manage Groups page appears. 2. Click Add Group at the bottom of the left pane. The Add Group dialog opens and the New tab is selected. 3. Specify the following: Group Name Description Options (include children of managed items) Group Type (Custom or Site) 4. Click Save. The new group is saved. It appears in the Groups tree on the Manage Groups page. The group does not contain any configured items, so it cannot be used for reporting. To make the group functional, you must add items or other groups to it. Manage Groups and Elements in CA Performance Center In addition to viewing the log file, you can verify synchronization of the integration by viewing CA ehealth groups and elements in CA Performance Center and manage options. Note: For more information about managing groups and elements (configuration items) in CA Performance Center, see the CA Performance Center documentation. To manage groups and elements in CA ehealth, see the CA ehealth Administration Guide. 30 Integration and User Guide

31 Types of CA Performance Center Views To view groups and elements 1. Log in to CA Performance Center as an administrator. 2. Click Admin, Groups. The Manage Groups page appears. 3. Drill down in the Groups tree to Inventory, Data Sources, ehealth Host Name. 4. Expand the CA ehealth data source to view the available groups in the Groups tree. 5. Select a group. The individual elements in that group appear in the right pane in the Items tab. 6. (Optional) Use the Search field to look for specific elements. 7. (Optional) Click the Properties tab to view the following: Group Name Description Option to include or exclude children of managed items Types of CA Performance Center Views Within CA Performance Center, one or more data views (charts) make up a specific report page. Default context pages shipped with CA Performance Center provide views for the supported base CA ehealth element types. You can also build custom pages for viewing CA ehealth charts. Two types of views are available in CA Performance Center: Summary views typically include data from multiple CIs of the same type (for example: Top-N Interfaces by Utilization). CI-based views display data from one specific CI (for example: an Inbound/Outbound Utilization chart for a specific network interface). In addition to the default hard-coded views, CA ehealth also provides a sample dynamic view for element Trend, group Top N, and device component Top N reports. This view lets you configure various view settings and display other variables on the page without having to wait for a new release. Note: For more information about CA Performance Center views, see the CA Performance Center view-level help. To access the Help topic, click the blue arrow in the top left of the view and select Help. A description of the view opens in a new window. Chapter 3: Using CA Performance Center 31

32 Edit the Settings for a View Edit the Settings for a View In CA Performance Center, a data view is one chart or table on the report page, not the report itself. Each view is associated with settings that you can edit as needed in your current session. For example, to see the data of one device as opposed to another device, you can add identical views to a report and can edit the setting to customize the view for different devices. You can then compare data for two devices in a single report. Note: The Edit option appears in the pull-down menu of a view only if editing is allowed for a view (for example, from the Custom View - ehealth tab). If editing is not enabled for a view, this menu option does not appear in the menu. If a user has role rights to retain shared view edits, the user can choose to apply the changes to their user account or to the current session. User account changes persist through future sessions until the user changes them. To edit the settings for a view 1. Click the gear icon on the right side of the view and select Edit from the pull-down menu. An ehealth Custom Settings dialog opens. 2. Change the settings for the view. The settings vary by element type. 3. Click Save. Your settings are saved and applied to the view. CA Performance Center Views That Contain CA ehealth Data You can use the CA Performance Center interface to view CA ehealth elements after adding the CA ehealth data source and synchronizing CA Performance Center and CA ehealth to share the configuration information. After the synchronization occurs, you can report on CA ehealth elements, devices, interfaces, and groups in CA Performance Center and perform all standard item and group navigation operations. You can also view CA ehealth element data with related element data from other data sources. Each view (chart) has a menu that lets you do the following: Edit the variables shown in the view and apply the changes to your current session (custom views only) Export the view to a CSV file Generate a URL Display view help 32 Integration and User Guide

33 CA Performance Center Views That Contain CA ehealth Data View Element-Based Reports You can view element-based CA ehealth reports from the CA Performance Center interface. The administrator or users with permission can create custom reports for CA ehealth views and drill down to the CA ehealth elements or groups. For example, to view a custom report such as CA ehealth Router Interfaces, you could access a page displaying information about Dallas, click a router to get detailed information about that router, and then click an interface from that page. To search for a specific element, you can use the Search field at the top right side of the CA Performance Center interface. You can also view CA ehealth element-based reports by starting from the Inventory page. If you know what you are searching for, typically the Search feature is faster than going through the Inventory page. The Inventory page is used more for tracking item status. To search for a specific element using the Search field 1. Enter a search string in the Search field at the top right side of the page. For example, you could type aus to display all configured items and site groups that contain aus. 2. Click the Search (magnifying glass) icon. 3. Drill down as needed from the higher level views to the detailed views. To view element-based reports from the Inventory page 1. Click Inventory and select ehealth Elements. A table on the Search page lists CA ehealth elements. 2. Select an ehealth element that is polling successfully from CA ehealth. All the views available for the selected report appear. The Start Date/Time and End Date/Time for the report automatically appear because each view in CA Performance Center has a time range. You can select a different time range from the pull-down list on upper left side of the page. You can also change the time by clicking the arrow buttons to the right of the date and time field. Chapter 3: Using CA Performance Center 33

34 CA Performance Center Views That Contain CA ehealth Data 3. (Optional) Create custom views for the element: a. Click the Custom View - ehealth tab. Several chart types are available for customizing views such as Trend, Gauge, and Pie Charts. b. Click the gear icon to the right of a view and select Edit. An ehealth Custom Settings dialog opens. c. Select variables and modify the settings. Custom Trend: Select as many as 12 variables for Trend reports. You can also change the type chart to be a Trend Chart or a Stacked Chart. Change the Title, Thresholds, Chart Type, Granularity, or ability to display Projection or Threshold lines. Note: The 'Most detailed' granularity captures Fast-Polled. Custom Gauge: Select a variable for the report. You can optionally change the Minimum and Maximum values, as well as the threshold values. You can apply your changes to all tenant users, to the current user, or to the current session. d. Click Save. 4. (Optional) Click the ehealth Polling History tab to view reports on variables such as Availability, Reachability, Missed Polls, and Latency for the element. 34 Integration and User Guide

35 CA Performance Center Views That Contain CA ehealth Data View Device-Based Reports You can view device-based ehealth reports from the CA Performance Center interface. The administrator or users with permission can create custom reports for CA ehealth views and can drill down to the CA ehealth devices or groups. For example, to view a custom report such as CA ehealth Routers, you could access a page displaying information about Tampa, and then click a router to get detailed information about that router. To search for a specific device, you can use the Search field at the top right side of the CA Performance Center interface. You can also view CA ehealth device-based reports by starting from the Inventory page. If you know what you are searching for, typically the Search feature is faster than going through the Inventory page. The Inventory page is used more for tracking item status. To search for a specific device using the Search field 1. Enter a search string in the Search field at the top right side of the page. For example, you could type aus to display all configured items and site groups that contain aus. 2. Click the Search (magnifying glass) icon. 3. Drill down as needed from the higher level views to the detailed views. To view device-based reports from the Inventory page 1. Click Inventory and select Devices. CA ehealth devices are listed in a table on the Search page. 2. Select an ehealth device that is polling successfully from CA ehealth. A page for the selected device appears (for example, Router Pages). Use the arrow button in the tab area to scroll over to view the ehealth System/Router Info tab. Select this tab to view out-of-the-box views for the device. The Start Date/Time and End Date/Time for the report automatically appear because each view in CA Performance Center has a time range. You can select a different time range from the pull-down list on the upper left side of the page. You can also change the time by clicking the arrow buttons to the right of the date and time field. 3. (Optional) Edit the report as follows: a. Click the gear icon to the right of the view and select Edit. The ehealth Custom Settings dialog opens. b. Modify any of the available fields (such as Threshold and Granularity). c. Click Save. You can apply your changes to the account or to the session. Chapter 3: Using CA Performance Center 35

36 CA Performance Center Views That Contain CA ehealth Data 4. (Optional) Create custom views for the device as follows: a. Click the Custom View - ehealth tab. Several chart types are available for customizing views such as Top N, Trend, Gauge, and Pie Charts. b. Click the gear icon to the right of the view and select Edit. The ehealth Custom Settings dialog opens. c. Select a variable (or multiple variables if the view supports them) and modify the other settings as desired. d. Click Save. You can apply your changes to the account or to the session. 36 Integration and User Guide

37 CA Performance Center Views That Contain CA ehealth Data View Interface-Based Reports You can view interface-based ehealth reports from the CA Performance Center interface. The administrator or users with permission can create custom reports for CA ehealth views and drill down to the CA ehealth interfaces or groups. To search for a specific interface, you can use the Search field at the top right side of the CA Performance Center interface. You can also view CA ehealth interface-based reports by starting from the Inventory page. If you know what you are searching for, typically the Search feature is faster than going through the Inventory page. The Inventory page is used more for tracking item status. To search for a specific interface using the Search field 1. Enter a search string in the Search field at the top right side of the page. For example, you could type aus to display all configured items and site groups that contain aus. 2. Click the Search (magnifying glass) icon. 3. Drill down as needed from the higher level views to the detailed views. To view interface-based reports from the Inventory page 1. Click Inventory and select Interfaces. CA ehealth interfaces are listed in a table on the Search page. 2. Select an ehealth interface that is polling successfully from CA ehealth. An Interface Pages view for the selected ehealth interface appears. Select the ehealth Interface Info tab to view out-of-the-box views for the interface. The Start Date/Time and End Date/Time for the report automatically appear because each view in CA Performance Center has a time range. You can select a different time range from the pull-down list on the upper left side of the page. You can also change the time by clicking the arrow buttons to the right of the date and time field. 3. (Optional) Edit the report as follows: a. Click the gear icon to the right of the view and select Edit. b. Modify any of the available fields (such as Threshold and Granularity). c. Click Save. CA Performance Center displays report views showing the element and time frame if data exists for the view. 4. (Optional) Create custom views for the interface as follows: a. Click the Custom View - ehealth tab. Several chart types are available for customizing views such as Trend and Gauge. Chapter 3: Using CA Performance Center 37