Ehealth Installation Enu

CA eHealth
Installation Guide
r6.2.2
This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are 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 used or disclosed by you except as may be permitted in 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 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 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 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, 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 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 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
CA Technologies Product References

This document may reference the following CA products: CA eHealth Performance Manager CA eHealth AdvantEDGE View CA eHealth Application Response CA eHealth Business Service Console (eHealth BSC) CA eHealth Distributed eHealth CA eHealth Fault Manager CA eHealth Live Health Application CA eHealth Response CA eHealth Service Availability CA eHealth SystemEDGE CA eHealth TrapEXPLODER CA eHealth Voice Quality Monitor (VQM) CA eHealth AIM for Apache CA eHealth AIM for Microsoft Exchange CA eHealth AIM for Microsoft IIS CA eHealth AIM for Microsoft SQL Server CA eHealth AIM for Oracle CA Insight AIM for CA eHealth CA Insight Database Performance Monitor for Distributed Databases (CA Insight DPM for Distributed Databases) CA eHealth Integration for Alcatel (eHealth - Alcatel) CA eHealth Integration for Cisco IP Solution Center (eHealth - Cisco ISC) CA eHealth Integration for Cisco WAN Manager (eHealth - Cisco WAN Manager) CA eHealth Integration for HP OpenView (eHealth - OpenView) CA eHealth Integration for Lucent (eHealth - Lucent) CA eHealth Integration for Netcool (eHealth - Netcool) CA eHealth Integration for Nortel Preside (eHealth - Nortel Preside) CA eHealth Integration for Nortel Shasta SCS GGSN (eHealth - Nortel GGSN)
CA eHealth Integration for Psytechnics (eHealth - Psytechnics) CA eHealth Integration for Starent (eHealth - Starent) CA SPECTRUM CA Unicenter Network and Systems Management (Unicenter NSM) CA Embedded Entitlements Manager (CA EEM) Note: CA Embedded Entitlements Manager (CA EEM) is the new name for eTrust Identity and Access Management (eTrust IAM).
Contact CA Technologies
Contact CA Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following: 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
Provide Feedback If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at http://ca.com/docs.
Contents
Chapter 1: Overview 9
About This Guide .............................................................................. 9 Audience ...................................................................................... 9
Chapter 2: Preparing for Installations and Upgrades
11
Installation Guidelines and Prerequisites ....................................................... 11 CA Insight Licensing ...................................................................... 11 Installation Guidelines..................................................................... 12 Installation Prerequisites .................................................................. 16 Upgrade Guidelines and Prerequisites .......................................................... 18 Upgrade Guidelines ....................................................................... 18 Upgrade Prerequisites ..................................................................... 21 Data Loss and Downtime .................................................................. 23 Merging Groups and Group Lists ........................................................... 24 Required Software for eHealth r6.2.2 .......................................................... 26 Extract the InstallPlus Program ............................................................ 26 Extract the Oracle Update Software ........................................................ 29 IPv6 Configuration Prerequisites ............................................................... 31 IPv6 Support and Limitations .................................................................. 31
Chapter 3: Installing eHealth (Windows)
33
eHealth Installation ........................................................................... 33 eHealth Installation Package ............................................................... 34 System Security .......................................................................... 34 Copy the DVDs to a Disk .................................................................. 35 Oracle 10g Software DVD ................................................................. 35 Start the eHealth Installation .................................................................. 35 Additional Tasks .......................................................................... 39 How to Activate a New TrapEXPLODER Configuration File .................................... 40 Start eHealth ................................................................................. 40 Add eHealth Licenses ......................................................................... 41 Install Report Center After eHealth is Installed ................................................. 42 Where to Go from Here ....................................................................... 42
Chapter 4: Installing eHealth (UNIX)
45
eHealth Installation ........................................................................... 45
Contents 5
eHealth Installation Package ............................................................... 46 System Security .......................................................................... 47 Guidelines for Installation from DVD ....................................................... 47 DVD-ROM Device Requirements ........................................................... 47 Copy the DVDs to a Disk .................................................................. 48 Mount an ISO Image on a Solaris System .................................................. 49 How to Configure Resource Limits on Solaris ................................................ 51 Start the eHealth Installation .................................................................. 52 Additional Tasks .......................................................................... 57 How to Activate a New TrapEXPLODER Configuration File .................................... 58 Start eHealth and Add eHealth Licenses ........................................................ 58 Install Report Center Manually After eHealth Is Installed ........................................ 60 Where to Go from Here ....................................................................... 61
Chapter 5: Upgrading eHealth (Windows)
63
eHealth Upgrade ............................................................................. 63 Copy the contents of the DVDs ............................................................ 64 eHealth Software Package ................................................................. 64 Start the eHealth Upgrade ................................................................. 65 Additional Tasks .............................................................................. 67 Activate a Distributed eHealth Cluster ...................................................... 67 Finalize Upgrade .......................................................................... 69 Cleanup Tasks ............................................................................ 70
Chapter 6: Upgrading eHealth (UNIX)
73
eHealth Upgrade ............................................................................. 73 eHealth Software Package ................................................................. 74 Start the eHealth Upgrade ................................................................. 74 Additional Tasks .............................................................................. 77 Activate a Distributed eHealth Cluster ...................................................... 77 Finalize Upgrade .......................................................................... 79 Cleanup Tasks ............................................................................ 80
Appendix A: Administration Tasks Reference
83
Tasks to Perform Before You Install or Upgrade eHealth ......................................... 83 Check the File System Format (Windows) .................................................. 83 Change the eHealth System Hostname (Windows) .......................................... 84 Add Swap Space (Windows and UNIX) ..................................................... 84 Check and Modify Kernel Requirements (UNIX) ............................................. 87 Mount the DVD Drive (UNIX) .............................................................. 93 Unmount the DVD Drive (UNIX) ........................................................... 98
6 Installation Guide
Tasks to Perform After You Install or Upgrade eHealth .......................................... 98 Specify the Mail Server (Windows) ......................................................... 99 Specify the Printer (Windows) ............................................................ 100 Change the Web Server Port Number (Windows and UNIX) ................................. 101 Enable the FtpCollector to Run on Solaris 5.9 and Solaris 10 ................................ 103 Authentication Options ................................................................... 104
Appendix B: Troubleshooting
117
Troubleshoot Installation Problems ........................................................... 117 Installation Program Exits before Completion .............................................. 117 Database Creation Is Incomplete ......................................................... 117 TrapEXPLODER Unable to Start ........................................................... 119 Windows Could Not Start the eHealth httpd61 on Local Computer ........................... 120 eHealth Console Fails to Start after Installation ............................................ 121 Insufficient Accessible Stack Size During Installations on HP-UX ............................ 122 Troubleshoot Upgrade Problems .............................................................. 124 System Does Not Meet Minimum Requirements ............................................ 124 Installation Program Exits During Activation ............................................... 124 One or More Kernel Parameters Are Not Configured Properly ................................ 125 Restore Oracle On Cluster Members ....................................................... 125 eHealth Upgrade to r6.2.2 Unsuccessful on a Cluster Member ............................... 126 Restore eHealth r5.7.9 or r6.0 on the Local System ........................................ 128 Restore eHealth r5.7 or r6.0 Across the Cluster ............................................ 131
Appendix C: Removing eHealth and Related Applications
135
Before You Remove eHealth .................................................................. 135 Files and Directories Backup .............................................................. 135 Windows Registry Backup (Windows Only) ................................................. 136 Directory Confirmation (UNIX Only) ....................................................... 136 Remove eHealth r6.2.2 ...................................................................... 137 Remove eHealth on a Windows System.................................................... 138 Remove Registry Entries and Perform Cleanup Tasks ....................................... 140 Remove eHealth on a UNIX System ....................................................... 143 Remove eHealth r5.7.9 or r6.0 ............................................................... 148 Remove eHealth r5.7.9 or r6.0 (Windows) ................................................. 149 Remove eHealth r5.7.9 or r6.0 (UNIX) .................................................... 150 Remove Report Center ....................................................................... 150 Remove Report Center from eHealth r6.0 Systems ......................................... 151 Disable Report Center on eHealth r6.2.2 Systems .......................................... 152 Remove Report Center from eHealth r6.2.2 Systems ....................................... 152
Contents 7
Index
155
Chapter 1: Overview
About This Guide
This guide describes how to do the following: Check and prepare your system for eHealth installation Install eHealth on Windows, Solaris, and HP-UX systems Upgrade eHealth on Windows, Solaris, and HP-UX systems Remove eHealth, Oracle, and third-party applications Troubleshoot installation and database creation problems
Audience
This guide is intended for eHealth administrators who are responsible for installing, starting, and licensing eHealth. To configure response elements, you must have administrative permissions for the eHealth console. To configure and manage your AR agents, you must have administrative permissions for the eHealth Web user interface.
Chapter 1: Overview 9
Chapter 2: Preparing for Installations and Upgrades

Before you install eHealth r6.2.2 or upgrade to r6.2.2 from eHealth r5.7.9, r6.0, or r6.1, read the guidelines and perform any necessary procedures in this chapter. This section contains the following topics: Installation Guidelines and Prerequisites (see page 11) Upgrade Guidelines and Prerequisites (see page 18) Required Software for eHealth r6.2.2 (see page 26) IPv6 Configuration Prerequisites (see page 31) IPv6 Support and Limitations (see page 31)
Installation Guidelines and Prerequisites

This section includes eHealth installation guidelines, prerequisites, and other information you need to know when planning an eHealth installation in your infrastructure. You can install eHealth on the following system types: Standard eHealth eHealth Traffic Accountant Distributed eHealth (back-end/polling system) Distributed eHealth (front-end/reporting system)
CA Insight Licensing
CA eHealth Performance Manager customers are eligible for one license of CA Insight Database Performance Monitor for Distributed Databases exclusively for self-monitoring of their CA eHealth embedded database(s). This license cannot be used to monitor non-eHealth embedded databases. You can download CA Insight Database Performance Monitor for Distributed Databases software from CA Support Online, http://ca.com/support. You can request a license key for CA Insight Database Performance Monitor for Distributed Databases from CA Total License Care, http://www.ca.com/us/servicecenter, under Licensing. Customers who want to deploy CA Insight Database Performance Monitor for Distributed Databases to monitor databases other than the CA eHealth Performance Manager embedded database can purchase additional licenses by contacting their CA sales representative.
Chapter 2: Preparing for Installations and Upgrades 11
Installation Guidelines
To avoid problems during the eHealth installation, follow these guidelines: Install eHealth on a separate, dedicated system. eHealth should not be installed on a system that has another enterprise class application installed, such as CA Spectrum. Stop the Windows Firewall/Internet Connection Sharing (ICS) service before installing eHealth to avoid failure of the NuTCRACKER installation. The creation and maintenance of time-aligned data will become an integral part of eHealth. It is estimated that the database will grow by 30 to 40% to support this new data. CA recommends that you use the Sizing Wizard at http://support.ca.com to get a more precise estimation of the impact on your database. During the regularization backfill process we anticipate increased system resource utilization including but not limited to: Increased CPU activity Increased memory usage Increased disk I/O
Note: For information about how to regulate backfill, contact Technical Support. When choosing the eHealth administrator account, do not use the main administrators account. Use a specific account for tightly controlled administration purposes only. Using a general, enterprise-wide account results in more unauthorized users accessing eHealth databases. If SystemEdge 4.3 has been applied, it must be shut down prior to installing eHealth. (Windows) Do not install eHealth on a system used as a domain controller.
(Windows) Before installing eHealth, stop and exit any unnecessary applications running on your system. The following CA services must be stopped if they are installed on your system: CA DAI Server CA DSM r11 Common Application Framework CA Message Queuing Server CA Pest Patrol Realtime Protection Service CA Unicenter NSM Systems Performance Agent for UAM
Also, disable all antivirus programs running on your system. You cannot install eHealth on a system that has McAfee 8.0 or PowerShell installed. Note: For a full list of services that must be stopped, see the eHealth Readme. If you do not stop these services before installing eHealth, the installation will fail. (UNIX) If you plan to configure your eHealth environment to be highly available, you must install third-party clusterware before you install eHealth. Note: See the eHealth High Availability and Disaster Recovery Administration Guide for more information about how eHealth integrates with high availability clusterware. (UNIX) Verify that you have the root user password for the target eHealth system. (UNIX) Determine that your system meets the minimum requirements for installing eHealth r6.2.2 by running the prerequisite checker program before installing eHealth. This lets you make any recommended adjustments and updates to your system before you run the eHealth installation program. To start the prerequisite check, insert the eHealth Software DVD. Log on as root and run the nhCheckInstallPreReqs command. If you do not run this check before installing eHealth, you will be alerted to system adjustments and updates during the eHealth installation process.
(UNIX) Before installing eHealth, you may have to mount the DVD drive. You may also want to copy the contents of the DVDs to a disk if the eHealth system does not have a local DVD drive, or if you want to avoid changing DVDs during installation. Note: For instructions on these and other operating system tasks, see Installing eHealth (UNIX) and Administration Tasks Reference.
eHealth r6.2.2 requires the March 24, 2010, or later Oracle 10.2.0.4 Out-of-Band (OOB) update. If you are patching a previous version of CA eHealth Without Database, you must manually install Oracle 10.2.0.4 and the following patches: Solaris 5932196, 64-bit Solaris 6674549, 64-bit Solaris 9119226, 64-bit Solaris Windows 9303471
Software/Database Location Guidelines

When choosing locations for the eHealth software, Oracle software, and Oracle database, follow these guidelines: You can create a layout configuration file (LCF) that allows you to specify where to place the database files. Note: Use the eHealth Sizing Wizard to create the LCF. See the eHealth Administration Guide for more information. Specify local disks or disk partitions as locations for the eHealth database files. If you plan to use more than nine locations for the eHealth database, you must use the eHealth sizing wizard to create an LCF for input to the eHealth installation program. Specify top-level directories or subdirectories, such as D:\ehealth61 or D:\oracle\product\ora10. Do not specify a root directory. If you are applying eHealth r6.2.2 to eHealth without the Oracle database, note the following: eHealth and Oracle must reside on the same system. The Oracle path cannot contain spaces. The installation process does not prompt for the destination location of Oracle. Instead, it prompts for the existing location of the Oracle software, which must already be installed.
Specify network drives that provide high bandwidth and low latency. For best performance, consider using storage area networks (SANs) over Fibre Channel or Gigabit Ethernet networks. However, SAN environments are not tested, therefore, support is limited. If you experience a problem related to the SAN, you may need to install on local disks until you can resolve the issue. (Windows) Do not specify file locations and installation directories by using the Universal Naming Convention (UNC). Instead, use a mapped drive. Note: CA neither tests on nor recommends the use of network-attached storage (NAS) technology to host any eHealth components.
Report Center Guidelines

When you install eHealth you have the option to install Report Center, a reporting system that enables you to create and run custom reports for eHealth elements. Read these guidelines before you install Report Center: You can install Report Center on Traffic Accountant systems. Report Center can be installed for use with either a standard eHealth system or a Traffic Accountant system, but not both. Although you can install Report Center on Solaris and HP-UX eHealth systems, users must log in to their eHealth web user accounts from Windows client systems to access Report Center. Running Report Center in a Distributed eHealth environment is not supported. You can install Report Center on Distributed eHealth (back-end) Systems, but you cannot install or use Report Center on Distributed eHealth Consoles (front-end).
Note: For more information about Report Center, see the eHealth Report Center User and Administration Guide.
How to Install VMware (Windows)

You can install eHealth on VMware. The following steps outline this process: 1. Configure VMware. 2. Create virtual machines. 3. Install the operating system on the newly created virtual machines. 4. Install eHealth. Note: For information about system requirements, see the eHealth Release Notes.
Installation Prerequisites
Read the following information to help ensure that you properly prepare the system on which you plan to install eHealth.
How to Determine Your System Resources

Use the following information to evaluate your system resources: If you plan to poll a large number of elements (approximately 50,000 or more), Report Center can cause the temporary space to grow up to 24 GB. The default temp space for eHealth systems is 7 GB. You must verify that the Oracle database tablespace NH_TEMP resides on a disk that has sufficient space for it to grow before installing Report Center. When upgrading, you can use the eHealth Sizing Wizard to size your system, but any LCF files that are generated can only be used for new installations. Time-aligned (regularized) statistics data is used by eHealth for custom reports and the Live Reporting feature. eHealth time-aligns data samples to help ensure consistent and efficient reporting. The data is stored in four tablespaces within the eHealth database. Typically, the additional disk space required for time-aligned data is 50 percent of the current statistics tablespace size. For planning purposes, use the sizing wizard to obtain disk planning information. If the disk locations where your current eHealth statistics database resides have enough free space to hold twice the current tablespace sizes, you should have enough disk space. If the locations do not have enough free space, you can use the nhManageDbSpace command to add more data files to increase the tablespace sizes, as well as move tablespaces to larger disk locations. Note: As of this release, time-aligned statistics data is now created during all eHealth installations, not just Report Center. Additional disk space is required for all eHealth installations. For details on freeing up space, see the eHealth Administration Guide. (UNIX) Before installing eHealth, run the prerequisite checker program to determine if your system meets the minimum requirements for installing eHealth r6.2.2. This allows you to make any recommended adjustments and updates to your system without interrupting the eHealth installation program. To start the prerequisite check 1. Insert the eHealth Software DVD. 2. Log on as root and type the following command:
nhCheckInstallPreReqs
Note: If you do not run this check before installing eHealth, you will be alerted to system adjustments and updates during the eHealth installation process.
How to Prepare for the eHealth Installation

Follow these guidelines to prepare for the eHealth installation: Remove any existing versions of Oracle if you are installing the Oracle database version shipped with eHealth. Use the commands and tools provided with eHealth to install and manage the Oracle database software. If you are applying eHealth r6.2.2 to eHealth without the Oracle database, Oracle and the required Oracle patches must be installed before you start the eHealth installation. Create hostnames by using characters such as AZ, az, 09, and dashes (). Hostnames cannot contain characters such as spaces, periods (.), and underscores (_). Verify that the Simple Network Management Protocol (SNMP) service is configured to support the community string public and to receive SNMP packets. Identify the locations where you plan to install the eHealth and Oracle software, and eHealth database files. (Windows) Create an ORA_DBA user group on the system. Note: For more information, see your Windows documentation. (Windows) Create an eHealth administrator account and add it as a member of the Administrators and ORA_DBA groups. Use the following guidelines when creating the account: It can contain lowercase letters and digits. Uppercase or mixed-case letters are not supported. The first character cannot be a digit. It can belong to a Windows 2003 Active Directory domain.
Upgrade Guidelines and Prerequisites
(UNIX) Create a specific administrator account that you can use for eHealth. You cannot use the root account as the eHealth administrator. Use the following guidelines when creating an administrator account: It can contain lowercase letters and digits. Uppercase or mixed-case letters are not supported. The first character cannot be a digit. The account must not use the eHealth installation directory as its home directory. Create the eHealth administrator account as a local user account (not an enterprise-wide account) to insulate eHealth and its data from other corporate activities and to limit dependencies on external machines (such as NIS/NIS+ servers). Do not set hard or soft resource limits (ulimits) for the eHealth administrator account. Do not place the eHealth administrator account home directory on a remote system. If you do so, the loss of a connection could disrupt the eHealth system.
(UNIX) To use diacritical characters on Solaris, you must set up a locale on the Solaris system that has the right character set. For US, this is locale en_us and character set Latin1.

This section includes eHealth upgrade guidelines, prerequisites, and other information you need to know when planning to upgrade eHealth, Oracle, and related applications.
Upgrade Guidelines
To avoid problems during the eHealth upgrade, follow these guidelines: Confirm that the current release of eHealth is polling and running reports without errors. You cannot use a layout configuration file (LCF) to move tablespaces and data files or otherwise manipulate the eHealth database during the upgrade process. For more information, see the eHealth Administration Guide. (Windows) Before upgrading eHealth, disable all antivirus programs running on your system. Re-enable the programs only after the upgrade has finished. eHealth will not operate on a system that has McAfee 8.0 installed. (UNIX) Confirm the root user password for the target eHealth system.
(UNIX) Before installing eHealth, run the prerequisite checker program to determine if your system meets the minimum requirements for installing eHealth r6.2.2. This step lets you make any recommended adjustments and updates to your system without interrupting the eHealth installation program. To upgrade eHealth r6.1 to r6.2.2, you must first install certification D03 and then use the eHealth r6.2.2 service pack installer to perform the upgrade. To start the prerequisite check 1. Insert the eHealth Software DVD. 2. Log on as root and type the following command:
Note: If you do not run this check before installing eHealth, you will be alerted to system adjustments and updates during the eHealth installation process.
Software Location Guidelines

When choosing locations for the eHealth software, Oracle software, and Oracle database, follow these guidelines: Specify local disks or disk partitions as locations for the eHealth database files. Specify top-level directories or subdirectories, such as D:\ehealth61 or D:\oracle\product\ora10. Do not specify a root directory. Specify network drives that provide high bandwidth and low latency. For best performance, consider using storage area networks (SANs) over Fibre Channel or Gigabit Ethernet networks. However, SAN environments are not tested, so support is limited. If you experience a problem related to the SAN, you may need to install on local disks until you can resolve the issue. (Windows) Do not specify file locations and installation directories by using the Universal Naming Convention (UNC). Instead, use a mapped drive.
Note: CA neither tests on nor recommends the use of network-attached storage (NAS) technology to host any eHealth components.
Report Center Guidelines

When you upgrade eHealth you have the option to install Report Center. Report Center is a reporting system that enables you to create and run custom reports for eHealth elements. If Report Center is already installed on your system, it will be upgraded along with eHealth, Oracle, and other related applications. Review these guidelines before you install Report Center: You can install Report Center on Traffic Accountant systems. Report Center can be installed for use with either a standard eHealth system or a Traffic Accountant system, but not both. If you are upgrading from an eHealth r6.0 Traffic Accountant system, you can choose to install Report Center r6.2.2. However, note the following: If your eHealth r6.0 Traffic Accountant system uses no base eHealth statistical elements and you upgrade to eHealth r6.2.2, the Report Center installation deploys the new eHealth r6.2.2 Traffic Accountant reports. If your eHealth r6.0 system uses statistics elements, Traffic Accountant data (some base eHealth statistical elements included), or both, the Report Center r6.2.2 installation deploys the base eHealth r6.2.2 Report Center statistical reports.
If you are upgrading from an r6.0 eHealth system (including a system using one or more Traffic Accountant components) with Report Center currently installed, the upgrade deploys the base eHealth r6.2.2 Report Center statistical reports. Although you can install Report Center on Solaris and HP-UX eHealth systems, users must log in to their eHealth web user accounts from Windows client systems to access Report Center. You can install Report Center on Distributed eHealth (back-end) Systems, but you cannot install or use Report Center on Distributed eHealth Consoles (front-end).
Note: For more information about Report Center, see the eHealth Report Center User and Administration Guide.
Remote Poller Site Upgrade Guidelines

Follow these guidelines for upgrading remote poller sites: If your sites are running a version of eHealth earlier than r5.6.5 Patch 3, update to eHealth r5.6.5 Patch 8, upgrade to eHealth r5.7.9 or r6.0, and then upgrade to eHealth r6.2.2. If you are running eHealth r5.0.2, you must migrate to eHealth r5.7.9 before upgrading to eHealth r6.2.2.
When you re-enable a remote polling site after an upgrade, and you use $NH_HOME_NEW/modules/remotePoller/spool (the default) as the location for new statistics and configuration output files, you must also update the FTP home directory to the new location, otherwise data will not get imported from the remote polling site. Note: For more information about configuring FTP connections, see the eHealth Remote Poller User Guide.
Upgrade the central site before you upgrade the remote poller sites. Because remote polling is backwards compatible, upgrading the central site first allows polling to continue from the remote sites that have not yet upgraded.
Use the following process when upgrading remote poller sites to eHealth r6.2.2: 1. Run the nhShowUpgradeChanges command on the central site to identify any group or group list configuration problems. You must resolve those problems before you upgrade. 2. Disable import polling from the remote sites on the central site. 3. Upgrade the central site to eHealth r6.2.2. 4. Enable import remote polling on the central site. 5. Disable one remote site at a time, upgrade the site to eHealth r6.2.2, and then re-enable the site. This step helps ensure that all but one site is enabled at a time.
Upgrade Prerequisites
Review the following information to make sure that you properly prepare the system on which you plan to upgrade eHealth.
How to Determine Your System Resources

Use the following information to evaluate your system resources: If you plan to poll a large number of elements (approximately 50,000 or more), Report Center can cause the temporary space to grow up to 24 GB. The default temp space for eHealth systems is 7 GB. You must verify that the Oracle database tablespace NH_TEMP resides on a disk that has sufficient space for it to grow before installing Report Center. When upgrading, you can use the eHealth Sizing Wizard to size your system, but any LCF files that are generated can only be used for new installations. Time-aligned (regularized) statistics data is used by eHealth for custom reports and the Live Reporting feature. eHealth time-aligns data samples to help ensure consistent and efficient reporting. The data is stored in four tablespaces within the eHealth database.
Typically, the additional disk space required for time-aligned data is 50 percent of the current statistics tablespace size. For planning purposes, use the sizing wizard to obtain disk planning information. If the disk locations where your current eHealth statistics database resides have enough free space to hold twice the current tablespace sizes, you should have enough disk space. If the locations do not have enough free space, you can use the nhManageDbSpace command to add more data files to increase the tablespace sizes, as well as move tablespaces to larger disk locations. Note: As of this release, time-aligned statistics data is now created during all eHealth installations, not just Report Center. Additional disk space is required for all eHealth installations. For details on freeing up space, see the eHealth Administration Guide.
(UNIX) Before installing eHealth, run the prerequisite checker program to determine if your system meets the minimum requirements for installing eHealth r6.2.2. This allows you to make any recommended adjustments and updates to your system without interrupting the eHealth installation program. To start the prerequisite check 1. Insert the eHealth Software DVD. 2. Log on as root and type the following command:
Note: If you do not run this check before installing eHealth, you will be alerted to system adjustments and updates during the eHealth install process.
How to Prepare for the eHealth Upgrade

Follow these guidelines to prepare for the eHealth upgrade: Identify a disk with at least 2 GB of free disk space for the eHealth r6.2.2 software. Update your eHealth elements and the poller configuration by rediscovering. Resolve any errors. If you are running any nhConfig jobs that import configuration information for eHealth integration modules, disable those jobs before upgrading. Back up the eHealth database.
Data Loss and Downtime

Data loss Data loss refers to the time period when eHealth is not polling elements. Downtime Downtime refers to the time period when users are unable to access the eHealth console, the eHealth web user interface, Report Center, or OneClick for eHealth and cannot run scheduled reports.
Standard eHealth Upgrades

In a typical eHealth environment (monitoring 50,000 elements or less), the data loss and downtime will be: Data loss: Minimal loss of statistical data during the eHealth upgrade process. (Traffic Accountant customers may see a gap in conversation data of two to three hours.) Downtime: One or more hours depending on the size of your database.
Note: On both stand-alone eHealth systems and systems that are part of a Distributed eHealth Cluster, the eHealth statistics poller is used to collect data during the eHealth upgrade. This process helps minimize data loss during the upgrade process.
Remote Polling and Distributed Upgrades

In a typical eHealth remote polling environment, you will encounter up to 30 minutes of data loss on each remote site during the activation of eHealth r6.2.2, in addition to the data loss that occurs during the eHealth upgrade process. The central site will also show these slight data gaps in reports. If you are upgrading to eHealth r6.2.2 in a Distributed eHealth environment, note the following: Upgrade all systems in the cluster before you activate eHealth. The cluster system might experience more than 30 minutes of data loss and approximately 1 hour or more of server downtime because of the Oracle upgrade. The actual times depend on the size and speed of your system. During this time, the cluster member being upgraded will be unavailable.
Merging Groups and Group Lists

Groups of elements are used for many purposes in eHealth, including reporting, security, and assigning Live Health profiles. In releases of eHealth before r5.7, groups had specific types, where a group of a certain type could only contain elements of that type. For example, a LAN/WAN group included Ethernet and WAN link elements, and a Router group included router and switch elements. As of eHealth r6.0, groups are universal. You can place elements of any type into the same group. This feature helps ease group maintenance.
Security
If you upgrade to eHealth r6.2.2 from eHealth r5.7.9, all groups with the same name, regardless of type, are merged into one group during the database conversion process. Also, group lists with the same name are merged into one list. Therefore, eHealth users who are only allowed access to certain technology-specific groups may be able to view and report on other groups and elements. For example, assume that you have three groups named Boston: a LAN/WAN group, a Router group, and a Server group. Mary is allowed to see only the group Boston-LAN/WAN, and Joe is allowed to see only the group Boston-Server. The administrator has access to all three. During the upgrade, eHealth merges them into one group, Boston, which both Joe and Mary will be able to view. This situation could potentially cause a problem if Joe does not have rights to view servers and Mary does not have rights to view LAN/WAN elements. To avoid the group merge, rename the groups to have unique names before you upgrade.
Conversion Check
Before you upgrade to eHealth r6.2.2 from r5.7.9, run a conversion check to generate a report which includes the following information: A warning about security changes due to merging Anticipated group and group list changes A summary of the groups and group lists that cannot be merged on a central site because of remote polling restrictions
After viewing this report and its recommendations, decide which groups and group lists need to be renamed uniquely. For example, you may want to rename them to avoid security breaches and to keep groups of different types unique for purposes of reporting or organization.
Run the Conversion Check To run the conversion check on a central site of a remote polling environment, insert the eHealth installation media and run the following command as the eHealth user:
nhShowUpgradeChanges
The eHealth upgrade process also runs this command to identify possible security impacts and configuration conflicts. When security impacts are found, the conversion software displays a warning, creates a log, and asks you if you want to continue. Note: As part of the database conversion, existing reports, scheduled reports, drill-downs, and web security references will also be updated.
Merged Groups and Group Lists on Remote Pollers

In the eHealth Remote Polling environment, when you upgrade each remote polling site, eHealth merges the groups and group lists that have the same name and were created on that polling site. To avoid the merge, you should rename the groups and group lists before you upgrade. When you upgrade a central site, any groups that were created on remote sites and imported to the central site could cause the upgrade to fail if those groups contain elements managed by more than one eHealth system. If you are unable to upgrade a central site due to errors with group membership and merges, contact Technical Support.
Required Software for eHealth r6.2.2

For eHealth r6.2.2, you need the eHealth r6.1 software, the eHealth r6.2.2 InstallPlus software, the Oracle 10g software, and the Oracle 10.2.0.4 Update software. You can either download this software from CA Support Online or obtain the software from DVD. For information about installing software from DVD, see the chapter Installing eHealth (UNIX) (see page 45). InstallPlus is the eHealth program that reduces downtime by installing all of the latest fixes and certifications in one procedure. To help ensure that you install the latest available software when you install eHealth, you must use InstallPlus. If you are downloading software from CA Support Online, do the following: Download the CA eHealth Performance Manager r6.2.2 ISO file, which contains the InstallPlus software. Download the CA eHealth Performance Manager for r6.1 ISO file, which contains the eHealth software. Download CA eHealth Performance Manager r6.1 (Oracle 10g) ISO image, which contains the Oracle 10g software. Download the CA eHealth Performance Manager r6.2 SP02 (Oracle 10.2.0.4 Patch) ISO image, which contains the Oracle Update software.
Extract the InstallPlus Program

The InstallPlus program performs the following tasks: Saves the latest installation files in a directory on the eHealth system. Prompts you for the location of the eHealth software. Installs the eHealth software plus the service packs and certification updates available for this release.
Note: InstallPlus does not replace the standard service pack installation program. Use InstallPlus only when you install an eHealth release for the first time, or when you upgrade from a previous eHealth release. After you have installed an eHealth release, continue to use the service pack installation program to install service packs for later service pack releases.
To extract the InstallPlus program from CA Support Online 1. Choose Products under Search Downloads on the Download Center page. 2. Make sure the All Products radio button is selected under Select a Product and then select 'CA eHealth Console Multiplatform' from the pull-down list. You may see more than one of these options, but just select one. 3. Select 6.2 under Select a Release. 4. Select SP02 under Select a Gen Level. 5. Click the Go button. The ISOs are listed. 6. Download the ISO images. For a r6.2.2 Windows installation, download the following: CA eHealth Performance Manager 6.2 SP02 for Windows - Download Only (contains the InstallPlus software) CA eHealth Performance Manager for Windows r6.1 DVD 1 of 2 (contains the eHealth software) CA eHealth Performance Manager for Windows r6.1 (Oracle 10g) DVD 2 of 2 (contains the Oracle software) CA eHealth Performance Manager 6.2 SP02 for Windows (Oracle 10.2.0.4 patch) DVD 2 of 2 (contains the Oracle Update software)
For a r6.2.2 Solaris installation, download the following: CA eHealth Performance Manager 6.2 SP02 for Solaris - Download Only (contains the InstallPlus software) CA eHealth Performance Manager r6.1 for Solaris DVD 1 of 2 (contains the eHealth software) CA eHealth Performance Manager r6.1 for Solaris (Oracle 10g) DVD 2 of 2 (contains the Oracle software) CA eHealth Performance Manager 6.2 SP02 for Solaris (Oracle 10.2.0.4 patch) DVD 2 of 2 (contains the Oracle Update software)
For a r6.2.2 HP installation, download the following: CA eHealth Performance Manager 6.2 SP02 for HP-UX DVD 1 of 2 Download Only (contains the InstallPlus software) CA eHealth Performance Manager 6.1 SP02 for HP-UX Re-Master DVD 1 of 2 (contains the eHealth software) CA eHealth Performance Manager 6.1 SP02 for HP-UX Re-Master (Oracle) DVD 2 of 2 (contains the Oracle software) CA eHealth Performance Manager 6.2 SP02 for HP-UX (Oracle 10.2.0.4 Patch) DVD 2 of 2 (contains the Oracle Update software)
7. Mount the CA eHealth Performance Manager r6.2.2 ISO file and copy the InstallPlus program to a new, empty directory. Confirm that you have at least the following disk space available for the InstallPlus software: Windows: 350 MB Solaris: 1100 MB HP-UX: 800 MB
Note: For the InstallPlus program to work correctly, the file must be saved in a new directory. 8. Extract the InstallPlus file by doing the following, depending on your platform: Windows: Double-click the LAN_release_WIN_splevel_PLUS.exe file to extract the InstallPlus files into the current working directory. LAN Represents the supported language, either English (ENU), French (FRA), or Japanese (JPN) release Represents the release number, such as 601 for eHealth r6.1. splevel Represents the service pack release level. The InstallPlus program files are extracted into the current directory. During the eHealth installation you will be prompted to navigate to this directory to start the eHealth installation.
UNIX: a. b. Log on as root and change to the new directory. Enter the following command to make the file executable:
chmod +x LAN_release_UNIX_splevel_PLUS.sh
LAN Represents the supported language; either English (ENU), French (FRA), or Japanese (JPN). release Represents the release number, such as 610 for eHealth r6.1. UNIX Represents SOL for Solaris or HPX for HP-UX. splevel Represents the service pack release level, such as 01. c. Run the following command to extract the InstallPlus files into the current working directory:
./LAN_release_UNIX_splevel_PLUS.sh
The InstallPlus program files are extracted into the current directory. During the eHealth installation you will be prompted to navigate to this directory to start the eHealth installation.
Extract the Oracle Update Software

The Oracle Update software contains security patches and other fixes for the eHealth database software. The Release Notes document includes a list of services that must be stopped on Windows target systems to help ensure that the Oracle software is updated successfully.
To extract the Oracle Update software 1. Mount the CA eHealth Performance Manager r6.2 SP02 ISO image and copy the Oracle Update zip file locally to a new, empty directory. Note: On Windows systems, do not use a directory path that contains spaces such as C:\Documents and Settings\All Users\eHealthInstall, or the Windows Desktop. The file is saved to a new directory. 2. Do one of the following, depending on your platform: Windows Double-click the ORA_WIN_VER.zip file to extract the Oracle Update patch set file into the current working directory. VER Represents the database release patch level, such as 10.2.0.3. UNIX a. b. Log on as root and change to the new directory. Run the following command to extract the Oracle Update patch set file into the current working directory:
Note: The eHealth installation must finish before you run this command.
/opt/eHealth/bin/sys/nhiUnZip ORA_platform_VER.zip
platform Represents SOL for Solaris or HPX for HP-UX. VER Represents the database release patch level, such as 10.2.0.3. The Oracle Update software file is extracted into the current directory.
IPv6 Configuration Prerequisites
IPv6 Configuration Prerequisites

The network that eHealth resides on must be capable of routing both IPv4 and IPv6 addressed packets. Host name and address lookup must be configured to support both IPv4 lookups (hosts) and IPv6 lookups (ipnodes). The host system that eHealth resides on must be configured to support IPv6. The host system must have a routable IPv6 address. IPv6 technology allows for non-routable addresses, but these will not work with eHealth outside of a simple hub the system might be connected to. The Operating Systems supported by eHealth have differing amounts of additional pre-installation setup needs, as follows: Solaris 9 and 10 and HP-UX require no additional configuration. Windows 2003 (either R1 or R2; either standard or enterprise) must have at least SP1 (SP2 is recommended). The design of IPv6 support on Windows requires that IPv6 be specifically enabled with the Windows NETSH command. A routable IPv6 address must also be added, either with this command or automatically by router assignment.
IPv6 Support and Limitations

The following eHealth support is available with IPv6: All of the basic behavior of eHealth supports IPv6. You can discover, poll, record statistics for and report on elements of agents on devices with IPv6 addresses. Systems running eHealth in cluster mode can have either IPv4 or IPv6 addresses as long as IPv4 and IPv6 subnets are reachable from each other. The Apache Web server for eHealth supports IPv6 as long as the Web browser also supports IPv6. Any Firefox browser and Internet Explorer 7 (IE7) support IPv6, while IE6 does not. The eHealth Trap Server supports IPv6 addresses as trap destinations and in variable bindings by using SNMPv1 and SNMPv2c respectively. This approach is done by overloading the ASN.1 IP address primitive with an IPv6 address. This non-standard approach is also being used by Cisco in SNMPv1. All the eHealth Live clients (Exceptions, Status and Trend) support IPv6. The new eHealth Traffic Accountant module with the eHealth NetFlow NMS supports IPv6 addresses as data. As this is an integration module it does have a limitation as described below. All the eHealth peripheral products (such as eHealth SystemEDGE and eHealth Trap Exploder) support IPv6.
IPv6 Support and Limitations
The eHealth Application Response controller (and all eHealth servers) support IPv6. There is a limitation for eHealth Application Response. Internal communications between eHealth processes gives priority to IPv6 addresses over IPv4. This approach does not apply where a user provides an IPv4 address as in discovery. All user supplied addresses are always given priority.
Limitations of IPv6 support in eHealth include the following: IPv6 will not function correctly on an eHealth host that has no IPv4 connectivity. eHealth r6.2.2 requires a dual addressed system with at least one of each of an IPv4 and a routable IPv6 address. On Windows 2003 only, the FTP command does not support IPv6. The result is that integration modules and an eHealth Central Site cannot establish communications with the IPv6 address of a NMS such as NetFlow or Cisco Wan Manager or an eHealth Remote Poller system. On Windows 2003, IE6 does not support IPv6. The eHealth OneClickEH console will not work with IPv6 addresses unless IE 7 is installed on the host. The eHealth Application Response agent can monitor IPv4 traffic on a system with an IPv6 address but it cannot monitor IPv6 traffic. For users of the eHealth High Availability feature, while Sun Cluster does support IPv6, the Veritas cluster ware package does not. For users of the eHealth Disaster Recovery feature, XoSoft WANSync does not support IPv6. The eHealth Traffic Accountant for RMON2 probes and the Cisco NetFlow NMS do not support IPv6. If the HA cluster ware supports IPv6 and you are using an IPv6 virtual address, eHealth will support only the discovery of IPv6 devices. Likewise, if the system has been configured to use an IPv4 virtual address, eHealth will discover only IPv4 addresses.
Chapter 3: Installing eHealth (Windows)

This chapter describes how to install eHealth r6.2.2 with embedded Oracle for the first time on a Windows system. The time required for the installation process varies depending on the speed of your system and disk devices, and the size of your database. You can save time by copying the eHealth and Oracle software installation media to a local disk. The installation program performs the following tasks: Installs the new release of eHealth and related applications Installs Oracle 10g Applies an Oracle update, if needed
Note: Review Preparing for Installations and Upgrades before starting the eHealth installation.
eHealth Installation
The eHealth installation program installs the core components of eHealth which enable it to gather, analyze, and manage performance data for the elements in your infrastructure. When you install the core eHealth software, you also install the following supporting applications on Windows systems: MKS NuTCRACKER 9.1, which supports scripting aspects of eHealth Oracle 10g database server for storing eHealth data Apache web server for hosting the eHealth Web user interface MKS XServer for running X Windows processes and eHealth commands During the installation, you can choose to specify another supported X server. (Optional) Cognos 8 (Report Center)
To view reports from the OneClickEH console, you need a PDF viewer, such as Adobe Reader. You can download the latest version of Adobe Reader software on the Adobe website at http://www.adobe.com. Note: If you experience problems during the installation, see Troubleshooting (see page 117).
Chapter 3: Installing eHealth (Windows) 33
eHealth Installation Package

The eHealth r6.2.2 installation package includes the following media:
Name CA eHealth Performance Manager for Windows r6.1 DVD
Contents eHealth software You can copy this software to the disk or install it from DVD. eHealth and Oracle software must be installed from the same source.
CA eHealth InstallPlus software, which includes: Performance Related applications such as Report Center and Manager 6.2 SP02 for OneClick for eHealth. Windows DVD eHealth documentation You must copy this software to the disk. CA eHealth Performance Manager for Windows r6.1 (Oracle 10g) DVD Oracle software You can copy this software to the disk or install it from DVD. eHealth and Oracle software must be installed from the same source.
CA eHealth Oracle Update software Performance You must copy this software to the disk. Manager 6.2 SP02 for Windows (Oracle 10.2.0.4 patch) DVD You can download an ISO image (.ISO file) of the installation DVD instead of receiving physical media. You must then burn the image file to a DVD that you can use on a Windows system.
System Security
When the installation program creates the eHealth database, it also changes the passwords of the Oracle sys and system accounts to ehealth to maintain system security. If you change these passwords, you must remember them and supply them when necessary. Important! You must use the nhManageUsers command when changing these passwords. Otherwise, a password mismatch results.
Start the eHealth Installation
Copy the DVDs to a Disk

You can save time during the eHealth installation by copying the installation media to a local disk. The installation media requires approximately 4 GB of disk space. Note: Do not copy the installation media to a location that has spaces in the directory name, such as the Windows Desktop. If you run the installation program from a directory such as D:\eHealth Software, the installation fails.
Oracle 10g Software DVD

Because Oracle does not officially support installation over a network, copying the installation media to the local system is preferable. Confirm that the target system has at least 2 GB of free disk space. Note: Throughout this guide, ehealth represents the full pathname of the directory in which you are installing eHealth.

Run the installation program as the eHealth administrator. If the installation program exits with a message that the Windows SNMP trap service is running, the program cannot configure TrapEXPLODER because both Windows SNMP trap service and TrapEXPLODER use port 162. You must either disable the Windows SNMP trap service or configure TrapEXPLODER to use a different port. For help, see the troubleshooting section TrapEXPLODER Unable to Start. If you encounter other problems with the installation, see the log file located in ehealth/log/install/instehealth.log. To start the eHealth installation program 1. Log on to the Windows system as the eHealth administrator. You must run the eHealth installation program as the eHealth administrator. 2. Create a new temporary directory with adequate space for the InstallPlus files if you are using the InstallPlus software on DVD. Do not use a directory path that contains spaces such as C:\Documents and Settings\All Users\eHealth Install.
3. Navigate to the directory into which you extracted the InstallPlus program files. Double-click setup.exe to start the installation program. Note: If you have not downloaded and extracted the InstallPlus program, see "Required Software for eHealth r6.2.2 (see page 26)". The Setup dialog appears. 4. (Optional) Select Start, Run from the Windows Desktop, and enter the following if you have created an LCF to specify the layout of your eHealth database:
InstPlusPath\setup -useLcf path\filename
InstPlusPath Represents the directory in which InstallPlus has been extracted (or the letter of the DVD drive). path\filename Represents the full path to the LCF. The eHealth utilities do not like a path with spaces, so CA recommends using a command-line window. 5. Specify the location of the release version of the eHealth software that you are installing and click Next. The Installation Wizard appears. 6. View the License agreement. You must accept the agreement to install eHealth. 7. Review the eHealth Readme file which contains important information about the current release of eHealth. 8. Select the eHealth Installation Directory. Specify a directory such as C:\ehealth62. Do not specify a top-level (or root) directory (such as C:\ or D:\). Also, do not refer to a directory using the Universal Naming Convention (UNC). Instead, use a mapped drive. Note: The default directory is ehealth. 9. Enter the eHealth User Password (the password of the current user log on). The installation program uses the password to configure the eHealth services. 10. Select the Date and Time Format. This dialog appears only for English eHealth. French eHealth uses a 24-hour time format, and Japanese eHealth uses a 12-hour time format. 11. Select the X Server. Install MKS XServer or specify another supported X server.
12. Enter the Web Server Port. The default port is 80. You can specify another port. If you select the default, the program checks to see if the port is in use. 13. Select the Program Folder. Note: The default folder is eHealth 6.1. 14. Specify the directory where the Oracle software will be installed. The default location follows Oracle conventions. Do not install Oracle in a root directory such as C:\ or D:\. Also, do not refer to a directory by using the Universal Naming Convention (UNC). Instead, use a mapped drive. Note: The default directory is ehdrive:\oracle\Oracle.10.2. 15. Specify the eHealth Database Name. The eHealth database name must be eight characters or less, it must begin with a letter, and it can consist of uppercase letters (AZ) and digits (09). For example EHEALTH or EHDATA1. This value defines the ORACLE_SID environment variable. Note: The default database name is EHEALTH. 16. Select the eHealth System Type: A standard eHealth system polls statistic elements. An eHealth Traffic Accountant system polls conversation elements (probes). A Distributed eHealth System is the polling back-end of a Distributed eHealth cluster. A Distributed eHealth Console is the reporting front-end of a Distributed eHealth cluster.
Note: If you choose the eHealth Traffic Accountant system, you are prompted for the location of the LCF. After specifying the file's location, go to Step 21. 17. Select Database Sizing Method. If you are supplying an LCF, select Custom, and specify the LCF location. Otherwise, select Typical. 18. Enter Database Sizing Information. If you are configuring a Distributed eHealth Console system, enter the number of elements that you plan to monitor in the cluster. The default is 500. Also, enter the number of days for which you will retain as-polled data. The default is 3. Note: For guidelines, see the Distributed eHealth Administration Guide.
19. Enter the Number of Directories for the eHealth Database. Follow the recommendations in the eHealth Sizing Wizard. At a minimum, specify at least two, distinct local disk drives. 20. Select Database Directories. For best performance, specify only one directory on each disk. The directories that you specify for the eHealth database files must be different from each other and different from the eHealth home directory. For example, if you specified D:\eHealth62 as the eHealth home directory, D:\database is a valid database directory, but D:\eHealth63\database is invalid. Do not specify a location by using the Universal Naming Convention (UNC). Instead, use a mapped drive. 21. Select Yes if you want to install Report Center. Note: You can install Report Center later by rerunning the eHealth installer or by using a manual procedure. 22. Select offset time zone information. Choose yes if your system will report on time zones that have a partial-hour offset from GMT. 23. Enter Mail Server. You can leave the SMTP field blank and specify the SMTP server after the installation finishes by setting the NH_NT_SMTP_SERVER environment variable. If you do not know the name of your SMTP server, ask your system administrator. 24. Enter Printer Name. You can leave the Share field blank and specify the printer after the installation finishes by setting the NH_PRINTER environment variable.
25. Install Oracle. The program has different prompts, depending on the installation source: Local disk: The program prompts you for the location of the Oracle Disk directory. DVD: The program prompts you to insert the Oracle DVD. After you insert the DVD, it may take a few minutes for the Oracle installation to begin. Accept the defaults.
26. Update Oracle. Specify the DVD or disk location of the Oracle Update software used to update the database. If you experience a failure during database creation and the installation program stops, see Database Creation Is Incomplete before restarting the installation program. The installation program finishes the installation of eHealth and related applications. To complete the eHealth installation 1. Complete the actions listed in the To Do List dialog, if it appears. Click Next. The Installation Complete dialog appears. 2. Select Yes, I want to restart my computer now (if it is not already selected) and click Finish. Note: You must restart your computer before running eHealth. 3. Click Yes when the XServer Optimizer dialog appears. This step optimizes the ability of the X server to render graphics. The Server Optimization dialog appears and the program starts running. After a few minutes, progress bars appear in all of the fields. 4. Click Close. eHealth is successfully installed.
Additional Tasks
After eHealth is installed, you might need to perform the following tasks: If you are planning to create a Distributed eHealth cluster, see the Distributed eHealth Administration Guide for details. If the target system will be a site in a remote polling environment, see the eHealth Remote Poller User Guide. Re-enable all antivirus programs that you disabled, except for McAfee 8.0, which cannot run on the same system as eHealth r6.2.2.
Start eHealth
If you copied the installation media to local disk directories, delete those directories to free disk space. You must install and configure the Distributed SNMPv3 Security Pack software (available from SNMP Research International) on your eHealth system if you plan to discover and poll SNMPv3 elements. Note: For more information, see the Distributed SNMP Security Pack Quick Start Guide provided by SNMP Research.
Rename your old trapexploder.cf file and restart TrapEXPLODER to activate the latest TrapEXPLODER features.
You can also enable LDAP authentication. Note: The eHealth r6.2 services still use version number 6.1 (for example: eHealth61, eHealth Httpd61, eHealth Tomcat61, and so on).
How to Activate a New TrapEXPLODER Configuration File

When you install a new version of eHealth and TrapEXPLODER over an older version, the previous trapexploder.cf file is not overwritten in order to preserve the old configuration data. When eHealth starts, it uses the old configuration file and does not enable the latest TrapEXPLODER features until you save the old configuration file under a different name. To activate the new features, follow this process: 1. Shut down TraxEXPLODER. 2. Rename the trapexploder.cf file to trapexploder.cf.old. 3. Restart TrapEXPLODER. This activates the new features with a newtrapexploder.cf file while preserving your old configuration file.
Start eHealth
This section describes how to start eHealth so that you can add license information. To start eHealth and open the eHealth console after installation 1. Log on to your system as the eHealth administrator. 2. Select Start, Programs, eHealth 6.1 from the Windows desktop. The eHealth server starts. The eHealth console and OneClick for eHealth open.
Add eHealth Licenses
Add eHealth Licenses

eHealth offers a variety of monitoring and management solutions that require specific licenses (for example, Traffic Accountant). Included with this release is a 30-day trial eHealth license. This means you can run eHealth, and discover and poll elements for 30 days out of the box. After 30 days, if you have not purchased permanent eHealth licenses, eHealth stops discovering and polling elements in your environment. Be sure to complete all your license purchases before the 30-day trial license expires. To obtain licenses and more information, log on to http://support.ca.com, and click Licensing. After you place your request, you will receive your licenses by email. You must then add the license information to your system. To add eHealth licenses 1. Enter the following commands to stop the eHealth server and the eHealth license manager:
nhServer stop nhLmgr stop
2. Open the license.dat file that resides in the ehealth/lmgr directory. 3. Copy and paste only the license keys from the email message into the file to overwrite the existing entries. Do not include the e-mail header information. 4. Save and close the file. You can add licenses at any time to extend your eHealth management capabilities. eHealth saves the license information and enables your access to eHealth and all associated applications. 5. Enter the following command to start the eHealth server and the eHealth license manager:
nhServer start
The eHealth server starts and the license.dat file is read by the system. The eHealth console and OneClick for eHealth open. Note: Use OneClick for eHealth to find the network devices that you want to poll and for which you want to run reports. For details about licensing and polling, see the eHealth Administration Guide.
Install Report Center After eHealth is Installed
License File Example The following is sample license information for 1000 standard poller licenses and one LAN/WAN license:
# license.dat - license file for FLEX/lm license manager # ... # Key Type TotalExpiresCodeCksum ----------------------------------------------# PollerStandard1000never3B9E2051BBA40DD98A2F77 # LAN/WANStandard1never5BBE70611CDB9B4C5A9526 # ...
Install Report Center After eHealth is Installed

You can install Report Center on Windows after you have installed eHealth using either of the following methods: Automated Uses the eHealth installer. This method automates the process of installing Report Center but causes the eHealth servers to stop during the installations of Report Center. This process can take anywhere from 20 minutes to 3 hours, and eHealth servers will be down during this time. Manual Uses a manual multi-step process on UNIX, which does not affect the eHealth servers.
To install Report Center by using the eHealth installer, rerun the eHealth installation on the same server, point it at the same eHealth location, and answer Yes when asked whether you want to install Report Center. Manual installations of Report Center require the additional step of copying cndcReporting.zip to $NH_HOME\crn\deployment.
Where to Go from Here

After completing the installation, you need to perform the following administration tasks before eHealth can begin to monitor your IT infrastructure: Run the discover process to identify the devices that eHealth will monitor Create groups and group lists to organize the elements that eHealth discovers Schedule reports to monitor the status of your resources Develop a database backup strategy to protect your data from unexpected events
For the following information, see the eHealth Administration Guide and the eHealth Overview Guide: Descriptions of system administration tasks A road map to follow to successfully administer your eHealth system An overview of the eHealth interfaces that you use to administer the system
Chapter 4: Installing eHealth (UNIX)

This chapter describes how to install eHealth r6.2.2 with embedded Oracle for the first time on a Solaris or HP-UX system. The time required for the installation process varies depending on the speed of your system and disk devices, and the size of your database. If you are installing eHealth with embedded Oracle, you can save time by copying the eHealth and Oracle software installation media to a local disk. The installation program performs the following tasks: Installs the new release of eHealth and related applications Installs Oracle 10g Applies an Oracle update, if needed
The eHealth core components gather, analyze, and manage performance data for the elements in your infrastructure. When you install the eHealth software, you also install the following supporting applications on UNIX systems: Oracle 10g database server for storing eHealth data Apache web server for hosting the eHealth Web user interface (Optional) Cognos 8 (Report Center)
To view eHealth PDF reports and documentation, you need a PDF viewer, such as Adobe Reader. You can download the latest version of Adobe Reader software on the Adobe website at http://www.adobe.com. Note: If you experience problems during the installation, see Troubleshooting (see page 117).
Chapter 4: Installing eHealth (UNIX) 45
eHealth Installation Package

The eHealth r6.2.2 installation package includes the following media:
CA eHealth Oracle Update software Performance You must copy this software to the disk. Manager 6.2 SP02 for Windows (Oracle 10.2.0.4 patch) DVD You can download an ISO image (.ISO file) of the installation DVD instead of receiving physical media. You must then mount the ISO file as if it were an actual DVD. Note: You must install the eHealth software and the Oracle software from the same source, either DVD or disk directory. The InstallPlus and Oracle update do not have to be installed from the same source. More information: Mount an ISO Image on a Solaris System (see page 49)
System Security
When the installation program creates the eHealth database, it changes the passwords of the Oracle sys and system accounts to ehealth to maintain system security. If you change these passwords, you must remember them and supply them when necessary. Important! You must use the nhManageUsers command when changing these passwords. Otherwise, a password mismatch results.
Guidelines for Installation from DVD

To prevent delays when installing from DVDs, use the following guidelines: Use a mount point named /cdrom. If you do not respond to prompts to insert DVDs in a timely manner, the eHealth installation program displays the following prompt:
The Oracle installation seems to be hung. Do you want to continue the install (y/n)?
DVD-ROM Device Requirements

The DVD-ROM device must be connected directly to your system and capable of reading 512-byte blocks. Oracle does not support installations from disk drives mounted over a network file system (NFS). The eHealth installation program assumes that a Solaris system is properly configured for Volume Management to automatically mount DVDs. However, Solaris 2.9 systems require that you modify the /etc/inetd.conf file to configure the rpc.smserved server to support removable media. To configure a Solaris 2.9 system to auto-mount DVDs: 1. Log in as the root user. 2. In a text editor, open the /etc/inetd.conf file. 3. Add the following line to the file:
1000155/1 tli rpc/ticotsord /usr/lib/smedia/rpc.smserverd \rpc.smserverd
4. Save your changes and close the text editor. 5. List the process ID (pid) of the inetd process in a terminal window by entering the following command:
ps ef | grep inetd
6. Find the row that contains /usr/sbin/inetd. The pid is the number in the second column of that row. 7. Enter the following command so that the inetd daemon rereads the configuration file:
kill -HUP pid
pid Specifies the process ID identified in Step 6.
Copy the DVDs to a Disk

If the eHealth system does not have a local DVD drive, or if you want to avoid changing DVDs during installation, do one of the following: Copy the eHealth and Oracle DVDs to a disk on the local system and then run the InstallPlus program. Copy the DVDs to an NFS-mounted (or network-accessible) system. This type of installation is supported on systems running Solaris 2.9 and 2.10 and HP-UX 11.11 and 11.23.
Follow these guidelines when copying DVDs to a disk: You must install the eHealth software and the Oracle software from the same source, either DVD or disk directory. The InstallPlus and the Oracle update installations do not have to be from the same source.
Note: Verify that you have the latest eHealth and Oracle security patches and fixes by downloading the InstallPlus software and Oracle update software from the eHealth product website at http://support.ca.com. When possible, use these downloads instead of the DVDs supplied with your eHealth package. To copy the contents of the DVDs to a disk 1. Mount the Software DVD. 2. Create a directory on a disk with free space equivalent to the size of the ISO image. Note: The installation program does not support the use of spaces in directory names. If you run the installation program from a directory such as /export/green/ca software/eh61, the installation fails. The directory is created.
3. Change to the directory on which you mounted the ISO image and enter the following command to copy the contents of the ISO image to the created directory:
find . -print | cpio -pdmv ehdata
ehdata Specifies the full path to the directory that you created in Step 2. The contents of the ISO image is copied. 4. Repeat steps 13 for the eHealth Software ISO image, Oracle Software ISO image, Oracle Update ISO image, and InstallPlus ISO image by using distinct directories for each image. After the contents of the ISO images are copied locally, extract the zip file in the Oracle Update directory and the executable file in the InstallPlus directory as described in Required Software for eHealth r6.2.2 (see page 26).
Mount an ISO Image on a Solaris System

If you have downloaded an ISO image of the installation DVD and moved the ISO file to your Solaris server, you must mount the ISO file as if it were an actual DVD to access the data in the file. You can use the lofiadm command to administer the loopback file driver, lofi, which allows a file to be associated with a block device. That file can then be accessed through the block device. 1. Use lofiadm to attach a block device by executing the following command:
# lofiadm -a /path/to/image/dvdImage.iso /dev/lofi/1
2. Mount the image by executing the following mount command:

# mount -F hsfs -o ro /dev/lofi/1 /mnt
3. Check to make sure that Solaris recognizes the image by executing the following:
# df -k /mnt Filesystem kbytes used /dev/lofi/1 512418 512418 # ls /mnt ./ ../ <other files in the mounted image> avail capacity 0 100% Mounted on /mnt
If the image was created properly, Solaris should be able to mount the ISO image and recognize the file names. Follow the instructions to copy the contents of the eHealth and Oracle Software DVDs to a disk, and the InstallPlus and Oracle update software. The eHealth installer will not recognize the mounted images as true DVDs. Important! Copy the files from the mount location to the local directory before running the installation. To unmount and detach the images, execute the following:
# umount /mnt # lofiadm -d /dev/lofi/1 # lofiadm Block Device File
Note: The full path to the command is: /usr/sbin/lofiadm More information: Copy the DVDs to a Disk (see page 48)
How to Configure Resource Limits on Solaris

You might need to configure Solaris systems with the resource limits required by eHealth. eHealth uses shared memory, and it is probable that the default resource limits are not adequate. The configuration required by eHealth depends on the version of Solaris that you are using. If you are using Solaris 10, do the following: 1. Determine what projects exist on the system by executing this command:
projects -l
2. Determine what project(s) [$NH_USER] is associated with by executing this command:

id p [$NH_USER]
In the following example, user nhuser is associated with the default project on the system belnotex7:
belnoteX7% id -p nhuser uid=391(nhuser) gid=50(gdm) projid=3(default)
3. (Optional) Execute the following command to change any of the resource limit values for the project(s) associated with [$NH_USER]:
projmod -s -K "project.max-shm-memory=(priv,4GB,deny)" -K "project.max-shm-ids=(priv,100,deny)" -K "process.max-sem-nsems=(priv,256,deny)" -K "project.max-sem-ids=(priv,100,deny)" project
In the following example, default is the project being modified:

projmod -s -K "project.max-shm-memory=(priv,4GB,deny)" -K "project.max-shm-ids=(priv,100,deny)" -K "process.max-sem-nsems=(priv,256,deny)" -K "project.max-sem-ids=(priv,100,deny)" default
Note that you can omit any attributes from this command if they are already correct. For example, to change only the number of file descriptors, execute the following command:
projmod -s -K "project.max-shm-memory=(priv,4GB,deny)" default

The eHealth installation program prompts you to supply information. Respond to the prompts to complete the installation. Many prompts provide a default response in brackets ([ ]). If you press Enter at these prompts, the installation program uses the default. Throughout this guide, ehealth represents the full pathname of the directory in which you are installing eHealth. To start the eHealth installation 1. Log on to the eHealth system as root (use the dash to log on with the root environment, not another user environment) by entering the following command:
su - root
The root user prompt appears. 2. Set the DISPLAY environment variable to a running X Server to prevent Oracle software installation problems by entering the following command:
setenv DISPLAY hostname:x.0
x Specifies the display number. The DISPLAY environment variable is set. 3. Enter the following command to verify that the value of the LANG environment variable has not changed:
env | grep LANG
If the command does not produce any output, the root profile does not have the LANG variable set. If you do not set a value, the installation program assumes the value is C (English). If you are installing French or Japanese eHealth, set the value of the variable as follows: For a Bourne or Korn shell, enter the following command:
LANG=value; export LANG
For a C shell, enter the following command:

setenv LANG value
For value specify the operating system language: fr (French) ja (Japanese)
The value of the LANG variable is set. Confirm that the eHealth administrator also has the same value for LANG.
4. Enter the following command to set the default file permissions to read-write by owner and group, and read-only for everyone else:
umask 002
The default file permissions are set. 5. Change to the directory where you extracted the InstallPlus files and enter the following command:
./INSTALL.NH
Note: If you have not downloaded and extracted the InstallPlus program, see "Required Software for eHealth r6.2.2 (see page 26)". 6. Enter eHealth software DVD mount point or disk location. If you are installing eHealth from the DVD, enter /cdrom. If you are installing eHealth from disk, supply the full path to the location of the eHealth software.
7. View the agreement and enter y to accept it and install eHealth. 8. Enter y to review the eHealth README file which contains the latest information about eHealth. The README file appears. Press the spacebar to scroll through it or q to exit the file. 9. Enter the name of the eHealth administrator account at the following prompt. You must specify a user account that already exists on your system:
What is the account name for the eHealth administrator?
The eHealth administrator account is set. 10. Specify the the location in which the Oracle 10g software will be installed at the following prompt:
Where do you want to install the Oracle software?
Confirm that you want the installation program to create a new directory by entering y at the following prompt:
'/Oracle10gLocation' does not exist. Do you want to create it (y|n)? [y]
The new directory is created. 11. Enter the name of the eHealth database, known as the Oracle session identifier (SID), at the following prompt:
What is the eHealth database name? [EHEALTH]
The name must be eight characters or less, it must begin with a letter, and it can consist of uppercase letters (AZ) and digits (09). The eHealth database name is configured.
12. Enter the full pathname of the directory in which you want to install eHealth at the following prompt:
Where do you want to install the eHealth software?
When specifying a location for the eHealth software, use partitions on a local disk. Do not specify a location on a disk that resides on another system in the network. You can install eHealth in any directory except /opt/eHealth, which is reserved. The eHealth system uses /opt/eHealth as a symbolic link that points to eHealth. If you want to install eHealth under /opt, specify a name such as /opt/ehealth62 or /opt/eh62. Note: During installation, eHealth sets the ownership of this directory to the user specified in Step 9, even if the directory already exists and is owned by another user. The eHealth installation directory is specified. 13. Confirm that you want the installation program to create a new directory by entering y at the following prompt:
'ehealth' doesnt exist. Do you want to create it (y|n)? [y]
The eHealth installation directory is created. 14. Select a date format for eHealth reports, the console, and the web user interface at the following prompt:
eHealth can display dates in one of the following formats. 1) mm/dd/yyyy 2) dd/mm/yyyy 3) yyyy/mm/dd 4) yyyy/dd/mm What date format should eHealth use? (1|2|3|4) [1]
15. Select a time format at the following prompt:

eHealth can display times in one of the following formats: 1) 12-hour clock (such as 5:00 PM) 2) 24-hour clock (such as 17:00) What time format should eHealth use? (1|2) [1]
This prompt does not appear when you install the French version of eHealth because that language automatically uses a 24-hour clock. 16. Enter the port number for the web server at the following prompt:
What port should the Web server use? [80]
eHealth installs an Apache web server that allows users to view and run eHealth reports from a web browser or use the Live Health applications. Accept port 80 as the default response unless port 80 is already in use.
17. Specify the type of eHealth system that you want to install at the following prompt:
eHealth System Type. (1) Standard eHealth System (2) eHealth Traffic Accountant (TA) System (3) Distributed eHealth System (back-end/polling system) (4) Distributed eHealth Console (front-end/reporting system) Please enter your selection [1]:
where: A standard eHealth system polls statistic elements. An eHealth Traffic Accountant system polls conversation elements (probes). A Distributed eHealth System is the polling back-end of a Distributed eHealth cluster. A Distributed eHealth Console is the reporting front-end of a Distributed eHealth cluster.
The default [1] is the standard eHealth system. Note: If you choose the eHealth Traffic Accountant type, you are prompted for the location of the LCF. After specifying the file's location, go to Step 22. 18. Specify the number of elements that you intend to poll at the following prompt:
The size of your eHealth database depends on the number of monitored elements and the number of days as-polled (unaggregated) data. eHealth retains aggregated data for a longer period. Number of elements:
19. Specify the number of days to retain as-polled data at the following prompt:
Enter the number of days for which you will retain as-polled data. This value determines the initial size of your eHealth database. If you change the default value, after installation you must change the statistics rollup schedule to match this value. Number of days [3]
By default, eHealth collects five-minute samples of data from each monitored element and keeps this raw data for three days. It then rolls up (aggregates) the as-polled samples into hourly and daily samples. Specify the number that you used when planning the system size by using the eHealth Sizing Wizard.
20. Enter the number of directories for the eHealth Database at the following prompt. Follow the recommendations in the eHealth Sizing Wizard. At a minimum, specify at least two, distinct local disk drives.
Your eHealth database requires one or more directories upon which to place your Oracle database. Each directory must be on a distinct partition and each directory should be on a distinct disk drive. I/O performance is impacted greatly by your responses. Enter number of directories to use for datafiles:
21. Enter directory pathnames. The installation program prompts you for the directory pathnames in which to store the eHealth database, one at a time. At each prompt, enter one directory pathname.
Enter directory 1: Enter directory 2: Enter directory 3: . .
The directories that you specify for the eHealth database files must be different from each other and different from the eHealth home directory or Oracle home directory. Do not specify /tmp as a directory pathname. This directory is intended for temporary files only, not database directories. 22. Select Yes if you want to install Report Center. Note: You can install Report Center later by rerunning the eHealth installer or by using a manual procedure. 23. Select offset time zone information. Choose yes if your system will report on time zones that have a partial-hour offset from GMT. 24. Install Oracle (only if you are installing eHealth with embedded Oracle). The program has different prompts, depending on the installation source: Local disk: The program prompts you for the location of the Oracle Disk directory. Enter the full pathname to the directory in which you copied the DVDs, excluding the disk and disk number. Example: /path/OracleBase path Specifies the full path to the location where the OracleBase software was copied. DVD: The program prompts you to insert the Oracle DVD. After you insert the DVD, it may take a few minutes for the Oracle installation to begin. Accept the defaults.
25. Update Oracle (only if you are installing eHealth with embedded Oracle). If the following prompt appears, it indicates that the installer has to examine the Oracle update software to determine if updates need to be applied:
Enter Database Update Kit DVD mount point or disk location:
Enter the full directory path to the Oracle update software on your local disk, for example: /home/mydisk2/dbPatchKit. If you have not downloaded and extracted the Oracle update zip file, see "Required Software for eHealth r6.2.2 (see page 26)". Note: For more information about how to install the update, open the Readme text file located on the top level of the Oracle update directory. The Oracle installer applies updates as needed. Note: If you experience a failure during database creation and the installation program stops, see Database Creation Is Incomplete before restarting the installation program. When the installation finishes, the following is displayed: A list of suggested or required tasks for you to perform The location of the log file containing a record of the installation
eHealth is successfully installed and activation is launched.
Additional Tasks
After eHealth is installed, you may need to perform the following tasks: If you are planning to create a Distributed eHealth cluster, see the Distributed eHealth Administration Guide for details. For information about high availability and disaster recovery in your eHealth environment, see the eHealth High Availability and Disaster Recovery Administration Guide. If the target system will be a site in a remote polling environment, you must perform additional steps after running the eHealth installation program. See the Using the eHealth Remote Poller guide. If you copied the installation DVDs to local disk directories, delete those directories to free disk space. You must install and configure the Distributed SNMPv3 Security Pack software (available from SNMP Research International) on your eHealth system if you plan to discover and poll SNMPv3 elements. For more information, see the Distributed SNMP Security Pack Quick Start Guide provided by SNMP Research. Rename your old trapexploder.cf file and restart TrapEXPLODER to activate the latest TrapEXPLODER features.
Start eHealth and Add eHealth Licenses
How to Activate a New TrapEXPLODER Configuration File

When you install a new version of eHealth and TrapEXPLODER over an older version, the previous trapexploder.cf file is not overwritten in order to preserve the old configuration data. When eHealth starts up, the old configuration file is used and does not let you access the latest TrapEXPLODER features until you save the old configuration file under a different name. To activate the new features, follow this process: 1. Shut down TraxEXPLODER. 2. Locate the trapexploder.cf file. On UNIX: /etc/trapexploder.cf On Windows: C:\Windows\system32\trapexploder.cf
3. Rename the trapexploder.cf file to trapexploder.cf.old. 4. Restart TrapEXPLODER. This activates the new features with a newtrapexploder.cf file while preserving your old configuration file.

eHealth offers a variety of monitoring and management solutions that require specific licenses (for example, Traffic Accountant). Included with this release is a 30-day trial eHealth license. This means you can run eHealth, and discover and poll elements for 30 days out of the box. After 30 days, if you have not purchased permanent eHealth licenses, eHealth stops discovering and polling elements in your environment. Be sure to complete all your license purchases before the 30-day trial license expires. To obtain licenses, and more information, log in to http://support.ca.com, and click Licensing. After you place your request, you will receive your licenses electronically. You must then add the license information to your system.
To start eHealth and add your eHealth licenses after installation 1. Source the eHealth resource file appropriate for your shell environment by using one of the following commands: Bourne: . ./nethealthrc.sh C: source nethealthrc.csh Korn: . ./nethealthrc.ksh
The eHealth environment is set. 2. Enter the following commands to stop the eHealth server and the eHealth license manager:
nhServer stop nhLmgr stop
3. Open the license.dat file that resides in the ehealth/lmgr directory. 4. Copy and paste only the license keys from the email message into the file to overwrite the existing entries. Do not include the e-mail header information. 5. Save and close the file. You can add licenses at any time to extend your eHealth management capabilities. eHealth saves the license information and enables your access to eHealth and all associated applications. 6. Enter the following command to start the eHealth server and the eHealth license manager:
nhServer start
The eHealth server starts and the licenses are read by the system. The eHealth console and OneClick for eHealth open. Note: Use OneClick for eHealth to locate the network devices that you want to poll and for which you want to run reports. For details about licensing and polling, see the eHealth Administration Guide. Example: License File The following is sample license information for 1000 standard poller licenses and one LAN/WAN license:
# license.dat - license file for FLEX/lm license manager # ... # Key Type TotalExpiresCodeCksum ------- --------------------------------------# PollerStandard1000never3B9E2051BBA40DD98A2F77 # LAN/WANStandard1never5BBE70611CDB9B4C5A9526 # ...
Install Report Center Manually After eHealth Is Installed
Install Report Center Manually After eHealth Is Installed

You can install Report Center manually on UNIX after you have installed eHealth. This process does not affect the eHealth servers. Note: You can use the eHealth installer to automatically add the Report Center feature, but installing it automatically causes the eHealth servers to stop during the installations of Report Center. To manually install Report Center on UNIX 1. Open a new command shell and source the new nethealthrc.sh or csh file. 2. Disable schedule job 'Update Report Center Element Types' by executing the following command:
nhSchedule -disable 100020
3. Run the following commands at the command line:

nhParameter -set reportCenterInstalled yes nhRptCtrConfig -action setAdminWebAccess -dbUser [$NH_USER] -adminUser admin -adminPassword [adminPwd] -adminURI http://localhost:9301/p2pd/servlet/dispatch
[$NH_USER] Specifies the eHealth administrator. [adminPwd] Specifies the password of the web user named admin. 4. Run the Cognos 8 (Report Center) installer from the rcInstall folder in the zipped patch kit or the InstallPlus kit. Zipped Patch Kit: Windows: [unzipped loc]/rcInstall/setup.exe Unix: [unzipped loc]/rcInstall/INSTALL InstallPlus Kit: Windows: [unzipped loc]/plus/patch/rcInstall/setup.exe UNIX: [unzipped loc]/plus/patch/rcInstall/INSTALL 5. Run the following command:
nhRptCtrConfig -action instStartCognos
The Cognos servers start. 6. Run the following command:

nhRptCtrConfig -action instConfigureRC
This deploys the sample reports and data model (metadata) for eHealth.
7. Run the following command:

nhRptCtrConfig -action instConfigureRegData 60
Note: Use 30 for non-hourly timezone data. This runs nh_reg_process.setup(60) to configure the regData. 8. Run the following command:
nhRptCtrConfig -action instFinalizeRC
This sets flags that enable Report Center related DB jobs and the Report Center tab in the eHealth web user interface. 9. Enable the schedule job 'Update Report Center Element Types' by executing the following command:
nhSchedule -enable 100020
Report Center is now enabled.

After completing the installation, you need to perform the following administration tasks before eHealth can begin to monitor your IT infrastructure: Run the discover process to identify the devices that eHealth will monitor Create groups and group lists to organize the elements that eHealth discovers Schedule reports to monitor the status of your resources Develop a database backup strategy to protect your data from unexpected events
For the following information, see the eHealth Administration Guide and the eHealth Overview Guide: Descriptions of system administration tasks A roadmap to follow to successfully administer your eHealth system An overview of the eHealth interfaces that you use to administer the system
Chapter 5: Upgrading eHealth (Windows)

This chapter describes how to upgrade eHealth Release r5.7.9 or r6.0 to eHealth r6.2.2 on a Windows system. The upgrade process includes an upgrade of the Oracle database from Oracle 9.2.0.8 to Oracle 10g. If you have an earlier version of Oracle (such as 9.2.0.3), you must upgrade to Oracle 9.2.0.8 and then upgrade to Oracle 10g. You must install eHealth r6.2.2 in a new directory on the existing eHealth system. The eHealth upgrade program performs the following tasks: Installs the new release of eHealth in a directory that is different from the location of eHealth r5.7.9 or r6.0 Copies configuration information and customized files to the new eHealth location Upgrades MKS Nutcracker software Upgrades Report Center, if installed If Report Center is not installed, you can choose to install it. Upgrades the version of the Oracle software Converts the database to the eHealth r6.2.2 schema Applies an Oracle update, if needed
Note: Make a back up copy of the eHealth database before you start the upgrade.
eHealth Upgrade
Before you begin the upgrade process, you may want to copy the contents of the DVDs to a disk if the eHealth system does not have a local DVD drive, or if you want to avoid changing DVDs during installation.
Chapter 5: Upgrading eHealth (Windows) 63
eHealth Upgrade
Copy the contents of the DVDs

To reduce the time spent changing DVDs you can copy the DVDs to a local disk drive. The DVDs require approximately 4 GB of disk space. Do not copy the DVDs to a location that has spaces in the directory name, such as the Windows Desktop. If you run the installation program from a directory such as D:\eHealth Software, the installation fails.
eHealth Software Package

Confirm that you have the appropriate software for the eHealth r6.2.2 release:
CA eHealth Oracle Update software Performance You must copy this software to the disk. Manager 6.2 SP02 for Windows (Oracle 10.2.0.4 patch) DVD
eHealth Upgrade
Start the eHealth Upgrade

Run the installation program as the eHealth administrator. Throughout this guide ehealth_new represents the full pathname of the directory in which you are installing eHealth r6.2.2, and ehealth_old represents the directory in which you installed eHealth r6.0 or r6.1. The eHealth installation program prompts you to supply information. Respond to these prompts to complete the installation. To start the eHealth upgrade 1. Log on to the Windows system as the eHealth administrator. You must run the eHealth installation program as the eHealth administrator. 2. Create a new temporary directory with adequate space for the InstallPlus files if you are using the InstallPlus software on DVD. Do not use a directory path that contains spaces such as C:\Documents and Settings\All Users\eHealthInstall. 3. Navigate to the directory into which you extracted the InstallPlus program files and double-click setup.exe. Note: If you have not downloaded and extracted the InstallPlus program, see Required Software for eHealth r6.2.2. The Setup dialog appears. 4. Specify the location of the release version of the eHealth software that you are installing and click Next. A dialog appears explaining when the installation program checks your database software for possible updates. 5. Click Yes. The eHealth Installation Wizard welcome window appears. 6. Click Next. 7. View the License agreement. You must accept the agreement to install eHealth. 8. Review eHealth README file, which contains important information about the current release of eHealth. 9. Select eHealth Installation Directory. Specify a directory such as C:\ehealth62. Do not specify a top-level (or root) directory (such as C:\ or D:\). Also, do not refer to a directory by using the Universal Naming Convention (UNC). Instead, use a mapped drive. Note: The default directory is ehealth 6.2.
eHealth Upgrade
10. Enter the eHealth User Password (the password of the current user log on). The installation program uses the password to configure the eHealth services. 11. Specify the directory where the Oracle software will be installed. The default location follows Oracle conventions. Do not install Oracle in a root directory such as C:\ or D:\. Also, do not refer to a directory using the Universal Naming Convention (UNC). Instead, use a mapped drive. 12. Select Date and Time Format. This dialog only appears for English eHealth. French eHealth uses a 24-hour time format, and Japanese eHealth uses a 12-hour time format. 13. Select Program Folder. Note: The default folder is ehealth 6.2. 14. Enter Yes if you do not have Report Center on your system or and you want to install it now, or if you want to upgrade your existing version. Note: Report Center can be manually installed later by rerunning the eHealth installer. 15. Select the correct offset time zone information. Choose yes if your system will report on time zones that have a partial-hour offset from GMT. 16. Click Next to begin the eHealth installation. 17. Specify the location of the Oracle software by inserting the Oracle software DVD or specifying a disk directory. 18. Update Oracle. Specify the DVD or disk location of the Oracle update software used to update the database. Note: For instructions on how to install the Oracle update, open the README text file located on the top level of the Oracle update directory. The installation program finishes the installation of eHealth and related applications.
Additional Tasks
To complete the eHealth installation 1. Complete the actions listed in the To Do List dialog, if it appears, and click Next. The Installation Complete dialog appears, and the the eHealth activation process starts. Note: If you are working in a cluster environment, see Activate a Distributed eHealth Cluster. A window appears showing the progress of the eHealth activation. The system reboots after activation completes. 2. Select Start, Programs, eHealth 6.1 from the Windows desktop. The eHealth console and OneClick for eHealth open. 3. Run reports to confirm that eHealth is polling and running reports normally. After a few days of proper function, perform the Finalize Upgrade procedure.
Additional Tasks
After you have successfully upgraded your system to eHealth r6.2.2, perform these tasks to help ensure that eHealth operates properly.
Activate a Distributed eHealth Cluster

After you have installed eHealth r6.2.2 on all cluster members, you must activate the software across the cluster from a single trusted cluster member. Note: Perform this step on the trusted system only. Do not perform this step on each cluster member. Trusted System A trusted system in a Distributed eHealth cluster is an eHealth system that can issue commands (such as nhRunCommand and nhPutFile) to modify the configuration and operation of other systems in the cluster. The trusted member that you select can be a Distributed eHealth System or a Distributed eHealth Console. When you run the nhUpgradeCluster -activate command from this system to activate eHealth r6.2.2 on all cluster members, the command establishes the trusted system as the controller system for the cluster upgrade process.
Additional Tasks
To activate eHealth r6.2.2 on all systems in a cluster Note: If the system encounters errors during any critical activation step, it rolls back the software to r5.7.9 or r6.0 and issues messages to this effect. After eHealth r6.2.2 is activated, the eHealth r5.7.9 or r6.0 environment is no longer active. 1. Log on as the eHealth administrator and open a new command prompt window. 2. Change to the ehealth_old\bin directory:
cd /d ehealth_old\bin
The directory is changed. 3. Confirm that all cluster member systems are running by entering the following command:
nhListClusterMembers -all
Cluster member output appears. Examine the output and ensure that all cluster members are responding with information. 4. Enter the following command to activate eHealth r6.2.2 on all cluster members:
nhUpgradeCluster -activate
The following prompt appears:

This command will run the requested cluster upgrade action on every member in the cluster. Press Ctrl-C to stop, or any other key to continue.
Additional Tasks
5. Press Return at the prompt. The nhUpgradeCluster -activate command performs the following processes (some, such as database conversion, require approximately one to ten hours to complete, depending on the size of your database): Establishes the current system as the controller system: you must run all subsequent cluster upgrade commands from this system Confirms the ability to communicate with other clustered systems Checks that all cluster members have the eHealth r6.2.2 software installed and are ready for activation Places all clustered systems in a mode that prevents configuration changes Stops eHealth r5.7.9 or r6.0 servers Starts the stand-alone poller Converts the database to use the eHealth r6.2.2 schema Recreates the eHealth r5.7.9 or r6.0 configuration in the eHealth r6.2.2 environment Starts eHealth r6.2.2 servers Restores all clustered systems to a mode that allows configuration changes Confirms that eHealth r6.2.2 has started on all systems in the cluster Reboots each Windows system in the cluster The activation process is completed, with all cluster members running eHealth r6.2.2. The ehealth_old\log\ runSwitchLocal.log file records the activation of the eHealth cluster upgrade.
Finalize Upgrade
After a few days, when you have run reports and confirmed that the upgrade to eHealth r6.2.2 was successful in your environment, finalize the installation changes. To finalize the installation changes 1. Open a terminal window on the eHealth system and log on as the eHealth administrator. 2. Enter the following command:
nhConvertDb -finalize
Additional Tasks
Note: During this process, eHealth disables (drops) the database tables that support rolling back to eHealth r5.7.9 or r6.0. Do not remove eHealth r5.7.9 or r6.0 until you are sure that eHealth r6.2.2 is running successfully. This command may take 5 to 15 minutes to complete. To follow the progress of the command, see the log file, ehealth_new\log\convert_finalize_date.time.log date/time Represents the date and time that the conversion occurred.
Cleanup Tasks
To help ensure the best performance of your eHealth r6.2.2 system, complete the following tasks: Rename your old trapexploder.cf file and restart TrapEXPLODER to activate the latest TrapEXPLODER features. Check scheduled jobs to confirm the accuracy of pathnames and file locations. If you stopped or disabled any nhConfig jobs for eHealth integration modules, enable those jobs. If you use Application Response (AR), upgrade AR agents and check ehealth_new/log/install/ARUpgrade.log for messages that application rule sets have changed. If you monitor custom applications, the rules carry over during an upgrade, but if you monitor default applications, the rules may change. Consider incorporating the changes into the ehealth_new/data/response/Rules.ard file. If you are not familiar with BT Studio and the process of customizing rule sets, consult with Technical Support for assistance. If you currently use any other agents to monitor eHealth, upgrade the agents (if needed) to a version supported by eHealth r6.2.2. For more information, see the device certification web page at http://support.ca.com/devices. Inform Live Health users to upgrade their Live Health client software. If you have created Live Exceptions Notifier rules to run scripts that are specified by hard-coded paths relative to the previous release of eHealth, move the scripts to the eHealth r6.2.2 home directory and update those rules. Authorize eHealth web users to use new functions of the eHealth Web user interface, as appropriate. If you copied the installation DVDs to local disk directories, delete those directories to free disk space.
Additional Tasks
If you plan to discover and poll SNMPv3 elements, you must install and configure the Distributed SNMPv3 Security Pack software (available from SNMP Research International) on your eHealth system. For more information, see the product documentation. (Optional) After eHealth r6.2.2 is polling normally and reports run well for a few days, remove the previous release of eHealth to regain disk space.
Chapter 6: Upgrading eHealth (UNIX)

This chapter describes how to upgrade eHealth r5.7.9 or r6.0 to eHealth r6.2.2 on a Solaris or HP-UX system. The upgrade process includes an upgrade of the Oracle database from Oracle 9.2.0.8 to Oracle 10g. If you have an earlier version of Oracle (such as 9.2.0.3), you must upgrade to Oracle 9.2.0.8 and then upgrade to Oracle 10g. You must install eHealth r6.2.2 in a new directory on the existing eHealth system. The eHealth upgrade program performs the following tasks: Installs the new release of eHealth in a directory that is different from the location of eHealth r5.7.9 or r6.0 Copies configuration information and customized files to the new eHealth location Upgrades Report Center, if installed. If Report Center is not installed, you can choose to install it. Upgrades the version of the Oracle software Converts the database to the eHealth r6.2.2 schema Applies an Oracle update, if needed
eHealth Upgrade
Before you install eHealth, you may have to mount the DVD drive. You may want to copy the contents of the DVDs to a disk if the eHealth system does not have a local DVD drive, or if you want to avoid changing DVDs during installation.
Chapter 6: Upgrading eHealth (UNIX) 73
eHealth Upgrade
eHealth Software Package

Confirm that you have the appropriate software for the eHealth r6.2.2 release.
Name CA eHealth Performance Manager for Windows r6.1 DVD CA eHealth Performance Manager 6.2 SP02 for Windows DVD
Contents eHealth software You can copy this software to the disk or install it from DVD. eHealth and Oracle software must be installed from the same source. InstallPlus software, which includes: Related applications such as Report Center and OneClick for eHealth. eHealth documentation
You must copy this software to the disk. CA eHealth Performance Manager for Windows r6.1 (Oracle 10g) DVD Oracle software You can copy this software to the disk or install it from DVD. eHealth and Oracle software must be installed from the same source.
CA eHealth Oracle Update software Performance You must copy this software to the disk. Manager 6.2 SP02 for Windows (Oracle 10.2.0.4 patch) DVD
Start the eHealth Upgrade

The eHealth installation program prompts you to supply information. Respond to these prompts to complete the installation. Some prompts provide a default response in brackets ([ ]). If you press Enter at these prompts, the installation program uses the default. Throughout this guide, ehealth_new represents the full pathname of the directory in which you are installing eHealth r6.2.2.
eHealth Upgrade
To start the eHealth upgrade 1. Log on to the eHealth system as root by entering the following command (use the dash to log on with the root environment, not another user environment):
su - root
The root user prompt appears. 2. Enter the following command to set the default file permissions to read-write by owner and group, and read-only for everyone else:
umask 002
The default file permissions are set. 3. Change to the directory in which you placed the eHealth software, and run the installation script by entering the following installation command:
./INSTALL.NH
4. Enter eHealth Software DVD mount point or disk location. If you are installing eHealth software from DVD, enter /cdrom. If you are installing eHealth software from the disk, supply the full path to the location of the eHealth software.
The eHealth installation program starts, and the eHealth license agreement appears. 5. View the agreement and enter y at the following prompt to accept the agreement to install eHealth:
Do you accept the terms of the license agreement? [y]
6. Enter y at the following prompt to review the README file which contains the latest information about eHealth:
Would you like to see the eHealth readme file? [y]
The README file appears. Press the spacebar to scroll through it or q to exit the file. 7. Enter the location in which the Oracle 10g software will be installed at the following prompt:
Where do you want to install the Oracle software?
Install Oracle in subdirectories of a directory called oracle, such as /oracle/product/ora10i. 8. Confirm that you want the installation program to create a new directory by entering y at the following prompt:
'/Oracle10gLocation' does not exist. Do you want to create it (y|n)? [y]
The new directory is created.
eHealth Upgrade
9. Enter the full pathname of the directory in which you want to install eHealth at the following prompt:
Where do you want to install the eHealth software?
When specifying a location for the eHealth software, use partitions on a local disk. Do not specify a location on a disk that resides on another system in the network. Note: You can install eHealth in any directory except /opt/eHealth, which is reserved. If you want to install eHealth under /opt, specify a name such as /opt/ehealth62 or /opt/eh62. The eHealth system uses /opt/eHealth as a symbolic link that points to the running release of eHealth. The eHealth installation directory is specified. 10. Enter y at the following prompt to confirm that you want the installation program to create a new directory (if you specified one):
'ehealth' doesnt exist. Do you want to create it (y|n)? [y]
The eHealth installation directory is created. 11. Upgrade Report Center. If Report Center is installed on your system, the following prompt appears:
Report Center 6.2 provides coverage for a limited number of distinct element types. This limitation may impact existing Report Center reports. For more information, see the 6.2 ReadMe file (Update Element Types in Report Center Jobs section). Do you want to continue the install (y|n) [y]?
y Continues the upgrade to Report Center and eHealth. Note: After completing the upgrade, you can run a command that lets you select the element types that you want Report Center to report on. For more information, see "Update Element Types in Report Center Jobs" in the eHealth r6.2.2 Readme. n Stops the eHealth installer before the upgrade is applied so that you can review the Readme file. Note: After reviewing the Readme, you must rerun the eHealth installer to apply the upgrade. 12. Select correct offset time zone information. Choose yes if your system will report on time zones that have a partial-hour offset from GMT. 13. Install Oracle. Specify the location of the Oracle software by inserting the Oracle software DVD or specifying a disk directory.
Additional Tasks
14. Update Oracle. If the following prompt appears, it indicates that the installer has to examine the Oracle update software to determine if updates need to be applied:
Enter Database Update Kit DVD mount point or disk location:
Enter the full directory path on the local disk, for example: /home/mydisk1/dbPatchKit If you have not downloaded and extracted the Oracle Update zip file, see "Required Software for eHealth r6.2.2 (see page 26)." Note: For instructions on how to install the Oracle update, open the README text file located on the top level of the Oracle update directory. The Oracle installer applies updates as needed. When the installation finishes, the following is displayed: A list of suggested or required tasks for you to perform The location of the log file containing a record of the installation
eHealth is successfully upgraded and activation is launched.
Additional Tasks
After you have successfully upgraded your system to eHealth r6.2.2, perform these tasks to help ensure eHealth r6.2.2 operates properly.
Activate a Distributed eHealth Cluster

After you have installed eHealth r6.2.2 on all cluster members, you must activate the software across the cluster from a single trusted cluster member. Note: Perform this task on the trusted system only. Do not perform this task on each cluster member. A trusted system is an eHealth system in a Distributed eHealth cluster that can issue commands (such as nhRunCommand and nhPutFile) to modify the configuration and operation of other systems in the cluster. The trusted member that you select can be a Distributed eHealth System or a Distributed eHealth Console. When you run the nhUpgradeCluster -activate command from this system to activate eHealth r6.2.2 on all cluster members, the command establishes the trusted system as the controller system for the cluster upgrade process.
Additional Tasks
In the activate procedure, ehealth_old is the directory in which you installed eHealth r5.7.9 or r6.0. Note: If the system encounters errors during any critical activation step, it rolls back the software to r5.7.9 or r6.0 and issues messages to this effect. After eHealth r6.2.2 is activated, the eHealth r5.7.9 or r6.0 environment is no longer active. To activate eHealth r6.2.2 on all systems in a cluster 1. Open a new terminal window and log on as the eHealth administrator. Change to the ehealth_old directory. Use one of the following commands to source the eHealth r5.7.9 or r6.0 resource file that is appropriate for your shell environment: Bourne: . ./nethealthrc.sh C: source nethealthrc.csh Korn: . ./nethealthrc.ksh
The eHealth resource file is sourced. 2. Enter the following command to confirm that all cluster member systems are running:
nhListClusterMembers -all
Cluster member output appears. Examine the output and confirm that all cluster members are responding with information. 3. Enter the following command on the main system to activate eHealth r6.2.2 on all cluster members:
The following prompt appears:

This command will run the requested cluster upgrade action on every member in the cluster. Press Ctrl-C to stop, or any other key to continue.
4. Press Enter. The nhUpgradeCluster -activate command performs the following processes (some, such as database conversion, require approximately one to ten hours to complete, depending on the size of your database): Establishes the current system as the controller system: you must run all subsequent cluster upgrade commands from this system Confirms the ability to communicate with other clustered systems Checks that all cluster members have the eHealth r6.2.2 software installed and are ready for activation Places all clustered systems in a mode that prevents configuration changes
Additional Tasks
Stops eHealth r5.7.9 or r6.0 servers Starts the stand-alone poller Converts the database to use the eHealth r6.2.2 schema Recreates the eHealth r5.7.9 or r6.0 configuration in the eHealth r6.2.2 environment Starts eHealth r6.2.2 servers Restores all clustered systems to a mode that allows configuration changes Confirms that eHealth r6.2.2 has started on all systems in the cluster
The activation process is completed, with all cluster members running eHealth r6.2.2. The ehealth_old\log\runSwitchLocal.log file records the activation of the eHealth cluster upgrade.
Finalize Upgrade
After a few days, when you have run reports and confirmed that the upgrade to eHealth r6.2.2 was successful in your environment, finalize the installation changes. To finalize the installation changes 1. Open a terminal window and log on as the eHealth administrator on the eHealth system. 2. Source the eHealth resource file. 3. Enter the following command:
nhConvertDb -finalize
Note: During this process, eHealth disables (drops) the database tables that support rolling back to eHealth r5.7.9 or r6.0. Do not remove eHealth r5.7.9 or r6.0 until you are sure that eHealth r6.2.2 is running successfully. This command may take 5 to 15 minutes to finish executing. To follow the progress of the command, see the log file, ehealth_new/log/convert_finalize_date.time.log date/time Represent the date and time that the conversion occurred.
Additional Tasks
Cleanup Tasks
To help ensure the best performance of your eHealth r6.2.2 system, complete the following tasks: If any user accounts are configured to automatically source the eHealth r5.7.9 or r6.0 resource file, update them to source the eHealth r6.2.2 resource file instead. Rename your old trapexploder.cf file and restart TrapEXPLODER to activate the latest TrapEXPLODER features. Check scheduled jobs to confirm the accuracy of pathnames and file locations. If you stopped or disabled any nhConfig jobs for eHealth integration modules, enable those jobs. If you use Application Response (AR), upgrade AR agents and check ehealth_new/log/install/ARUpgrade.log for messages that application rule sets have changed. (If you monitor custom applications, the rules carry over during an upgrade, but if you monitor default applications, the rules may change.) Consider incorporating the changes into the ehealth_new/data/response/Rules.ard file. If you are not familiar with BT Studio and the process of customizing rule sets, consult with Technical Support for assistance. If you currently use any other agents to monitor eHealth, upgrade the agents (if needed) to a version supported by eHealth r6.2.2. Note: For more information, see the device certification web page at http://support.ca.com/devices. Inform Live Health users to upgrade their Live Health client software. If you have created Live Exceptions Notifier rules to run scripts that are specified by hard-coded paths relative to the previous release of eHealth, move the scripts to the eHealth r6.2.2 home directory and update those rules. Authorize eHealth web users to use new functions of the eHealth web user interface, as appropriate. If you copied the installation DVDs to local disk directories, delete those directories to free disk space. If you plan to discover and poll SNMPv3 elements, you must install and configure the Distributed SNMPv3 Security Pack software (available from SNMP Research International) on your eHealth system. For more information, see the product documentation.
Additional Tasks
(Solaris only): If your eHealth system is part of a High Availability cluster that has Sun cluster software installed, you must upgrade to the latest CAehealthHA Solaris package installed with eHealth r6.2.2. Note: For more information, see the eHealth High Availability and Disaster Recovery Administration Guide.
(Optional) After eHealth r6.2.2 is polling normally and reports run well for a few days, remove the previous release of eHealth to regain disk space.
Appendix A: Administration Tasks Reference

Tasks to Perform Before You Install or Upgrade eHealth
Before you install or upgrade eHealth, perform the following tasks: Check the File System Format (Windows) (see page 83) Change the eHealth System Hostname (Windows) (see page 84) Add Swap Space (Windows and UNIX) (see page 84) Check and Modify Kernel Requirements (UNIX) (see page 87) Mount the DVD Drive (UNIX) (see page 93) Unmount the DVD Drive (UNIX) (see page 98)
Note: Before installing the eHealth software, you must create an eHealth administrator account. To create a user group and the eHealth administrator account on your system, see your system administrator. Several of the UNIX-specific procedures require root privileges. If you do not know the password for root, ask your UNIX system administrator for assistance.
Check the File System Format (Windows)

The disks on which you install the eHealth and Oracle 10g software must use the Windows NTFS format. To check that a disk uses NTFS 1. Open My Computer from the Start menu. 2. Select a disk on which you want to install some or all of the eHealth software, and right-click to display the shortcut menu. 3. Select Properties. 4. Select the General tab, and verify that the value for File system is NTFS. If the disk uses the File Allocation Table (FAT) file system format, you must use the Windows convert command to convert it to NTFS format. For instructions, see your Windows documentation.
Appendix A: Administration Tasks Reference 83
Change the eHealth System Hostname (Windows)

Your eHealth system must use a valid hostname. Hostnames can contain the characters AZ, az, 09, and dashes (). Hostnames cannot contain spaces, periods (.), and underscores (_). If your hostname contains invalid characters, you must change it before installing eHealth. To change the hostname of your eHealth system 1. Select Start, Control Panel, System from the Windows desktop. The System Properties dialog appears. 2. Select the Computer Name tab; then click Change. The Computer Name Changes dialog appears. 3. Change the hostname in the Computer name field. 4. Click OK. The hostname is changed.
Add Swap Space (Windows and UNIX)

Swap space (or virtual memory storage file) is temporary storage used when a systems memory requirements exceed the size of available RAM. Systems swap processes and datafiles between the swap space and the physical memory as needed. The amount of swap space a system has is dependent upon the system configuration. Use the eHealth Sizing Wizard to determine your system requirements. If your system has less than the recommended amount of available swap space, you must add more swap space by locating additional unused disk space. The sum of your current swap space and the unused disk space must equal the swap space requirements for your configuration. When you add swap space, you must change the virtual memory paging file size. To do so, you must be logged on as a user who is a member of the Administrators group. Note: For more information, see Using the eHealth Sizing Wizard. To add swap space to a Windows system 1. Log on to the eHealth system as the a user with administrative privileges. 2. Select Start, Control Panel, System. The System Properties dialog appears.
3. Select the Advanced tab and under Performance, click Settings. The Performance Options dialog appears. 4. Select the Advanced tab. Under Virtual Memory, click Change. 5. Select the desired drive from the Drive list. For optimal performance, specify a drive other than the one on which you plan to install eHealth. 6. Click Custom Size under Paging File Size for Selected Drive and specify a value in the Initial Size field that is at least the size recommended by the eHealth sizing wizard. 7. Click Set and then click OK. 8. Click OK in the Performance Options dialog. 9. Click OK in the System Properties dialog. Swap space is added. For more information about virtual paging files, see your Windows documentation. To add swap space to a Solaris UNIX File System (UFS) 1. Log on to the eHealth system as root and execute the following command to locate disks with unused space:
df -k
A list of disks appears. 2. Execute the following command:

mkfile size [k|m|b] swapFilePath/swapFileName
size Represents the number of bytes to be allocated, but it can be flagged as KB, MB, or blocks, with the k, m, or b suffixes, respectively. swapFilePath/swapFileName Represents the full path and file name for the additional swap file. 3. Edit the /etc/vfstab file to add the following line:
swapFilePath/swapFileName - - swap - no -
4. Enable the new swap file by executing this command:

swap -a swapFilePath/swapFileName
The swap file is now in use. 5. Confirm the swap space settings by executing this command:
swap -l
Swap space is added. For details on allocating additional swap space, see the administration manual provided with your Solaris system.
To add swap space to a Solaris Zettabyte File System (ZFS) 1. Remove the swap area by executing this command:
swap -d /dev/zvol/dsk/rpool/swap
2. Confirm that the swap area is removed by executing this command:

$ swap -l
The following message appears: No swap devices configured 3. Resize the swap volume, as shown in the following example:
$ zfs set volsize=6G rpool/swap
4. Activate the swap area by executing this command:

$ swap -a /dev/zvol/dsk/rpool/swap
5. Confirm the swap space settings by executing this command:

$ swap -l
The following information appears:

swapfile dev /dev/zvol/dsk/rpool/swap 182,2 swaplo 8 blocks 2097144 free 2097144
To add swap space to an HP-UX system Use the SAM tool to add swap space to an HP-UX system. For complete instructions, see the administration manual provided with your system. 1. Log on to the eHealth system as root and start the SAM tool by entering the following command:
/usr/sbin/sam
2. Select Disks and File Systems, Swap, Actions, Add File System Swap. A list of file systems appears. 3. Select the file system to use for swap from the list. 4. Specify values for Minimum Swap (Mbytes) and Maximum Swap (Mbytes). 5. Specify the swap priority. 6. Specify the time at which you want to enable swap and click OK. Swap space is added to the system. For details on allocating additional swap space, see the administration manual provided with your HP-UX system.
Check and Modify Kernel Requirements (UNIX)

Before you install eHealth r6.2.2, run the prerequisite checker program to determine if your system meets the minimum requirements. The checker verifies that the kernel parameter values on your system are configured for at least the required minimums. If they are not, the checker generates a list of recommended configuration adjustments. If your kernel parameters are not set for the required minimums, you must modify them. This section describes how to modify kernels on Solaris and HP-UX systems. For more information about modifying kernels on your system, see your system documentation.
Solaris Kernel Requirements

Solaris systems often use a default maximum shared memory segment of 1,048,576. You must modify your kernel to increase the maximum shared memory segment and change the settings of other parameters. The following table summarizes the required settings for a Solaris kernel:
Parameter maxusers shmmni shmmax semmsl semmni
Minimum Setting Parameter Description 2048 128 25% of RAM 512 128 Maximum number of users Number of shared memory identifiers Maximum shared memory segment Maximum number of semaphores, per ID Number of semaphore identifiers
Modify a Solaris Kernel

To simplify the process of setting kernel parameters on Solaris systems, eHealth provides a template file on the eHealth Software DVD containing the appropriate kernel settings. By using the template file as described in this section, you reduce the chances of making a simple syntax or formatting error that might cause the installation to fail. To modify your kernel parameters 1. Perform one of the following actions: Replace your existing system configuration file with the template etc_system.SunOS file, and edit the file as necessary to define other parameters required for your site. (This method is recommended if you have made few changes to your etc_system.SunOS file.) Copy and paste kernel settings from the template file to your existing etc_system.SunOS file (this may be easier if you have made many changes to your etc_system.SunOS file). Note: If you are running Solaris 2.10, the recommended way of setting IPC resource control limits is now through projects. Edits made to the etc_system.SunOS file are still valid but force a reboot to enable the parameters. For additional information, see your system documentation or contact your system administrator. 2. Log in to your system as root. 3. Mount the eHealth Software DVD. 4. Enter the following command to create a backup of your kernel parameter file, where date is todays date:
cp /etc/system /etc/system.orig.date
5. Do one of the following to make a copy of the template file: If you use Solaris with Volume Management, run the following command, including the DVD label after /cdrom. For example:
cp /cdrom/cdLabel/eHealth/etc_system.SunOS /etc/system
Otherwise, use the following command:

cp /cdrom/eHealth/etc_system.SunOS /etc/system
6. Use a text editor to check the /etc/system.orig.date file for any parameters that are not defined in the new etc_system.SunOS file. Copy and paste these parameters into the new etc_system.SunOS file.
7. Save your changes to the etc_system.SunOS file. Important! In the etc_system.SunOS file, spaces before or after commands or empty lines at the end of the file will cause the script to fail. Remove any spaces or empty lines before saving the file. 8. Enter the following command to reboot the system and reconfigure the Solaris kernel:
shutdown -i6 -g1 -y
To copy and paste kernel settings from the template file 1. Log in to your system as root. 2. Mount the eHealth Software DVD. 3. Enter the following command to create a backup of your kernel parameter file, where date is todays date:
cp /etc/system /etc/system.orig.date
4. Do one of the following to append the contents of the template file to the existing system file: If you use Solaris with Volume Management, use the following command, including the CD label after /cdrom. For example:
cat /cdrom/cdLabel/eHealth/etc_system.SunOS >> /etc/system
Otherwise, use the following command:

cat /cdrom/eHealth/etc_system.SunOS >> /etc/system
5. Review the contents of the etc_system.SunOS file by using a text editor. The kernel parameters defined for eHealth appear after the following text:
# Added for eHealth
Confirm that these kernel parameters are not defined elsewhere in the file. If a parameter is already defined in the file, insert an asterisk (*) before that line to disable it. 6. Save your changes to the etc_system.SunOS file. Important! In the etc_system.SunOS file, spaces before or after commands or empty lines at the end of the file will cause the script to fail. Remove any spaces or empty lines before saving the file. 7. Enter the following command to reboot the system and reconfigure the Solaris kernel:
sync; sync; shutdown -i6 -g1 -y
HP-UX Kernel Requirements

The following are the minimum kernel requirements for HP-UX systems:
Parameter MSGSEG MSGTQL MSGMAP MAXUPRC NCALLOUT SEMMNS SEMMNI SEMMAP
Required Setting 32,767 NPROC (MSGTQL + 2) ((NPROC*9)/10) (16 + NKTHREAD) (SEMMNI*2) 4,096 (SEMMNI+2)
Parameter Description Number of segments available for messages Number of message headers Maximum number of message map entries Maximum number of user processes Maximum number of pending timeouts Number of semaphores in the system Maximum number of semaphore sets in the entire system Maximum number of semaphore map entries Maximum number of processes
NPROC DBC_MAX_PCT
4,096
13 for a 1 GB system Maximum dynamic buffer cache size 7 for a 2 GB system as a percent of system RAM size 5 for a 3 GB system 4 for a 4 GB system
DBC_MIN_PCT KSI_ALLOC_MAX MAX_THREAD_PR OC MAXDSIZ
2 (NPROC*8) 256 Varies based on the amount of physical memory: 0xC0000000 for a 3 GB or greater system
Minimum dynamic buffer cache size as a percent of system RAM size System-wide limit of queued signals that can be allocated Maximum number of kernel threads allowed per process Maximum data segment size for 32-bit systems in bytes
Parameter
Required Setting 0x80000000 for a 2 GB 0x40000000 or a 1 GB
Parameter Description
MAXDSIZ_64BIT MAXSSIZ MAXSSIZ_64BIT MAXSWAPCHUNK S MAXUSERS MESG MSGMNI NCSIZE
2,147,483,648 (or 0x80000000) 170,000,000 (or 0xa21fe80) 1,073,741,824 (or 0x40000000) 16,384 32 or greater 1 NPROC
Maximum data segment size for 64-bit systems in bytes Maximum stack segment size for 32-bit systems in bytes Maximum stack segment size for 64-bit systems in bytes Maximum number of swap chunks Maximum number of users Message feature indicator Number of message queue identifiers
((8*NPROC+2048)+ Directory Name Lookup Cache VX_NCSIZE) (DNLC) space needed for inodes. (The default value for VX_NCSIZE is 1,024) (15*NPROC+2048) 4,096 (8*NPROC+2048) Maximum number of open files Maximum number of file locks available on the system Maximum number of open inodes
NFILE NFLOCKS NINODE NKTHREAD SEMA SEMMNU SEMVMX SHMEM SHMMAX
(((NPROC*7)/4)+16 Maximum number of kernel threads ) supported by the system 1 (NPROC-4) 32,768 1 Varies based on the amount of physical memory: 0xFFFFFFFF for a 4 GB system Semaphore feature indicator Number of semaphore undo structures Maximum value of a semaphore Shared memory feature indicator Maximum allowable size of one shared memory segment in decimal bytes
Parameter
Required Setting 0xC0000000 for a 3 GB system 0x80000000 for a 2 GB system 0x40000000 for a 1 GB system
Parameter Description
SHMMNI SHMSEG
512 200
Maximum number of shared memory segments in the system Maximum number of shared memory segments to which one process can attach Maximum system-selected page size in KB Number of bytes reserved for directory pathname cache used by the VxFS file system
VPS_CEILING VX_NCSIZE
64 1,024
Modify an HP-UX Kernel

On HP-UX systems, eHealth requires that you use a 64-bit kernel. This section describes how to verify that you are using a 64-bit kernel and how to modify the HP-UX configuration kernel. To modify HP-UX kernels, use the System Administration Manager (SAM) tool, which is an optional package for HP-UX. Note: Before you modify the configuration, you must load the package containing the SAM tool. If you did not load this package, refer to the system administration manual that was provided with your HP-UX system. To verify that you are using a 64-bit kernel 1. Log in to the eHealth system as root. 2. Enter the following command:
getconf KERNEL_BITS
If the command returns 64, you are using a 64-bit kernel and you should verify the configuration of it. If the command returns a different value, you need to upgrade to a 64-bit kernel. For more information, refer to your HP-UX documentation.
To modify the configuration of an HP-UX kernel 1. Log on to your system as root. 2. Start the SAM tool by entering the following command:
/usr/sbin/sam
3. Select Kernel Configuration, Configurable Parameters. 4. Change the value of a parameter by selecting it from the list and selecting Actions, Modify Configurable Parameter. 5. Press Enter to apply the changes, and click OK. 6. Select Actions, Create a New Kernel. 7. Click Yes when the system prompts you to reboot the kernel.
Mount the DVD Drive (UNIX)

To help ensure that your system can access the DVD, mount the DVD drive on a directory. After inserting the DVD into the drive, use the mount command and specify that directory. Mount a DVD drive on the existing /cdrom directory. If that directory does not exist, create it. This section includes the following topics: Verify That the DVD Directory Exists (see page 93) Verify That the DVD Drive is Mounted (see page 94) Mount the DVD Drive Locally (see page 95) Mount the DVD Drive from a Remote System (see page 96)
Verify That the DVD Directory Exists

The DVD is normally mounted to the /cdrom directory. To verify that the /cdrom directory exists on your system, enter the following command:
ls /
This command lists the files and directories under the root directory. If the /cdrom directory exists on your system, it appears in the list of directories. If the /cdrom directory is not listed, you must create it.
To create the /cdrom directory 1. Log on to the eHealth system as root. 2. Enter the following command in a terminal window:
mkdir /cdrom
The directory is created.
Verify That the DVD Drive is Mounted

Before you can install eHealth, you must mount the DVD drive on the /cdrom directory of a Solaris system. Note: Before you perform this procedure on a Solaris system, turn off Volume Management. To verify that the DVD drive is mounted 1. Display the list of mounted file systems by entering the following command:
/etc/mount
2. Verify whether the DVD drive is mounted on your system by checking the mount command output. Use the following sample output as a guideline:
/dev/sr0 on /cdrom
Note: /dev/sr0 is the standard default names for the DVD device drivers. If the DVD drive is mounted from a remote system, the mount command displays output similar to the following, where server is the name of the remote system:
server:/cdrom on /cdrom
3. Do one of the following: If the DVD drive is mounted, begin the software installation process. If the DVD drive is not mounted, do one of the following: If the drive is connected to your system, mount it by following the instructions in the section Mount the DVD Drive Locally (see page 95). If the drive is connected to another system, mount it by following the instructions in the section Mount the DVD Drive from a Remote System (see page 96).
Mount the DVD Drive Locally

This section describes how to mount the DVD drive on a Solaris system. To mount a DVD drive that is locally connected to a Solaris system 1. Log on to the eHealth system as root and insert the eHealth Software DVD that includes the InstallPlus program into the DVD drive. 2. Create a DVD mount point, if necessary, by entering the following command:
mkdir /cdrom
cdrom Represents the mount point. The DVD mount point is created. 3. Mount the DVD drive. Use the following command as a guideline, depending on your system:
/etc/mount -F hsfs -r /dev/sr0 /cdrom
Note: /dev/sr0 or /dev/dsk/c0t6d0s0 are the default names for the Solaris DVD device driver. Depending upon your system setup, you may need to contact your UNIX system administrator to obtain the appropriate DVD device name. If the mount command fails, see your system documentation for the appropriate command. The DVD drive is mounted. If the system does not recognize the DVD after you have followed these instructions (the system displays a device busy message), restart the system and try again.
Mount the DVD Drive from a Remote System

To mount the eHealth Software DVD over a network file system (NFS), you must first examine and load the exports file on the remote system, as well as mount the DVD drive on both the remote and local system. You must have root privileges on the NFS server to mount the DVD. To examine and load the exports file on the remote system 1. Log on to the remote system as root and change to the appropriate directory by entering one of the following commands: Solaris: cd /etc/dfs HP-UX: cd /etc
The directory is changed. 2. List the exports file on the remote system by entering one the following commands: Solaris: ls dfstab HP-UX: ls exports
The list appears. If the file is not listed, use a text editor to create the file. 3. Confirm that the exports file contains one of the following lines: Solaris: share -F nfs -o ro /cdrom HP-UX: /cdrom -ro
If it does not contain the line, or if you created a new file in Step 2, use a text editor to add this line to the end of the file. 4. Load the exports file on the remote Solaris system by entering one of the following commands: Solaris: shareall HP-UX: The file is automatically loaded. To verify, enter the following command:
usr/etc/showmount -e If the file is not loaded, enter the following: exports -o ro /cdrom
The exports file is loaded on the remote system.
To mount the DVD drive on the remote system 1. (HP-UX systems only) Examine the contents of the /etc/checklist file by entering the following command:
grep /cdrom /etc/checklist
The command produces output that is similar to the following:

device /cdrom cdfs ro
device Specifies the name of the DVD device driver. If this output does not appear, use a text editor to add this line to the end of the /etc/checklist file. If the line is disabled, with a pound (#) character, edit the file to remove the pound character. 2. Mount the DVD drive by using one of the following commands as guidelines: Solaris: /etc/mount -F hsfs -r /dev/sr0 /cdrom HP-UX: /etc/mount /dev/dsk/c201d2s0 /cdrom -r -t cdfs
Note: /dev/sr0 and c201d2s0 are the standard default names for the DVD device drivers. If the mount command fails, see your system documentation for the appropriate device driver. 3. Log off of the remote system. The remote system DVD drive is mounted. To mount the DVD on your local system 1. Log on to the local system as root. 2. Mount the DVD drive by entering the following command, where server is the name of the remote system:
/etc/mount server:/cdrom /cdrom
The DVD is mounted on the local system.
Tasks to Perform After You Install or Upgrade eHealth
Unmount the DVD Drive (UNIX)

For some UNIX systems you must unmount the DVD drive to eject the DVD in the drive. To unmount a DVD drive 1. Enter the following command to move to another directory if your current directory is the /cdrom directory:
cd /
2. Unmount the DVD drive by entering the following command:

umount /cdrom
If the DVD drive is mounted to a Solaris system running Volume Management, enter the following command to eject the disc:
eject
3. Remove the eHealth DVD from the drive. The DVD drive is unmounted.

After you install or upgrade eHealth, perform the following tasks: Specify the Mail Server (Windows) (see page 99) Specify the Printer (Windows) (see page 100) Change the Web Server Port Number (Windows and UNIX) (see page 101) Enable the FtpCollector to Run on Solaris 5.9 and Solaris 10 (see page 103) (Optional) Enable and Configure Authentication Options (see page 104)
Specify the Mail Server (Windows)

If you did not specify the name of your SMTP mail server during the eHealth installation, set the NH_NT_SMTP_SERVER environment variable to specify the SMTP server name. This variable defines the SMTP server that eHealth uses to send email messages. To set the NH_NT_SMTP_SERVER environment variable 1. Open the Environment Variables dialog by doing the following: a. b. c. From the Windows desktop, select Start, Control Panel, System. Select the Advanced tab. Click Environment Variables.
2. Look for the NH_NT_SMTP_SERVER variable under System variables; then select one of the following options to specify the name of your mail server: If the variable is not defined, add it as follows: Select any system variable, and then click New. The New System Variable dialog appears. Enter the variable NH_NT_SMTP_SERVER in the Variable Name field of the New System Variable dialog. Specify the name of your SMTP mail server (for example, yellow.xyzcorp.com) in the Variable Value field. Click OK.
If the variable is defined, edit its value as follows: Select the NH_NT_SMTP_SERVER variable in the list. Click Edit. The Edit System Variable dialog appears. Specify the name of your SMTP mail server (for example, yellow.xyzcorp.com) in the Variable Value field. Click OK.
3. Click OK to close the Environment Variables dialog. 4. Click OK to close the System Properties dialog. 5. Stop and restart the eHealth server to enable the NH_NT_SMTP_SERVER variable. The mail server is specified.
Specify the Printer (Windows)

If you did not do so during the eHealth installation, specify the name of your printer. If you use a network printer, the name must include the network print server and print share name. To determine the print share name 1. Select Start, Printers from the Windows desktop. 2. Right-click the icon for the printer that you want to use and select Properties from the shortcut menu. The Properties dialog opens. 3. Select the Sharing tab. 4. Record the value shown in the Shared as field. This is the print share name. Use this name when specifying a network printer for use with eHealth. To set the NH_PRINTER environment variable 1. Open the Environment Variables dialog: a. b. c. Select Start, Settings, Control Panel from the Windows desktop. Select System and the Advanced tab. Click Environment Variables.
2. Look under System variables for the NH_PRINTER variable. 3. Do one of the following: If the variable is not defined, add it as follows: Select any system variable and click New. Enter the following variable in the Variable Name field: NH_PRINTER Click OK.
If the variable is defined, specify the name of your printer as follows: Select the NH_PRINTER variable in the list. Click Edit. Specify the name of your printer in the Variable Value field of the Edit System Variable dialog. Use the print share name. For example, \\purple\1188-CP1120 Click OK.
4. Click OK to close the Environment Variables dialog.
5. Click OK to close the System Properties dialog. 6. Stop and restart the eHealth server to enable the NH_PRINTER variable. The printer is specified.
Change the Web Server Port Number (Windows and UNIX)

During a new installation, eHealth installs and configures the Apache web server (on Windows systems it automatically starts upon reboot of the system). However, if another web server or process is using the default web port (80), you must specify another port number and start the server manually. To change the Apache web server port number on Windows 1. Open the Environment Variables dialog: a. b. c. From the Windows desktop, select Start, Control Panel, System. Select the Advanced tab. Click Environment Variables.
2. Select NH_HTTP_PORT under System variables and then click Edit. 3. Specify the port number that you want the Apache web server to use in the Variable Value field. 4. Click OK in the Edit System Variable dialog. 5. Click OK in the Environment Variables dialog. 6. Click OK in the System Properties dialog. 7. Regenerate the web server configuration file to reflect the new port number: a. b. Open a command prompt window. Enter the following command:
ehealth/bin/ nhHttpdCfg -user %NH_USER% -grp Administrators -nhDir /ehealth -outFile /ehealth/web/httpd/conf/httpd.conf
ehealth Represents the installation directory for eHealth r6.2.2. Note: Enter the command on one line. Do not press Enter to match the formatting shown in the example. 8. Start the Apache web server manually by using the Services dialog. The web server file is changed to reflect the new port number.
9. Verify that the Apache web server is set to start automatically when you restart the eHealth system: a. Select Start, Control Panel, Administrative Tools, Services. The Services dialog appears. b. c. d. Select eHealth httpd61. Select Action, Properties if the Startup Type is not set to Automatic. Select Automatic from the Startup type list and then click OK.
To change the Apache web server port number on UNIX 1. Log on as the eHealth administrator. 2. Edit the nethealthrc.sh.usr file to set the NH_HTTP_PORT environment variable to the port that you want to use for your web server. For example, enter this definition in the nethealthrc.sh.usr file to set NH_HTTP_PORT to use port 80:
NH_HTTP_PORT="80"; export NH_HTTP_PORT
Note: You must set this variable in the nethealthrc.sh.usr file. You cannot set it directly in the httpd.conf file. 3. Enter the following command to regenerate the web server configuration file to reflect the new port number:
nhHttpdCfg -user ehUser -grp group -nhDir ehealth -outFile ehealth/web/httpd/conf/httpd.conf
ehUser Represents the name of the eHealth administrator account. group Represents the name of the primary group of which the eHealth administrator account is a member. ehealth Represents the full path of the eHealth installation directory. Note: Enter the command on one line. Do not press Enter to match the formatting shown in the example. The file reflects the new port number. 4. Enter the following command to start the web server:
nhHttpd start
Note: If you start the web server from the command line, you must use this command to restart it when it stops or after the system reboots. The port number is changed.
Enable the FtpCollector to Run on Solaris 5.9 and Solaris 10

After installing eHealth, you must enable the FtpCollector to run on Solaris 5.9 and Solaris 10 machines. Note: HP-UX does not support CNDC, so the FtpCollector cannot run on HP-UX machines. To enable the FtpCollector to run on Solaris 5.9 1. Do the following as root in $NH_HOME/modules/cndc/bin: Execute the following command to set the uid bit for FTP Collector:
chmod u+s FtpCollector
Execute the following command to set the owner as root:

chown root FtpCollector
2. Do the following as root in /opt: Execute the following command to find the location of oracle home:
echo $ORACLE_HOME
If a value is not returned, log on as the eHealth user and find the value by executing the command. Then, as root, execute the following command:
ln -s <value of ORACLE_HOME> eHealth-oracle
To enable the FtpCollector to run on Solaris 10, modify /etc/user_attr to give the eHealth user privileged port access. The following commands should be able to start and stop the FtpCollector when run as nhuser: nhServer start nhManageCndc -start FTP (or ALL) nhReset
The FtpCollector should start and run as nhuser without logging any information about switching between users at startup. On Windows, which has no concept of privileged ports, the FTP Collector service should start without mention of switching users at startup.
Authentication Options
eHealth offers the following integration options for authentication: CA Spectrum to eHealth one-way single authentication support eHealth SAML support eHealth RADIUS support
All three methods let you use CA Spectrum, but only the CA Spectrum to eHealth one-way single authentication option lets you drill down from CA Spectrum OneClick to the eHealth Web user interface without providing additional credentials. The RADIUS and SAML options prompt you for credentials every time you drill down from CA Spectrum to eHealth.
How To Enable One-way Authentication from CA Spectrum to eHealth

The limited CA Spectrum to eHealth single authentication option provides one-way drill-down from CA Spectrum to eHealth through CA EEM. This integration lets you use CA Spectrum to access the eHealth Web user interface without being challenged for a user login. This authentication option is not bi-directional. Note: CA EEM offers support for several types of authentication, including LDAP. User name synchronization across eHealth, CA EEM and CA Spectrum must be maintained. Note: Although OneClick for eHealth user names and Web UI user names are case-sensitive, CA EEM treats user names as case-insensitive for validation purposes. To enable a CA Spectrum user to take advantage of this feature, the following process must occur: 1. If the user does not already have an eHealth web user account, the administrator must establish one for the user. 2. To help ensure that the user can access all features available through the eHealth Web user interface, the administrator must enable those privileges by configuring the CA Spectrum users web user account appropriately. 3. The user must have three identical user accounts (with the same user name) for the CA EEM server, eHealth Apache web server, and CA Spectrum user database server.
4. The CA Spectrum administrator for the system must install CA EEM software and follow the installation procedures in the CA EEM documentation. CA EEM must be installed on a separate, standalone server system. Note: If you want to use LDAP authentication with the integration, you must configure the CA EEM server accordingly. For more information, see the CA EEM documentation. 5. The eHealth administrator for the system must run the nhWebSso command line utility to enable the CA Spectrum eHealth system to use one-way drill-down authentication.
Install CA EEM Software

CA EEM is a proprietary software product that enables a limited one-way single authentication drill-down option from CA Spectrum to the eHealth Web user interface. Note: For information about the required version of CA EEM and download information, see the eHealth Release Notes. For information about configuring eHealth and CA Spectrum to use SSO with CA SiteMinder, contact CA Services.
Run the nhWebSso Command Line Utility

The CA Spectrum to eHealth one-way single authentication support and the eHealth SAML support use the nhWebSso utility to enable or disable the authentication option on an eHealth Apache server. This command has the following format and must be executed on your eHealth server:
nhWebSso [ -h ] [ -rev ] | { -hostname hostName [-idleTimeout idleTimeout] [-disableFallback] } | -disable
-h (Optional) Displays this command usage. -hostname hostName (Required if -disable is not specified.) Specifies the fully qualified hostname of a CA EEM backend server. -idleTimeout idleTimeout (Optional) Specifies the idle timeout (in minutes) before the user is rechallenged for authentication when accessing eHealth from an external application. Default: 10 minutes -disableFallback (Optional) Specifies that single authentication fallback is disabled. -disable Disables single authentication when specified. Example: Enable Support
nhWebSso -hostname hostName -idleTimeout 10 -disableFallback
Example: Disable Support

nhWebSso -disable
SAML Authentication
eHealth SAML is a web user authentication option that uses Security Assertion Markup Language (SAML) for exchanging the credentials information (SAML assertions) between different web sites. The primary use case for SAML is for Single-Sign-On (SSO) across multiple domains or firewall. Note: For information about supported SAML versions, see the Release Notes. eHealth SAML support provides the capability of integrating the eHealth Apache server as a SAML Destination Site (or Relying Party). The eHealth Apache server is also a SAML compliant web site. Since eHealth SAML support is not intended to be a eHealth general SSO solution, eHealth SAML support uses SAML primarily for web user authentication instead of SSO. With SAML, the authentication process is done inside a SAML Source Site and only the Source Site stores (or has access to) the users' passwords. The Source Site provides a user's authenticity (assertions) in the form of XML to the SAML Compliant Destination Site. In general, you must access a SAML Source Site for authentication before you can access the resources on a SAML Destination Site, like eHealth. Note: For more information about how SAML deploys a single Source Site and multiple Destination Sites, see the SAML documentation.
Requirements and Considerations for SAML Support

You must meet the following requirements before you enable the eHealth SAML support module: You must install and configure a working Identity and Access Management (IAM) system with a user directory or database. This system must be installed as the SAML Source Site. The following are a few of the commercially available IAM systems: CA SiteMinder Federation Security Services Oracle COREid Federation (formerly Oblix) RSA ClearTrust Federated Identity Manager
You must install and configure a working SAML-compliant CA EEM server (see page 105). Note: For information about supported versions of CA EEM, see the Release Notes.
You must install an eHealth server that includes eHealth SAML support. This system must be installed as the Destination Site. The IAM and CA EEM servers must be installed on two different standalone servers, and must be on separate systems from your eHealth server.
No proxy server can reside between the eHealth Apache server and the CA EEM server. A X.509 certificate is required for the IAM system. This certificate must also be imported to the CA EEM server in which the assertion is validated. Network connectivity must be established between the eHealth, CA EEM, and IAM servers. The IAM and CA EEM systems must be configured to use the same user directory so that HTTP Basic Access Authentication is possible. eHealth user accounts must be imported to the IAM and CA EEM user directories. This task must be completed manually on each server. Identical web user names must exist on the eHealth, CA EEM, and IAM servers. You must manage passwords from the IAM server. A web browser (HTTP) cookie must be enabled in the browser.
Additionally, the following should be considered: When eHealth SAML support is enabled, RADIUS support is automatically disabled. User accounts update must be manually maintained and synchronized. Changes made to eHealth user accounts from OneClickEH do not automatically trigger the same update on the CA EEM or IAM servers. eHealth SAML support uses the Browser/Artifact Profile as defined by the supported SAML specification. Other profile types are not supported. Note: For more information about supported versions of SAML, see the Release Notes. eHealth SAML support assumes the assertion (SAML Artifact) sent to the eHealth server will be in the form of a URL query string, and the name "SAMLart" is the only supported name used for the SAML Artifact. For example: http://www.eHealth.com/web/frames?SAMLart=AAEdIy2DbBdHQNcZwPMU 6y9Q/uaK+gsj+scBo+HtpbqT38u0E6wyNNd6 The policies for user names and passwords can vary between the eHealth, IAM, and CA EEM servers. When you create or update a user account, you must make sure it complies with all policies.
eHealth Integration as a SAML Destination Site

The following are some key notes for integrating and configuring the eHealth web server as a SAML Destination Site. Only the Browser/Artifact Profile (defined in SAML 1.1 specifications) is supported. The SAML artifact must be sent to eHealth Apache server only as part of the eHealth URL link for requesting eHealth resources in the following form: http://<eHealth server>?SAMLart=<a valid and not-expired SAML Artifact> For example: http://www.eHealth.com/web/frames?SAMLart=AAEdIy2DbBdHQNcZwPMU 6y9Q/uaK+gsj+scBo+HtpbqT38u0E6wyNNd6 Only the Source-Site-First Scenario (defined in SAML 1.1 specifications) is supported. End users are always authenticated by the Source Site first and are then able to access a Destination Site's resource through a remote URL link on the Source Site's web portal. If end users attempt to access the eHealth server (Destination Site) directly, they are not authenticated by a SAML artifact. Instead, the standard Apache HTTP Basic Authentication is imposed and the users are authenticated against the user directory configured in the CA EEM server. For this reason, eHealth SAML support requires that the CA EEM server and the IAM system on the Source Site must be configured to use the same user directory. If the Oracle COREid Federation is used as the IAM system on the Source Site, you can use the Inter-site Transfer Service to do a click-through Destination Site Redirect with automated assertion generation. eHealth SAML support provides a SAML Authentication Service html page at: http://www.eHealth.com/SAMLAuthServices.html. You can configure this html page as the Receiver URL of the eHealth Destination Site. If you use the Inter-site Transfer Service, the resulting URL from this Inter-site Transfer Service must be in the following form: Receiver URL: http://<your eHealth server>/output/SAMLAuthServices.html For example: http://www.eHealth.com/SAMLAuthServices.html?TARGET=DetinationReso urce&SAMLart=artifact The end user is then authenticated with the artifact appended in this URL and is granted access to the Destination Resource.
How to Configure SAML Support

After you meet the requirements and configure user directories with account information, you can implement eHealth SAML support.
To configure eHealth SAML support in your environment, do the following: 1. Synchronize the user names between the eHealth database and the CA EEM and IAM user directories. This task must be done manually. 2. If you are using a CA Spectrum server with an eHealth server and want to enable SAML support, you must synchronize the CA Spectrum user accounts with the eHealth, CA EEM, and IAM servers. 3. Enable eHealth SAML support in eHealth by using the nhWebSso utility (see page 106).
Log In to eHealth Using SAML

When eHealth SAML support is enabled, a user logs in to a SAML Source Site for authentication and then accesses eHealth (the SAML Destination Site) through a remote URL link created on the SAML Source Site. Note: It is the responsibility of the third-party integrator to generate a proper eHealth URL link on the SAML Source Site with a valid SAML Artifact appending to this URL link. The third-party integrators point of view expects the end user to always access eHealth resources through a URL link on the Source Site. The standard way of accessing eHealth (through the eHealth Web user interface) with the use of Apache default HTTP Basic Access Authentication is still supported. However, an end user going directly through the eHealth Web user interface is not authenticated through SAML authentication. Additionally, the following eHealth components do not authenticate an end user by using SAML: OneClick for eHealth (OneClickEH) eHealth Live Clients CA Spectrum OneClick
RADIUS Authentication
Remote Authentication Dial In User Service (RADIUS) support provides the eHealth web server (Apache) with the option of authenticating web users against an external RADIUS server. When RADIUS support is enabled, the authentication process is performed and shifted from the internal eHealth Apache server to the RADIUS server, without change to the end-user experience. Note: Authentication through RADIUS is supported only on Solaris systems. The RADIUS server software is not bundled in the eHealth kit. It must be installed and configured separately from eHealth.
Requirements and Considerations for RADIUS Support

You must meet the following requirements before you enable the eHealth RADIUS support module: You must install eHealth on a Solaris system. The RADIUS server must be installed on a separate system from the eHealth server. No proxy server can reside between the eHealth Apache server and the RADIUS server. Network connectivity must be established between the eHealth and RADIUS servers. Identical web user names must exist on the eHealth and RADIUS servers. You cannot rename web users in eHealth when using eHealth RADIUS support. A fully qualified domain name (FQDN) is required to access the Apache server. A web browser (HTTP) cookie must be enabled in the browser. You must manage passwords from the RADIUS server. When eHealth RADIUS support is enabled, eHealth SAML support and eHealth SPECTRUM Single Sign-On (SSO) support are automatically disabled. The policies for user names and passwords can vary between the eHealth, an IAM, and CA EEM servers. When you create or update a user account, make sure it complies with all policies.
How to Configure RADIUS Support

After you meet the requirements, you can configure and enable eHealth RADIUS support. To configure eHealth RADIUS support in your environment, do the following: 1. Configure a user directory on the RADIUS server. The directory must be configured with a flat text file that contains user profiles, LDAP, or SQL server data. eHealth support for RADIUS fails if the Radius server installation or configuration is invalid. Note: For information about how to configure a user directory on RADIUS, see the RADIUS documentation. 2. Synchronize the user names between the eHealth database and the RADIUS user directory. This task must be done manually. You might need to reset user identities in certain situations.
3. Synchronize the CA Spectrum user accounts with the eHealth and RADIUS servers if you are using a CA Spectrum server with an eHealth server and want to enable RADIUS support. Note: eHealth CA Spectrum SSO does not authenticate with the RADIUS server. Instead, the default CA Spectrum authentication is used to log in to CA Spectrum OneClick. When users drill down to eHealth, they are prompted for RADIUS credentials. 4. Enable eHealth RADIUS support in eHealth by using the nhWebRadius utility (see page 112).
Run the nhWebRadius Command Line Utility

After you configure RADIUS and synchronize user accounts, you must enable eHealth RADIUS support so that users can log in by using their RADIUS credentials. The eHealth command prompt utility nhWebRadius enables RADIUS support and modifies the directives in httpd.conf to direct Apache to load and authenticate by using the eHealth Apache module mod_auth_radius. This utility configures eHealth to use a Radius server as an external authentication server. The following information is required: RADIUS Server Hostname RADIUS client shared secret This command has the following format and must be executed on your eHealth server:
nhWebRadius [ -h ] [ -rev ] | { -hostName Host Name [-port Port Number] sharedSecret Shared Secret -authTimeout Authentication Timeout -authRetries Authentication Retries [-CookieTimeout CookieTimeout] [-disableFallback] } | -disable
-h (Optional) Displays this command usage. -hostName Host Name (Required) Specifies the fully qualified hostname of a RADIUS back-end server. This option is required if you do not specify the -disable argument. -port Port Number (Optional) Specifies the port number of a RADIUS back-end server. Default: 1812
-sharedSecret Shared Secret (Required) Specifies the Shared Secret for this Apache RADIUS Module. This Shared Secret must match an associated RADIUS Client configuration on a RADIUS back-end server. It tells the RADIUS server that the web host server is a valid RADIUS client. -authTimeout Authentication Timeout (Optional) Specifies how long Apache waits for each authentication attempt before giving up and deciding that the RADIUS server is down or authentication has failed. -authRetries Authentication Retries (Optional) Specifies how many times Apache will re-authenticate a user after each attempt fails or times out before giving up and deciding that the RADIUS server is down or authentication has failed. -disableFallback (Optional) Prevents the user from using a local password file for user authentication. -cookieTimeout Cookie Timeout (Optional) Specifies the time period (in minutes) that the RADIUS Cookie remains valid. Once a RADIUS Cookie expires, the Apache RADIUS Module must authenticate a user account by using a RADIUS server. As long as the browser session remains valid, the end user is not challenged for authentication even if the RADIUS Cookie is expired. This value controls the number of communications between the Apache RADIUS Module and the RADIUS server for security purposes. Default: 10 minutes -disable (Required) Disables RADIUS. This argument is required if you do not specify the -hostName argument. Example: Enable RADIUS Support
nhWebRadius hostName radiushostname port 1812 shareSecret test123 authTimeout 2 authRetries 2 cookieTimeout 15
or
nhWebRadius hostName radiushostname shareSecret test123
Example: Disable RADIUS Support

nhWebRadius disable
Limitations in Live Health With RSA Tokens and User Credentials

Two limitations apply to Live Health client applications when you use eHealth RADIUS support with an RSA token for web authentication: In the Live Health login console, the checkbox Use as Default Login must never be selected. This limitation is imposed because of the one-time use nature of RSA tokens. Using the same RSA tokens in different authentication attempts typically lock the user account. In the Live Trend application, the default normal polling rate is five minutes. This polling rate is configurable from the server side. The value of the normal polling rate is set by the Poller and specified in the file $NH_HOME/data/liveTrend/NormalPollRateInSec. In general, when you enable eHealth RADIUS support, setting -cookieTimeout (in minutes) to less than five minutes typically incur in the failure of charting updates. When such an error occurs, close and reopen the Live Trend application to resolve the issue.
Error Handling
Login failure can occur with CA Spectrum eHealth One-way SSO, eHealth RADIUS, and eHealth SAML support because of the following misconfiguration or network issues: The authentication server is down or not reachable because of a network breakdown. In this case, the Apache server falls back to the standard eHealth authentication mechanism. The web user is not recognized (for example, a user account does not exist in the SAML server user directory) or is not authenticated by the authentication server. In this case, the Apache server falls back to the standard eHealth authentication mechanism. The web user exists in the authentication server but has an invalid password. In this case, the Apache server falls back to the standard eHealth authentication mechanism. The web user exists in the CA EEM, RADIUS, or SAML user directory and authenticates on the corresponding server, but does not have a valid eHealth account. In this case, the user is denied access and is redirected to an error page.
Fallback is a configurable option that can be turned off by an administrator. A user is denied access when fallback is disabled. The default eHealth administrator account 'admin' is available to fall back to the standard eHealth authentication, regardless of the previously mentioned errors.
Use Advanced Logging Troubleshooting Tool

You can access the Advanced Logging option, which provides you with tools for troubleshooting and debugging the eHealth web software. This feature is available to eHealth web administrators only. Web users cannot access it. Note: Use advanced logging solely as a troubleshooting tool and only under the direction of Technical Support. These log files can consume a significant amount of disk space. Do not enable them on a regular basis. If you enable advanced logging, eHealth stores the files by default in the /ehealth/web/output/users/username directory. Creating Technical Support Information If you experience any problems or errors while using the eHealth products and features, Support might direct you to create a troubleshooting zip file. You must be logged in as the eHealth web administrator to create these files. To create a troubleshooting zip file 1. Log in as the eHealth web administrator. 2. Click the Administration tab on the eHealth Web user interface navigation bar. 3. Click eHealth Management in the left pane, and click Advanced Logging. 4. Click Create Technical Support Information on the Advanced Logging page. 5. Locate Areas to Include and select one or more areas as instructed by your Technical Support Engineer. 6. Do one of the following if your eHealth system is a member of a Distributed eHealth cluster, in the Cluster Members field: Select Host to specify the cluster member for which you want to collect troubleshooting information. The default is the local cluster member. Select Cluster to collect the same information from all cluster members except the local member. Select All to collect the same information from all cluster members.
7. Locate the File Directory field and specify the directory in which to create the Zip file. The default is /ehealth/tmp.
8. Locate the Call Ticket Number field and specify the number of the call ticket for your problem report. If specified, the number is used in the Zip file name for identification purposes. If you do not have a call ticket associated with this problem, leave the field blank. 9. Click Create File. The troubleshooting zip file is created. The Troubleshooting Tool When there is a problem in a specific area, Support typically requests certain files that can help to diagnose the problem. To assist with the file collection, this tool collects copies of files from various subdirectories of the eHealth installation. It creates a zip file named diagnostics_callTicketNumber_date_time.zip in the specified File Directory location. Email or FTP the zip file to Support to assist with the process of troubleshooting the problem that you have reported. Note: Depending upon the options that you select, the troubleshooting zip file can be very large. Typical zip files can range in size from 50 KB to 150 MB. If you have had Advanced Logging enabled for a long time, the zip file can be several Gigabytes in size. After Support confirms that they have received the file, delete the zip file from your File Directory location to free up disk space. Certain types of problems can require you to enable advanced logging features before creating the troubleshooting zip file. The web server advanced logging features are on the Advanced Logging page of the eHealth web interface. To enable advanced logging for eHealth system processes, you must use OneClick for eHealth (OneClickEH). Your Support engineer can assist you when advanced logging is necessary. Errors and Troubleshooting eHealth gathers as many of the troubleshooting files as possible into the zip file. For each troubleshooting option, the tool searches for each file and then checks for available space in the File Directory location. If it cannot find a specific file or if File Directory does not have enough free space to hold a file, the tool omits that file and proceeds to the next one. The zip file contains a log file that lists the files that were included and those files that were omitted.
Appendix B: Troubleshooting
Troubleshoot Installation Problems
This section provides troubleshooting information for problems that you may encounter during the eHealth r6.2.2 installation process.
Installation Program Exits before Completion

Valid on Windows and UNIX Symptom When the installation program runs, it exits with an error. Solution 1. Review the error messages. 2. Correct the problem that generated the error. 3. Restart the installation program. It is designed to skip time-consuming steps that it has already completed, such as installing Oracle and creating the database.
Database Creation Is Incomplete

This section includes the following procedures: Recover from incomplete database creation on Windows Recover from incomplete database creation on UNIX
Symptom The installation program stops due to an error during database creation. Solution Complete the following procedure before restarting the installation program.
Appendix B: Troubleshooting 117
To recover from incomplete database creation on Windows 1. Determine the problem that caused the error and resolve it. For example, if the database creation failed due to insufficient disk space, add more disk space to the local system or allocate space on high-performance network drives. 2. Delete the database instance in a command prompt window by entering the following command:
cd %NH_HOME% bin nhDestroyDB -s oracle_sid
oracle_sid Represents the name of the database instance (typically EHEALTH). The eHealth database directories are deleted. 3. Restart the installation program. To recover from incomplete database creation on UNIX 1. Determine the problem that caused the error and resolve it. For example, if the database creation failed due to insufficient disk space, add more disk space to the local system or allocate space on high-performance network drives. 2. Log on as root in a terminal window and enter the following command:
ipcs
The ipcs output appears, including the processes using shared memory and semaphores. 3. Examine the shared memory and semaphores sections for active processes associated with the eHealth administrator account. Stop each of those processes by entering the following commands: For shared memory, enter the following command:
ipcrm -m id
id Represents the identification number associated with shared memory. For semaphores, enter the following command:
ipcrm -s id
id Represents the identification number associated with semaphores. The processes are stopped.
4. Delete all directories (and their contents) that you specified as locations for the eHealth database. Delete the Oracle initialization file by entering the following command:
rm -f $ORACLE_HOME/dbs/initsid.ora
$ORACLE_HOME Represents the full path to the location in which you installed the Oracle software sid Represents the name of the eHealth database instance (SID) The directories and files are deleted. 5. Restart the installation program.
TrapEXPLODER Unable to Start

Valid on Windows Symptom By default, both TrapEXPLODER and the Windows SNMP trap service use port 162. This creates a port conflict and generates an error message. Solution In Windows Services, stop the Windows SNMP Trap Service, and set to Manual or Disabled to ensure the problem does not happen again. To use both the Windows SNMP trap service and TrapEXPLODER, you must configure TrapEXPLODER to listen on a different port. The following procedure configures a port number for TrapEXPLODER. Complete this procedure after you install eHealth (which includes TrapEXPLODER). To configure a non-default port number for TrapEXPLODER 1. Start the regedit utility. Important! If you are not familiar with the regedit utility, do not perform this task without the help of a system administrator. 2. Navigate to the following directory: HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA TrapEXPLODER\CurrentVersion 3. Select Edit, New, DWORD Value, and enter TrapPort as the name. The new entry is created. 4. Right-click TrapPort and select Modify. The Edit DWORD Value dialog appears.
5. Enter the port number that you want TrapEXPLODER to use and click OK to close the dialog. 6. Exit the regedit utility. TrapEXPLODER now uses a new SNMP port.
Windows Could Not Start the eHealth httpd61 on Local Computer

Valid on Windows Symptom This message appears when the default website is activated, stopping the Hypertext Transfer Protocol Daemon (HTTPd) from running. Solution Do the following to stop the default website service: 1. Right-click My Computer on your desktop and click Manage. The Computer Management window opens. 2. Click Services and Applications, Internet Information Service, Web Sites, Default Web Site. 3. Right-click Default Web Site and select Stop.
eHealth Console Fails to Start after Installation

Valid on Windows Symptom Xlib and X server errors appear when the eHealth r6.2.2 console fails to start after you complete the installation process. This problem may occur on a Windows 2003 system when the MKS XServer does not start automatically. Example: An Xlib error occurred. A functioning X server must be running. Solution Complete the following procedures to troubleshoot the X server errors. To set the MKS XServer icon on the taskbar To set the MKS XServer icon to appear in the Windows taskbar, select one of the following options: Start MKS XServer: From the Windows desktop, select Start, Programs, Vision, MKS XServer Server. Start the eHealth console: Select Start, Programs, eHealth 6.1, eHealth.
To set MKS XServer to start automatically on system startup 1. Double-click MKS XServer Profiles in the Control Panel. The MKS XServer Profiles dialog appears. 2. Select the Global Settings tab. Under Server, select Load MKS XServer at Windows startup, and click OK. The MKS XServer profile is reset to start automatically.
To enable TCP-Unix 1. Select Start, Control Panel. 2. Double-click Vision Communications. The Vision Communications dialog appears. 3. Select the Transports tab. 4. Verify that TCP-Unix is enabled. If it is not, select TCP-Unix and click Properties. The Transport Properties dialog opens. 5. Select Enable this transport. Click OK. TCP-Unix is enabled.
Insufficient Accessible Stack Size During Installations on HP-UX

During eHealth r6.2.2 installations on HP-UX, you may observe the following error:
FAIL -- Insufficient accessible stack size, 128MB available, 144MB required.
To fix this error, you need to change the value of the maxssiz kernel configuration on the HP system. To check the current value of the stack size, run ulimit a as root. The correct setting for the maxssiz kernel configuration is different for eHealth r6.0.6 and r6.1.2 or later. For r6.0.6, the correct value is 134217728, and for r6.1.2 or later, the correct value is 170000000. To change this value on an HP-UX 11.11 system 1. Log into the HP system as root. 2. Change to csh as follows:
#csh
3. Set the DISPLAY environment variable to your desktop as follows:

#setenv DISPLAY machine:0.0
4. Launch SAM (System Administration Manager) as follows:

#sam &
The SAM UI appears on your desktop. 5. Double-click Kernel Configurations. 6. Double-click Configurable Parameters.
7. Double-click maxssiz and change this parameter to the appropriate value. 8. Click File, Exit. 9. Click OK to create a new kernel now. 10. Click OK to 'Move Kernel into place and shutdown/reboot system now'. 11. Click OK on the note. The system reboots. To change this value on an HP-UX 11.23 system 1. Log into the HP system as root. 2. Change to csh as follows:
#csh
3. Set the DISPLAY environment variable to your desktop as follows:

#setenv DISPLAY machine:0.0
4. Launch SAM as follows:

#sam &
The SAM UI appears on your desktop. 5. Double-click Kernel Configurations. 6. Double-click Kernel Configuration (character mode). The sam hpterm display appears. 7. Select Tunables by pressing Enter. 8. Click the down arrow, select maxssiz, and press Enter. 9. Press m to modify, enter the appropriate value, and press Enter. 10. Enter y for 'Do you want to hold this change till the next boot?'. 11. Enter y for 'Do you want to save the current kernel configuration?'. 12. Press <enter> to skip entering comments. 13. Enter y for 'Do you want to proceed?'. 14. Press Enter to continue. 15. Press ESC 3 times to Go Up and exit the Kernel Configuration tool. 16. Press Enter to exit sam hpterm. 17. Click File, Exit SAM. 18. Reboot the system manually.
Troubleshoot Upgrade Problems

This section provides troubleshooting information for problems that you may encounter during the eHealth upgrade process on Windows and UNIX systems.
System Does Not Meet Minimum Requirements

Valid on Windows and UNIX Symptom Message appears showing that the installation program has determined that the system on which you are upgrading eHealth does not meet minimum system requirements. Solution Confirm that your system meets the minimum system requirements.
Installation Program Exits During Activation

Valid on Windows and UNIX Symptom The installation program rolls the software on that system back to r5.7 or r6.0, displaying messages to that effect. Messages instruct you to perform cleanup tasks before trying the installation again.
Solution 1. Correct the problem that generated the error. For example, if the installation program indicates insufficient disk space, add more disk space to the local system or allocate space on high-performance network drives. 2. Restart the eHealth installation program. The installation program is designed to skip time-consuming steps that it has already completed successfully.
One or More Kernel Parameters Are Not Configured Properly

Valid on UNIX Symptom Message appears showing one or more of the kernel parameters are not configured appropriately. Example:
-------------------------------------------------System configuration check results: +------------------+------------------+----------+ | System Parameter | Current | Required | | Name | Value | Minimum | +------------------+------------------+----------+ | SEMMNI | 0 | 128 | +------------------+------------------+----------+ | SEMMSL | 200 | 512 | +------------------+------------------+----------+ | SEMMNS | 1000 | 1024 | +------------------+------------------+----------+ One or more system configurations are not correct; installation of eHealth could proceed, but you may encounter errors. Please change your system configuration to match the requirements before running eHealth.
Solution Modify the kernel parameter values to be at least the required minimum. For more information, see your operating system documentation or Check and Modify Kernel Requirements.
Restore Oracle On Cluster Members

When you upgrade cluster members to Oracle 10g, each member can remain in a transition state (after upgrade but before activation) until all cluster members are ready to be activated. In a transition state, eHealth and the eHealth database are fully functional, although the eHealth environment is neither a complete r6.2.2 environment nor a complete prior (Oracle 9i-based) environment. In this state the eHealth prior version is running against the Oracle 10g database. If a problem (such as a system disaster) occurs during this time or you wish to roll back to the previous version of Oracle, you must reload and recreate the Oracle 9i database. Note: You must back up the database after the upgrade attempt but before you perform this procedure.
To recreate the Oracle 9i database 1. Roll back the cluster member to the transition state in preparation to restore the previous version of the database if eHealth r6.2.2 has been activated. This step also updates the nethealthrc file in the old home directory. 2. In transition state, stop the Oracle 10g database and eHealth server, if running, and restart the database. 3. Destroy the database as root user by entering the following command:
$NH_HOME/bin/nhDestroyDb -s OracleSID
OracleSID Specifies the name of the Oracle instance (the Oracle session identifier or SID) for the eHealth database. 4. Restore the Oracle 9i environment by entering the following command:
$NH_HOME_NEW/bin/sys/nhsRestore9iEnv
5. Source the nethealthrc file from the old home by entering the following command:
opt/eHealth/nethealthrc.*
6. Create the Oracle 9i database by doing one of the following: Enter the following command:
$NH_HOME/bin/nhCreateDb -s OracleSID
Note: Do not change the OracleSID. Use a LCF to create the database.
7. Execute the following command to load the saved database:

nhLoadDb
eHealth Upgrade to r6.2.2 Unsuccessful on a Cluster Member

Valid on Windows and UNIX Symptom The upgrade to eHealth r6.2.2 was not successful on a cluster member. Solution Restore (roll back to) eHealth r5.7.9 or r6.0 on the local system or on all cluster members. This action minimizes data loss because you can troubleshoot the upgrade problems while eHealth r5.7.9 or r6.0 continues to collect and report on data. Note: eHealth r5.7.9 or r6.0 cannot be restored after you finalize the upgrade.
Rollback Downtime
During the rollback process, eHealth experiences downtime from the time that the eHealth r6.2.2 services stop to the time that the eHealth r5.7.9 or r6.0 services start. (On Windows systems, the rollback process also requires a system reboot.) When possible, roll back an individual cluster member rather than the entire cluster so that eHealth experiences downtime on that system only. If you roll back all cluster members, eHealth experiences more downtime. Important! If you discovered new elements by using eHealth r6.2.2, that information is lost when you roll back to eHealth r5.7.9 or r6.0. To restore eHealth r5.7.9 or r6.0, do the following 1. Remove systems from the cluster. 2. Restore eHealth r5.7.9 or r6.0 on the system or across the cluster. 3. Activate eHealth r6.2.2 after resolving upgrade problems.
Remove a System from the Cluster

If you plan to restore eHealth r5.7.9 or r6.0 on one member of the cluster, leaving the rest of the cluster on eHealth r6.2.2, consider removing that system from the cluster first. In either case, after you roll back the system to eHealth r5.7.9 or r6.0, you will be able to use eHealth to run reports for that system locally. You might want to remove the system from the cluster if your organization cannot tolerate the errors or if you expect that you will not be able to reactivate eHealth r6.2.2 on that system soon. If you do not remove the system from the cluster before rolling it back to eHealth r5.7.9 or r6.0, expect the following results: Reports run from an r6.2.2 Distributed eHealth Console do not include information about elements or groups managed by the eHealth r5.7.9 or r6.0 system. If you use an r6.2.2 Distributed eHealth Console to run an element-specific report for an element managed by the eHealth r5.7.9 or r6.0 system, the report fails. Some scheduled jobs, such as the Synchronize job, generate errors concerning that system.
Leaving the system in the cluster may be acceptable if you plan to reactivate eHealth r6.2.2 on that system after resolving any issues, and if report and job errors do not pose a problem. If you remove the system from the cluster before rolling back to eHealth r5.7.9 or r6.0, expect the following results: Scheduled jobs and reports do not generate errors regarding that cluster member. Reports run from an r6.2.2 Distributed eHealth Console do not include information about elements or groups managed by the eHealth r5.7.9 or r6.0 system that was removed.
To remove the system from the cluster To remove the system from the member tables of all systems in the Distributed eHealth cluster (including the one on which you run the command), run the following command on one of the cluster members on which eHealth r6.2.2 is operating:
nhRemoveClusterMember -all -name hostname
Note: For more information about removing a cluster member and how to use the nhRemoveClusterMember command and its arguments, see the Distributed eHealth Administration Guide. Also, see that guide for information about how to restore the member to the cluster with the nhRestoreClusterMember command after reactivating eHealth r6.2.2.
Restore eHealth r5.7.9 or r6.0 on the Local System

This section includes the following procedures: Restore eHealth r5.7.9 or r6.0 on a Windows system Restore eHealth r5.7.9 or r6.0 on a UNIX system
To restore eHealth r5.7.9 or r6.0 on a Windows system 1. Log on as the eHealth administrator, open a new command prompt window, and restore eHealth r5.7.9 or r6.0 on the local system by entering the following command:
nhUpgradeCluster -rollback -local
This command performs the following actions: Stops eHealth r6.2.2 services Recreates the eHealth r5.7.9 or r6.0 configuration Reboots the system Starts eHealth r5.7.9 or r6.0 services, including the web server
Some of these steps, such as restarting servers and the system, can take several minutes to complete. eHealth r5.7.9 or r6.0 is restored on the system. 2. Reactivate eHealth r6.2.2 after you resolve the issue that prevented a successful upgrade.
To restore eHealth r5.7.9 or r6.0 on a UNIX system 1. Log on as the eHealth administrator and change to the ehealth_new directory (the eHealth r6.2.2 installation directory). Using one of the following commands, source the eHealth r6.2.2 resource file appropriate for your shell environment: Bourne: . ./nethealthrc.sh C: source nethealthrc.csh Korn: . ./nethealthrc.ksh
2. Restore eHealth r5.7.9 or r6.0 on the system by entering the following command:
nhUpgradeCluster -rollback -local
This command starts the following actions: Stops eHealth r6.2.2 servers Recreates the eHealth r5.7.9 or r6.0 configuration Starts eHealth r5.7.9 or r6.0 servers, including the web server
Some of these steps, such as restarting servers, take several minutes to complete. 3. Close all terminal windows that use eHealth r6.2.2 environment variables, or source the eHealth r5.7.9 or r6.0 resource file in those windows. After restoring eHealth r5.7.9, you cannot run eHealth r6.2.2 commands in those windows. After you resolve the issue that prevented a successful upgrade, reactivate eHealth r6.2.2.
Restore eHealth r5.7 or r6.0 Across the Cluster

This section includes the following procedures: Restore eHealth r5.7.9 or r6.0 across the Windows cluster Restore eHealth r5.7.9 or r6.0 across a UNIX cluster
To restore eHealth r5.7.9 or r6.0 across a Windows cluster 1. On the trusted system from which you issued the nhUpgradeCluster -activate command, log on as the eHealth administrator. Open a new command prompt window. This step helps ensure that you are using the eHealth r6.2.2 environment. 2. Restore eHealth r5.7.9 or r6.0 on all systems in the cluster by entering the following command:
nhUpgradeCluster -rollback
This command performs the following actions on every system in the cluster: Stops eHealth r6.2.2 services Recreates the eHealth r5.7.9 or r6.0 configuration Reboots the Windows systems in the cluster Starts eHealth r5.7.9 or r6.0 services, including the web server
Some of these steps, such as restarting servers, can take several minutes to complete. Upon successful completion of the rollback process, all Windows systems in the cluster will reboot, and all cluster members will be running eHealth r5.7.9 or r6.0.
To restore eHealth r5.7.9 or r6.0 across a UNIX cluster 1. Log on as the eHealth administrator on the trusted system from which you ran the nhUpgradeCluster -activate command, and change to the ehealth_new directory (the eHealth r6.2.2 installation directory). Source the eHealth r6.2.2 resource file appropriate for your shell environment. 2. Restore eHealth r5.7.9 or r6.0 on all systems in the cluster by entering the following command:
nhUpgradeCluster -rollback
This command performs the following actions on every system in the cluster: Stops eHealth r6.2.2 servers Recreates the eHealth r5.7.9 or r6.0 configuration Starts eHealth r5.7.9 or r6.0 servers, including the web server
Some of these steps, such as restarting servers, take several minutes to complete. Upon successful completion of the rollback process, all systems in the cluster reboot and all cluster members run eHealth r5.7.9 or r6.0. 3. Close all terminal windows that use eHealth r6.2.2 environment variables, or source the eHealth r5.7.9 or r6.0 resource file in those windows. After restoring eHealth r5.7.9 or r6.0, you cannot run eHealth r6.2.2 commands in those windows.
Reactivate eHealth r6.2.2 after a r5.7.9 or r6.0 Rollback

After you resolve the issues that caused activation errors, reactivate eHealth r6.2.2, then continue the upgrade process. For further information, see the Distributed eHealth Administration Guide. This section includes the following procedures: Reactivate eHealth r6.2.2 on a local Windows system Reactivate eHealth r6.2.2 on a local UNIX system
To reactivate eHealth r6.2.2 on a local Windows system 1. On the system to be reactivated, log on as the eHealth administrator and open a command prompt window. 2. Enter the following command:
nhUpgradeCluster -activate -local
Note: If you issue this command from a trusted system that was removed from a cluster, the command indicates the status of eHealth on all systems in the cluster, even though the activation process occurs only on the local system.
3. To confirm that eHealth r6.2.2 is running on the local system, enter the following command:
nhUpgradeCluster -validate -local
4. Restore the system if you removed it from the cluster by using the following command:
nhRestoreClusterMember
The system reboots, and eHealth r6.2.2 is reactivated on the local system. To reactivate eHealth r6.2.2 on a local UNIX system 1. Log on as the eHealth administrator on the system to be reactivated, and source the eHealth r6.2.2 resource file appropriate for your shell environment. 2. Enter the following command:
nhUpgradeCluster -activate -local
Note: If you issue this command from a trusted system that was removed from a cluster, the command indicates the status of eHealth on all systems in the cluster, even though the activation process occurs only on the local system. 3. Enter the following command to confirm that eHealth r6.2.2 is running on the local system:
nhUpgradeCluster -validate -local
4. Use the following command to restore the system if you removed it from the cluster:
nhRestoreClusterMember
eHealth r6.2.2 is reactivated on the local system.
Reactivate eHealth r6.2.2 on all Cluster Members after a r5.7.9 or r6.0 Rollback
After you resolve the issues that caused activation errors, reactivate eHealth r6.2.2 and then continue the upgrade process. Note: For more information, see the Distributed eHealth Administration Guide. To reactivate eHealth r6.2.2 on all members of a Windows cluster 1. Log on as the eHealth administrator on the trusted system that you used to roll back the upgrade and open a command prompt window. 2. Enter the following command to activate eHealth r6.2.2 on all members of the Distributed eHealth cluster:
This command also confirms that eHealth r6.2.2 is running on all members of the cluster. However, if you need to perform this validation step manually, use the following command:
nhUpgradeCluster -validate
The systems reboot, and eHealth r6.2.2 is reactivated on all cluster members. To reactivate eHealth r6.2.2 on all members of a UNIX cluster 1. Log on as the eHealth administrator on the trusted system that you used to roll back the upgrade, and source the eHealth r6.2.2 resource file appropriate for your shell environment. 2. Enter the following command to activate eHealth r6.2.2 on all members of the Distributed eHealth cluster:
This command also confirms that eHealth r6.2.2 is running on all members of the cluster. However, if you need to perform this validation step manually, you can use the following command:
nhUpgradeCluster -validate
eHealth r6.2.2 is reactivated on all cluster members.
Appendix C: Removing eHealth and Related Applications

Before You Remove eHealth
Before you remove eHealth, complete the following tasks: Files and Directories Backup (see page 135) Windows Registry Backup (Windows Only) (see page 136) Directory Confirmation (UNIX Only) (see page 136)
Files and Directories Backup

If you are removing eHealth r6.2.2 to move it to another location on the same system or to another system, save your eHealth database by following the instructions in the eHealth Administration Guide. You should also create backup copies of the following files, where ehealth represents the full pathname of the directory in which you installed eHealth: ehealth\lmgr\license.dat - the eHealth license file that is system-specific (not required when moving eHealth to another system) ehealth\sys\password.cfg (if the system is in a Distributed eHealth cluster) Any customized web help or files that you created ehealth\log ehealth\web\webCfg
(UNIX only) Save the following configuration information and log files for future reference: ehealth/nethealthrc.csh ehealth/nethealthrc.csh.usr ehealth/nethealthrc.ksh ehealth/nethealthrc.sh ehealth/nethealthrc.sh.usr
Appendix C: Removing eHealth and Related Applications 135
Before You Remove eHealth
Windows Registry Backup (Windows Only)

Some of the removal instructions require you to change registry entries. As a precaution, back up the Windows registry first. This backup lets you restore the registry settings if you delete the wrong entries. To back up the Windows registry 1. Enter the following command at a command prompt:
regedit
The Registry Editor opens. 2. Click File, Export. The Export Registry File window opens. 3. Select All under Export range. 4. Specify a file name and location for the registry backup. 5. Click Save. The Windows registry is backed up.
Directory Confirmation (UNIX Only)

Confirm the locations of the following: Directory in which you installed eHealth Directory in which you installed the Oracle software Directories that you specified for the eHealth database
To determine the directory in which you installed eHealth r6.2.2 1. Use the symbolic link to eHealth and change to that directory by entering the following command:
cd /opt
2. List the files in the current directory by entering the following command:
ls -al
The output of this command shows an eHealth file which points to the eHealth installation directory. Write down the full path. Do not include the last slash that appears in the installation directory. The following is an example of output from this command:
eHealth -> /export/disk1/ehealth/
In this example, the eHealth installation directory is /export/disk1/ehealth.
Remove eHealth r6.2.2
To determine the directory in which you installed the Oracle software 1. Enter the following command in a terminal window:
cat /var/opt/oracle/oraInst.loc
2. Examine the directory path associated with the line inventory_loc. The location of the Oracle software is the directory path that appears before the text oraInventory. The following is an example of the output from the command:
inventory_loc=/export/SystemName/oracle/oraInventory.
In this example, the location of the Oracle software is /export/SystemName/oracle. To determine the directories in which you installed the eHealth database 1. Change to the directory in which the installation program saved the database creation log file. Enter the following command, where ehealth represents the directory in which you installed eHealth:
cd ehealth/log/install
2. Enter the following command:

more CreateDb.log
The file contents appears. 3. Locate the Database Directories section of the file contents and verify the directories that you specified for the eHealth database.

Perform the procedures in this section to remove eHealth r6.2.2, its database, and all eHealth-related applications on Windows and UNIX systems. This section contains the following procedures: Remove eHealth on a Windows System Remove eHealth on a UNIX System
Remove eHealth on a Windows System

The eHealth removal process includes the following steps: Stop all eHealth services and destroy the eHealth database. Remove Oracle, MKS XServer, MKS NuTCRACKER, and eHealth (including Report Center, if installed). Remove eHealth-related registry entries and variables, and perform cleanup tasks.
To stop eHealth services and destroy the database 1. Save the critical files described in Files and Directories Backup (see page 135). 2. Open a command prompt window and enter the following commands to stop all eHealth services and the eHealth database:
nhServer stop nhStopDb -s oracle_sid
oracle_sid Represents the name of the database instance (typically EHEALTH). The services and database are stopped. 3. Destroy the eHealth database by entering the following command:
nhDestroyDb -s oracle_sid
Progress bars appear. Ignore error messages that indicate the uninstallation process cannot access a file. The database is destroyed. 4. Confirm that the eHealth database service does not exist: a. Select Start, Control Panel, Administrative Tools, Services. The Services windows opens. If the window is already open, select Action, Refresh. b. If the service OracleServiceORACLE_SID appears in the list of services, return to the command window and enter the following command to delete it:
oradim -delete -sid %ORACLE_SID%
Note: The OracleServiceORACLE_SID service may still appear in the Services dialog after you delete it. However, it will no longer appear after you restart the system. 5. Open Windows Explorer and verify that the database file folders that you specified during the eHealth installation still exist. If the folders exist, delete them.
To remove the Oracle Software 1. Use Windows Explorer to navigate to the file ORACLE_BASE\Oracle.10.2\oui\bin\ directory and double-click setup.exe. ORACLE_BASE Represents the directory in which you installed the Oracle software. The Oracle Universal Installer opens. 2. Click Deinstall Products. The Inventory dialog opens. 3. Expand Oracle Homes in the Contents tab and click the box next to EHORA[version]. The Remove button becomes active. 4. Click Remove. The Confirmation dialog opens. 5. Click Yes. The Oracle deinstall process begins. This process takes approximately five minutes. The Inventory dialog appears. There should be no products installed. 6. Click Close. 7. Click Cancel and then Exit. The Oracle software is removed. To remove the MKS XServer application Important! If the MKS XServer application is used by an application other than eHealth, do not remove it. 1. Right-click the XServer icon on your Windows task bar (the X symbol), and select Close. XVision is stopped. 2. Select Start, Settings, Control Panel. Double-click Add/Remove Programs. 3. Select the MKS XServer program and click Remove. 4. Click Yes when prompted to remove MKS XServer and all of its components and click OK if you encounter the following error message: Severe: Unable to complete deregistration. MKS XServer is removed.
To remove the MKS NuTCRACKER software 1. Open the Services dialog. If it is already open, select Action, Refresh. 2. Select the NuTCRACKER Service. Select Action, Stop. The service is stopped. 3. Close the Services window. 4. Select the MKS Platform Components [version] program in the Add/Remove Programs dialog, and click Remove. The Add or Remove Programs dialog appears. 5. Click Yes. The NuTCRACKER software is removed. To remove the eHealth software (including Report Center, if installed) 1. Confirm all eHealth-related services and applications are stopped. 2. Select eHealth 6.2.2 in the Add or Remove Programs window and click Change/Remove. 3. Click OK when prompted to confirm the uninstall request. The eHealth Setup Status dialog appears and begins to uninstall eHealth. 4. Click Yes when prompted to restart your computer. Upon startup, the eHealth software is removed.
Remove Registry Entries and Perform Cleanup Tasks

After you remove the software, remove the registry entries for those products and eHealth-related environment variables. To remove registry entries and perform cleanup tasks 1. Start the regedit utility. Important! If you are not familiar with the regedit utility, do not modify the registry without the help of a system administrator. 2. Back up the Windows registry as described in Windows Registry Backup (Windows Only) (see page 136) if you have not already done so.
3. Remove eHealth registry entries as follows: a. b. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE directory. Delete the Concord Communications folder if it appears by right-clicking the entry and choosing Delete from the shortcut menu. The Confirm Key Delete dialog appears. c. Click Yes.
The registry entries are removed. 4. Remove Oracle 10g registry entries: a. b. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE directory. Delete the entire ORACLE folder.
5. Remove all MKS NuTCRACKER registry entries: a. b. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Datafocus directory. Delete the subkey NUTCRACKER OE.
6. Remove the Apache Tomcat registry entry: a. b. Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Tomcat Service Manager. Delete subkey eHealth Tomcat63.
7. Remove the OracleEHORA10TNSListener registry entry, if it exists: a. b. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services directory. Delete the OracleEHORA10TNSListener folder.
8. Remove the Report Center registry entry: a. b. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Delete the eHealth Report Center63.version folder.
9. Exit the regedit utility. 10. Stop the Distributed Transaction Coordinator service as follows: a. b. Click Start, Programs, Administrative Tools, Services. Select Distributed Transaction Coordinator and click Stop.
Note: You must stop this service to delete the Oracle software installation directory in the next step.
11. Use Windows Explorer to navigate to the following directories and delete them: eHealth software installation directory Oracle software installation directory nutcroot (the MKS NuTCRACKER software directory)
12. Use Windows Explorer to navigate to the Program Files directory and delete the following directories: Oracle MKS XServer, if it exists
13. (Optional) Remove the Live Health client software if it is installed on the eHealth system. Note: For instructions, see the eHealth Help. To remove all eHealth-related environment variables 1. Select Start, Control Panel. 2. Double-click System and then select the Advanced tab. 3. Click Environment Variables. 4. Scroll under System variables to find the Path variable, select it, and then click Edit. 5. Scroll in the Variable value field to find all entries that refer to the following directories. Select each entry and delete it. ehealth oracle nutcroot MKS XServer, if it exists
6. Click OK when you have finished deleting all of the entries. 7. Delete all System variables pertaining to eHealth. These variables will have the prefix NH_. 8. Click OK to close the Environment Variables dialog. 9. Click OK to close the System Properties dialog. 10. Restart your system. The eHealth variables are removed and the changes are activated.
Remove eHealth on a UNIX System

Follow the procedures in this section to remove the eHealth applications and Oracle database from Solaris and HP-UX systems. To remove eHealth r6.2.2 1. Log on as root in a terminal window and enter the following command to change to the directory in which you installed eHealth:
cd ehealth
2. Source the eHealth resource file that is appropriate for your shell environment using one of the following commands: Bourne: . ./nethealthrc.sh C: source nethealthrc.csh Korn: . ./nethealthrc.ksh
If you cannot source the eHealth resource file, eHealth may not be installed or you may not be in the correct directory. 3. Stop all eHealth processes by entering the following commands, depending on your system: Solaris:
cd /etc/init.d ./nethealth stop
HP-UX:
cd /sbin/init.d ./nethealth stop
The eHealth processes are stopped. 4. Stop all httpd processes by entering the following command:
./httpd stop
5. Stop the TrapEXPLODER server by entering the following command:

./trapexploder stop
6. Stop the eHealth license manager process by entering the following commands:
cd ehealth/bin ./nhLmgr stop
The eHealth license manager process is stopped.
7. Confirm that ORACLE_HOME is defined by entering the following command:

echo $ORACLE_HOME
If the environment variable is not defined, you must set the value to the location in which you installed Oracle. For a Bourne or Korn shell, enter:
ORACLE_HOME=fullpath export ORACLE_HOME
For a C shell, enter:

setenv ORACLE_HOME "fullpath"
fullpath Represents the full path to the location in which you installed Oracle. 8. Verify the name of the eHealth database by entering the following command:
env | grep ORACLE_SID
9. Destroy the eHealth database by doing the following: a. Enter the following command:
nhDestroyDb -s oracle_sid
oracle_sid Represents the name of the eHealth database. a. (HP-UX only) Enter d at the confirmation prompt to indicate destroy the database.
The database is destroyed. 10. List all Oracle-related processes by entering the following command:
ps -ef | grep ora_...._ | grep -v grep
If the command provides no output, all Oracle-related processes are stopped. However, if some of those processes are still running, it produces output similar to the following:
ehUser ehUser ehUser ehUser ehUser ehUser ehUser 5495 5487 5499 5485 5493 5497 5491 1 1 1 1 1 1 1 0 0 0 0 0 0 0 Jan Jan Jan Jan Jan Jan Jan 16 16 16 16 16 16 16 ? ? ? ? ? ? ? 0:00 0:25 0:03 0:01 0:55 0:03 0:09 ora_reco_JAN13 ora_dbw0_JAN13 ora_arc1_JAN13 ora_pmon_JAN13 ora_smon_JAN13 ora_arc0_JAN13 ora_ckpt_JAN13
11. Enter the following command for each process identification number (pid):
kill pid; sleep 2; kill -9 pid
pid Represents the process identification number shown in the ps -ef output. The pid process is ended. 12. Remove the Oracle software directory and other Oracle directories by entering the following commands:
rm rm rm rm -rf -rf -rf -rf $ORACLE_HOME /var/opt/oracle /opt/ORCLfmap /var/tmp/.oracle
Note: After removing the /var/tmp/.oracle file, you may need to reset permissions on the /var/tmp directory. The Oracle directories are removed. 13. Remove each of the eHealth database directories that you specified in the eHealth installation program using the following command:
rmdir
14. Examine the shared memory and semaphores sections for active processes associated with the ehUser account. Enter the following command to confirm that Oracle is not using shared memory and semaphores:
ipcs -a
For example, in the following ipcs output, the ehUser is associated with a shared memory process (pid 9985) and a semaphores process (pid 4915200):
IPC status from <running system> as of Thu Jan 23 11:45:34 EST 2008 T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME Message Queues: T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME Shared Memory: m 0 0x50000d08 --rw-r--r-root root root root 1 4 331 331 13:12:52 13:12:52 13:12:52 m 9985 0x822b58ec --rw-rw---- ehUser software ehUser software 23 167772160 5483 14706 11:45:27 11:45:27 19:38:16 T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME Semaphores: s 4915200 0x2796f8f4 --ra-ra---- ehUser software ehUser software 119 11:45:27 19:38:17
15. Stop these processes by using the following commands: For shared memory, enter the following command:
ipcrm -m 9985
For semaphores, enter the following command:

ipcrm -s 4915200
16. Confirm that the processes are stopped by repeating Step 14. If necessary, repeat Step 15. Upon completion of this step, you have removed the Oracle database and software. 17. Remove the eHealth home directory by entering the following commands:
cd ehealth cd .. rm -rf ehealth
18. Remove eHealth configuration and license files by entering the following commands:
cd /etc rm nh.install.cfg trapexploder.cf trapexploder.lic
19. Remove the startup script files by entering the following commands, depending on your system: Solaris:
cd /etc/init.d rm nethealth.sh httpd.sh trapexploder nethealth httpd
HP-UX:
cd /sbin/init.d rm nethealth.sh httpd.sh trapexploder nethealth httpd
20. Change to the rc0.d directory by entering the following command, depending on your system: Solaris: cd /etc/rc0.d HP-UX: cd /sbin/rc0.d
21. View all files in the directory by entering the following command:
ls -al
A list of all files appears.
22. Remove any files that relate to eHealth, the web server, and TrapEXPLODER. These files have the following format: K###nethealth or S###nethealth K###httpd or S###httpd K###trapexploder or S###trapexploder
Run the following command to be prompted for each file before it is deleted:
rm -i
23. Change to the rc1.d directory by entering the following command, depending on your system: Solaris: cd /etc/rc1.d HP-UX: cd /sbin/rc1.d
24. Repeat Steps 21 and 22. 25. Change to the rc2.d directory by entering the following command, depending on your system: Solaris: cd /etc/rc2.d HP-UX: cd /sbin/rc2.d
26. Repeat Steps 21 and 22. 27. Change to the rc3.d directory by entering the following command, depending on your system: Solaris: cd /etc/rc3.d HP-UX: cd /sbin/rc3.d
28. Repeat Steps 21 and 22. 29. Remove the symbolic link to eHealth by entering the following commands:
cd /opt rm eHealth
30. Remove the embedded TrapEXPLODER software by entering the following command:
rm -rf trapx
31. Change to the /tmp directory by entering the following command:

cd /tmp
32. View all files in the directory by entering the following command:
ls -al
A list of files appears.
Remove eHealth r5.7.9 or r6.0
33. Remove all eHealth-related files and configuration files by entering the following command:
rm -rf install.cfg install.cfg.trap
34. (Optional) Remove any directories that begin with orapatch, OraInstall, and oracle; then remove any files that begin with nhCreateDbQuery and instnethealth. 35. Remove the following license manager directory, if it exists, by entering this command:
rm -rf /var/tmp/.flexlm
36. (Optional) Remove the Live Health client software is installed on the eHealth system. For instructions, see the eHealth Live Health Web Help. 37. (Optional) Open and work from a new terminal window If you plan to reinstall eHealth. The terminal window used in the removal procedure should not be used because the environment settings that were sourced during eHealth removal will interfere with the reinstallation.

To free disk space, use the following procedure to remove eHealth r5.7.9 or r6.0 from your system after upgrading successfully to eHealth r6.2.2. Before you begin, confirm the location in which you installed eHealth r5.7.9 or r6.0. Important! Do not remove eHealth r5.7.9 or r6.0 until after you have finalized the installation changes. This section contains the following procedures: Remove eHealth r5.7.9 or r6.0 (Windows (see page 149)) Remove eHealth r5.7.9 or r6.0 (UNIX) (see page 150)
Remove eHealth r5.7.9 or r6.0 (Windows)

To remove eHealth release r5.7.9 or r6.0 1. Rename the old eHealth installation directory to test for any processes that still use it. For example, if eHealth r5.7.9 or r6.0 is installed in D:\ehealth, change the folder name to D:\old_ehealth. 2. Wait a day or two to verify that eHealth r6.2.2 is working properly. If you encounter any new problems related to required files that reside in the old eHealth directories, resolve them before proceeding. 3. Start the registry editor at a command prompt by entering the following command:
regedit
The registry editor opens. Note: If you are not familiar with the regedit utility, do not perform this procedure without the help of a system administrator. 4. Back up the Windows registry as described in Windows Registry Backup (Windows Only) (see page 136). 5. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services directory and completely remove eHealth r5.7.9 or r6.0 from the system by deleting the following registry folders related to eHealth r5.7.9 or r6.0. Do not delete any Oracle-related entries or any entries related to eHealth r6.2.2. ehealth57 or ehealth60 ehealth httpd57 or ehealth httpd60 ehealth Tomcat60 FLEXlm License Server57 or FLEXlm License Server60 TrapEXPLODER57 or TrapEXPLODER60
The registry folders are deleted.
Remove Report Center
6. Exit the registry editor. 7. Use Windows Explorer to delete the following: The directory in which eHealth r5.7.9 or r6.0 is installed, and all of its subdirectories and files. The eHealth r5.7.9 or r6.0 program folder located in C:\Documents and Settings\All Users\Start Menu\Programs. eHealth r5.7.9 or r6.0 is the default. The administrator who installed it may have named it differently.
Important! Do not delete the eHealth 6.2.2 program folder. eHealth r5.7.9 or r6.0 is removed.
Remove eHealth r5.7.9 or r6.0 (UNIX)

To remove eHealth Release r5.7.9 or r6.0 1. Rename the old eHealth installation directory to test for any processes that still use it. For example, if eHealth r5.7.9 is installed in /export/ehealth, change the folder name to /export/old_ehealth. 2. Wait a day or two to verify that eHealth r6.2.2 is working properly. If you encounter any new problems related to required files that reside in the old eHealth directories, resolve them before proceeding. 3. Log on as root. 4. Remove the eHealth r5.7.9 or r6.0 installation directory (ehealth_old) and its contents by entering the following command:
rm -rf ehealth_old
The eHealth r5.7.9 or r6.0 directory and its contents are removed.

If you no longer want to use Report Center, you can remove the software. In eHealth r6.0, this will free up disk space. In eHealth r6.2.2, Report Center is part of the eHealth installation and uninstalling it will not free up disk space because RegData is now used by other features in eHealth. However, in eHealth r6.2.2 you have the option of disabling Report Center (Cognos) servers in order to free up disk space.
The procedures in this section describe the removal and disabling of Report Center software separately from eHealth. Follow the procedures if: You are removing Report Center from eHealth r6.0 systems before upgrading to eHealth r6.2.2. You have already installed eHealth r6.2.2 along with the latest version of Report Center.
Note: Report Center can be reinstalled manually outside of the regular eHealth installation.
Remove Report Center from eHealth r6.0 Systems

The Report Center removal program deletes tables associated with reports and configuration information, and other data that was created for Report Center, and frees up a significant amount of disk space on your system. To remove Report Center from eHealth r6.0 Windows systems 1. Log in to the eHealth system as the eHealth administrator. 2. Navigate to the Control Panel and click Add/Remove Programs to access the removal program. 3. Select the eHealth Report Center application and click Remove. 4. Click Yes when prompted to verify that you want to remove the application. 5. Specify the Report Center components that you want to remove. 6. Delete the backup_RptCtr_600_00 folder in the eHealth home directory, if the folder still exists, after the removal program has finished. To remove Report Center from eHealth r6.0 UNIX systems 1. Log in to the eHealth system as the eHealth administrator. 2. Change to the eHealth home directory and source the appropriate nethealthrc file for your shell environment. 3. Run the following command to remove the Report Center software:
./backup_RptCtr_600_00/uninstall
4. Specify the Report Center components that you want to remove. 5. After the removal program has finished, remove the backup director by entering the following command:
rmdir backup_RptCtr_600_00
Disable Report Center on eHealth r6.2.2 Systems

You can disable Report Center (Cognos) servers to increase available disk space. To disable Report Center on Windows 1. Right-click on the service named "eHealth Report Center61:9301" on the Windows Services panel, and select disable. 2. Rename $NH_HOME/sys/nhReportCenter.cfg to $NH_HOME/sys/nhReportCenter.cfg.backup 3. Run the following command:
nhParameter -set reportCenterInstalled no
To disable Report Center on UNIX 1. Rename $NH_HOME/sys/nhReportCenter.cfg to $NH_HOME/sys/nhReportCenter.cfg.backup 2. Run the following command:
nhParameter -set reportCenterInstalled no
Remove Report Center from eHealth r6.2.2 Systems

eHealth r6.2.2 does not include an uninstaller for Report Center, which is part of the regular eHealth installation. However, you can manually uninstall Report Center if you no longer need it. Note: Uninstalling Report Center will not make more disk space available because RegData is now shared by other eHealth features. To remove Report Center from eHealth r6.2.2 systems 1. Log in to the eHealth system as the eHealth administrator and open the command line interface. 2. Stop Report Center servers by entering the following command:
nhReportCenter stop
3. Enter the following text to check for running processes:

cogbootstrapservice BIBusTKServerMain java with "Xmx768"
4. Enter the following text to stop any running services: a. b. c. Windows: Stop "eHealth Report Center:9301" Service Run $NH_HOME/crn/bin/shutdown Stop any remaining processes.
5. To disable Report Center-related database jobs, clean out Report Center entries from the NH_PARAMETER table :
$NH_HOME/bin/sys/nhisql "delete from nh_parameter where setting_name like 'reportCenter%' and setting_name not like 'reportCenterSampleDb%'"
6. (Optional) Remove Cognos Content Store database by running the following command:
$NH_HOME/bin/nhRptCtrConfig -action clearCognosSchema
Important! This step destroys any reports you have developed in Report Center. 7. Run the following commands to eliminate folders and files: Important! Use this list for eHealth r6.2.2 Report Center cleanup only. Do not use this for previous releases of eHealth. a. Delete the following folders:
$NH_HOME/crn
b.
Delete the following files: $NH_HOME/sys/nhReportCenter.cfg $NH_HOME/upgrade/*.ats $NH_HOME/upgrade/pkg* $NH_HOME/reportcenterrc.*
Index
A
adding, swap space 84 Apache web server 101
I
installation guidelines 12 installation media 34, 46 prerequisites 16 installation media mounting 93 unmounting 98 installing additional tasks 39, 57, 67, 70, 77 finalizing upgrade 69, 79 on UNIX 52, 74 on Windows 35, 65 postinstallation tasks 98 preinstallation tasks 83 Report Center 42, 60 InstallPlus program 26 ISO image, mounting on a Solaris system 49
B
backing up files and directories 135 Windows registry 136
C
cleanup tasks 70, 80 clusters activating eHealth 132, 134 removing systems 127 restoring eHealth 131 rollback downtime 127 troubleshooting upgrades 126 conversion check 24
D
data and time format 52 data loss 23 directories, confirmation (UNIX) 136 Distributed eHealth activating 23, 67, 77 downtime 23
K
kernel requirements, checking and modifying 87
L
licenses 41 Live Health 70
E
eHealth console 121
M
mail server, specifying 99 MKS X server 121 mounting the DVD drive 93
F
file system format 83
G
groups and group lists 24 guidelines remote poller sites 20 report center 15, 20 software and database locations 14, 19
N
NTFS 83 Nutcracker installing 33 registry entries 140 uninstalling 138
H
hostnames, changing 84
O
Oracle registry entries 140 software 29, 35 uninstalling 138
Index 155
overview 9
V
virtual memory 84 VMware, how to install 15
P
port numbers, changing 101 printer, specifying 100
W
web server port number 101
R
registry entries 136, 140 remote poller 20, 25 Report Center guidelines 15, 20 installing 42, 60 resource files 143 restoring eHealth 128, 131 rollback 132, 134 root user 12
S
SAM tool 92 security 24, 34 SMTP mail server 99 software and database location, guidelines 14, 19 swap space 84 System Administration Manager 92 system hostname, changing 84 system resources, determining 16
T
Traffic Accountant, LCF 15, 20 TrapEXPLODER activating 40, 58 error 119 troubleshooting 117
U
uninstalling eHealth r5.7 or r6.0 148 eHealth r6.2 137 preuninstallation tasks 135 Report Center 150 unmounting the DVD drive 98 upgrading data loss and downtime 23 guidelines 18 installing 65, 74 merging groups and group lists 24 prerequisites 21

Ehealth Installation Enu

Uploaded by

Copyright:

Available Formats

Ehealth Installation Enu

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ehealth Installation Enu

Uploaded by

Copyright:

Available Formats

CA eHealth

CA Technologies Product References

Chapter 2: Preparing for Installations and Upgrades

Chapter 3: Installing eHealth (Windows)

Chapter 4: Installing eHealth (UNIX)

eHealth Installation ........................................................................... 45

Chapter 5: Upgrading eHealth (Windows)

Chapter 6: Upgrading eHealth (UNIX)

Appendix A: Administration Tasks Reference

Appendix C: Removing eHealth and Related Applications

Chapter 2: Preparing for Installations and Upgrades

Installation Guidelines and Prerequisites

Chapter 2: Preparing for Installations and Upgrades 11

Installation Guidelines and Prerequisites

Installation Guidelines and Prerequisites

Chapter 2: Preparing for Installations and Upgrades 13

Installation Guidelines and Prerequisites

Software/Database Location Guidelines

Installation Guidelines and Prerequisites

Report Center Guidelines

How to Install VMware (Windows)

Chapter 2: Preparing for Installations and Upgrades 15

Installation Guidelines and Prerequisites

How to Determine Your System Resources

Installation Guidelines and Prerequisites

How to Prepare for the eHealth Installation

Chapter 2: Preparing for Installations and Upgrades 17

Upgrade Guidelines and Prerequisites

Upgrade Guidelines and Prerequisites

Upgrade Guidelines and Prerequisites

Software Location Guidelines

Chapter 2: Preparing for Installations and Upgrades 19

Upgrade Guidelines and Prerequisites

Report Center Guidelines

Remote Poller Site Upgrade Guidelines

Upgrade Guidelines and Prerequisites

How to Determine Your System Resources

Chapter 2: Preparing for Installations and Upgrades 21

Upgrade Guidelines and Prerequisites

How to Prepare for the eHealth Upgrade

Upgrade Guidelines and Prerequisites

Data Loss and Downtime

Standard eHealth Upgrades

Remote Polling and Distributed Upgrades

Chapter 2: Preparing for Installations and Upgrades 23

Upgrade Guidelines and Prerequisites

Merging Groups and Group Lists

Upgrade Guidelines and Prerequisites

Merged Groups and Group Lists on Remote Pollers

Chapter 2: Preparing for Installations and Upgrades 25

Required Software for eHealth r6.2.2

Required Software for eHealth r6.2.2

Extract the InstallPlus Program

Required Software for eHealth r6.2.2

Chapter 2: Preparing for Installations and Upgrades 27

Required Software for eHealth r6.2.2

Required Software for eHealth r6.2.2

Extract the Oracle Update Software

Chapter 2: Preparing for Installations and Upgrades 29

Required Software for eHealth r6.2.2