Guest

Cisco Application Networking Manager

Release Note for the Cisco Application Network Manager (Software Version 4.x)

  • Viewing Options

  • PDF (637.6 KB)
  • Feedback
Release Notes for the Cisco Application Networking Manager

Table Of Contents

Release Notes for the Cisco Application Networking Manager

New Features in ANM 4.3

Object Grouping

RBAC Reporting and Export Enhancement

Automatic ACE HA Pair Selection when Configuring a Domain

View All Option in Operations Window Listing

Complete Device CLI Audit Log

Retain ANM Users when Uninstalling ANM Server

Monitoring Dashboard Displays GSS VIP Answer and DNS Rules

Alarm Notifications for Device Status and HA Redundancy State Changes

Dedicated Screen Polling Status

New Web Services APIs

New Features in ANM 4.2

Dynamic Workload Scaling

ANM Backups for use with ANM Server or ANM Virtual Appliance

Remote Authorization of ANM Users

Source Email Address for Alert Emails

Health Monitor Probe for Redirect Real Servers and Server Farms

Operations Enhancement

New Features in ANM 4.1

VMware vCenter Import and Mapping

Topology Maps

Monitoring Enhancements

Operations Enhancements

Virtual Server Enhancements

Statistical Data Export

SSL RBAC Enhancements

Scheduled ACE Backup

Web Services API

Feature Support on ACE A4 (1.0) Module and Appliance

64-bit Linux Kernel Support

ANM Virtual Appliance

ANM Graphical User Interface Look and Feel Enhancements

Supported Devices and Software

ANM Product Documentation Set

Installing ANM 4.x Software

ANM Operating Considerations

Assigning Names to ACE Objects

Using the Firefox Web Browser to Access ANM 4.x

Clearing the Browser Cache

Software Version ANM 4.3 Resolved and Open Caveats

Software Version 4.3 Resolved Caveats

Software Version 4.3 Open Caveats

Software Version ANM 4.2 Resolved and Open Caveats

Software Version 4.2 Resolved Caveats

Software Version 4.2 Open Caveats

Software Version ANM 4.1 Resolved and Open Caveats

Software Version 4.1 Resolved Caveats

Software Version 4.1 Open Caveats

Copyright Notices

Apache 2.0 License, Version 2.0

Bouncy Castle Copyright Notice

Castor

Common Public License Version 1.0

GNU GENERAL PUBLIC LICENSE

GNU LESSER GENERAL PUBLIC LICENSE

Copyright Statement for JasperReports

Mozilla Public License Version 1.1

Obtaining Documentation and Submitting a Service Request


Release Notes for the Cisco Application Networking Manager


June 2011


Note The most current documentation for released products is available on cisco.com.


This release note applies to software versions 4.3, 4.2, and 4.1 for Cisco Application Networking Manager (ANM) and contains the following sections:

New Features in ANM 4.3

New Features in ANM 4.2

New Features in ANM 4.1

Supported Devices and Software

ANM Product Documentation Set

Installing ANM 4.x Software

ANM Operating Considerations

Software Version ANM 4.3 Resolved and Open Caveats

Software Version ANM 4.2 Resolved and Open Caveats

Software Version ANM 4.1 Resolved and Open Caveats

Copyright Notices

Obtaining Documentation and Submitting a Service Request

New Features in ANM 4.3

This section describes the new and updated features of ANM 4.3 and includes the following topics:

Object Grouping

RBAC Reporting and Export Enhancement

Automatic ACE HA Pair Selection when Configuring a Domain

View All Option in Operations Window Listing

Complete Device CLI Audit Log

Retain ANM Users when Uninstalling ANM Server

Monitoring Dashboard Displays GSS VIP Answer and DNS Rules

Alarm Notifications for Device Status and HA Redundancy State Changes

Dedicated Screen Polling Status

New Web Services APIs

Object Grouping

ANM 4.3 includes the new group feature that allows you to create groups of the following ANM objects: real servers, virtual servers, GSS VIP answers, or GSS DNS rules. The group feature allows you to display and manage a specific group of ANM objects without having to filter the object display. When creating a group, you specify whether the group is available to just you or is available globally to all ANM users. For more information about the grouping feature, see the following sections in the User Guide for the Cisco Application Networking Manager 4.3:

Managing Virtual Server Groups

Managing GSS VIP Answer and DNS Rule Groups

Managing Real Server Groups

RBAC Reporting and Export Enhancement

ANM 4.3 allows you to include the domain objects available to the user when exporting user information to an Excel spreadsheet. For more information, see the "Displaying a List of Users" section of the User Guide for the Cisco Application Networking Manager 4.3.

Automatic ACE HA Pair Selection when Configuring a Domain

With ANM 4.3, when you add objects such as real servers to a domain on an ACE that has an HA peer, ANM automatically adds the redundant objects from the HA peer to the list of selected objects. You configure and edit domains from the Domain window (Admin > Role-Based Access Control > Organization > Domains).

View All Option in Operations Window Listing

With ANM 4.3, the Operations windows (Config > Operations) for virtual servers, real servers, GSS VIP answers, and GSS DNS rules contain a Rows per page option that includes an All setting for displaying all related configured items in one window. Use the All setting for viewing purposes only. ANM does not allow you to perform any operation from an Operations window if you have more than 200 items selected. For example, if you use the All option to display and select more than 200 virtual servers and then attempt to perform the suspend operation, ANM cancels the request and displays an error message.

Complete Device CLI Audit Log

ANM 4.3 increases the character limit for the audit log detail display (Config > device(s) to view > Device Audit) from 4,000 to 100,000. The Detail field contains CLI commands sent to the device and/or error messages. ANM truncates the display if the number of characters for the CLI commands exceeds 100,000 characters. You can view the complete audit output in the audit log file.

Retain ANM Users when Uninstalling ANM Server

When uninstalling ANM, ANM 4.3 allows you to retain the anm and anm-mysql Linux user accounts for a subsequent ANM server installation. These users are created on the Linux file system during the previous installation of ANM; they are not the user accounts that are used to log in to ANM. If you have local custom scripts based on the user IDs of these Linux user accounts, you can preserve them to avoid having to remap them after performing an ANM upgrade. For more information, see the Installation Guide for Cisco Application Networking Manager 4.3.

Monitoring Dashboard Displays GSS VIP Answer and DNS Rules

ANM 4.3 displays all configured GSS VIP answers and DNS Rules in the Device Configuration Summary table of the Monitoring Dashboard (Monitor > Devices > Groups > All Devices > Dashboard). This table displays the total number of configured VIP answers and DNS rules and their operating state.

Alarm Notifications for Device Status and HA Redundancy State Changes

ANM 4.3 can generate a threshold alarm when a virtual context HA fault tolerant (FT) state changes or when an ACE 4710 or ACE module device status changes. You configure these new alarm notifications from the Threshold Groups window (Monitor > Alarm Notifications > Threshold Groups).

Dedicated Screen Polling Status

ANM 4.3 includes the new Polling Status window (Monitor > Settings > Polling Status), which displays the polling status of the devices that ANM manages. Because ACE devices are partitioned into virtual contexts that can be polled individually, the Polling Status window displays the status of each ACE virtual context. From this window, you have the option to restart polling to a virtual context or device that currently has polling disabled.

New Web Services APIs

ANM 4.3 includes additional APIs that allow you to activate, suspend, and retrieve a list of ACE virtual servers, GSS Answers, and GSS DNS Rules. For more information about the ANM API set, see the API Reference Guide for Cisco Application Networking Manager 4.3.

New Features in ANM 4.2

This section describes the new and updated features of ANM 4.2.


Note Some of the features described in this section specify the use of an ACE module or appliance using software release A4(2.0). Check Cisco.com for the availability of this software release.


This section includes the following topics:

Dynamic Workload Scaling

ANM Backups for use with ANM Server or ANM Virtual Appliance

Remote Authorization of ANM Users

Source Email Address for Alert Emails

Health Monitor Probe for Redirect Real Servers and Server Farms

Operations Enhancement

Dynamic Workload Scaling

ANM 4.2 allows you to configure Dynamic Workload Scaling (DWS), which is an ACE feature that permits on-demand access to remote resources, such as VMware Virtual Machines (VMs) that you own or lease from an Internet service provider (or cloud service provider). This feature uses Cisco's Nexus 7000 series switches with Cisco's Overlay Transport Virtualization (OTV), which is a Data Center Interconnect (DCI) technology used to create a Layer 2 link over an existing IP network between geographically distributed data centers.

ANM 4.2 supports the DWS feature for both ACE module and appliance software release A4(2.0) as follows:

Real Server and Virtual Server windows permit monitoring of DWS.

Operations window allows you to track real server locality (local or remote) and virtual servers DWS state (for example, load balancing traffic to local VMs only or to both local and remote VMs).

Topology window that shows real server locality and server farm DWS state.

For more information, see the User Guide for the Cisco Application Networking Manager 4.2 or the Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide (software version 4.2).

ANM Backups for use with ANM Server or ANM Virtual Appliance

ANM Virtual Appliance can now create or use ANM backups for the restore or upgrade operations. The ANM backups created on the Virtual Appliance and the ANM server software can be used interchangeably across both installations. For instance, an ANM backup on an ANM server with a compatible version can be restored or upgraded on an ANM Virtual Appliance and vice versa.

ANM 4.2 includes the following new ANM Virtual Appliance CLI commands to facilitate the creation and use of the ANM backups:

anm-tool load-inventoryLoads an ANM backup image created either by ANM server using the /opt/CSCOanm/bin/anm-tool backup command or by ANM Virtual Appliance using anm-tool save-inventory command.

anm-tool save-inventoryProduces an image that can be used to restore or upgrade an ANM server on either ANM Virtual Appliance or ANM server.

For more information, see the Installation Guide for the Cisco Application Networking Manager 4.2 or the Installation Guide for the Cisco Application Networking Manager Virtual Appliance 4.2.

Remote Authorization of ANM Users

ANM 4.2 supports remote authorization through TACACS+ server. When ANM authorizes a remote user, it sends a request to the TACACS+ server which returns the role and domain names of the requested user. The definitions of roles and domains are stored locally on ANM. Combining this feature with the existing remote authentication feature allows you to set up ANM so that all ANM user authentication and authorization is performed remotely using a TACACS+ server.

ANM 4.2 also introduces the Fallback To Local option for TACACS+, RADIUS, and AD/LDAP. When this feature is enabled, ANM falls back to the local user when the AAA server is unreachable.

For more information, see the User Guide for the Cisco Application Networking Manager 4.2.

Source Email Address for Alert Emails

ANM 4.2 provides an option to set the Mail From email address when specifying the SMTP server to use for outgoing alert email (Monitor > Settings > SMTP Configuration). By default, the Mail From address is set to anm@hostname.

You can request alert emails when configuring a threshold group (Monitor > Alarm Notifications > Threshold Groups) or when enabling the historical data export feature (Monitor > Settings > Historical Data Export).

With this feature, your SMTP server can check the source of alert emails based on the Mail From email address. For more information, see the User Guide for the Cisco Application Networking Manager 4.2.

Health Monitor Probe for Redirect Real Servers and Server Farms

ANM 4.2 supports the ACE ability to probe the destination of a redirect real server, which is accomplished by associating a health probe with a redirect serverfarm or a redirect real server. The following ACE software releases support this health probe feature:

ACE module: A4(2.0) and A2(3.2a)

ACE appliance: A4(2.0) and A3(2.7)

Using ANM 4.2, you can configure a routed health probe when configuring a redirect real server (Config > Devices > Load Balancing > Real Servers) or server farm (Config > Devices > Load Balancing > Server Farms). For more information, see the User Guide for the Cisco Application Networking Manager 4.2.

Operations Enhancement

ANM 4.2 provides the following operations enhancements:

Ability to specify the customized username and password prompts to use when importing a Cisco Catalyst 6500 series switch or Cisco 7600 series router into ANM. For more information, see the User Guide for the Cisco Application Networking Manager 4.2.

Improved the on-demand polling response time for real and virtual servers from the Operations and Monitoring windows. ANM 4.2 also reduces the activate/suspend waiting time for real server and virtual server from the Operations window.

New Features in ANM 4.1

This section describes the new and updated features of ANM 4.1 and includes the following topics:

VMware vCenter Import and Mapping

Topology Maps

Monitoring Enhancements

Operations Enhancements

Virtual Server Enhancements

Statistical Data Export

SSL RBAC Enhancements

Scheduled ACE Backup

Web Services API

Feature Support on ACE A4 (1.0) Module and Appliance

64-bit Linux Kernel Support

ANM Virtual Appliance

ANM Graphical User Interface Look and Feel Enhancements

VMware vCenter Import and Mapping

ANM 4.1 bridges the visibility gap between the vCenter Server administrators and ACE administrators. The application/server administrators using VMware vCenter to manage their VMware environment can access ANM functionality to manage the servers that benefit from the ACE load-balancing services. For example, you can add or delete servers, activate or suspend traffic, or change load-balancing weights. The new ANM functions related to this feature include the following:

Import VMware vCenter into ANM similar to other devices that ANM supports. ANM discovers the virtual machines that are associated with a vCenter and maps them to existing ACE real servers.

Detect the addition or deletion of virtual machines in vCenter and suggest actions to be performed on the ACE through ANM.

Topology Maps

ANM 4.1 topology maps (Config > Operations > Real Servers, Config > Operations > Virtual Servers) provide a graphical representation of an application network. Using the topology map tools, you can graphically see the relationship between the virtual IP of the service through the supporting server farms to the target servers. You can access a topology map from the virtual server and the real server windows of the ANM Monitor and Operations sections. This feature also works when you enable the vCenter plug-in and access ANM functionality from a vSphere Client.

The topology maps display the following items:

GSS DNS Rule/Answer Group/Answer VIP information (if available).

ACE virtual servers, real servers, and VMware virtual machines.

Details for each of the real servers and virtual machines that are displayed in the graph.

A set of topology map tools provide zoom, pan, and print capabilities.

Monitoring Enhancements

ANM 4.1 provides the following monitoring enhancements:

Support for real-time charts in the existing monitoring graphs feature.

Extended real server view includes corresponding virtual machine details (Monitor > Devices > Load Balancing > Real Servers).

Real server graph support is available on CISCO ACE SLB in VMware vSphere client while using the ANM vSphere client plug-in.

Operations Enhancements

ANM 4.1 provides the following operations enhancements:

Support for on-demand polling of selected objects from all operations pages.

Graph and Topology options added to virtual server and real server pages.

HA peer objects in virtual and real server operations pages are collapsed into one row for better readability and manageability.

Addition of the Stat Age column to the real and virtual server operations pages that indicate the age of the displayed statistics.

Virtual Server Enhancements

ANM 4.1 provides the list of virtual servers that do not match ANM's virtual server definition for Monitoring (Monitor > Devices > Load Balancing > Virtual Servers) and Operations (Config > Operations > Virtual Servers) through a toggle button on the page. This feature is not supported for configuration.

Statistical Data Export

ANM 4.1 includes the statistical data export feature (Monitor > Settings > Historical Data Export) that enables the following:

Allows the automatic export of all the collected historical monitoring data.

Allows you to download the data dictionary in XML that documents the format of the exported statistical data file organization and file content.

Allows you to disable/enable the monitoring/statistical data export.

Purges the exported data based on user-defined conditions.

Sends notifications when the disk usage is higher than the threshold defined in the purging policy after the purging.

SSL RBAC Enhancements

ANM 4.1 supports finer granularity in the SSL RBAC domain definition and RBAC role definition in order to limit the domain definition to a subset of SSL certificates and keys in an entire context, as opposed to all the certificates and keys in a given context. The following screens are changed for this feature:

RBAC—Roles screen (Admin > Role-Based Access Control > Roles > Add) contains new role profiles.

RBAC—Domains screen (Admin > Role-Based Access Control > Domains > Add) contains domain object certificates and keys that allow you to selectively pick the keys and certificates to define a domain membership.

Home page (Home > Welcome) has hyperlinks only for allowed operations for the logged-in user.

Screens contain partial operations that you do not have access to display relevant error messages.

Listing on certificate and keys listing page (Config > Devices > SSL > Certificates) is limited to the domain membership defined in the role definition.

Dashboard listing (Monitor > Devices > Dashboard) and alarm notifications (Monitor > Alarm Notifications > Alarms) window output is filtered based on the domain membership.

New option for certificate expiration threshold setting (Monitor > Alarm Notifications > Threshold Groups > Add) to enable domain sensitive e-mail notification.

Scheduled ACE Backup

ANM 4.1 includes the ACE backup/restore feature that enables the following:

Supports automatic backup for the ACE module (software version A2(3.x) or later releases) and ACE appliance (software version A4(1.0)) based on user-defined schedules

Allows you to create/edit/delete a one-time/daily/weekly/monthly schedule (Config > Global > All Schedules)

Allows you to create/view a schedule and to associate schedules with selected devices using an enhanced All Backups window (Config > Global > All Backups).

Web Services API

ANM 4.1 provides an API set that allows you to manage the Cisco Application Control Engine (ACE) module, Cisco Application Control Engine (ACE) appliance, Cisco Content Services Switch (CSS) and Cisco Content Switching Module (CSM), and Cisco Content Switching Module with SSL (CSM-S). ANM Web Services provides APIs to support configuration functionalities. All APIs are implemented as synchronous calls and each call is a transaction.

Feature Support on ACE A4 (1.0) Module and Appliance

ANM 4.1 allows you to configure the following new features that are associated with ACE modules and appliances using software version A4(1.0):

TCP Inband Health Monitoring for ACE A4 (1.0) modules in the Server Farms page (Config > Devices > Load Balancing > Server Farms) and in the Virtual Servers page (Config > Devices > Load Balancing > Virtual Servers > Add).

Configuration of the compression feature is now also available for the ACE module.

Kal-ap primary-oos is supported for ACE modules with software version A2(3.1) or later releases and ACE appliances with software version A4(1.0) (Expert > Policy > Map > Action, and Config > Devices > Load Balancing > Virtual Servers > Add).

Support a new CLI called logging-all under the SIP Parameter map for ACE modules and appliances (Config > Virtual Contexts > Load Balancing > Parameter Maps > SIP Parameter Maps, and Config > Devices > Load Balancing > Virtual Servers > Add).

Support the SSL Bulk Import feature that is available for modules and appliances under Config > Devices > SSL > Certificates and Config > Devices > SSL > Keys.

64-bit Linux Kernel Support

ANM 4.1 supports both 32-bit and 64-bit Server Edition Red Hat Enterprise Linux AS 5.3 and AS 5.4 kernels.

ANM Virtual Appliance

ANM 4.1 includes ANM Virtual Appliance, which is a closed Linux kernel virtual appliance. The functions associated with this feature are as follows:

Closed appliance—no root access

Cisco IOS-like CLI shell commands to encapsulate anm-license and anm-tool functionality

Delivered as an OVF virtual appliance

ANM Graphical User Interface Look and Feel Enhancements

The ANM 4.1 GUI has a new color scheme that enhances a user's experience.

Supported Devices and Software

For information about Cisco devices that are supported by ANM, see the Supported Devices Table for the Cisco Application Networking Manager 4.x located at the following URL:

http://www.cisco.com/en/US/products/ps6904/products_device_support_tables_list.html

ANM Product Documentation Set

In addition to this release note, the ANM documentation set includes the following publications. You can access the ANM documentation on Cisco.com at the following URL:

http://www.cisco.com/en/US/products/ps6904/tsd_products_support_series_home.html

Installation Guide for the Cisco Application Networking Manager 4.x—Includes complete installation and configuration information for the ANM software.

Installation Guide for the Cisco Application Networking Manager Virtual Appliance 4.x—Includes complete information about ANM virtual appliance functionality, installation, configuration, and administration procedures.

User Guide for the Cisco Application Networking Manager 4.x—Includes complete information about ANM functionality and detailed procedures for its use. Contains all of the information found in online help. Available either on cisco.com or from the ANM online help.

Web Service API Reference Guide for Cisco Application Networking Manager 4.3—Includes complete information about the Cisco Application Networking Manager Web Services application program interface (API) implementation and explains how to use it to manage your network.

Context-sensitive online help—Includes help topics for all pages in the UI (also provides access to PDFs of the user guide). Select an option from the ANM GUI, and click Help.

Supported Devices Table for the Cisco Application Networking Manager 4.x—Includes complete supported device and firmware versions for ANM.

Supplemental License Agreement for the Cisco Application Networking Manager—Describes licensing limitations and restrictions.

Installing ANM 4.x Software

You can install the ANM software on a dedicated server or on a VMware virtual appliance. The two ANM applications are as follows:

ANM server—Dedicated server with ANM server software and Red Hat Enterprise Linux (RHEL) operating system installed on it.

To install ANM server, see the Installation Guide for the Cisco Application Networking Manager 4.x, which provides step-by-step instructions for installing and upgrading ANM on a dedicated server.

ANM Virtual Appliance—VMware virtual appliance with ANM server software and Cisco Application Delivery Engine Operating System (ADE OS) installed on it. Cisco distributes ANM Virtual Appliance in Open Virtual Appliance (.OVA) format.

To install ANM Virtual Appliance, see the Installation Guide for the Cisco Application Networking Manager Virtual Appliance 4.x, which provides step-by-step instructions for installing and upgrading ANM on a VMware virtual machine.

ANM Operating Considerations

This section describes the ANM 4.x operating considerations and includes the following topics:

Assigning Names to ACE Objects

Using the Firefox Web Browser to Access ANM 4.x

Clearing the Browser Cache

Assigning Names to ACE Objects

When naming ACE objects (such as a real server, virtual server, parameter map, class map, health probe, and so on), use a string of typical length 1 to 64 characters, with no spaces. ANM supports strings that include alphanumeric characters (a-z, A-Z, 0-9) and the special characters underscore (_), hyphen (-), dot (.), and asterisk (*) only.

If you are using ANM with an ACE module or ACE appliance and you configure a named object at the ACE CLI, keep in mind that ANM does not support all special characters that the ACE CLI allows you to use when configuring a named object. If you use special characters that ANM does not support, you may not be able to import or manage the ACE using ANM.

Using the Firefox Web Browser to Access ANM 4.x

The ANM 4.x client supports use with Firefox 3.6 on Windows XP, Windows Vista, or Windows 7 (ANM 4.2 only). When you use Firefox 3.x to access ANM for the first time, the Firefox web browser displays a warning that the site is untrusted (see Figure 1).

Figure 1 Firefox 3.6 Untrusted Connection Warning

When Firefox displays this warning, follow the prompts to add a security exception and download the self-signed certificate from the ANM server. After you complete this procedure, Firefox accepts the ANM server as a trusted site both now and during all future login attempts.

Procedure


Step 1 In the This Connection Is Untrusted window, click I Understand the Risks.

Step 2 Click Add Exception to add a security exception to the Firefox web browser.

The Add Security Exception popup window appears identifying the location of the ANM server.

Step 3 In the Add Security Exception popup window, click Get Certificate.

Firefox retrieves the ANM self-signed certificate and the window's Confirm Security Exception button becomes active.

Step 4 Click Confirm Security Exception.

Firefox recognizes the ANM server as a trusted site and the ANM Login window appears.


Clearing the Browser Cache

If you reinstall ANM or upgrade to a newer release, before you access ANM, make sure that you delete the cookies and clear the browser cache of each client to avoid possible issues with the GUI function buttons being inaccessible.

Software Version ANM 4.3 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 4.3:

Software Version 4.3 Resolved Caveats

Software Version 4.3 Open Caveats

Software Version 4.3 Resolved Caveats

Table 1 lists the resolved caveats that apply to ANM software version 4.3.

Table 1 Resolved Caveats in Software Version 4.3 

Bug ID
Summary
Explanation

CSCtl16379

ACE - SNMP cshMonProbeInheritedPort always returns 0

When polling OID 1.3.6.1.4.1.9.9.508 (cshMonServerfarmRealProbeStatsTable) on the ACE, the value returned by cshMonProbeInheritedPort is always 0; therefore, the SNMP instance id does not have information about the probe inherited port.

Workaround: None.

CSCtn05664

Cannot search or filter objects under role-based access control domains.

When adding a domain (Admin > Role-Based Access Control > Domains > Add) and you use the Objects search function, the search function and the entire object filtering section become unresponsive. You must reload the window to recover from this issue.

Workaround: Manually select individual objects without using the search function to avoid this issue.

CSCto52742

Issue with ANM certificate expiration computation when the polling frequency changed.

When you change the polling frequency to a value other than the default of 5 minutes, the change creates a problem with the periodic computation of certificate expirations. This issue results in ANM not issuing certificate expiry notifications until after the requested interval. For example, if you configure ANM to issue expiry notifications 60 days before any certificate is due to expire, ANM issues the notifications at 15 days.

Workaround: Use the default polling frequency.

CSCto83275

ANM Virtual Appliance (VA) does not show any syslog in the Event page when logging timestamp is enabled on the ACE.

When you enable the logging timestamp feature on a monitored ACE, the ANM VA Event window (Monitor > Events) does not show any syslog events.

Workaround: Disable the logging timestamp feature on the ACE.

CSCto90215

Configuration changes made when an ACE reboot in an HA setup causes a failure.

When two ACEs are operating in HA mode and you make a change to the primary ACE while it is rebooting, ANM does not make the change. The order in which ANM displays the ACEs in the GUI is important for this issue to occur. For example, if ANM displays ACE A above ACE B and ACE A reboots, then this issue occurs. However, if ACE A displays below ACE B and ACE A reboots, then this issue does not occur.

Workaround: None.

CSCtq13020

Editing virtual servers may remove the actions from the configuration.

When you edit a virtual server (Config > Devices > Load Balancing > Virtual Server) to change the associated HTTP parameter map and the policy map contains match statements (implicit classes), the actions defined inside some of the match statements might be erroneously removed. The order of the match statements might also be changed.

Workaround: Use the ACE CLI to edit the virtual server configuration.

CSCtq65780

Error occurs when importing SSL certificates into ANM and DM when the ACE is configured with a DSA SSH key.

When the ACE is configured with DSA keys, the SSL certificate and keys import functions fail intermittently with an error.

Workaround: Try importing the SSL certificates again or change the ACE SSH keys to RSA.

CSCtq67235

Virtual context name are not displayed with the switch number in audit log and alarm page.

When displaying the audit logs and alarm page, the virtual context names are missing the switch number.

Workaround: None.

CSCtq77609

ANM is sending duplicate emails after 5 minutes.

With ANM 4.2, when ANM is configured for certificate expiry threshold monitoring and generates an email notification for a certificate that is within the expiry threshold, it also sends a second email notification exactly 5 minutes later. This issue happens once per day.

Workaround: None.


Software Version 4.3 Open Caveats

Table 2 lists the open caveats that apply to ANM software version 4.3.

Table 2 Open Caveats in Software Version 4.3 

Bug ID
Summary
Explanation and Workarounds

CSCsu22694 (device bug: CSCsv35266)

Editing a Layer 4 Payload sticky configuration reports exceptions.

When you edit a Layer 4 payload sticky configuration within ANM and remove the "response sticky" option from the sticky configuration, removing other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM goes out-of-synchronization with the CLI, requiring you to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information.

Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it.

Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtf20628

ANM plugin: SLB Tab: property of tab: that request tunneled through local proxy

In some rare cases, in webplugin for vsphere, the requests to ANM are tunneled through a local proxy on the client machine, which can cause problems with a timely refresh of the plugin screens. This problem appears to be an erratic and uncommon with no clear cause.

Workaround: None.


Software Version ANM 4.2 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 4.2:

Software Version 4.2 Resolved Caveats

Software Version 4.2 Open Caveats

Software Version 4.2 Resolved Caveats

Table 3 lists the resolved caveats that apply to ANM software version 4.2.

Table 3 Resolved Caveats in Software Version 4.2 

Bug ID
Summary
Explanation

CSCsr75526 (device bug: CSCsu51832)

Config: Cannot edit Expect Status code for health probe.

If you edit a health probe and change the Expect Status Code to a new value or a new range, ANM instructs you that the new values overlap the existing ones and does not remove the old values before adding the new values.

Workaround: Delete the existing Min. Expect Status Code and Max. Expect Status Code values before adding the new values.

CSCtg51126

Scheduled backup to remote host failed but ANM does not display the failure.

When a scheduled backup to remote host (FTP, SFTP, TFTP) fails to copy the backup file to the remote host, ANM does not report the problem.

CSCtg81082

Need to provide an optional field for adding the From email address for alarm notifications.

When configuring alarm notifications, you cannot specify the notification From address, which is set as the ANM host name.

CSCth29784

The Activate/Suspend screen is slow to response.

When activating or suspending an ACE that has a large configuration or is responding slowly to SNMP, the change in operating state can take several minutes to display.

Workaround: Only do an SNMP query for rows that are being changed rather than for the entire SNMP table.

CSCtj19308

Graceful suspend should use "inservice standby" instead of "weight 0."

When gracefully suspending a CSM, ANM always sends "weight 0." Some CSM versions either do not block new connections or block sticky entries.

CSCtj29691

ANM displays incorrect ACL/VLAN association on ACL screen.

When the VLAN interface is in bridged mode and you apply both Ethertype and Extended ACLs to the VLAN interface, ANM is unable to display the ACL/VLAN association in the ACL window.

Workaround: Do the following:

1. From the ACL window, choose the ACL entry and click Edit.

2. To assign or remove the ACL from the VLAN interface, choose Config > Devices > Network > VLAN Interfaces and edit the Input/Output Access Group.

CSCtj31444

Obfuscate sensitive information in ANM log files and properties files.

When specific circumstances occur, ANM records sensitive information, such as access credentials and certificate data that is exported using terminal, in certain log files that can be viewed in the lifeline.

Workaround: None.

CSCtj41788

ANM fails to discover device if prompt is changed.

When the username and passwords prompts for a Cisco Catalyst 6500 series switch has been customized, ANM cannot import the switch during the device discovery process and displays the following error message:

Device authentication error with wrong enable password
 
        

Workaround: Use the default username and passwords prompts on the Cisco Catalyst 6500 series switch.

CSCtj58527

ANM: Device information dashboard showing "uptime" as null.

When the ACE has been operating for over 300 days, ANM shows the ACE "uptime" as null in the device dashboard.

Workaround: Reboot the ACE to reset the uptime value.

CSCtj66189

The Real Servers window shows the wrong real server pair in a split HA.

When viewing real servers using the Config > Operations tab, the menus do not collapse for HA ACE module redundant real servers. This issue occurs only when the ACE modules are in the same Cisco Catalyst 6500 series switch chassis or when the modules are in different slot positions in two different switch chassis.

Workaround: If you are using two different Cisco Catalyst 6500 series switches, place the ACE modules in the same slot position in both chassis.

CSCtj94111

The threshold groups option causes a java error in ANM 4.1.

When you upgrade from ANM 3.0 to ANM 4.1, the Threshold window (Monitor > Threshold) does not display and the following error message appears:

Java.lang.NullPointerException
 
        

Workaround: None.

CSCtk32283

ANM user details missing.

When the description field for a user account contains multiple lines that were separated using the Enter key, the User Edit window is blank when you try to edit the user account.

Work Around: Do the following:

1. Delete the user.

2. Recreate the same user, but do not use the Enter key to separate the lines in the description field.

CSCtk35011

ANM 4.1 threshold groups send malformed traps.

When using ANM 4.1(0) and you have the threshold groups' "notify by trap" feature configured on port 162, the trap is malformed, missing the agent IP address and so on.

Workaround: Configure the "notify by trap" feature on port 524 (to syslog).

CSCtk57801

Incorrect SSL certificate expiration date formats can cause misleading expiration alarms.

When the ACE "show crypto certificate" output is corrupt and the data is malformed, the ANM parsing logic is affected, which causes ANM to generate incorrect expiration alarms for the certificates affected by the corrupted data.

Workaround: Ignore the alarms that ANM generates for these particular certificates or on the ACE side, remove these certificates and re-import with a newer version of ACE that has the corrupted output issue fixed. Related ACE bug is CSCtj79967.

CSCtk65602

ANM: Network Topology Map displays DNS rule as "null."

When an answer is configured under multiple answer groups, the network topology map displays the DNS rule as "null."

Workaround: None.

CSCtl57133

ANM4.1 VA cannot receive Syslog messages

Even when the syslog setup is done correctly from ACE, no syslog events appear in the ANM4.1 Virtual Appliance Events window.

Workaround: None.

CSCtl77567

Change in global polling settings can cause virtual context (VC) polling to stop.

When global polling configuration changes relating to polling frequency or polling enable/disable are made in the Global polling settings window, polling stops on certain VCs.

Workaround: Restart ANM.


Software Version 4.2 Open Caveats

Table 4 lists the open caveats that apply to ANM software version 4.2.

Table 4 Open Caveats in Software Version 4.2 

Bug ID
Summary
Explanation and Workarounds

CSCsu22694 (device bug: CSCsv35266)

Editing a Layer 4 Payload sticky configuration reports exceptions.

When you edit a Layer 4 payload sticky configuration within ANM and remove the "response sticky" option from the sticky configuration, removing other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM goes out-of-synchronization with the CLI, requiring you to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information.

Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it.

Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtf20628

ANM plugin: SLB Tab: property of tab: that request tunneled through local proxy

In some rare cases, in webplugin for vsphere, the requests to ANM are tunneled through a local proxy on the client machine, which can cause problems with a timely refresh of the plugin screens. This problem appears to be an erratic and uncommon with no clear cause.

Workaround: None.

CSCtn05664

Cannot search or filter objects under role-based access control domains.

When adding a domain (Admin > Role-Based Access Control > Domains > Add) and you use the Objects search function, the search function and the entire object filtering section become unresponsive. You must reload the window to recover from this issue.

Workaround: Manually select individual objects without using the search function to avoid this issue.


Software Version ANM 4.1 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 4.1:

Software Version 4.1 Resolved Caveats

Software Version 4.1 Open Caveats

Software Version 4.1 Resolved Caveats

Table 5 lists the resolved caveats that apply to ANM software version 4.1.

Table 5 Resolved Caveats in Software Version 4.1 

Bug ID
Summary
Explanation

CSCtd26323

Perf: A "Transform error=cuesXpath is not defined" error message displays on ANM.

When the ANM GUI is transitioning between some pages, a popup window sometimes appears that contains the error message "Transform error=cuesXpath is not defined" or some other "cuesXpath" error message. This error message, which is triggered by the backend GUI model code, is harmless and is to be ignored. Workaround: Click OK to close the popup window and continue using the ANM GUI.

CSCtg21604

HA dashboard does not show "My IP" address for FT interface.

The HA dashboard does not display the IP address configured for the FT interface. It only displays the peer IP address. Workaround: Upgrade the ACE module to version A2(3.0) or A2(3.1) where the MIB support is available. After upgrading the ACE image, we recommend that you perform a chassis level synchronization followed by a module synchronization.

CSCti85147

Many issues are noticed while restoring configuration with VC (existing VC) from the Admin context.

ANM "CLI Sync" fails on a module context that is restored from a different module. The following issues are observed:

i) ACE module is imported into the ANM.

ii) Restore configuration on ACE module from other configuration from ANM GUI.

iii) This will trigger an ANM auto-sync on the restored contexts.

iv) On some occasions when the restored configuration is large or if there is a big discrepancy between the running configuration and the restored configuration. ANM "CLI Sync" fails and the module cannot be imported into ANM.

Workaround:

i) Unmanage the ACE module in question from ANM.

i) CLI Sync the CAT6k module in which the ACE module resides in.

iii) Re-import the ACE module whose configuration is just restored.

CSCti94843

ANM domain page appears to hang.

When ANM has a large number of domain objects, for example, more than 30 objects, when you restart and navigate to Admin > RBAC > Domain page, the application takes a long time to come online.


Software Version 4.1 Open Caveats

Table 6 lists the open caveats that apply to ANM software version 4.1.

Table 6 Open Caveats in Software Version 4.1 

Bug ID
Summary
Explanation and Workarounds

CSCsr75526 (device bug: CSCsu51832)

Config: Cannot edit Expect Status code for health probe.

If you edit a health probe and change the Expect Status Code to a new value or a new range, ANM instructs you that the new values overlap the existing ones and does not remove the old values before adding the new values. Workaround: Delete the existing Min. Expect Status Code and Max. Expect Status Code values before adding the new values.

CSCsu22694 (device bug: CSCsv35266)

Editing a Layer 4 Payload sticky configuration reports exceptions.

When a Layer 4 Payload sticky configuration is edited within ANM, if the "response sticky" option is removed from that sticky configuration, then removing some other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM becomes goes out-of-synchronization with the CLI and you will need to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsu51106

The real server and backup server port for the server farm should have a default value.

The real server and backup server port fields under the server farm should be initialized with the default values for the correct server farm type. Currently, only the primary real server port is initialized with a default value of 0. According to the CLI, the minimum is 1. In addition, if the server farm type is Redirect, both the primary and backup server ports must be 0.

Workaround: None. However, Port 0 on ANM indicates that the real server is configured to take "any" port, and ANM will not send data port 0 while generating the CLI.

CSCsu76450

The action list name field allows special characters.

The Action list name field on the ACE allows special characters, for example, "(!,@,$,%,&)" but ANM does not allow them. If special characters have been used in the CLI, ANM will discover them, but you cannot create them within ANM.

Workaround: Do not use the special characters in the Action list name.

CSCsu85936

The UI does not refresh to display a new class map from the reference table.

When you add a virtual server with HTTP as its protocol, choose L7 Load Balancing, add a new rule with the match condition type "class-map", click on the "+" icon to add a new class map, and click the Close button in the Class Map window, the virtual server screen does not refresh to display the new class map. Workaround: Exit out of the Edit screen and return.

CSCsv40714

CSS/CSM: The operations state column of the VIP on the CSS and CSM should be N/A.

The CSS and CSM Virtual Server Operational state should appear as "N/A" because this column does not apply for these devices. Instead the CSS and CSM Virtual Server Operational state is empty. This condition happens each time. Workaround: None.

CSCsv40734

The message should be refined so that it does not look like an exception.

Errors on the Operations pages have the string "Exception" even when errors from the device are being displayed to the user. This might give the user the impression that the issue is more severe than it is. This problem occurs whenever an error occurs. For example, this problem occurs when a device is unreachable, or active CSS Content Rules are being activated. Workaround: None.

CSCsv99351

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly.

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly and throws an exception. Workaround: Change the mount point to ensure that there are no spaces in it. You might not be able to do this action in all circumstances; however, if the server is used as a dedicated ANM server as intended, you should be able to do this action.

CSCsx61268

The netmask field of the stickiness page is showing incorrect values.

The Netmask field of the Stickiness page is showing values of the cookie name, sticky type, or header name for sticky types where this netmask field is not applicable. Workaround: None.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information. Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it. Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtd61405

Mismatch between the numbers that display in the monitor dashboard and the launched views.

When you go from the dashboard window and to a monitor view that the dashboard launches, the number of entities (real servers, VLANs, and so on) shown in the launched monitor view can be less than the number shown in the dashboard. The reason for this discrepancy is that the dashboard obtains its entity counts from the configuration information of an imported virtual context; however, the launched monitor view shows only the SNMP-based data of the polled entities. If polling is disabled or fails for a virtual context, the dashboard count and the count shown in the launched monitor view will not match. Workaround: None.

CSCtf20628

ANM plugin: SLB Tab: property of tab: that request tunneled through local proxy

In some rare cases, in webplugin for vsphere, the requests to ANM are tunneled through a local proxy on the client machine, which can cause problems with a timely refresh of the plugin screens. This problem appears to be an erratic and uncommon with no clear cause. Workaround: None.

CSCtg51126

Scheduled backup to remote host failed but ANM does not display the failure.

When a scheduled backup to remote host (FTP, SFTP, TFTP) fails to copy the backup file to the remote host, ANM does not report the problem.

CSCtg65582

ANM auto-sync for ACE does not update the image version.

On all the ACE appliances and ACE modules, when ACE software image is upgraded, even after the Admin context auto CLI sync, the ACE version is not updated.

Workaround: For ACE appliances, on ANM All Devices list, select the appliance and click CLI Sync.

For ACE modules, on ANM ALL Devices list, select the chassis and click CLI Sync.

CSCtg81082

Need to provide an optional field for adding the From email address for alarm notifications.

When configuring alarm notifications, you cannot specify the notification From address, which is set as the ANM host name.

CSCth29784

The Activate/Suspend screen is slow to response.

When activating or suspending an ACE that has a large configuration or is responding slowly to SNMP, the change in operating state can take several minutes to display.

Workaround: Only do an SNMP query for rows that are being changed rather than for the entire SNMP table.

CSCtj19308

Graceful suspend should use "inservice standby" instead of "weight 0."

When gracefully suspending a CSM, ANM always sends "weight 0." Some CSM versions either do not block new connections or block sticky entries.

CSCtj29691

ANM displays incorrect ACL/VLAN association on ACL screen.

When the VLAN interface is in bridged mode and you apply both Ethertype and Extended ACLs to the VLAN interface, ANM is unable to display the ACL/VLAN association in the ACL window.

Workaround: Do the following:

1. From the ACL window, choose the ACL entry and click Edit.

2. To assign or remove the ACL from the VLAN interface, choose Config > Devices > Network > VLAN Interfaces and edit the Input/Output Access Group.

CSCtj31444

Obfuscate sensitive information in ANM log files and properties files.

When specific circumstances occur, ANM records sensitive information, such as access credentials and certificate data that is exported using terminal, in certain log files that can be viewed in the lifeline.

Workaround: None.

CSCtj41788

ANM fails to discover device if prompt is changed.

When the username and passwords prompts for a Cisco Catalyst 6500 series switch has been customized, ANM cannot import the switch during the device discovery process and displays the following error message:

Device authentication error with wrong enable password
 
        

Workaround: Use the default username and passwords prompts on the Cisco Catalyst 6500 series switch.

CSCtj58527

ANM: Device information dashboard showing "uptime" as null.

When the ACE has been operating for over 300 days, ANM shows the ACE "uptime" as null in the device dashboard.

Workaround: Reboot the ACE to reset the uptime value.

CSCtj66189

The rservers window shows the wrong rserver pair in a split HA.

When viewing rservers using the config > operations tab, the menus do not collapse for HA ACE module redundant rservers. This issue occurs only when the ACE modules are in the same Cisco Catalyst 6500 series switch chassis or when the modules are in different slot positions in two different switch chassis.

Workaround: If you are using two different Cisco Catalyst 6500 series switches, place the ACE modules in the same slot position in both chassis.

CSCtj94111

The threshold groups option causes a java error in ANM 4.1.

When you upgrade from ANM 3.0 to ANM 4.1, the Threshold window (Monitor > Threshold) does not display and the following error message appears:

Java.lang.NullPointerException
 
        

Workaround: None.

CSCtk32283

ANM user details missing.

When the description field for a user account contains multiple lines that were separated using the Enter key, the User Edit window appears blank when trying to edit the user account.

Work Around: Do the following:

1. Delete the user.

2. Recreate the same user, but do not use the Enter key to separate the lines in the description field.

CSCtk35011

ANM 4.1 threshold groups send malformed traps.

When using ANM 4.1(0) and you have the threshold groups' "notify by trap" feature configured on port 162, the trap is malformed, missing the agent IP address and so on.

Workaround: Configure the "notify by trap" feature on port 524 (to syslog).

CSCtk57801

Incorrect SSL certificate expiration date formats can cause misleading expiration alarms.

When the ACE "show crypto certificate" output is corrupt and the data is malformed, the ANM parsing logic is affected, which causes ANM to generate incorrect expiration alarms for the certificates affected by the corrupted data.

Workaround: Ignore the alarms that ANM generates for these particular certificates or on the ACE side, remove these certificates and re-import with a newer version of ACE that has the corrupted output issue fixed. Related ACE bug is CSCtj79967.

CSCtk65602

ANM: Network Topology Map displays DNS rule as "null."

When an answer is configured under multiple answer groups, the network topology map displays the DNS rule as "null."

Workaround: None.

CSCtl57133

ANM4.1 VA cannot receive Syslog messages

Even when the syslog setup is done correctly from ACE, no syslog events appear in the ANM4.1 Virtual Appliance Events window.

Workaround: None.

CSCtl77567

Change in global polling settings can cause virtual context (VC) polling to stop.

When global polling configuration changes relating to polling frequency or polling enable/disable are made in the Global polling settings window, polling stops on certain VCs.

Workaround: Restart ANM.


Copyright Notices

Third-party software used under license accompanies the Cisco Application Networking Manager Software, release 4.1. One or more of the following notices may apply in connection with the license and use of such third-party software.

The copyright notices in this document are as follows:

Apache 2.0 License, Version 2.0

Bouncy Castle Copyright Notice

Castor

Common Public License Version 1.0

GNU GENERAL PUBLIC LICENSE

GNU LESSER GENERAL PUBLIC LICENSE

Copyright Statement for JasperReports

Mozilla Public License Version 1.1

Apache 2.0 License, Version 2.0

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, 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. 

Bouncy Castle Copyright Notice

Copyright (c) 2000 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)

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 NONINFRINGEMENT. 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.

Castor

exolab.org

The code of this project is released under a BSD-like license [license.txt]:

Copyright 2000-2002 (C) Intalio Inc. All Rights Reserved.

Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document.

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. The name "ExoLab" must not be used to endorse or promote products derived from this Software without prior written permission of Intalio Inc. For written permission, please contact info@exolab.org.

4. Products derived from this Software may not be called "Castor" nor may "Castor" appear in their names without prior written permission of Intalio Inc. Exolab, Castor and Intalio are trademarks of Intalio Inc.

5. Due credit should be given to the ExoLab Project (http://www.exolab.org/).

THIS SOFTWARE IS PROVIDED BY INTALIO AND CONTRIBUTORS ``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 INTALIO 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.

Common Public License Version 1.0

(text)

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 to a 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.

Copyright © 2006 by the Open Source Initiative

Technical questions about the website go to Steve M.: webmaster at opensource.org

Policy questions about open source go to the Board of Directors.

The contents of this website are licensed under the Open Software License 2.1 or Academic Free License 2.1

OSI is a registered non-profit with 501(c)(3) status. Donating to OSI is one way to show your support.

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR EDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you."

A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a. The modified work must itself be a software library.

b. You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.

c. You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.

d. If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:

a. Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)

b. Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

c. Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.

d. If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.

e. Verify that the user has already received a copy of these materials or that you have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:

a. Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.

b. Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

Copyright Statement for JasperReports

* * JasperReports - Free Java report-generating library. * Copyright (C) 2001-2006 JasperSoft Corporation http://www.jaspersoft.com * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public * License as published by the Free Software Foundation; either * version 2.1 of the License, or (at your option) any later version. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this library; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.

Mozilla Public License Version 1.1

1. Definitions.

1.0.1. "Commercial Use"

means distribution or otherwise making the Covered Code available to a third party.

1.1. "Contributor"

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

1.2. "Contributor Version"

means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. "Covered Code"

means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof.

1.4. "Electronic Distribution Mechanism"

means a mechanism generally accepted in the software development community for the electronic transfer of data.

1.5. "Executable"

means Covered Code in any form other than Source Code.

1.6. "Initial Developer"

means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. "Larger Work"

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

1.8. "License"

means this document.

1.8.1. "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 any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is:

a. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications.

b. Any new file that contains any part of the Original Code or previous Modifications.

1.10. "Original Code"

means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.10.1. "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.11. "Source Code"

means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. "You" (or "Your")

means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. 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. Source Code License.

2.1. The Initial Developer Grant.

The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

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 Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and

b. under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof).

c. the licenses granted in this Section 2.1 (a) and (b) are effective on the date Initial Developer first distributes Original Code 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 Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices.

2.2. Contributor Grant.

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 Code 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 makes Commercial Use of the Covered Code.

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) separate from the Contributor Version; 3) 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 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Application of License.

The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.

Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.

You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims

If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained.

(b) Contributor APIs

If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the legal file.

(c) Representations.

Contributor represents that, except as disclosed pursuant to Section 3.4 (a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License.

3.5. Required Notices.

You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. 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 than 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.6. Distribution of Executable Versions.

You may distribute Covered Code in Executable form only if the requirements of Sections 3.1, 3.2, 3.3, 3.4 and 3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under 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 version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version 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 any 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.7. Larger Works.

You may create a Larger Work by combining Covered Code 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 Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the legal file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

6.1. New Versions

Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number.

6.2. Effect of New Versions

Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works

If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. Disclaimer of warranty

Covered code 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 code 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 code is with you. Should any covered code 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 code is authorized hereunder except under this disclaimer.

8. Termination

8.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. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that:

a. such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above.

b. any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant.

8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license.

8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination.

9. 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 code, 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 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.

10. U.S. government end users

The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" 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 Code with only those rights set forth herein.

11. 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 California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, 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.

12. 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.

13. Multiple-licensed code

Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the MPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A.

Exhibit A - Mozilla Public License.

"The contents of this file are subject to the Mozilla Public License 
Version 1.1 (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.mozilla.org/MPL/
 
   
Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific language governing rights and limitations
under the License.
 
   
The Original Code is ______________________________________.
 
   
The Initial Developer of the Original Code is ________________________.
Portions created by ______________________ are Copyright (C) ______
_______________________. All Rights Reserved.
 
   
Contributor(s): ______________________________________.
 
   
Alternatively, the contents of this file may be used under the terms
of the _____ license (the  "[___] License"), in which case the
provisions of [______] License are applicable instead of those
above. If you wish to allow use of your version of this file only
under the terms of the [____] License and not to allow others to use
your version of this file under the MPL, indicate your decision by
deleting the provisions above and replace them with the notice and
other provisions required by the [___] License. If you do not delete
the provisions above, a recipient may use your version of this file
under either the MPL or the [___] License."
 
   

NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.