ca ehealth readme · pdf filesince r6.3.0, ca ehealth has been released with maintenance kits...

Chapter 1: CA eHealth r6.3.2.07 Readme

What’s new in CA eHealth r6.3.2.07

Platform Updates

■ Added support for Windows 2012 R2 Standard Edition

■ Supports Oracle 11.2.0.4 (Updating or installing eHealth 6.3.2.07 will upgrade Oracle to 11.2.0.4.)

■ Apache FIPS implemented

Updated Browser Support

■ Firefox version 31.0

■ Chrome version 36.x

■ Support for Windows 8 client

Updates to Third-Party Software

This release contains updates to the following included technologies:

■ Apache HTTP Web Server version 2.4.10

■ Oracle Java Runtime Environment (JRE) 1.7.0_71

■ Open SSL version 1.0.1i

■ Apache Tomcat Web Server 7.0.55

■ MKS Toolkit 9.6

■ Oracle 11.2.0.4

See the CA eHealth Release Notes for a complete list of other included third-party software. The license texts for the above-listed technologies appear at the end of this document, except where noted above.

Please review these third-party software revisions on each vendor’s respective website in order to determine which functionality and security concerns have been addressed.

Release r6.3.2.07

This release contains changes to the following areas:

■ Database platform: Updating to 6.3.2.07 will upgrade Oracle to 11.2.0.4.

■ Integrations: The most recent CA eHealth revision that has been fully tested for CA SiteMinder integration is r6.3.1.01. As such, SiteMinder is not compatible with eHealth r6.3.2.07. CA recommends continuing with r6.3.1.01 until additional compatibility eHealth-SiteMinder compatibility is announced.

Since r6.3.0, CA eHealth has been released with Maintenance Kits instead of service packs. These maintenance kits are cumulative and the revision is indicated in the fourth decimal, as in Release 6.3.2.xx. Each Maintenance Kit is a full installation kit; and it will use the same eHealth home directory ($NH_HOME) for updates. The r6.3.2.07 kits contain both the InstallPlus kit and the complete CA eHealth kit. When you are prompted to enter the CA eHealth disk location, supply the CA eHealth directory from the r6.3.2.07 kit.

You can use eHealth maintenance kits to:

■ Perform an eHealth Update or Upgrade

■ Perform a fresh installation of eHealth, and subsequent Machine Migration

Update:

An update Installs eHealth 6.3.2.x using the existing eHealth home directory

Upgrade:

An upgrades Installs eHealth 6.3.1.x into a new eHealth home directory

Machine Migration:

Requires a fresh Install eHealth 6.3.2.x on a system following the instructions in "Migrating CA eHealth Servers" in the CA eHealth Installation Guide

Please use the tables below to determine the installation mechanism to get your system to eHealth 6.3.2.07.:

Source eHealth Release

Source OS Destination ehealth Release

Destination OS

Installation Mechanism

6.2.2( D15 or less)

Windows 2003, Solaris 9 , HP-UX11, Solaris 10

6.3.2.x All Machine Migration

6.2.2 (D12 or less)

Solaris 10 6.3.2.x Solaris 10 1) Upgrade to 6.3.1.06

2) Update to 6.3.2.n

6.3.0.n (D11 or less)

Solaris 10 6.3.2.x Solaris 10 Update

6.3.1.n (D13 or less)


6.3.2.n (D15 or less)


6.3.0.n (D11 or less)

Linux 5.5 or 5.6 6.3.2.x Linux 5.8 1) Update OS to 5.8

2) Update eHealth

6.3.1.n (D13 or less)

Linux 5.8 6.3.2.x Linux 5.8 Update

6.3.2.n (D15 or less)

Linux 5.8 6.3.2.x Linux 5.8 Update

6.3.0.n (D11 or less)

Linux 5.y 6.3.2.x Linux 6.y Machine Migration

6.3.1.n (D13 or less)


6.3.2.n (D15 or less)


6.3.0.n (D11 or less)

Windows 200x 32 bit

6.3.2.x Windows 2008 64 bit

Machine Migration

6.3.1.n (D13 or less)

Windows 200x 32 bit


Machine Migration

6.3.1.n (D13 or less)

Windows 2008 64 bit


Update

6.3.2.n (D15 or less)

Windows 2008 64 bit


Update

6.3.0.n (D11 or less)

All Windows OS 6.3.2.x Windows 2012

Machine Migration

6.3.1.n (D13 or less)


Machine Migration

6.3.2.n (D15 or less)


Machine Migration

Existing OS Existing eHealth Release/Certification Level

New OS New eHealth Version/Certification Level

Installation Mechanism

Window 2008 64 bit

6.3.2.x (D15 or lower), 6.3.1.x (D13 or lower)

Windows 2008 64-bit

6.3.2.07 (D15) Update

Window 2008 64 bit

6.3.2.x (D15 or lower), 6.3.1.x (D13 or lower)

Windows 2012 64-bit

6.3.2.07 (D15) Machine Migration

Windows 2008 32 bit, Windows 2003 32 bit

6.3.1.x (D13 or lower), 6.3.0.x (D11 or lower), 6.2.2.x (D15 or lower)

Windows 2008 64 bit, Windows 2012 64 bit


RedHat 6.5 6.3.2.x (D15 or lower)

RedHat 6.5 6.3.2.07 (D15) Update

RedHat 5.8 6.3.2.x (D15 or lower), 6.3.1.x (D13 or lower)

RedHat 6.5 6.3.2.07 (D15) Machine Migration

RedHat 5.8 6.3.2.x (D15 or lower), 6.3.1.x (D13 or lower)

RedHat 5.8 6.3.2.07 (D15) Update

RedHat 5.5, RedHat 5.6

6.3.0.x (D11 or lower)


RedHat 5.5, RedHat 5.6



Solaris 5.10 6.3.2.x (D15 or lower), 6.3.1.x (D13 or lower), 6.3.0.x (D11 or lower)

Solaris 5.10 6.3.2.07 (D15) Update

Solaris 5.9 6.3.0.x (D11 or lower), 6.2.2.x (D15 or lower)

Solaris 5.10 6.3.2.07 (D15) Machine Migration

HP-UX 11


Windows 2008 64 bit, Windows 2012 64 bit, Solaris 5.10, RedHat 5.8, or RedHat 6.5,


Important: The Destination eHealth Release MUST be on a Certification Level that is greater than or equal to the Source Certification Level 6.3.2.x where n=07 D15

Update:

Install eHealth 6.3.2.x on top of the existing eHealth

Upgrade:

Install eHealth 6.3.1.x in a parallel directory

Machine Migration:

Install eHealth 6.3.2.x on a different system following the instructions in "Migrating CA eHealth Servers" in the CA eHealth Installation Guide

Updates to Third-Party Software

This release contains updates to the following included technologies:

■ Apache HTTP Web Server version 2.4.10

■ Oracle Java Runtime Environment (JRE) 1.7.0_71

■ Open SSL version 1.0.1i

■ Apache Tomcat Web Server 7.0.55

■ MKS Toolkit 9.6

See the CA eHealth Release Notes for a complete list of other included third-party software. The license texts for the listed technologies appear at the end of this document, except where noted above.

You can review the listed versions of software on the websites of the vendors to determine whether the versions resolve the functionality and security concerns at your organization.

Performing an Update or Upgrade

When performing upgrades and updates, follow the instructions described in Appendix A for a fresh installation. Updates and upgrades may have fewer user prompts.

During updates Release 6.3.2.07, the installation program recognizes the prior installation of CA eHealth on your system and does not prompt you for the CA eHealth home directory. You are prompted for Oracle kits.

Note: If eHealth was installed using pre-installed Oracle version 10G, upgrading to the eHealth using Oracle 11G on the same system is not supported in the release 6.3.2.07. This upgrade case will be supported in a future eHealth release. Alternatively, you can upgrade to eHealth 6.3.2.07 on a different system. You need to save the Oracle 10G database in ASCII mode on the existing eHealth system, and install eHealth 6.3.2.07 using Oracle 11G fresh on a separate system; and then load the ASCII saved Oracle 10G database into the eHealth 6.3.2.07 system.

For our unbundled Oracle customers, there are 2 use cases.

1. A fresh install, in which case the customer needs to install Oracle 11.2.0.4 first and then install eH 6.3.2.07 using the normal current unbundled instructions,

2. An eHealth update install. The eHealth update install using unbundled Oracle, is more complex with Oracle 11g. For example, if you have eH 6.3.2.05 with unbundled Oracle 11.2.0.3 running and you want to update eHealth to 6.3.2.07, then you FIRST upgrade unbundled Oracle to 11.2.0.4 (while still on eH 6.3.2.05) THEN update eHealth to 6.3.2.07. The complex part comes from the Oracle 11.2.0.3 to 11.2.0.4 upgrade. Since eHealth is already installed, the ORACLE_HOME and ORACLE_HOME_NAME values MUST remain the same. This means it needs to be an in-place upgrade. The problem is the difference between Oracle 10g and 11g. In Oracle 10g the patchsets (which bump the minor version from 10.2.0.4 to 10.2.0.5) were a collection of patches and could be applied on top of an existing Oracle installation. Oracle changed this in 11g and the patchset is now a FULL Oracle install. So 11.2.0.4 is really a full Oracle install and the Oracle installer complains if you try to install it over 11.2.0.3. So, you need to "move 11.2.0.3 aside" so that you can install 11.2.0.4 in the same ORACLE_HOME and ORACLE_HOME_NAME as the original Oracle installation (so eHealth variables are the same). Look in links for "Oracle 11g upgrade doc" and search for the section: "Optionally Performing an In-Place Upgrade (Into the Same Oracle Home)". It explains how to detach the ORACLE_HOME_NAME so it can be reused and then you rename the old 11.2.0.3 directory so you can install 11.2.0.4 to the old ORACLE_HOME directory.

Updating Clusters

When updating a cluster from CA eHealth r6.3.0 or r6.3.1 to r6.3.2, update the front-end system first before updating the back-end system. This updates certifications on the front-end system, allowing reporting on not yet discovered elements on back-end systems with the new certification before all systems in the cluster are updated to CA eHealth r6.3.2.

Note: All systems that are brought to Release 6.3.2 by means other than a fresh installation or a database load are updates. Therefore, the systems may require activation in a CA eHealth cluster environment. Rollback to the previous release is unavailable.

Installing CA eHealth r6.3.2.07

Download Procedure for Fresh eHealth 6.3.2.07 Installation

1. Go to Support site URL.

2. Click Download Center tab on the left.

3. Click Published Solutions tab under the Download Center.

4. Under “Select a Product” choose “CA eHealth E2E Console - MULTI-PLATFORM” from dropdown list.

5. Select 6.32 as a release, then click “Go” at the bottom; download the following media depending on your OS types.

6. Click the green Matches arrow on the top middle of the page to advance to the next page if you don’t see your items listed.

■ CA EHEALTH 6.3.2.07 MAINTENANCE RELEASE

■ CA EHEALTH 6.3.2 ORACLE 11.2.0.4 BASE

■ CA EHEALTH 6.3.2 ORACLE 11.2.0.4 UPDATE

Installation procedure for a fresh 6.3.2.07 installation on Windows, Linux and Solaris

Directory names are just suggestions not recommended or mandatory.

1. Create a directory named 6.3.2.07_download and three subdirectories each named eh63207, OracleBase, and OracleUpdate on the partition where ehealth 6.3.2.07 will be installed.

2. Copy CA EHEALTH 6.3.2.07 MAINTENANCE RELEASE into the directory named eh63207, then unzip it using a zip utility.

3. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.4 BASE into the directory named OracleBase, then unzip it using a zip utility .

4. Copy CA EHEALTH 6.3.2 ORACLE 11.2.0.04 UPDATE into the directory named OracleUpdate, then unzip it using a zip utility.

5. Go to directory eh63207 and click setup.exe (Windows) or run ./Install (Linux and Solaris) to start the 6.3.2.07 fresh installation.

6. When prompted, enter full path for OracleBase directory, then the full path for OracleUpdate directory.

7. Follow the prompts to complete the fresh installation, refer to the Appendix A for details.

http://www.https:/support.ca.com/irj/portal/SolutionCDNResults

http://www.https:/support.ca.com/irj/portal/SolutionCDNResults

Device Certification Updates

The following sections provide information about supported devices.

Manufacturer Model Version

Adtran 908e R10.5.3.E

Arris E6000

AUS-RIC-APP01 SWAP

Avaya Networks 4850GTS-PWR+FW:5.6.2.1 5.6.2.027

Avaya Networks 5698TFD

Avaya Networks 4850GTS

Avaya Networks 5650TD FW:6.0.0.10,SWv6.2.0.008

Bluecoat SG6000 Series SGOS 6.2.10.7

Broadsoft Broadworks Application server

v20

Brocade NetIron XMR 5.3.00e

Brocade Vdx6740

Checkpoint 4800

Checkpoint Checkpoint

Checkpoint R75.40

Cisco s2t54

Cisco 2901

Cisco 2921 15.2(4)M4

Cisco 3700 Version 12.4(25b)

Cisco 3925

Cisco 4500 L3

Cisco 5500 WLC

Cisco 5500 WLC

Cisco ASR Version 15.0(56027)

Cisco C3560 12.2(55)SE5

Cisco Catalyst 3850 switch series XE release 3.3.1SE

Cisco Cisco ASR 1002 12.2(33)XND3


Cisco MSP 1-RU DiVA Connect V4.02.067

Cisco n5000-uk9 5.2(1)N1(6)

Cisco n7000-s1-dk9 6.0(3)

Cisco Nexus 1000

Cisco Nexus 93128

Cisco Nexus 1000v

Cisco Nexus 5000 5.2(1)N1(5)

Cisco Nexus 5548

Cisco Nexus 5596 1100W

Cisco Nexus 6001 6.0(2)N1(2)

Cisco Nexus 7004 6.1(2)

Cisco Nexus n5000 6

Cisco Nexus_5548

Cisco NX N7000 6.2(6a)

Cisco NX7K N7000-S2-DK9 6.1(4)

Cisco router 1841 v12.4(15)T13b

Cisco Router 2901 15.2(4)M3.1.

Cisco S670 8.0.5-075

Cisco SG500-28

Cisco UCS-6100

Cisco WAVE 7541

Cisco Wave Mgr 214

DCC DB

Dell Poweredge 2950 2.3.1

eaton 9130 and 9390

EMC Brocade-DS-6510B

EMC DS-5300B

Emerson LibertPac

Emerson liebert 160KVA & 20 KVA


F5 Model BIG-IP 6900 11.4.1 Build 647.71

F5 VIP 4200V

F5 Viprion BIG-IP 11.5.1 Build 0.131

F5 Signaling Delivery Controller 4.0.2

F5 BIG-IP VPR-B4300 11.4.0

FireEye NX10000 FireEye/7300 --Central Management System (CMS)

Forti Analyzer 400B

Fortigate 5101C FG-51C-FW-4.00-672

Gigamon Gigavue H series 2.8.0.2

H3G HP A5500 5.20 Release 2208P01

Hitachi NAS Platform 10.2.3072.06

Huawei AR1220 5.120 (AR1220 V200R003C01SPCc00)

Huawei AR3260 5.16

Huawei NE40E&80E 5.15

IBM RackSwitch G8052

IBM TS3500

IBM x3550 1.06

Infoblox 1420 6.6.11

Infoblox 2220 6.6.11

Insight 11.5 agent

Interface Masters Niagara SNMPTR

Juniper JA1500

Juniper MX104

Juniper Mx480

Juniper Mx960 11.4R7.5

Juniper SRX1400

Juniper T1600 12.3R5.7




Juniper IDP 8200

Juniper M320 10.0R4.7

Keytronix ISAD

Linux NET-SNMP 5.5

Load Balancer BIGIP 3600

Mcafee Esm 5600

Mcafee WG 5500

McAfee Web Gateway device

MCU MSE 8420

Mediatrix 33xx

Mediatrix 41XX - 4108/4116/4124

Microsoft Windows 2012

Motorola Nx 7530 5.5.4.0-018R

Netasq U150 Firewall

NetScaler NetScaler ns10.1 Build 122.17.nc

Nortel Networks 4850 GTS

Nortel Networks 5520-48T-PWR

Nortel Networks 5520-48T-PWR FW:5.0.0.3 SW:v5.0.6.027

Nortel Networks 5520-48T-PWR

Nortel Networks 5530-24TFD SW:v6.1.1.016

Nortel Networks 5632FD

Nortel Networks Ethernet Routing Switch 5632FD

6.1.3.025

Nudesign SNMPv3 Master Agent

One Access 1645

Palo Alto Networks PA-2000

Palo Alto Networks PA-5020 5.0.12

POLYCOM QDX6000

RAD datacomm 204a ftmyflgy Hw: 2.01, Sw: 2.234


Radware Load balancer 2008

Radware LoadBalancer 1008

Riverbed 550M Linux 2.6.9-34.EL-rbt-16251SMP #2 SMP

Solaris 11 5.4.1

Technicolor TG670

Tiesse Tiesse Imola 5262

UTOD ConcentratorGateway

VMware vApps

VMware UCOS 4.0.0.0-45

CA eHealth Cumulative Device Support

You can view a complete list of devices that are certified for use with CA eHealth at the following website: http://ehealth-spectrum.ca.com/devices/

Note: To access this website, supply your CA Technologies Support Contract ID and password. By logging in to the secure side of this site, you can view information about how each device was certified. This login method is recommended because it gives you access to specific information about the support that is provided for each device.

Chapter 2: Updates to Time Zones

Many changes were made to the CA eHealth time zone support in eHealth 6.3.2.01 release. To obtain these fixes you must be running at least ehealth 6.3.2.01 or later. In general, the changes included:

■ Modifications to internal time zone mapping files.

– Aliases were added to support more local country mappings.

– Time zones with the wrong operating system mapping that caused incorrect mapping to DST and non-DST time zones were fixed.

– Missing time zone definitions for either a DST or a non-DST instance were added. In particular Brasilia, Brazil/east was added to support GMT-3 with DST support.

– Other changes are brought on by countries or regions changing their DST rules over time. For example, most of Russia changed their DST rules, and cities such as Moscow no longer use DST.

■ Updates to 3rd party libraries used in time zone support code. CA eHealth now follows the Olson time zone database. This means that time zone and DST support changes can be more quickly rolled out to the customer base.

■ Oracle 11g has built in support for Africa/Harare time zone (once it has been enabled).

■ A number of other time zone related bugs were fixed, especially in the reporting and user interface areas (both OCE and Web UI).

These changes can highlight other time-related problems on your systems. For example, setting the wrong time zone or setting the wrong DST setting, due to either an error or due to implementing your own fixes to the CA eHealth time zone files. In either case, you may notice different behavior once these time zone changes are installed with this release. Even with the updated time zone support, you can still have issues that require you to modify your time zone settings.

However, there can be other time zone issues that are not fixed by just updating the CA eHealth software. The issues can include problems with the actual operating system time zone definitions. Be vigilant about implementing the current time zone information for your particular operating system. Microsoft, Sun, Oracle, and Red Hat all provide updates occasionally. For example, many of the Russian time zone changes were made toward the end of 2011. Without further updates, the operating system would likely still use DST and be incorrect by 1 or 2 hours.

New Time Zone Support for Oracle

To turn on support for the Africa/Harare time zone in Oracle, follow the process that is documented on the following website:

http://mpoojari.wordpress.com/2011/06/04/upgrade-timezone-version-to-14-after-upgrading-to-11-2-0-2/

Note: In previous versions of CA eHealth that used Oracle 10g, support for Africa/Harare required a separate Oracle patch.

Deprecated Time Zones

The following time zones are deprecated. Contact Technical Support for help in removing these items from your database.

■ msk-2msd - Russian Standard Time Windows

■ gmt-4.30 - Afghanistan Standard Time Windows

■ sanodst - South Africa Standard Time Windows

Chapter 3: Operating System Support

Install CA eHealth on a dedicated Windows, UNIX, or Linux workstation with one of the following operating systems:

■ Windows Server 2012 R2

– 64-bit systems are supported.

– User Account Control (UAC) must be disabled.

– No other major applications should be running on the system.

– A fresh Windows installation is required.

■ Windows 2008

– 64-bit systems are supported.

– User Account Control (UAC) must be disabled.

– No other major applications should be running on the system.

■ Solaris

– 2.10 (SPARC)

■ Linux

– Red Hat Enterprise Linux 6.5

– Red Hat Enterprise Linux 5.8 or higher

The installation must be run on a 64-bit system.

Note: CA ARCserve software supports CA eHealth on Linux.

Important! Set the Time Zone variable TZ on Linux before installation, and make this value part of the user profile. Make sure that 32 bit glibc-2.12-1.107.el6.i686 is installed on the RHEL 6.5 system before starting installation. In absence of this library the install package will not open.

Chapter 4: Installation with Operating System Support Changes in Release 6.3.2, Release 6.3.2.05 and Release 6.3.2.07

The list of supported operating systems was updated in CA eHealth Release 6.3.2.07. Carefully review the following information:

Support has been added for the following operating systems:

■ Windows 2008 (64-bit)


■ Red Hat Linux 6.5 (64-bit)

Support was removed for the following operating systems:

■ Red Hat Linux 5.5 and 5.6 (removed in Release 6.3.1)

■ Solaris 5.9 (removed in Release 6.3.1)

■ Windows 2003 (removed in Release 6.3.1)

■ Windows 2008 R1 (32-bit) (removed in Release 6.3.2)

The following list describes the operating systems that CA eHealth r6.3.2.07 supports:

■ Solaris 5.10 (64-bit)

■ Red Hat Linux 5.8 (64-bit)

■ Red Hat Linux 6.5 (64-bit) supported by r6.3.2.05 and higher



Important! Review the following information before you install CA eHealth Release 6.3.2.07:

Of the operating systems that are no longer supported, only Red Hat Linux supports an in-place update of the operating system from 5.5 or 5.6 to the Red Hat Linux 5.8 version that CA eHealth Release 6.3.1 and higher requires. For Red Hat Linux 5.5 or 5.6, you can update the operating system in-place to Red Hat Linux 5.8, and then run the CA eHealth 6.3.1 or 6.3.2 update installation.

The Linux, Solaris and Windows operating systems do not support an in-place major release operating system update. For Solaris 5.9, Windows 2003, Windows 2008 R1 (32-bit), and Linux 5.8 where you currently have CA eHealth running on an operating system that is going out of support, you must follow the two server migration instructions. Red Hat does NOT support in-place upgrades from Linux 5.x to 6.x.x., you must follow the two server migration instructions

These instructions describe how to:

1. Save your old eHealth data

2. Install a fresh CA eHealth Release 6.3.2 on a supported operating system

3. Load your saved eHealth data from the old system

Note: See "How to Migrate a Standalone CA eHealth Server" in the CA eHealth Installation Guide for this procedure.

If you plan to change the operating system where CA eHealth is running, such as changing from 32-bit Windows to 64-bit Windows, or Linux from 5.x to Linux 6.x, use the two-server migration procedure.

For Solaris 10 (5.10), an existing release of CA eHealth (before Release 6.3.1) may be running on the system. For those systems, the normal CA eHealth installation procedure can handle the update to CA eHealth Release 6.3.2.

Chapter 5: Oracle System Requirements

CA eHealth Release 6.3.2 requires the Oracle 11g Enterprise Edition 11.2.04 or later database. You can update your Oracle DBMS in the following ways:

■ Upgrade Oracle before updating to CA eHealth Release 6.3.2 (if you are installing CA eHealth Without Database).

■ If you are not installing CA eHealth Without Database, the Oracle upgrade is performed during the CA eHealth Release 6.3.2.x update.

During this typical installation, Oracle is upgraded from 10g to 11g. A corresponding 11.2.04 OOB is provided and is also installed. The 11.2.04 OOB contains the latest Oracle SPU (for Linux and Solaris) and the Oracle Patch Bundle 23 for Windows.

Oracle no longer provides updates to version 10.2.0.4 or 10.2.0.5. Go to CA Technologies Support to obtain the most recent OOB (11.2.04).

Important! Review the following information:

■ Perform a backup of your data (nhSaveDb) before starting the upgrade to CA eHealth Release 6.3.2.xx. This is a best practice because a database schema change is part of the eHealth update. Perform an ASCII database save because a binary save is not supported. That is, only an ASCII database save can be loaded between the Oracle 10g and the Oracle 11g versions.

Important! eHealth 6.3.2.07 requires using Oracle 11.2.0.4. If eHealth 6.3.2.x was installed using pre-installed Oracle 11.2.0.3, follow the below steps to update to eHealth 6.3.2.07.

1. Ensure that the existing eHealth is running without problem.

2. Stop eHealth by running

a. nhServer stop

b. Manually stop remaining eHealth processes if any

3. Perform in place Oracle 11.2.0.4 upgrade install (refer instructions provided by Oracle, https://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#UPGRD52735 (eHealth 6.3.2.07 requires using Oracle 11.2.0.4. If eHealth 6.3.2.x was installed using pre-installed Oracle 11.2.0.3, follow the below steps to update to eHealth 6.3.2.07. )

– Backup the following Oracle 11.2.0.3 directories

a. $ORACLE_HOME/dbs

b. $ORACLE_HOME/database

c. $ORACLE_HOME/network/admin

d. $ORACLE_HOME/owb/bin/admin

e. $ORACLE_HOME/hostname_dbname

f. $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_hostname_dbname

– Stop database by running

http://www.ca.com/support


– nhStopDb immediate

– Manually stop remaining Oracle processes if any, such as Oracle<SID> VSS Writer Service and OracleMTSRecoveryService

– Detach the current Oracle Home by running

– $ORACLE_HOME/oui/bin/setup –detachHome ORACLE_HOME=this oracle home

– Rename the current $ORACLE_HOME, i.e. $ORACLE_HOME_11203

– Install Oracle 11.2.0.4 Software to the same location as Oracle 11.2.0.3 installed. For example, if Oracle 11.2.0.3 was install at d:\Oracle, and it is renamed to d:\Oracle_11203; install Oracle 11.2.04 to d:\Oracle.

– Restore the saved Oracle 11.2.0.3 directories in step 3.a into newly installed Oracle 11.2.0.4.

– Ensure Oracle start automatically by running

– oradim -EDIT -sid $ORACLE_SID -startmode AUTO

– Upgrade Oracle single instance by running

– $ORACLE_HOME/bin/dbua

4. Ensure that Oracle client is before the Oracle server in the system PATH.

5. Ensure that the environment variable NH_ORA_CLIENT_HOME is pointing to the correct location.

6. Reboot the system (Windows).

7. Verify that eHealth works without problem using Oracle 11.2.0.4.

8. Install eHealth 6.3.2.07.

See the following guides for other system requirements:

■ Release Notes

■ Integration Modules Release Notes

Chapter 6: CA eHealth and CA Spectrum® Considerations

The following considerations apply to the integration of CA Spectrum with CA eHealth.

CA Spectrum r8.x or r9.0.x is not supported with the present version of CA eHealth.

CA Spectrum Integration

The following information pertains to the CA Spectrum and CA eHealth integration:

■ CA Spectrum communicates with CA eHealth through the CA eHealth web server (Apache) port by using a web services API.

■ The CA Spectrum discovery uses same code as the OneClick for eHealth (OCE) Interactive Discover UI, which uses Java classes.

■ Name synchronization performance is significantly improved with CA eHealth r6.2.2 and CA Spectrum r9.2.H03. (PRD00052498)

How to Enable One-way Authentication from CA Spectrum to CA eHealth

The CA Spectrum to CA eHealth single authentication option provides one-way drill-down from CA Spectrum to CA eHealth through Embedded Entitlements Manager. This integration lets you use CA Spectrum to access the CA eHealth web user interface without being challenged for a user login. This authentication option is not bi-directional.

Note: Embedded Entitlements Manager offers support for several types of authentication, including LDAP. The Embedded Entitlements Manager integration for CA eHealth and CA Spectrum is limited to one-way single sign-on from CA Spectrum to CA eHealth. Though Embedded Entitlements Manager supports more authentication types, any implementation beyond single authentication is considered a customization, and coverage is not included as part of standard CA support. Contact CA Services for more information about custom implementations, including the LDAP option.

The user name synchronization across CA eHealth, Embedded Entitlements Manager, and CA Spectrum must be maintained.

Note: Although OneClick for CA eHealth user names and web user interface user names are case-sensitive, Embedded Entitlements Manager 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 a CA eHealth web user account, the administrator must establish one for the user.

a. Log in to the CA eHealth OneClick Portal (http://<EHEALTH_CONSOLE>/OneClickEH) and click Launch OneClick for eHealth.

b. In the left pane, select Tasks and Information, User Administration.

c. Right-click User Administration and select New User.

d. Specify a User account and password, and appropriate access permissions that includes CA eHealth OneClick access.

2. To ensure that all features are accessible through the CA eHealth web user interface, the administrator must enable those privileges by configuring the web user account of the CA Spectrum user appropriately.

3. The user must have three identical user accounts (with the same user name) for the Embedded Entitlements Manager server, CA eHealth Apache Web server, and CA Spectrum user database server.

4. The CA Spectrum administrator for the system must install Embedded Entitlements Manager software and must follow the installation procedures in the Embedded Entitlements Manager documentation. Embedded Entitlements Manager must be installed on a separate, standalone server system.

Note: If you want to use the LDAP authentication with the integration, configure the Embedded Entitlements Manager server accordingly. For more information, see the Embedded Entitlements Manager documentation.

The CA eHealth administrator for the system must run the nhWebSso command-line utility to enable the CA Spectrum - CA eHealth system to use the one-way drill-down authentication. Run this utility on both the CA eHealth back-end polling server and the CA eHealth reporting front-end server. You run this utility on both servers because the Alarm Detail Reports are run against the back-end polling server that manages the element being reported.

CA Embedded Entitlements Manager (EEM) Information

CA Embedded Entitlements Manager (EEM) is a proprietary software product that enables a limited and one-way, single authentication drill-down option from CA Spectrum to the CA eHealth Web user interface.

Note: For information about the required version of CA EEM and download information, see the Release Notes. For information about configuring CA eHealth and CA Spectrum to use CA SSO with CA SiteMinder, contact CA Services.

CA Embedded Entitlements Manager (EEM) Usernames

Although OneClick for CA eHealth usernames and web usernames are case-sensitive, CA Embedded Entitlements Manager (EEM) treats usernames as case-insensitive for validation purposes.

If you know that the user accounts have different cases, you can enable or disable case-sensitivity. Use the –caseInsensitive switch in the following command:

nhWebSso –hostname <EEM server> -caseInsensitive

See the CA eHealth Command and Environment Variables Reference Guide for more information on the nhWebSso command.

Run nhWebSso Command Line Utility

The CA Spectrum to CA eHealth one-way single authentication support and the CA eHealth SAML support use the nhWebSso utility to enable or disable the authentication option on a CA eHealth Apache server.

See the Command and Environment Variables Reference Guide for more information on the nhWebSSo command.

Chapter 7: Notifier Can Send Traps Using SNMPv2c Form

The Notifier can send traps using the SNMPv2c form when agent addresses are of the IPv6 family type. The Notifier continues to send traps using the SNMPv1 form when agents have IPv4 addresses.

Chapter 8: Known Issues

CA eHealth Known Issues

The following are known issues related to the current version of CA eHealth.

Diacritical Characters Not Supported

The following information is relative to using diacritical characters in this release of CA eHealth:

■ The use of diacriticals will not work correctly with command line utilities on the Windows platform.

■ The use of diacriticals in Process sets and DCI rules in OneClick for CA eHealth is not supported.

■ New custom jobs in the Scheduler do not support diacriticals.

■ Users with diacriticals in their names do not have web access logs or cannot use advanced logging.

■ Diacriticals cannot be used in report names. When creating groups or grouplist names with diacriticals, do not use the max number of characters.

■ CA eHealth does not support the system-wide use of diacriticals. If you must use diacritical characters, you can use them in the web console. However, you must turn on ISO 8859-1 support.

To turn on ISO 8859-1 support

1. Log in to the CA eHealth Web Interface as the web admin.

2. Select Site Configuration under CA eHealth Management on the Administration page.

The Site Configuration page appears.

3. Set the Support Western European special characters (ISO 8859-1) field to Yes.

4. Click Save.

ISO 8859-1 support is turned on.

Gateway Statistics Should Be Summarized to One Element Per Cluster

The way that UCM works is that Gateways, PRI, t1-cas, FXO, and FXS register to only one server in the cluster. CNDC exports one element per server. Consequently, all but one of the elements would have data at any one time. Any of these devices might jump to another server if they are reset or unregister and reregister, so the same element would not always have the data.

The above elements were modified to generate one element per UCM cluster. (This element should already exist in customers configurations.) The element, no matter which server the device is registered to, is associated with the publisher. This approach is already taken for user, extension, and department statistics.

Insufficient Swap Space

On Solaris systems, the installation might display an error message requesting enough swap space for all the Solaris zones combined rather than enough swap space for just the zone on which you are performing the installation. This error cancels the installation.

The workaround for this issue is to perform the installation with the -noCheck argument, which bypasses the check for available swap space.

Example: ./INSTALL.NH -noCheck

Retired Elements May Appear

When CA eHealth is integrated with CA Spectrum, retired elements may appear in reports that are run on web service inventory.

Email Address Field Has Character Limitation

The length of the -after command for reports is limited to 200 characters. This command is typically used for nhMail to email the report output upon completion. If this limit is exceeded, the workaround is to enter the target email addresses into a distribution list. You can then reference the distribution list in the report rather than individual email addresses.

Old discoverResults*.log Files Not Deleted

Symptom:

The discoverResults.log files are not being deleted properly after discovery process finishes.

Solution:

The product only cleans up discoverResults*.log files created after the installation of a kit containing the fix from Release 6.3.2.01 onward. All discoverResults*.log files created prior to Release 6.3.2.01 should be deleted manually (these are the files with "MM.dd.HHmmss.SSS" time-stamp format in their filename).

CA eHealth Live Health Application Known Issues

The following are known issues for CA eHealth Live Health Application.

Remote Polled Groups Appear Incorrectly

Remotely polled groups show up in the Live Exceptions Browser when they should not, since they will never contain alarms (alarms only exist on the system that is actually polling an element).

Warning Message Appears During Startup of Live Reporting

A Java security warning is shown when Live Reporting is launched, prompting you to allow access to the application or block access to the application.

This is a known issue. This warning is caused by calls from JavaScript code to Live Reporting applet and security enhancements in Java 7.

Note: Select the 'Remember the Choice" option to ensure hat the warning is no longer displayed when Live Reporting is launched.

Important: To run Live Reporting, you need to allow access to the application .

Chapter 9: Workaround for Run Now option for Scheduled Reports from CA eHealth OneClick

Example of performing a fresh installation of CA eHealth Release 6.3.2.xx on Solaris

In the following example, suppose that you want to perform a fresh installation of CA eHealth Release 6.3.2.xx on a Solaris system. The following steps describe this process:

1. Download the following files into three distinct directories and extract them:

■ Download CA_eHealth_632nn_Solaris.zip and extract to: /export/extract_ehkit_dir

■ Download CA_eHealth_632nn_Oracle_11204_base_solaris.tar and extract to: /export/extract_oracle_software_dir

■ Download CA_eHealth_632nn_Oracle_11204_update_solaris.tar and extract to: /export/extract_oracle_update_dir

2. After extracting CA_eHealth_632nn_Solaris.zip into /export/extract_ehkit_dir, there are two files and one directory:

■ Files: Install and ENU_632nn_SOL_00_PLUS.sh

■ Directory: eHealth

3. To install CA eHealth, log in as root and run the Install script as follows:

#cd /export/extract_ehkit_dir

# ./Install

Verifying environment...

This utility extracts the eHealth InstallPlus software to the specified directory and then automatically starts the InstallPlus program.

4. Specify a new directory on the eHealth system in a disk partition that contains at least 1060 MB of free space. If this directory already exists and it is not empty, you will be asked to remove that directory or provide a different directory name.

Extract directory: /export/extract_install_dir/temp

Extracting InstallPlus kit...

Extraction complete...

Enter eHealth disk location: /export/extract_ehkit_dir/eHealth

Do you accept the terms of the license agreement? y

Would you like to see the eHealth readme file? n

------------------------------------------------------------------------------

eHealth SunOS 5.10 Release 6.3.2.xx InstallPLUS - English

Copyright (C) CA 1995-2014.

All rights reserved.

Chapter 10: Third Party Software Agreements

The following third party software agreements are updated or new since CA eHealth Release 6.3.2:

Apache HTTP Web Server 2.4.10

Apache HTTP Web Server 2.4.10

This product is distributed with content from Apache HTTP Web Server 2.4.10, the use of which is governed by the following terms:

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or

otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications

represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable

copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License. APACHE HTTP SERVER SUBCOMPONENTS:The Apache HTTP Server includes a number of subcomponents with separate copyright notices and license terms. Your use of the source code for the these subcomponents is subject to the terms and conditions of the following licenses.

For the mod_mime_magic component:

/** mod_mime_magic: MIME type lookup via file magic numbers

* Copyright (c) 1996-1997 Cisco Systems, Inc.

*

* This software was submitted by Cisco Systems to the Apache Group in July * 1997. Future revisions and derivatives of this source code must * acknowledge Cisco Systems as the original contributor of this module.

* All other licensing and usage conditions are those of the Apache Group.*

* Some of this code is derived from the free version of the file command * originally posted to comp.sources.unix. Copyright info for that program * is included below as required.

* ---------------------------------------------------------------------------

* - Copyright (c) Ian F. Darwin, 1987. Written by Ian F. Darwin.

*

* This software is not subject to any license of the American Telephone and * Telegraph Company or of the Regents of the University of California. *

* Permission is granted to anyone to use this software for any purpose on any * computer system, and to alter it and redistribute it freely, subject to * the following restrictions:

* 1. The author is not responsible for the consequences of use of this * software, no matter how awful, even if they arise from flaws in it.

* 2. The origin of this software must not be misrepresented, either by * explicit claim or by omission. Since few users ever read sources, credits * must appear in the documentation.

* 3. Altered versions must be plainly marked as such, and must not be * misrepresented as being the original software. Since few users ever read * sources, credits must appear in the documentation.

* 4. This notice may not be removed or altered.

* -------------------------------------------------------------------------

For the modules\mappers\mod_imagemap.c component:

"macmartinized" polygon code copyright 1992 by Eric Haines, [email protected]

For the server\util_md5.c component: /************************************************************************

* NCSA HTTPd Server

* Software Development Group

* National Center for Supercomputing Applications

* University of Illinois at Urbana-Champaign

* 605 E. Springfield, Champaign, IL 61820

* [email protected]

* Copyright (C) 1995, Board of Trustees of the University of Illinois

* md5.c: NCSA HTTPd code which uses the md5c.c RSA Code

* Original Code Copyright (C) 1994, Jeff Hostetler, Spyglass, Inc.* Portions of Content-MD5 code Copyright (C) 1993, 1994 by Carnegie Mellon * University (see Copyright below).

* Portions of Content-MD5 code Copyright (C) 1991 Bell Communications * Research, Inc. (Bellcore) (see Copyright below). * Portions extracted from mpack, John G. Myers - [email protected] * Content-MD5 Code contributed by Martin Hamilton ([email protected]) */ these portions extracted from mpack, John G. Myers - [email protected] */

/* (C) Copyright 1993,1994 by Carnegie Mellon University * All Rights Reserved.

* Permission to use, copy, modify, distribute, and sell this software * and its documentation for any purpose is hereby granted without * fee, provided that the above copyright notice appear in all copies * and that both that copyright notice and this permission notice * appear in supporting documentation, and that the name of Carnegie * Mellon University not be used in advertising or publicity * pertaining to distribution of the software without specific, * written prior permission. Carnegie Mellon University makes no * representations about the suitability of this software for any * purpose. It is provided "as is" without express or implied * warranty.

* CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO * THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY * AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE * FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTUOUS ACTION, ARISING * OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS * SOFTWARE.

* Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)

** Permission to use, copy, modify, and distribute this material * for any purpose and without fee is hereby granted, provided * that the above copyright notice and this permission notice * appear in all copies, and that the name of Bellcore not be * used in advertising or publicity pertaining to this * material without the specific, prior written permission * of an authorized representative of Bellcore. BELLCORE * MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY * OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS", * WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.*/

For the srclib\apr\include\apr_md5.h component:

/* * This is work is derived from material Copyright RSA Data Security, Inc. * * The RSA copyright statement and Licence for that original material is * included below. This is followed by the Apache copyright statement and * licence for the modifications made to that material.

*//* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work.

RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind.These notices must be retained in any copies of any part of this documentation and/or software. */

For the srclib\apr\passwd\apr_md5.c component:

/** This is work is derived from material Copyright RSA Data Security, Inc. * * The RSA copyright statement and Licence for that original material is * included below. This is followed by the Apache copyright statement and * licence for the modifications made to that material. */

/* MD5C.C - RSA Data Security, Inc., MD5 message-digest algorithm /* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software./*

* The apr_md5_encode() routine uses much code obtained from the FreeBSD 3.0

* MD5 crypt() function, which is licenced as follows:

* "THE BEER-WARE LICENSE" (Revision 42):* <[email protected]> wrote this file. As long as you retain this notice you * can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp For the srclib\apr-util\crypto\apr_md4.c component:

* This is derived from material copyright RSA Data Security, Inc. Their notice is reproduced below in its entirety.

* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.

* License to copy and use this software is granted provided that it * is identified as the "RSA Data Security, Inc. MD4 Message-Digest * Algorithm" in all material mentioning or referencing this software * or this function. License is also granted to make and use derivative works provided * that such works are identified as "derived from the RSA Data * Security, Inc. MD4 Message-Digest Algorithm" in all material * mentioning or referencing the derived work.

* RSA Data Security, Inc. makes no representations concerning either * the merchantability of this software or the suitability of this * software for any particular purpose. It is provided "as is" * without express or implied warranty of any kind.* These notices must be retained in any copies of any part of this * documentation and/or software.

For the srclib\apr-util\include\apr_md4.h component:

* This is derived from material copyright RSA Data Security, Inc. * Their notice is reproduced below in its entirety.

* Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All * rights reserved.

* License to copy and use this software is granted provided that it * is identified as the "RSA Data Security, Inc. MD4 Message-Digest * Algorithm" in all material mentioning or referencing this software or this function. * License is also granted to make and use derivative works provided * that such works are identified as "derived from the RSA Data * Security, Inc. MD4 Message-Digest Algorithm" in all material mentioning or referencing the derived work.

* RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this * software for any particular purpose. It is provided "as is" * without express or implied warranty of any kind. * These notices must be retained in any copies of any part of this * documentation and/or software. /

For the srclib\apr-util\test\testmd4.c component:

* This is derived from material copyright RSA Data Security, Inc. * Their notice is reproduced below in its entirety.

* Copyright (C) 1990-2, RSA Data Security, Inc. Created 1990. All * rights reserved.

* RSA Data Security, Inc. makes no representations concerning either * the merchantability of this software or the suitability of this * software for any particular purpose. It is provided "as is" * without express or implied warranty of any kind. These notices must be retained in any copies of any part of this * documentation and/or software.

For the srclib\apr-util\xml\expat\conftools\install-sh component:

# install - install a program, script, or datafile

# This comes from X11R5 (mit/util/scripts/install.sh).

# Copyright 1991 by the Massachusetts Institute of Technology

# Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

For the test\zb.c component:

/* ZeusBench V1.01

===============

This program is Copyright (C) Zeus Technology Limited 1996. This program may be used and copied freely providing this copyright notice is not removed. This software is provided "as is" and any express or implied warranties, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall Zeus Technology Ltd. be liable for any direct, indirect, incidental, special, exemplary, or consequential damaged (including, but not limited to, procurement of substitute good or services; loss of use, data, or profits;or business interruption) however caused and on theory of liability. Whether in contract, strict liability or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.

Written by Adam Twiss ([email protected]). March 1996

Thanks to the following people for their input:

Mike Belshe ([email protected])

Michael Campanella ([email protected])

*/

For the expat xml parser component:

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd

and Clark Cooper

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

====================================================================

COPYRIGHT TEXT:

Please see the file called LICENSE.

Cryptographic Software Notice

-----------------------------

This distribution may include software that has been designed for use with cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See <http://www.wassenaar.org/> for more information.

The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.

The following provides more details on the included files that may be subject to export controls on cryptographic software:

Apache httpd 2.0 and later versions include the mod_ssl module under modules/ssl/ for configuring and listening to connections over SSL encrypted network sockets by performing calls to a general-purpose encryption library, such as OpenSSL or the operating system's platform-specific SSL facilities. In addition, some versions of apr-util provide an abstract interface for symmetrical cryptographic functions that make use of a general-purpose encryption library, such as OpenSSL, NSS, or the operating system's platform-specific facilities. This interface is known as the apr_crypto interface, with implementation beneath the /crypto directory. The apr_crypto interface is used by the mod_session_crypto module available under modules/session for optional encryption of session information.Some object code distributions of Apache httpd, indicated with the word "crypto" in the package name, may include object code for the OpenSSL encryption library as distributed in open source form from <http://www.openssl.org/source/>.The above files are optional and may be removed if the cryptographic functionality is not desired or needs to be excluded from redistribution. Distribution packages of Apache httpd that include the word "nossl" in the package name have been created without the above files and are therefore not subject to this notice.

Apache Tomcat 7.0.55

This product includes Apache Tomcat 7.0.55 and certain third-party software components that were obtained from the Apache Software Foundation under various licenses set forth below, and are distributed by CA for use with this CA product in unmodified, object code form, under the CA license agreement. The following information sets out certain notices, attributions and/or other information CA is required to provide to you by the third party licensors of these components. The terms contained in the CA license agreement are offered by CA alone and not by the third party licensors. The contents set forth below are for informational purposes only and do not modify the terms of the license agreement between you and CA. The third party licensors of these components provide them on an "AS-IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE, and disclaim liability for any claim or loss, including, without limitation, direct, indirect, special, punitive, exemplary or consequential damages. Source code for Apache Tomcat may be obtained from http://tomcat.apache.org. In addition, CA makes the source code for certain components contained in Apache Tomcat available at http://opensrcd.ca.com/ips/12084_2 under the terms of their respective open source licenses. Apache Tomcat and the accompanying third-party software components are distributed in accordance with the following license agreements:

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special ,incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that afile or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

APACHE TOMCAT SUBCOMPONENTS:

Apache Tomcat includes a number of subcomponents with separate copyright notices and license terms. Your use of these subcomponents is subject to the terms and conditions of the following licenses.

For the ecj-x.x.x.jar component:

Eclipse Public License - v 1.0

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and

b) in the case of each subsequent Contributor:

i) changes to the Program, and ii) additions to the Program; where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.

"Program" means the Contributions distributed in accordance with this Agreement.

"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;

iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and b) a copy of this Agreement must be included with each copy of the Program. Contributors may not remove or alter any copyright notices contained within the Program. Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal

actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.

5. NO WARRANTY EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.

All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

For the Windows Installer component:

* All NSIS source code, plug-ins, documentation, examples, header files and graphics, with the exception of the compression modules and where otherwise noted, are licensed under the zlib/libpng license.

* The zlib compression module for NSIS is licensed under the zlib/libpng license.

* The bzip2 compression module for NSIS is licensed under the bzip2 license.

* The lzma compression module for NSIS is licensed under the Common Public License version 1.0.

zlib/libpng license

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

bzip2 license

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

3. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Julian Seward, Cambridge, UK.

[email protected]

Common Public License version 1.0

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and b) in the case of each subsequent Contributor:

i) changes to the Program, and

ii) additions to the Program;

where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which:

(i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and

(ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.

"Program" means the Contributions distributed in accordance with this Agreement.

"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;

iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and

b) a copy of this Agreement must be included with each copy of the Program.

Contributors may not remove or alter any copyright notices contained within the Program. Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. If Recipient institutes patent litigation against a Contributor with respect toa patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.

All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

Special exception for LZMA compression module Igor Pavlov and Amir Szekely, the authors of the LZMA compression module for NSIS, expressly permit you to statically or dynamically link your code (or bind by name) to the files from the LZMA compression module for NSIS without subjecting your linked code to the terms of the Common Public license version

1.0. Any modifications or additions to files from the LZMA compression module for NSIS, however, are subject to the terms of the Common Public License version 1.0.

For the following XML Schemas for Java EE Deployment Descriptors:

- javaee_5.xsd

- javaee_web_services_1_2.xsd

- javaee_web_services_client_1_2.xsd

- javaee_6.xsd

- javaee_web_services_1_3.xsd

- javaee_web_services_client_1_3.xsd

- jsp_2_2.xsd

- web-app_3_0.xsd

- web-common_3_0.xsd

- web-fragment_3_0.xsd

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0

1. Definitions.

1.1. Contributor. means each individual or entity that creates or contributes to the creation of Modifications.

1.2. Contributor Version. means the combination of the Original Software, prior Modifications used by a Contributor (if any), and the Modifications made by that particular Contributor.

1.3. Covered Software. means (a) the Original Software, or (b) Modifications, or (c) the combination of files containing Original Software with files containing Modifications, in each case including portions thereof.

1.4. Executable. means the Covered Software in any form other than Source Code.

1.5. Initial Developer. means the individual or entity that first makes Original Software available under this License.

1.6. Larger Work. means a work which combines Covered Software or portions thereof with code not governed by the terms of this License.

1.7. License. means this document.

1.8. Licensable. means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. Modifications. means the Source Code and Executable form of any of the following:

A. Any file that results from an addition to, deletion from or modification of the contents of a file containing Original Software or previous Modifications;

B. Any new file that contains any part of the Original Software or previous Modification; or

C. Any new file that is contributed or otherwise made available under the terms of this License.

1.10. Original Software. means the Source Code and Executable form of computer software code that is originally released under this License.

1.11. Patent Claims. means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. 1.12. Source Code. means (a) the common form of computer software code in which modifications are made and (b) associated documentation included in or with such code.

1.13. You. (or .Your.) means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License. For legal entities, .You. includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, .control. means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants.

2.1. The Initial Developer Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual property claims, the Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license:

(a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer, to use, reproduce, modify, display, perform, sublicense and distribute the Original Software (or portions thereof), with or without Modifications, and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using or selling of Original Software, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Software (or portions thereof). (c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial Developer first distributes or otherwise makes the Original Software available to a third party under the terms of this License.

(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code that You delete from the Original Software, or (2) for infringements caused by: (i) the modification of the Original Software, or (ii) the combination of the Original Software with other software or devices.

2.2. Contributor Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:

(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof), either on an unmodified basis, with other Modifications, as Covered Software and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or portions thereof); and (2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination).

(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first distributes or otherwise makes the Modifications available to a third party. (d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any code that Contributor has deleted from the Contributor Version; (2) for infringements caused by: (i) third party modifications of Contributor Version, or (ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or (3) under Patent Claims infringed by Covered Software in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Availability of Source Code. Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License. You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange.

3.2. Modifications.

The Modifications that You create or to which You contribute are governed by the terms of this License. You represent that You believe Your Modifications are Your original creation(s) and/or You have sufficient rights to grant the rights conveyed by this License.

3.3. Required Notices.

You must include a notice in each of Your Modifications that identifies You as the Contributor of the Modification. You may not remove or alter any copyright, patent or trademark notices contained within the Covered Software, or any notices of licensing or any descriptive text giving attribution to any Contributor or the Initial Developer.

3.4. Application of Additional Terms.

You may not offer or impose any terms on any Covered Software in Source Code form that alters or restricts the applicable version of this License or the recipients. rights hereunder. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, you may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.5. Distribution of Executable Versions.

You may distribute the Executable form of the Covered Software under the terms of this License or under the terms of a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable form does not attempt to limit or alter the recipient.s rights in the Source Code form from the rights set forth in this License. If You distribute the Covered Software in Executable form under a different license, You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.6. Larger Works.

You may create a Larger Work by combining Covered Software with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Software.

4. Versions of the License.

4.1. New Versions. Sun Microsystems, Inc. is the initial license steward and may publish revised and/or new versions of this License from time to time. Each version will be given a distinguishing version number. Except as provided in Section 4.3, no one other than the license steward has the right to modify this License.

4.2. Effect of New Versions.

You may always continue to use, distribute or otherwise make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. If the Initial Developer includes a notice in the Original Software prohibiting it from being distributed or otherwise made available under any subsequent version of the License, You must distribute and make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. Otherwise, You may also choose to use, distribute or otherwise make the Covered Software available under the terms of any subsequent version of the License published by the license steward.

4.3. Modified Versions.

When You are an Initial Developer and You want to create a new license for Your Original Software, You may create and use a modified version of thisLicense if You: (a) rename the license and remove any references to the name of the license steward (except to note that the license differs from this License); and (b) otherwise make it clear that the license contains terms which differ from this License.

5. DISCLAIMER OF WARRANTY.

COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN .AS IS. BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION.

6.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

6.2. If You assert a patent infringement claim (excluding declaratory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You assert such claim is referred to as .Participant.) alleging that the Participant Software (meaning the Contributor Version where the Participant is a Contributor or the Original Software where the Participant is the Initial Developer) directly or indirectly infringes any patent, then any and all rights granted directly or indirectly to You by such Participant, the Initial Developer (if the Initial Developer is not the Participant) and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively and automatically at the expiration of such 60 day notice period, unless if within such 60 day period You withdraw Your claim with respect to the Participant Software against such Participant either unilaterally or pursuant to a written agreement with Participant.

6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses that have been validly granted by You or any distributor hereunder prior to termination (excluding licenses granted to You by any distributor) shall survive termination.

7. LIMITATION OF LIABILITY.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY.S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

8. U.S. GOVERNMENT END USERS.

The Covered Software is a .commercial item,. as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of .commercial computer software. (as that term is defined at 48 C.F.R. ? 252.227-7014(a)(1)) and commercial computer software documentation. as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Software with only those rights set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provision that addresses Government rights in computer software under this License.

9. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by the law of the jurisdiction specified in a notice contained within the Original Software (except to the extent applicable law, if any, provides otherwise), excluding such jurisdiction's conflict-of-law provisions. Any litigation relating to this License shall be subject to the jurisdiction of the courts located in the jurisdiction and venue specified in a notice contained within the Original Software, with the losing party responsible for costs, including, without limitation, court costs and reasonable attorneys. fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. You agree that You alone are responsible for compliance with the United States export administration regulations (and the export control laws and regulation of any other countries) when You use, distribute or otherwise make available any Covered Software.

10. RESPONSIBILITY FOR CLAIMS.

As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)

The code released under the CDDL shall be governed by the laws of the State of California (excluding conflict-of-law provisions). Any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California and the state courts of the State of California, with venue lying in Santa Clara County, California.

Open SSL 1.0.1i

OpenSSL 1.0.1i

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit(http://www.openssl.org/) and distributed in accordance with the following licensing terms:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL

please contact [email protected].

OpenSSL License

/* ====================================================================

* Copyright (c) 1998-2014 The OpenSSL Project. All rights reserved.

* Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact: [email protected].

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

* "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

* This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim * Hudson ([email protected]).

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]).

The implementation was written so as to conform with Netscapes SSL.

http://[email protected]./

http://[email protected]./

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

"This product includes cryptographic software written by Eric Young ([email protected])" The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgment:

"This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence * [including the GNU Public Licence.]

Chapter 11: Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

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.


mailto:[email protected]

http://ca.com/docs

http://ca.com/docs

ca ehealth readme · pdf filesince r6.3.0, ca ehealth has been released with maintenance kits...

Documents