TIBCO Middleware release notes

TIBCO Runtime Agent™

Release NotesSoftware Release 5.6.2January 2010

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, TIBCO, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Designer, TIBCO Administrator, TIBCO Enterprise Message Service, TIBCO Rendezvous, TIBCO Repository, and TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.This Product is covered by U.S. Patent No. 6,970,981. Copyright © 1999-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.4.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 5.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 5.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Release 5.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Release 5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Release 5.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Release 5.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Release 5.5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Release 5.5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Release 5.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.4.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Release 5.3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Release 5.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Release 5.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

TIBCO Runtime Agent Release Notes

iv | Contents

Release 5.3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Release 5.1.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Release 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.6.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.6.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.5.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.5.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Release 5.5.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Release 5.5.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Migration and Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Release 5.6.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Release 5.6.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Release 5.6.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Release 5.5.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Release 5.5.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Release 5.5.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Release 5.5.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Release 5.5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Release 5.4.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Release 5.4.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Release 5.4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Release 5.3.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Release 5.3.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Release 5.3.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Release 5.3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Release 5.2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Release 5.1.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Release 5.1.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Appendix A Upgrading to Release 5.6 Compatibility Section Errata Pages . . . . . . . . . . . . . 116

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Project and Domain Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Appendix B traUpgradeManager Utility Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

traUpgradeManager Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122


Contents | v

Appendix C License Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124


vi | Contents


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 16

• Deprecated Features, page 25

• Migration and Compatibility, page 29

• Closed Issues, page 35

• Known Issues, page 87


https://support.tibco.com

2 | Release Notes

New Features

This section lists features added since the last major (5.0.0) release of this product.

Release 5.6.2The following are new features in this release.

Third-party Software Bundle

The following third-party software is now bundled with TIBCO Runtime Agent.

• JRE 1.6

• Apache Tomcat 5.5.27

• Entrust 7.2 SP1 patch 153378

Supported Platforms

• SUSE Linux Enterprise Server 11 is now supported.

Updated Package Contents

• TIBCrypt 2.14.100.006

• TIBCO Enterprise Message Service 5.1.3 Client Libraries

• TIBCO Hawk 4.8.1 (Hotfix04)

• TIBCO Rendezvous 8.2.1

Additional Options for the TRA Upgrade Manager Utility

TRA Upgrade Manager Utility now supports manual upgrade of JRE paths to version 1.6 in addition to RV paths to 8.2 as well as downgrades to lower versions on specific machines. It also adds include and exclude arguments to allow fine grain control.

Release 5.6.1

Supported Platforms

AIX 6.1, Red Hat Enterprise Linux4.6, 4.7 and 5.2, and SUSE Linux Enterprise 10.2 are now supported.


New Features | 3

Updated Package Components

• TIBCrypt 2.13.1

• TIBCO XML 5.4.3

• TIBCO XML Canon WebDAV Designer Plug-in 1.2.0

• TIBCO Adapter SDK 5.4.1

• TIBCO Hawk 4.8.1 (Hot Fix 3)

• TIBCO Rendezvous 8.1.2

• TPCL 5.6.1

• Data Direct 3.7 P45

• Tomcat 5.5.27

Release 5.6.0

Supported Platforms

Windows Server 2008 is now supported.

64-bit Installation Improvement

64-bit installation packages are now provided with near-zero configuration.

In order to use TIBCO products (such as TIBCO ActiveMatrix BusinessWorks) with TIBCO Runtime Agent in a 64-bit configuration, manual configuration steps may be required as a post-installation activity. Please consult your TIBCO product documentation for further details.

JRE 1.6 Support

JRE 1.6 is now supported.

Vendor-supplied Database Drivers

Database drivers supplied by the database vendor are now supported for Oracle (thin and thick) and Microsoft SQL Server.

Password Encryption in Application Deployment

• The server.xml file for the Tomcat server now encrypts passwords.


4 | Release Notes

• You can now choose to use dynamically generated keys to encrypt password-type data when deploying applications using AppManage. In addition, AppManage can now encrypt password-type data in exported application configuration files with a user-defined encryption key.

Deployment Revision History Management

You can now limit the number of revisions to keep for a deployed application.

LDAP Integration Enhancements

• Domains not already integrated with LDAP at creation time can now be selected for LDAP integration at a later time with the Domain Utility.

• You can now specify the time of day for LDAP synchronization to begin. You can now specify the time of day for expiration of corporate users.

• An alternative algorithm is now provided for computing group hierarchy, which can improve performance when querying from LDAP servers with a large number of groups.

Additional Options for the buildear Utility

The following options have been added to the builder utility:

• -a Specify a properties file containing aliases for DTL library locations.

• -x Overwrite the specified output file if it exists.

• -v Validate the project before creating the archive.

Selectable TIBCO Rendezvous Releases

A new utility called traUpgradeManager now enables you to change the Rendezvous version you use for your software installation. Supported Rendezvous versions are 7.5.4 and above.

Logging Enhancement

Additional logging messages for critical events and activities that are clear and easy to understand are now included in the ApplicationManagement.log file.

Adding Machines for Domains with SSL-enabled EMS Transport

You can now add machines via the command line to a domain that uses SSL-enabled TIBCO Enterprise Message Service for domain transport.


New Features | 5

Security Providers in FIPS 140-2 Mode

TIBCrypt can now be initialized in FIPS 140-2 mode when using the Entrust security provider. It can also likewise be initialized in FIPS 140-2 mode when using the IBM provider on IBM machines.

Tomcat Shutdown Security

A password is now required when shutting down the Tomcat server via the shutdown port for better security of that port.

Updated Package Components

• TIBCrypt 2.13.0

• TIBCrypt Password 2.12.004

• TIBCO XML 5.4.3

• TIBCO XML Tools Palette 5.6.0

• TIBCO Adapter SDK 5.5

• TIBCO Enterprise Message Service 4.4.3

• TIBCO Hawk 4.8.1

• TPCL 5.6.0

Obfuscate Utility Enhancement

• A custom encryption key and a machine key are supported for password encryption.

• - password and -passwordFile are supported to encrypt passwords using a custom encryption key for better security.

Transparent Application Failover with Oracle 10gR2 (and the Oracle Thin Driver)

When a TIBCO Administration Domain is persisted in Oracle 10gR2 RAC (using the Oracle Thin Driver) that is configured for Transparent Application Failover, TIBCO Administrator can continue to function without any interruptions or loss of operation when failover between Oracle RAC Database instances occurs.

Release 5.5.4C++ applications are supported on Solaris 10 (x86).


6 | Release Notes

TIBCO Rendezvous® 8.1 is included in the TIBCO Runtime Agent installation package.

Release 5.5.3No new features have been introduced in release 5.5.3.

Release 5.5.2The following platforms are now supported:

• Windows Vista Business Edition

• HP-UX 11.23 on PA-RISC

• HP-UX 11.31 on Itanium


Release 5.5.0

TIBCO Enterprise Message Service Supported as Domain Transport

TIBCO Enterprise Message Service is now supported as a message transport for an administration domain. This support allows you to create a domain that does not use TIBCO Rendezvous.

When using Enterprise Message Service as the domain message transport, you must use a database repository for domain storage. Applications can only be deployed using the local option, which means that application data is sent to the target machine on which the application is running and the application does not interact with the administration server.

TIBCO Rendezvous is set as the default transport when creating an administration domain. To set TIBCO Enterprise Message Service as the domain transport, select the Show Advanced check box in the Administration Configuration panel in TIBCO Domain Utility and provide values for the Enterprise Message Service server. The server should be running before configuring the domain. The server need not be running on a machine that is part of the administration domain.


New Features | 7

Life Cycle Promotion Support

• Export an application’s EAR file. You can use the appManage -export option to create and export an application’s EAR file. In previous releases you could only export EAR files for all applications in a domain (using appManage -batchExport).

• Import and Export Access Control Lists. The ImportDomainSecurity and ExportDomainSecurity command line utilities include options for importing and exporting access control lists among administration domains.

Additional Platform Support

• A 64-bit installer is available for the AIX 5.3 and 5.2 platforms. No manual steps are required to enable TIBCO applications to run in 64-bit mode on these platforms.

• A 64-bit installer is available for Linux Kernel 2.4 glibc 2.2, Linux Kernel 2.4 glibc 2.3, and Linux Kernel 2.6 glibc 2.3. No manual steps are required to enable TIBCO applications to run in 64-bit mode on these platforms.

• A 64-bit installer is not available for the HP-UX and Solaris platforms. TIBCO applications on HP-UX and Solaris platforms can be enabled to run in 64-bit mode, but you must manually change certain .tra files. See the TIBCO Runtime Agent Installation Guide for details.

• Solaris 10 on x86

Support for JAAS

TIBCO Administrator implements the Java Authentication and Authorization Service (JAAS) framework. This allows you to perform Web authentication and authorization in applications that use the administration server. See the TIBCO Administrator Server Configuration Guide for details.


Release 5.4.2TIBCO Rendezvous® 7.5.2 is bundled in this release. During installation, Rendezvous® 7.5.1 that was bundled in TIBCO Runtime Agent™ release 5.4.0 is replaced with Rendezvous 7.5.2. If you have installed Runtime Agent™ 5.4.1, Rendezvous 7.5.2 is not replaced.


8 | Release Notes

Release 5.4.1TIBCO Rendezvous 7.5.2 is bundled in this release. During installation, Rendezvous 7.5.1 that was bundled in TIBCO Runtime Agent release 5.4.0 is replaced with Rendezvous 7.5.2.

Release 5.4.0

AppManage Enhancements

• Service Instance Runtime Variables

You can set a service instance runtime variable by exporting an application’s deployment configuration file and adding a runtime variable to the NVPairs element section to the file.

You can only change instance runtime variables using AppManage and TIBCO Runtime Agent 5.4 must be used with the TIBCO Hawk® Agent or the instance variables will be ignored.

• Change an application’s transport

You can use the -MoveAppData option to change the transport setting for a given application from rv (TIBCO Rendezvous) to local, or the reverse. You can also use the -batchMoveAppData option to change transport settings in batch mode.

See the TIBCO Runtime Agent Scripting Deployment User’s Guide for details.

DB2 Support

DB2 is now supported for administration domain and application repository storage. Note that the IBM DB2 thin driver is not packaged with TIBCO Runtime Agent. You must add the driver files under the install-path/tibco/tpcl/5.4/jdbc folder.

The default page size for DB2 is 4k and this is not enough for creating a domain. You must create a bufferpool with 32k and then create a tablespace that uses this bufferpool. The table space must be made available to the given DB2 user.

Third-party Software Bundles

• JRE 1.5.0 is now bundled with TIBCO Runtime Agent.

• Apache Jakarta Tomcat 5.5 is now bundled with TIBCO Runtime Agent


New Features | 9

Microsoft Active Directory Application Mode

Microsoft Active Directory Application Mode is supported as an LDAP directory service for an administration domain. See TIBCO Runtime Agent Domain Utility User’s Guide for configuration information.


Release 5.3.3 includes the following JRE packages that have Daylight Saving Time patches for United States time zones for 2007:

• SDK 1.4.2.12 for HP-UX PA-RISC and Itanium.

• J2SE 1.4.2_13 for Windows, Solaris and Linux.

• IBM Java 1.4.2 build ca142-20060824 (SR6) for AIX. See AIX Platforms on page 32 for important information about using Runtime Agent 5.3.3 on the AIX platform.



Release 5.3.0The following list of new features is replicated in TIBCO Administrator™ Release Notes.

Local Application Data

You can configure an administration domain to push local application data to each target machine on which an application is deployed. This allows the application to run without accessing application data from the administration server. See the TIBCO Administrator Server Configuration Guide for more information.

You can also specify an application to use local application data when it is deployed using the TIBCO Administrator GUI. See the TIBCO Administrator User’s Guide for more information.


10 | Release Notes

Password Policy

When creating an administration domain, you can specify that a password policy be used in the domain. Doing so allows the applications running in the domain to meet fundamental security requirements defined in the Sarbanes-Oxley Act. See the TIBCO Administrator Server Configuration Guide for more information.

The policy can be set when creating or editing an administration domain or later modified using the TIBCO Administrator GUI. See the TIBCO Administrator User’s Guide for more information.

Cluster Support

You can now install TIBCO applications into a cluster environment. Note that TIBCO applications are cluster-unaware. The applications can be managed seamlessly by cluster software, but do not use any cluster features. Several new fields are available in TIBCO Domain Utility that allow you to configure a administration domain for use in a cluster. See the TIBCO Runtime Agent Installing Into a Cluster guide for more information.

Additional Deployment Options

Two new deployment options are available in the TIBCO Administrator GUI and in the AppManage utility.

• When redeploying an application, you can choose to not stop running instances that are already deployed. Doing so minimizes the downtime caused by redeployment.

• You can now force an application to be redeployed even when it is in a synchronized state.

When using TIBCO Domain Utility to create an administration domain you can specify that a restrictive policy be used for the domain. Similarly, when using the TIBCO Administrator GUI to manage the password policy, you can modify the StrongPolicy.xml file and load it into the domain. The following features in the restrictive policy and StrongPolicy.xml file are not available. They are commented out in the StrongPolicy.xml file and must not be set:

• 

• 

As a result, users are not forced to change their password on first login and passwords do not expire. If the above features are set, users will be unable to use the TIBCO Administrator GUI to login to the domain.


New Features | 11

Application Domains

An application domain stores data in an application repository rather than in the administration domain repository. This allows you to store configuration information required by the application at runtime in a repository that is independent of the administration domain repository. Application domains are defined in the TIBCO Administrator GUI. This feature is available only to TIBCO applications that support it.

Permissions on Roles

Roles are used in setting permissions for application resources, such as applications, services, portlets, pages, workflow and so on. Permissions can now be set on roles themselves, as on applications resources. This means you can specify who is permitted to access a role and at what access level.

The roles dialog has an additional tab labeled Security where access permissions to the role can be set. A user, role or both can be assigned and the following permission types set:

• Read access that allows viewing role details such as the role name, description, membership list and roles tree.

• Write access that allows changing role details such as the role name, description, membership list and roles tree. Write access also allows a user to create or delete child roles and the role itself.

• Administer access that allows setting authorization permissions on the role. This can be set from the security module.

Support for Groups with Large Membership in Active Directory

When an administration domain is configured to use Active Directory and more than 1000 users are defined for a group, all users in the group are now loaded into TIBCO Administrator.

LDAP Alias Support

For all supported LDAP servers, TIBCO Administrator now supports the use of LDAP aliases in corporate LDAP directories. An alias points to another object in a namespace. You can also specify that an alias be dereferenced when creating an LDAP based administration domain.

Local Users in LDAP Integrated Domains

You can create local users in an administration domain that is integrated with an LDAP directory. See the TIBCO Administrator User’s Guide for details.


12 | Release Notes

Caching Support

TIBCO Administrator now includes the EHCache product that provides a simple, fast and thread-safe cache facility. EHCache allows you to configure caching per object type. You can specify that only certain objects are cached after the first iteration. See the TIBCO Administrator Server Configuration Guide for more information.

Command Line Utilities

The following command line utilities are new in this release. The utilities are in the TIBCO_TRA_HOME\bin directory.

• CorpRoleSynchronizer

This utility allows you to synchronize LDAP groups for an administration domain. If the LDAP directory that is associated with your administration domain undergoes significant changes, you can use the CorpRoleSynchronizer utility to bring the domain in sync with the LDAP directory. See the TIBCO Administrator User’s Guide for more information.

• CorpUserSynchronizer

This utility allows you to pre load LDAP user objects into an administration domain. Pre loading users prevents the administrator server from being overloaded if many new users access an application in a short period of time. See the TIBCO Administrator User’s Guide for more information.

• RedeployAllAppsForUser

This utility allows you to change the password in all deployed applications’ properties files (.tra files) that are used to retrieve configuration data from the administration server. The command determines which applications in the given domain use the specified userid, and then updates their configurations and redeploys them. See the TIBCO Administrator Server Configuration Guide for more information.

New Administration Server Properties

The following properties for the administration server are new in this release:

• DisableAdministratorClearLocks—Objects stored in the admininstration, authorization and application domains can acquire locks. By default, these locks are cleared when the administration server starts. You can change this behavior by setting DisableAdministratorClearLocks to true so that locks are not cleared when the administration server starts for the administration domain where the property is set.


New Features | 13

• repo.isRepoNavigatorEnabled. If set to true (the default), the repository instances on the administration server can be viewed using the URL: http://<host:port>/administrator/repo. When this property is enabled, any user can view global variables, which may pose as a security hole. If security is a concern, this property should not be enabled.

AppManage Options

The AppManage utility has been enhanced with several new options. See the TIBCO Runtime Agent Scripting Deployment User’s Guide for more information.

The batchStart, batchStop and batchKill options are now included that allow you to do the following operations in batch mode.

• Deploy applications

• Undeploy applications

• Start or stop applications

• Delete applications

• Kill applications

The max option allows you to create a deployment configuration file that includes all possible XML tags.

Additional Platform Support

Solaris 10 is now supported, both in 32-bit and 64-bit modes.

Documentation

The TIBCO Runtime Agent Installing Into a Cluster guide is new in this release. The guide is part of the TIBCO Runtime Agent documentation set and is available in the TIBCO_TRA_HOME\doc folder.



14 | Release Notes

Release 5.2.0

Scripts

• Scripting deployment. This was previously released as an add-on-pack and is now included in this release. The following command line utilities are part of scripting deployment:

— The buildear utility builds an enterprise archive file based an Enterprise Archive resource that is defined in a TIBCO Designer project.

— The AppManage utility creates an XML based deployment configuration file where deployment options can be defined. The utility uploads the deployment file and enterprise archive file into an administration domain. It is used to undeploy or delete applications. It can also start or stop service instance. The utility can batch deploy, undeploy or delete applications.

See the TIBCO Runtime Agent Scripting Deployment User’s Guide for details.

TIBCO Domain Utility Command Line Mode

The Domain Utility in can be run in command line mode. The following tasks can be performed from the command line using the domainutilitycmd utility. See the TIBCO Runtime Agent Domain Utility User’s Guide for details.

• Creating a domain

• Deleting a domain

• Adding a secondary server

• Adding a machine to a domain

• Changing TIBCO Rendezvous parameters

• Changing Domain Credentials

Multilingual User Interface Support

The Multilingual User Interface (MUI) provides a localized Graphical User Interface (GUI) in Japanese or English for TIBCO Runtime Agent applications. Previously, MUI support required a separately installed package. In this release, MUI support is included in the base product. TIBCO Runtime Agent includes a utility for choosing the user interface language. The utility is available from the Windows Start menu, or from TIBCO_TRA_HOME\bin\MUILangChooser.

Using the installer in silent mode and domainutilitycmd with the create domain option you can install Administrator and create a domain without using a GUI.


New Features | 15

New Platform Support

• AIX 5.2 and 5.3 are now supported.

• Red Hat Linux Advanced Server 3.0 is now supported.

Release 5.1.2The tramodify utility can be used to switch adapter dependency from one TIBCO Runtime Agent version to another. See the TIBCO Runtime Agent Administrator’s Guide for more information.

Release 5.0.0

Tibicudata.dat location

Tibicudata.dat is in $TIBCO_TRA_HOME/config/g11n.e

JRE and TIBCO Rendezvous locations

JRE and TIBCO Rendezvous are now installed in their own directories. The TRA installer now embeds the TIBCO Rendezvous installer rather than shipping only pieces of TIBCO Rendezvous.

System Path

TIBCO Runtime Agent no longer modifies the system path during installation.


16 | Release Notes

Changes in Functionality

This section lists changes in functionality since the last major (5.0.0) release of this product.

Release 5.6.2

Administration Domain Vulnerability Addressed

Unix Systems On Unix systems copy and run one of the following scripts. The scripts remove read access to the properties files where administration domain credentials are stored. Your administration domain access can be limited to the user id used when installing TIBCO Runtime Agent, or granted to a group. Use the first script to allow only the owning user to have access. Use the second script to also allow access to a group of users.

Only run the scripts if you are logged in as the user that installed TIBCO Runtime Agent.

• Use the following if your administration domain should only be authorized for the current user.

chmod 600 $TIBCO_HOME/tra/domain/*/*.properties

• Use the following if your administration domain should be authorized for the current user's group. The TIBCO_ADMIN_GROUP_NAME environment variable must be set to the name of the group whose members are authorized to run TIBCO Runtime Agent utilities.

chmod 640 $TIBCO_HOME/tra/domain/*/*.propertieschgrp $TIBCO_ADMIN_GROUP_NAME $TIBCO_HOME/tra/domain/*/*.properties

TIBCO Runtime Agent release 5.6.2 corrects a security vulnerability where an unauthorized user could gain access to administration domain credentials. A user with administrator credentials has full access to run all TIBCO Runtime Agent utilities.

After upgrading to release 5.6.2 newly created administration domains are protected. However, you must manually update all existing administration domains by using the procedure for your operating system that is described in this section.

After completing the procedure, only the users, groups or both, that you specify can run TIBCO Runtime Agent utilities.


Changes in Functionality | 17

Windows On Window s, complete the following procedure for each administration domain’s AdministrationDomain.properties and AuthorizationDomain.properties files.

1. Navigate to the directory, TIBCO_HOME\tra\domain\domain-name

2. Right-click a .properties file and select Properties

3. Click the Security tab.

4. Select the Users group or user name to remove and click Remove.

5. Click Add to assign a user or group that contains users authorized to run TIBCO Runtime Agent utilities.

Domain Utility Enhancements

The user id used by the person installing TIBCO Runtime Agent has full permissions to TIBCO Runtime Agent software. When creating an administration domain or adding a machine to an administration domain, you can specify a group that has full access to the software. Members of this group are authorized to run TIBCO Runtime Agent utilities.


18 | Release Notes

A group name is not validated when entered (due to differences between operating systems, allowable characters, and so on). You should verify the accuracy of the group name you enter.

Default Security Provider Changed for TIBCO Administrator

The default security provider for TIBCO Administrator has been changed from entrust to j2se on all systems except for AIX. This avoids an incompatibility between SQL Server drivers and Entrust library when using JRE 1.6.

SSL Vulnerability Addressed

This release of TIBCO Runtime Agent includes updates to address the SSL/TLS vulnerability referenced in CVE-2009-3555 and US-CERT VU#120541. Specifically, this release of TIBCO Runtime Agent includes the TIBCO Rendezvous 8.2.1 release. Additionally, this release of TIBCO Runtime Agent also includes an updated version of the underlying security provider library that provides the SSL/TLS functionality. These updates provide an interim fix that disables SSL/TLS renegotiation by default. Once the industry has standardized a permanent fix to the SSL/TLS protocols, TIBCO will update accordingly.

Release 5.6.1There are no changes in functionality in this release.

Property Name Location in Domain Utility Description

Authorized Group Name 1. Select Domain Configuration

2. Select Create a New Administration Domain and click Next.

3. Click Show Advanced and scroll down to the bottom of the screen.

Type the name of an existing group. Members of this group can run TIBCO Runtime Agent utilities in the new administration domain.

Property Files Group Name 1. Select Machine Management

2. Select Add Machine and click Next.

3. Click Show Advanced and scroll down to the bottom of the screen.

Type the name of an existing group. Members of this group can run TIBCO Runtime Agent utilities on the machine.



Release 5.6.0

Removed Platform Support

Support for the following platforms is removed in this release:

• Linux kernel 2.4 with glibc 2.2

• Microsoft Windows 2000

• JRE 1.4

Removed Utilities

The following utilities are removed:

• MigrateDomainStorage

• prepareDeployment

• redeploy

Domain Utility GUI Changes

The following changes have been made to the Domain Utility GUI:

• TIBCO Enterprise Message Service Server URL When creating a domain, adding a machine to a domain, and adding a secondary server, you now configure the server URL in a single field instead of separate fields for hostname and port number. You can also provide multiple server URLs in the field for fault tolerant Enterprise Message Service servers.

• AJP Port The AJP Port field is removed.

Dynamic Linking with TIBCO Rendezvous Client Library

TIBCO Hawk HMA (tibhawkhma) is now dynamically-linked with TIBCO Rendezvous client libraries on all platforms.

Refer to TIBCO Runtime Agent Installation for more information.

Release 5.5.4Linux kernel 2.4, glibc 2.2 on x86 is no longer supported.

Release 5.5.3There are no functionality changes in this release.


20 | Release Notes



Release 5.5.0If you install TIBCO Rendezvous and Rendezvous is already installed on the machine, the installer updates your existing Rendezvous installation to version 7.5.2. You must accept the upgrade, or the installation cannot continue.




Release 5.4.0

AIX 5.1

AIX 5.1 is no longer supported.

Solaris 7

Solaris 7 is no longer supported.

HP-UX 11.0

HP-UX 11.0 is no longer supported.






Release 5.3.0The following list of changes in functionality is replicated in TIBCO Administrator Release Notes.

TIBCO Administrator Repository Edition

Repository Edition is no longer available as the same functionality is provided in TIBCO Administrator Enterprise Edition. To manually migrate application repositories created using Repository Edition, see the TIBCO Runtime Agent Upgrading to 5.3 guide.

Rulebase Configuration

In previous releases TIBCO Hawk rulebases were required to use a naming convention and consequently a rulebase could only be used by one deployment and service combination. The naming convention is removed in this release and the same rulebase can be used by one or more services. See the TIBCO Administrator User’s Guide for more information.

Naming and Renaming Users

The panels in the TIBCO Administrator GUI that are used to name and rename users have changed. See the TIBCO Administrator User’s Guide for more information.


22 | Release Notes

TIBCO Enterprise Message Service Plug-in

The panels used in the EMS server plug-in to configure the EMS server have changed. Unit capabilities have been added to durations and capacity and sizes. Durations now accept input with ms/millisecond/milliseconds, s/second/seconds, m/minute/minutes, and h/hour/hours. Capacity accept input with b/byte/bytes, k/kilobyte/kilobytes, and m/megabyte/megabytes. Parsing is case-insensitive and the unit constants are localized.

Release 5.1.3

HP-UX

On the HP-UX platform, JRE 1.4.2_02 is now used instead of JRE 1.4.1_00.

AIX

After installing TIBCO Runtime Agent 5.1.3 over an existing installation of Runtime Agent™ 5.1.2 on AIX, you will have two installed versions of JRE

TIBCO_HOME/jre/1.4.0TIBCO_HOME/jre/1.4.1

All TIBCO applications that were installed prior to installing Runtime Agent 5.1.3 will be pointing to JRE 1.4.0. One way to make all applications use the new JRE 1.4.1 is to do the following:

cd TIBCO_HOME/jremv 1.4.0 1.4.0.originalln -s 1.4.1 1.4.0

No .tra files for any TIBCO applications have been updated. Everything will work and nothing needs to be redeployed.

To use a newer JDK than what is included in the installation:

Install JDK 1.4.2 (assume into /opt/jdk). You will then have the following:

/opt/jdk/jre

After installation of JDK 1.4.2, do the following:

ln -s /opt/jdk/bin/javac /opt/jdk/jre/bin/javacln -s /opt/jdk/lib/tools.jar /opt/jdk/jre/lib/tools.jarcd TIBCO_HOME/jremv TIBCO_HOME/jre/1.4.0 TIBCO_HOME/jre/1.4.0.originalln -s /opt/jdk/jre TIBCO_HOME/jre/1.4.0



Release 5.0The TIBCO Runtime Agent directory structure has changed in release 5.0. The new directory structure requires that scripts and property files (“.tra” files) be modified to set PATH, CLASSPATH, and LD_LIBRARY_PATH correctly.

Table 1

Files TRA 1.0.x Location TRA 5.0.x Location

(Non TIBCO) Third Party Core Libraries

%TIBCO_TRA_HOME%/lib/ex %TIBCO_TPCL_HOME%/lib

JDBC Libraries %TIBCO_TRA_HOME%/lib/jdbc %TIBCO_TPCL_HOME%/jdbc

Third Party DLLs

%TIBCO_TRA_HOME%/bin %TIBCO_TPCL_HOME%/bin

Java Home %TIBCO_JAVA_HOME% %TIBCO_JAVA_HOME%

Java library %TIBCO_JVM_LIB% %TIBCO_JVM_LIB%

Rendezvous libraries

%TIBCO_RV_HOME%/lib or %TIBCO_TRA_HOME%/lib

%TIBCO_RV_HOME%/lib

Rendezvous binaries

%TIBCO_RV_HOME%/bin or %TIBCO_TRA_HOME%/bin

%TIBCO_RV_HOME%/bin

Rendezvous dll %TIBCO_RV_HOME%/bin or %TIBCO_TRA_HOME%/bin

%TIBCO_RV_HOME%/bin

Tra.jar %TIBCO_TRA_HOME%/lib/tra.jar %TIBCO_TRA_HOME%/lib/TIBCOrt.jar %TIBCO_TRA_HOME%/lib/TIBCOxml.jar %TIBCO_TRA_HOME%/lib/TIBCOtsm.jar

TIBCO JMS jar files

%TIBCO_TRA_HOME%/lib/TIBCOjms.jar

TRA C++ libraries

%TIBCO_TRA_HOME%/lib %TIBCO_TRA_HOME%/lib

TRA dlls %TIBCO_TRA_HOME%/bin %TIBCO_TRA_HOME%/bin

TRA binaries %TIBCO_TRA_HOME%/bin %TIBCO_TRA_HOME%/bin

TRA tools libraries

%TIBCO_TRA_HOME%/tools/lib %TIBCO_TRA_HOME%/lib


24 | Release Notes

TRA tools binaries

%TIBCO_TRA_HOME%/tools/bin %TIBCO_TRA_HOME%/bin

TRA tools dlls %TIBCO_TRA_HOME%/tools/bin %TIBCO_TRA_HOME%/bin

TIBCO Wrapper bin

%TIBCO_TRA_HOME%/tools/wrapper/bin

%TIBCO_TRA_HOME%/bin

TIBCO Wrapper lib

%TIBCO_TRA_HOME%/tools/wrapper/lib

%TIBCO_TRA_HOME%/lib

TIBCO Wrapper include

%TIBCO_TRA_HOME%/tools/wrapper/include

%TIBCO_TRA_HOME%/include/wrapper

Table 1

Files TRA 1.0.x Location TRA 5.0.x Location


Deprecated Features | 25

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 5.6.2The following features are deprecated in this release.

• Support for AIX 5.2 platform.

• Support for Internet Explorer 5.5, Mozilla suite, and Firefox 1.x browsers.

• Support for JRE 1.5

With JRE 1.5 having reached its end of service life (see Sun’s announcement at http://java.sun.com/javase/downloads/index_jdk5.jsp), only limited support for this JRE version is provided. It is strongly recommended to upgrade it to the supported version.

Release 5.6.1No features are deprecated in this release.

Release 5.6.0The following feature is deprecated in this release.

• Support for Netscape Navigator




http://java.sun.com/javase/downloads/index_jdk5.jsp

26 | Release Notes

Release 5.5.2The following features are deprecated in this release.

• Repo Data Formats Two data formats are deprecated in the repository: binary and VC. If you are still using binary- or VC-formatted Repo instances, you should convert them into XML format according to the following instructions:

a. Run RepoExport to export your instances.

b. Create XML-formatted Repo instances.

c. Import the exported data into the newly created Repo instances.

• Transport Using Rendezvous Agent Transport using Rendezvous Agent (rva) in the repository is deprecated in this release.

• Runtime Agent Tools The following Runtime Agent tools are deprecated in this release:

— prepareDeployment

— redeploy

— migrateDomainStorage

— repoVersion

— repoManager

— repoStopServer

— import2xSecurity

— export2xSecurity

• ICJava Library ICJava Library is deprecated in this release.

• Java Runtime Environment 1.4.2 JRE 1.4.2 is deprecated in this release.

Release 5.5.1The following feature is deprecated in this release.

• MigrateDomainStorage The MigrateDomainStorage command line utility is deprecated in this release.


Deprecated Features | 27

Use the following procedure to migrate a file based domain to a database based domain. Using the procedure, you create an administration domain that uses a database for domain storage and add machines to the domain. After exporting applications and ACLs from the file-based domain, you import the same to the newly created database domain. After migration, you can clean-up the file based domain.

1. Using TIBCO Domain Utility, create an administration domain that uses a database for domain storage. The domain name must be unique among domains running on the host machine. See Creating a Domain that Uses a Database in the TIBCO Runtime Agent Domain Utility User’s Guide for details.

2. Using TIBCO Domain Utility, add the machines that will host TIBCO applications to the new database administration domain. See Adding a Machine to a Domain in the TIBCO Runtime Agent Domain Utility User’s Guide for details.

3. Using the AppManage utility, export all applications in the file based domain to a directory. For example, the next command line exports all applications found in the myfiledomain domain to the c:\test directory.AppManage -batchexport -dir c:\test -user user1 -pw pw1

-domain myfiledomain

4. Using the ExportDomainSecurity utility, export the ACLs used in the file based domain to the acls.xml file. For example, the next command line exports all ACLs found in the myfiledomain domain to the c:\test\acls.xml file. ExportDomainSecurity –file c:\test\acls.xml –acls -user user1

-pw pw1 -domain myfiledomain

The following restrictions apply when migrating a file based domain to a database based domain:

• Application domains are not moved to the new database domain. You must recreate application domains in the new database domain using TIBCO Administrator. See Working With Application Domains in the TIBCO Administrator User’s Guide for more information.

• TIBCO Enterprise Message Service configurations are not moved to the new database domain and must be reconfigured using TIBCO Domain Utility. See EMS Server Plug-in the TIBCO Runtime Agent Domain Utility User’s Guide.

• Application server configurations (Servlet Engines) are not moved and must be reconfigured using TIBCO Domain Utility. See Adding or Updating a Servlet Engine to a Domain in the TIBCO Runtime Agent Domain Utility User’s Guide.


28 | Release Notes

5. Using the AppManage utility, import the applications into the database domain. For example, the next command line imports all applications found in the c:\test directory to the mydatabasedomain domain.AppManage -batchDeploy -nostart -user user1 -pw pw1 -domain

mydatabasedomain

6. Using the ImportDomainSecurity utility, import the ACLs into the database domain. For example, the next command line imports all ACLs found in the c:\test\acls.xml file to the mydatabasedomain domain. ImportDomainSecurity –file c:\test\acls.xml –overwrite -user

user1 -pw pw1 -domain mydatabasedomain

7. Stop the applications in the file based domain before starting them in the database based domain. Note that you need not restart all applications at once. Applications can be stopped individually in the file based domain and started individually in the database domain.

8. After verifying that all applications are working correctly in the database domain, you can cleanup the file based domain as follows:

— Undeploy all applications from the file based domain

— Delete all applications from the file based domain

— Delete any secondary servers defined in the file based domain

— Remove each machine from the file based domain

— Delete the file based domain


Migration and Compatibility | 29

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 5.6.2

Upgrading to Release 5.6.2

See the TIBCO Runtime Agent Upgrading to Release 5.6 guide for information about upgrading to TIBCO Runtime Agent 5.6. The guide is available in the TIBCO_HOME\tra\version_num\doc\tra folder.

Upgrading to use JRE 1.6 and TIBCO Rendezvous 8.2 with TRA

At the end of Installation of TIBCO Runtime Agent 5.6.2, it will automatically invoke the TRA Upgrade Manager to assist with upgrading the .tra files to use JRE 1.6 and TIBCO Rendezvous 8.2.1. The TRA Upgrade Manager will prompt for a directory to use as a base directory for making changes. All .tra files in the specified directory or any of its subdirectories will be updated. For typical use, it is recommended to provide the directory TIBCO_HOME/tra/5.6 where TRA 5.6 is installed (for example, c:\tibco\tra\5.6 in a typical Windows installation). You may choose to provide a different base directory depending on the scope of change you want in effect for the TRA Upgrade Manager.

You can also separately start the TRA Upgrade Manager at a later time to update domains, applications, or services on a machine to use JRE 1.6. Note that any deployed application not upgraded or redeployed will continue to use JRE 1.5 even if its product has been upgraded. TIBCO Adapters, TIBCO ActiveMatrix BusinessWorks and other products that use TRA maintain templates for applications which use them. The TRA Upgrade Manager merely upgrades the templates.

Once TIBCO Runtime Agent 5.6.2 is installed, any TIBCO products that are subsequently installed will be configured to use JRE 1.5 and TIBCO Rendezvous 8.2. Therefore, the TRA Upgrade Manager utility must be run again to set the JRE to use JRE 1.6, if desired.

Due to third party libraries incompatible with JRE 1.6, some products will not function correctly if upgrade to use JRE 1.6. This is mostly applicable to adapters where the third party libraries that interfaces with the enterprise application or information system are not yet upgraded to use JRE 1.6. Please check your specific


30 | Release Notes

TIBCO product documentation or contact TIBCO Global Support for JRE 1.6 compatibility for your specific product. In such situations you can also use TRA Upgrade Manager to downgrade to use JRE 1.5. You can upgrade and downgrade JRE versions independently of TIBCO Rendezvous versions.

Release 5.6.1


See the TIBCO Runtime Agent Upgrading to Release 5.6 guide for information about upgrading to TIBCO Runtime Agent 5.6. The guide is available in the TIBCO_HOME\tra\version_num\doc\tra folder.

Release 5.6.0

Using JVM 1.6 on HP-UX 11i

If you wish to use JVM 1.6 for your TIBCO applications on HP-UX 11i, you need to update your HP-UX 11i system with the latest patch. Otherwise, you must manually export the path of your JVM 1.6 in order to start the administration servers, TIBCO Hawk agents, TIBCO ActiveMatrix BusinessWorks engine, TIBCO Adapter software, and deployed applications using JVM 1.6. In other words, you must execute one of the following shell commands (depending on whether you have a 32-bit or 64-bit installation) before invoking any executable for TIBCO software or applications:

% export SHLIB_PATH=JRE_1.6_path/lib/PA_RISC2.0/server (32-bit)% export SHLIB_PATH=JRE_1.6_path/lib/PA_RISC2.0W/server (64-bit)

For example:

% export SHLIB_PATH=/home/swadmin/jre1.6/PA_RISC2.0/server

Release 5.5.4


See the TIBCO Runtime Agent Upgrading to Release 5.5 guide for information about upgrading to TIBCO Runtime Agent 5.5. The guide is available in the TIBCO_TRA_HOME\doc\tra folder.



Release 5.5.3



Release 5.5.2



Release 5.5.1



Release 5.5.0



Release 5.4.2


You can upgrade directly from release 5.4.0 to release 5.4.2 without first installing release 5.4.1.


32 | Release Notes


Release 5.4.1


See the TIBCO Runtime Agent Upgrading to Release 5.4 guide for information about upgrading to TIBCO Runtime Agent 5.4. The guide is available in the TIBCO_TRA_HOME\tra folder.

Release 5.4.0



Release 5.3.3

AIX Platforms

This section applies only to TIBCO java-based applications running on AIX platforms.

After installing TIBCO Runtime Agent 5.3.3, you must set the LDR_CNTRL environment variable in the shell used to launch TIBCO applications. After setting the environment variable in your shell, TIBCO applications will correctly use Runtime Agent 5.3.3 software.

• For example, for C shell: setenv LDR_CNTRL USERREGS


See the TIBCO Runtime Agent Upgrading to Release 5.3 guide for information about upgrading to TIBCO Runtime Agent 5.3. The guide is available in the <install-path>\tibco\tra\5.3\doc\tra folder.



Release 5.3.2



Release 5.3.1



The TIBCO Runtime Agent Upgrading to Release 5.3 guide incorrectly states that all released 5.x.x adapters are compatible with TIBCO Runtime Agent release 5.3. The guide also states that future adapter releases will support release 5.3. While most future adapter releases will support release 5.3, you should check the adapter’s documentation for its TIBCO Runtime Agent release requirement.

Only the following adapters are compatible with the TIBCO Runtime Agent 5.3.1 and 5.3.0 releases:

• TIBCO Adapter for EJB 5.1.2

• TIBCO Adapter for MQSeries 5.2.0, 5.2.1

• TIBCO Adapter for ActiveDatabase 5.2.1

• TIBCO Adapter for CORBA 5.2.0

• TIBCO Adapter for COM 520, 5.3.0

• TIBCO Adapter for LDAP 520, 5.3.0

• TIBCO Adapter for Oracle Applications 5.2.1

• TIBCO Adapter for Files 5.4.0

• TIBCO Adapter for ClarifyCRM 5.2.0

• TIBCO Adapter for Infranet 5.1.0

• TIBCO Adapter for Lotus Notes 5.1.0

• TIBCO Adapter for R/3 5.2.1

• TIBCO Adapter for Remedy 5.1.0

• TIBCO Adapter for Siebel 5.2.0


34 | Release Notes

• TIBCO Adapter for Teradata 5.2.1

• TIBCO Adapter for Tuxedo 5.3.0

• TIBCO Adapter for Kenan 5.1.0

• TIBCO Adapter for PeopleSoft 8 5.2.1

• TIBCO Adapter for SWIFT 5.2.0

Release 5.3.0



Release 5.2.0



Release 5.1.3

Migration

See the TIBCO ActiveEnterprise Features, Migration and Compatibility guide for information about migrating custom adapters to use this TIBCO Adapter™ SDK release. The guide is available in the TIBCO_TRA_HOME\doc\tra folder.

Release 5.1.2

Installing TIBCO Adapter 4.x or TIBCO BusinessWorks 2.x

If a TIBCO Adapter 4.x application or TIBCO BusinessWorks™ 2.x is installed after TIBCO Runtime Agent 5.1.2 is installed, you should choose the installation option to use the external TIBCO Rendezvous product installed by TIBCO Runtime Agent 5.1.2.


Closed Issues | 35

Closed Issues

The table in this section list issues that were closed in the named releases.

Closed in Release

Change Request ID Summary

5.6.2 1-9VNRW8 The schema could not be correctly loaded with a recursive xs:extension definition.

5.6.2 1-AAF385 When the Use SSL? option was disabled in the JMWQueue configuration, the SSL configuration was not cleaned up completely and the TIBCO ActiveMatrix Adapter for Database would fail during initialization.

5.6.2 1-A5WHSY The Adapter Tester did not appear as expected if only a version 6.0.x adapter was installed.

5.6.2 1-A2CTG7 The Test Connection button under the JMS sessions in TIBCO Designer threw an error while the MQSeries adapter tried to connect to an SSL-enabled TIBCO Enterprise Message Service server (with JNDI Lookup).

5.6.2 1-96QV5Q After the TIBCO ActiveMatrix BusinessWorks engine was requested to stop, the engine would continue running but cease communicating with the TIBCO Hawk Agent (and therefore TIBCO Administrator). Because the engine was still running, attempts to restart it failed. This occurred when multiple PAR files were defined in an EAR file.

5.6.2 1-ABR7MD The TIBCO Administrator GUI did not display logs correctly if the number of lines in the log file was more than 1000.

5.6.2 1-9ZDWJO Add feature to provide the durable name as GV when creating the queue in the adapter endpoint.

5.6.2 1-A3WQ0L TIBCO Designer changed Union tags in schemas.

5.6.2 1-8J2D4Q In TIBCO Designer, for certain cases TIBCO ActiveMatrix BusinessWorks mapping output may not be well-formed XML. This caused an error message to be displayed in TIBCO Designer when web service calls based upon that mapping were made.

5.6.2 1-9K7MSX The Domain Utility did not find entries when creating a domain integrated with Active Directory Application Mode.


36 | Release Notes

5.6.2 1-A0AKY5 When validating a project in TIBCO Designer, a benign message "DAVstore: Setting connection timeout to 40000 milliseconds" was printed for valid projects.

5.6.2 1-9BSSHP When an EAR file was deployed via AppManage, an exception was thrown, but the deployment was successful.

5.6.2 1-9TAWRT Plain text was shown in the pop-up message box for the password value when changing a global variable from the PASSWORD to Integer type in Global Variable Advanced Editor.

5.6.2 1-7VMGMN The deployment of TIBCO BusinessWorks FormBuilder and Portal applications failed when using TIBCO Administrator domain in a Microsoft Cluster.

5.6.2 1-A11ERN Update JDBC driver to Data Direct 3.7 P64 (aka Build 0064) to properly interoperate with DB2 v9.1 on z/OS.

5.6.2 1-9T9WS9 When a new TIBCO BusinessEvents concept was added to a TIBCO ActiveMatrix BusinessWorks project stored in TIBCO XML Canon, the save operation failed with Null Pointer Exception (NPE). Renaming the Concept would bypass the NPE, but yielded a blank (empty) '.concept' file.

5.6.2 1-9U9QF7 After deploying TIBCO BusinessEvents 3.0.1 HF 4, adding a new concept to a project with a TIBCO BusinessEvents activity yielded a Missing File Exception in the console despite normal UI behavior.

5.6.2 1-9VKXNS Global Variables were not being accepted in a TIBCO Adapter for SWIFT configuration.

5.6.2 1-9W9SZJ Hitting Refresh/F5 in TIBCO Designer after building the EAR file caused memory to grow continuously.

5.6.2 1-9WHF6K Adding a new child role under a Role that had a large number of existing children was extremely slow.

5.6.2 1-9X4TPV In TIBCO Runtime Agent 5.6.1, the setting in the ehCache configuration file for setting the value for maximum memory elements had no effect, resulting in memory growth.

5.6.2 1-A22TQV The schema could not be loaded correctly when it contained the recursive xs:extension definitions.

Closed in Release



Closed Issues | 37

5.6.1 1-9OW61O The 64 bit JMS libraries were missing in TIBCO Runtime Agent 5.6.0 installation on the HP-UX and AIX platforms.

5.6.1 1-9K459Q

1-9MQ9DK

The domainutilitycmd command failed when trying to use the ChangeDomainCredentials task to change the domain administrator password.

5.6.1 1-9PEE3V The TIBCO BusinessWorks Engine shut down and the parameters were not passed on the first deployment.

5.6.1 1-9OEG6H Waiting for check pointing and killing job timeout did not work as expected in TIBCO BusinessWorks 5.4.

5.6.1 1-9PP1Q5 TIBCO XML Mime parser threw the None Point exception when parsing a payload with content-type=multipart/related without boundary parameter set.

5.6.1 1-9OB8T6 The application domain tables aumap and admap were not updated with the new password in case we changed the database password using domainutility.

5.6.1 1-9AD0V8 One of the XML parsers in TIBCOxml didn't properly handle the tibco-char processing instruction, causing those special characters to disappear after parsing.

5.6.1 1-9L4G7Q In the Properties tab of a TIBCO XML Canon project, the build number was displayed incorrectly as 1.2.0 ${build.number}.

5.6.1 1-936V01 When millions of subscriptions existed in a domain, actions such as login which accessed the subscription table in the domain database were very slow; taking multiple seconds to complete. Since these accesses were processed one at a time, users experienced very long wait times.

5.6.1 1-8WRDTO When using a DB2 database domain, deployment delays and failures would result due to DB2 locks.

5.6.1 1-8YH7JB The following issue has been fixed in the updated JDBC drivers:

XA transactions could not be ended, thus preventing transaction starts.

Closed in Release



38 | Release Notes

5.6.1 1-90H0U2,

1-8Y9C16

In the Java SDK, only two threads ran concurrently even when the adapter created more than two threads for a JMS session.

5.6.1 1-8YXYIJ, 1-8X16LJ

Any Add or Delete operation on Membership of a Standard Role via API also checked if members of the Role were valid users.

This caused a serious performance issue when a Role had large number of users assigned as members.

5.6.1 1-88HNMX, 1-8WWXDH, 1-8YJ0AH, 1-92MAIP

When specifying an XML type substitution in the SOAP response message, the SOAP Service failed and the error message Caused by: com.tibco.util.RuntimeWrapException: Internal Error: displayed.

5.6.1 1-98RSC5 After stopping one of the active EMS FT servers, other EMS servers display as stopped in the All Service Instances dialog in the TIBCO Administrator GUI.

5.6.1 1-96MRX9 An application that used a message filter for an Adapter did not deploy correctly in TIBCO Administrator 5.4.

5.6.1 1-9AD12X Fixed edge case in parsing schemas with circular references in multilevel extended complex types.

5.6.1 1-9ALWA4 The TIBCO BusinessWorks inbound security policy failed to validate inbound SOAP messages during authentication or signature if the certificate had a root CA with the Name Constraints X509v3 extension marked as critical.

5.6.1 1-9CBP3M, 1-9C43CL

The JDBC driver failed to accept data larger than 32KB if the data type was CLOB.

5.6.1 1-9H3C6U Commit didn't work in DB-LINK with TIBCO JDBC Driver.

5.6.1 1-9GRJ0G When using a JMS queue as the transport type for publication and subscription services, the multi-thread mechanism did not work well.

5.6.1 1-9GHFAG When logging in to TIBCO eBusiness Applications, an error message similar to the following appeared:Invalid fourth parameter to SWE service method 'ProcessCommand'.

Closed in Release



Closed Issues | 39

5.6.1 1-9L3SXX The Null Pointer Exception was thrown during validation when the schema model had an all group, and the containing instance element was empty.

5.6.1 1-9CDY92 The Java To XML activity did not display the class correctly. It was caught in the infinite loop displaying element.

5.6.1 1-9LWTYM The TIBCO BusinessWorks Service Agent didn’t report a validation error when it received a SOAP request message that contained multiple SOAP Body elements that did not meet the SOAP specification.

5.6.1 1-9EV1MZ A single schema was created for a given Java class and all of the classes on which it depended.

5.6.1 1-9MFIWP The vulnerability to XSS attacks in Apache Tomcat 5.5.25 is fixed in Apache Tomcat 5.5.27. This fix has been packaged in this hotfix.

5.6.1 1-9OSS27 The ArrayList object with one element was previously serialized and stored in BLOB in TIBCO Runtime Agent 5.5.4. The location was changed to the List table in TIBCO Runtime Agent 5.6.0. This change broke Portal functionality for HTML markup greater than 3000 or 4000 characters, depending on the database.

5.6.1 1-9HM63J If you selected the Save changes without asking radio button in the TIBCO Designer Preferences dialog, the project would not be saved if the Apply button was not clicked before saving the project.

5.6.1 1-9L4FQP The Null Pointer Exception was thrown during validation when the schema model had an all group and the containing instance element was empty.

5.6.1 1-9KL49F TIBCOXML threw an incorrect exception when a malformed request was received.

5.6.1 1-9EJSCF Adjust the http pseudo-mime parser to handle axis breakage with chinked mime (axis did not have enough line separators).

5.6.1 1-9CZHTR The Prevent array out of bounds exception was thrown during validation when the schema model had an all group, and the containing instance element was empty.

Closed in Release



40 | Release Notes

5.6.1 1-9CD0B3 The JDBC driver failed to accept data larger than 32KB for Oracle procedures if the data type was CLOB.

5.6.1 1-9DAITH (Solaris 10 x86 Only) The tibicudata.dat and tibicudata32.dat files were missing in the TIBCO Runtime Agent build.

5.6.1 1-9BDEUG An SDK exception occurred when starting an application in TIBCO Administrator if the application used a message filter.

5.6.1 1-9BDFGD An exception in the start method occurred when starting TIBCO Designer using JRE 1.6.0.

5.6.1 1-929961 In XPath Formula Builder, when dragging and dropping from the Data, Functions or Constants tab, in the extreme right corner of the wizard, Expression Evaluates to or a related message appeared. However, the message window was blank.

5.6.1 1-96QPVS A comma within a string value in the Constraint field of a string type global variable could not be escaped. The comma separated the value into two strings.

5.6.1 1-9P00FU In a cluster environment, the domainutlity or domainutlitycmd command failed to recognize the existing TIBCO Administrator server. You could not delete or update the TIBCO Administer configuration, it gave a wrong warning: There are no domains that support your requested tasks.

5.6.1 1-8UZCPL One of the XML parsers in TIBCO XML didn't properly handle the tibco-char processing instruction, causing those special characters to disappear after parsing.

5.6.1 1-7BS8DI If a domain was configured to use a database server, when the database port was later changed using Domain Utility, the software would continue to use the old port, which would result in failed connections to the database.

5.6.0 1-8TTOAG The domainutilitycmd command did not support obfuscated and encrypted data in the password field for the EMS parameters when adding the machine to an EMS based domain.

5.6.0 1-8OPD0Q The number of lines to return specified in the Trace tab in the Administrator GUI was returning an error when the log file had more lines than the specified number.

Closed in Release



Closed Issues | 41

5.6.0 1-8LXPV3 The obfuscate utility did not encrypt all the values in the property file. It was just taking the last value to be encrypted and changing all the values with this value.

5.6.0 1-8EYHBE When undeploying the application, if the hawkagent was down on the remote machine, the TIBCO Administrator still undeployed the component. The component showed as undeployed from the TIBCO Administrator GUI while the project folders still existed on the remote machine and associated process was still running.

5.6.0 1-8EL2EG If you uploaded a new EAR file on top of an existing application, you were not able to see the global variables if they were previously not deployment level settable. In the new EAR file, they were changed to deployment level settable.

5.6.0 1-8CG9BM When updating a project and recreating the EAR file, the list of process definitions was not updated accordingly. If you removed some process definitions, the old process definitions were still visible in Application Management > Ap Name > Service Instances > BW Process > Process Definitions.

5.6.0 1-85UUN4 The domainutilitycmd command expected <RvDaemon>8022</RvDaemon> to be in a particular format like <RvDaemon>tcp:8022</RvDaemon> when trying to add the machine, it failed with the following exception:Error -- java.lang.StringIndexOutOfBoundsException: String index out of range: -1

at java.lang.String.substring(String.java:1762)

at java.lang.String.substring(String.java:1735)

5.6.0 1-85CBEI If we undeployed and redeployed the application after uploading the new EAR file, these files reappeared.

5.6.0 1-8Y0BJV When using the AppManage utility to export applications, the UTF-8 encoding was changed to the ISO8859-1 encoding in the configuration XML file.

5.6.0 1-8FR41U In an EMS domain, the message encoding of a deployed application was always ISO8859-1 instead of the application’s encoding.

Closed in Release



42 | Release Notes

5.6.0 1-8FPK21 It took much more time to do RepoImport or RepoExport in TIBCO Runtime Agent 5.5 than to do RepositoryImport or RepositoryExport in Repository 4.1.2 even when using the same version of JRE 1.5.0.

5.6.0 1-8EV374 The dependant JRE home for TIBCO Runtime Agent 5.4 was not found.

5.6.0 1-87FXOO When a global variable was created under a folder in TIBCO Designer and was set both at the deployment and service levels, the global variable could not be changed in the TIBCO Administrator GUI or by using the AppManage utility at the instance level.

5.6.0 1-86WHX6 ParseXML threw a Null Pointer Exception when the validator could not resolve the type of an element that substituted a wildcard.

5.6.0 1-85UP4I TIBCO BusinessWorks did not support xml:id.

5.6.0 1-8M2LG7 Domain corrupted in database based domains where the references in the ADLIST table would be deleted and the application management would lost the applications and folders.

5.6.0 1-91RIQN If enabling SSL for a domain and selecting TIBCO EMS for the domain communication using the default values, a machine would not be added to the domain.

5.6.0 1-93LXBT If the vpd.properties file was corrupt or empty, TIBCO Hawk would ignore all the TIBCO software installed on the machine.

5.6.0 1-8Z1342 A servlet engine would not be added to a domain using the domainutilitycmd utility after installing TIBCO Runtime Agent 5.5.4.

5.6.0 1-8YKD54 After changing the global variables for an EAR file and reloading it in TIBCO Administrator, TIBCO Administrator GUI threw a java.util.ConcurrentModificationException exception when viewing the new global variables.

5.6.0 1-8WS6H5 After registering TIBCO BusinessWorks Collaborator components to a domain on Windows platforms, the State of the TIBCOServers-Workflow_Server_Server_Name service in the Instances list in TIBCO Administrator GUI was stopped.

Closed in Release



Closed Issues | 43

5.6.0 1-8X3IYK (AIX Only) TIBCO Designer would not start up and the error message "Exception in thread 'main' " displayed after installing TIBCO Runtime Agent 5.5.4.

5.6.0 1-8Y3G4V After installing TIBCO Runtime Agent 5.3.3 or 5.4.3, TIBCO Adapter for Files applications would not start up and the error message "exec(): 0509-036 Cannot load program ./adfilesagent" displayed.

5.6.0 1-89JQDQ All the .tra files contained the incorrect TIBCO_HOME/jre/version/lib/i386/client/libjvm.so directory and Domain Utility would not start up.

5.6.0 1-81RETH In the TIBCO_HOME\tra\version\template\domainutility\cmdline\CreateDomain.xml file, TIBCO Rendezvous and TIBCO Enterprise Message Service were not in separate comment blocks.

5.6.0 1-84MAHZ TIBCO Installation Manager didn’t start up on HP-UX 11i (v2, v3) (IA-64/Itanium) platforms.

5.6.0 1-84MQ6G After using the AppManage -export option to export an EAR file and configure for an application, all the tibco_*** files were deleted from the temporary directory used by the AppManage -export option and the application would not be deployed.

5.6.0 1-8WOOOC After enabling HTTPS for a domain the second time, the TIBCO Administrator server would not start up.

5.6.0 1-8OSSS7 If enabling SSL for a domain and using TIBCO Enterprise Message Service for the domain communication, machines would not be added to the domain using the domainutilitycmd utility.

5.6.0 1-8K2S88 Domain Utility didn’t support Time of Day for LDAP Group membership.

5.6.0 1-8KDXZU After installing TIBCO Rendezvous 8.0, it would not be used with TIBCO Runtime Agent and other TIBCO products.

5.6.0 1-8B1J39 Domain Utility didn’t support Database URL when adding a machine to a domain with a database backend.

Closed in Release



44 | Release Notes

5.6.0 1-8IRNB9 The error message was not correct if the Database URL was blank in the Database configuration dialog while creating a domain with a database backend.

5.6.0 1-8IRNCO The configuration records in the Domain Utility Confirm dialogs were not updated accordingly to reflect any changes.

5.6.0 1-8A2ORJ Users marked 'Inactive' in LDAP would continue to get authenticated successfully through Portal where the TIBCO domain was integrated with LDAP.

5.6.0 1-848CZT Typical installation of TIBCO Runtime Agent 5.5.0 did not work on the following platforms:

HP-UX 11.23 on PA-RISC

HP-UX 11.31 on Itanium

5.6.0 1-8T2VLL (HP-UX Only) TIBCO Runtime Agent used the system JAVA_HOME instead of picking it up from the related .tra file.

5.6.0 1-8ZM0CH The new extended vm options which have spaces in the value like -XX:OnOutOfMemoryError="Kill -9 %p", -XX:OnError="cat or

kill with followed args were not picked by TIBCO Runtime Agent.

5.6.0 1-8XK12H TIBCO BusinessWorks services would not start up from TIBCO Administrator GUI.

5.6.0 1-8AS69P After enabling HTTPS for a domain, the Appmanager utility could not be used to deploy the applications in the domain.

5.6.0 1-787I68 TIBCO BusinessWorks engines did not use the java initial heap size defined in the TIBCO Administrator GUI because it wrote java.heap.size.min rather than java.heap.size.initial into the engine’s .tra file.

5.6.0 1-75WRA2 When registering a servlet engine, if an incorrect username and password were provided, the incorrect validation error message Please provide the administrator password appeared.

5.6.0 1-7YR13H When editing a TIBCO Enterprise Message Service server SSL configuration and encountering an error, the exception was not written to the Domain Utility log file.

Closed in Release



Closed Issues | 45

5.6.0 1-7RN9AF Port numbers used in an administration domain were not auto incremented when creating a domain using domainutilitycmd.

5.6.0 1-7GFBPU The domainutilitycmd script would not be used to change an administration domain transport from TIBCO Rendezvous to TIBCO Enterprise Message Service, or the reverse.

5.6.0 1-7GF8H9 When an SSL connection failed while specifying the identity file and password for the client's identity, the exception was written to the administrator.log for the administration domain, not domainutility.log.

5.6.0 1-7FHUXT When using the domainutilitycmd script to add, update or remove an Enterprise Message Service server from an administration domain, invalid values for server related options were ignored. The task successfully completed message appeared even if incorrect values had been provided.

5.6.0 1-7DTHWX When using the ImportDomainSecurity utility to import ACLs into an administration domain, ACLs set on the Authenticated Users role were ignored.

5.6.0 1-7C76U9 When using the ImportDomainSecurity utility, ACLs set on the Guest role were not imported into an administration domain.

5.6.0 1-7BVBRJ The .tra files in the TIBCO_HOME/tra/version/bin didn’t point to the correct Tomcat version.

5.6.0 1-7GJQKD You didn’t need to provide the administrator user credentials when changing the database for a domain using Domain Utility.

5.6.0 1-7Y48OO A spurious unicode character displayed in the Confirm dialog after generating and installing a self-signed certificate.

5.6.0 1-6OEHC3 If the LDAP Search attribute for Group Name was specified as sAMAccountName and the Group was renamed in Microsoft Active Directory without updating its pre-Windows 2000 name, TIBCO Administrator failed to detect the renamed Group.

5.6.0 1-7CGP5S TIBCO BusinessWorks threw a validation error when xsi:type appeared on the node defined as xsd:any.

Closed in Release



46 | Release Notes

5.6.0 1-8CQWBC Fixed edge case in parsing schemas with circular references in multilevel extended complex types.

5.6.0 1-8HEX1D XSLT engine failed when there was no following sibling after xsl:variable in the context.

5.6.0 1-8U5KPP TIBCO BusinessWorks didn’t resolve xsi:type for the wildcard node itself, but resolved the descendent nodes.

5.6.0 1-8UC2GX After replacing designer.exe with the JRE 1.6 wrap, TIBCO Designer threw an exception when saving a new project.

5.6.0 1-79U8T5 Not all fields were shown when type hierarchy was recursive with multiple levels of extension.

5.6.0 1-85GDA2 There was mapper validation error on AIX platforms.

5.6.0 1-88HNMX When specifying XML type substitution in the SOAP response message, the SOAP Service failed and the error message "Caused by: com.tibco.util.RuntimeWrapException: Internal Error:" displayed.

5.6.0 1-86NGUV The outOfValidityOK flag was ignored in the CertChainVerifier chain which was a single element self-signed chain.

5.6.0 1-8EN5NN After installing TIBCO Runtime Agent, the startagent file was in the TIBCO_HOME/hawk/bin directory on UNIX platforms.

5.6.0 1-3JKL3P When using the ExportDomainSecurity utility, LDAP cyclic groups result in an incorrect export and, after importing, LDAP Sync failed.

5.6.0 1-82KRRM tibhawkhma64.exe was not used with TIBCO Runtime Agent 64-bit installer on Linux platforms.

5.6.0 1-6NBNMB When using ImportDomainSecurity to import roles on which users have permissions set, the import fails if roles of the same names already existed in the target administration domain.

Closed in Release



Closed Issues | 47

5.6.0 1-7DYOUD An exception similar to the following occurred after exporting ACLs from an administration domain to which ACLs were imported.Exception in thread "main" java.lang.NoClassDefFoundError: com/tibco/administrator/FolderConsole at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620)... at com.tibco.pof.util.ExportDomainSecurity.main(ExportDomainSecurity.java:249)

5.6.0 1-7ZP4Y1 After installing TIBCO Runtime Agent on Linux glibc 2.2 (TIB_tra-suite_5.5.0_linux24gl22_x86.tar), the TIBHawkhma process did not start and core dumps. As a result, machine statistics such as CPU and Memory Usage did not display inside the TIBCO Administrator GUI.

5.6.0 1-7P53ZC The Edit Service Instance Advanced tab panel displayed empty when there were no service level global variables defined in the EAR file.

5.6.0 1-5155DD Provide a facility to create a design time library (LibraryBuilder) from the command line, similar to creating ear files with the buildear command.

5.5.4 1-7Z2YUE The XSLT engine failed when there was no sibling after the xsl:variable in the context. An error similar to the following would display in the TIBCO BusinessWorks Transform XML activity:

"java.lang.IllegalArgumentException: returnExpr".

5.5.4 1-6NYY58 When TIBCO PortalBuilder™ instantiated a large number of threads, and each thread invoked ExpandedName.makeName(), all threads remained waiting on ExpandedName.makeName() due to thread contentions.

5.5.4 1-8CZGKP The Entrust 7.2 security provider has been updated with Patch 134641, which is validated as FIPS 140-2 compliant.

5.5.4 1-7ZRM41 TIBCO PortalBuilder displayed notification messages that were not localized.

Closed in Release



48 | Release Notes

5.5.4 1-86D040 The web servers hosting TIBCO PortalBuilder would stop responding due to a heavy load. High CPU and memory usage would occur on each web server. This has been fixed by removing ReaderWriterLocks around authorization checks.

5.5.4 1-88XF09 Removed the synchronization on the LDAP Group object while checking membership of a user in a certain (static or dynamic) group. This will increase the performance by removing the contention caused by the LDAP Group object. Since multiple requests for group membership are for different users, this will not add any more LDAP requests.

5.5.4 1-88CTA9 When authenticating a self-signed certificate (root or leaf) from a server, the software failed to verify the certificate's common name against the server's hostname.

5.5.4 1-895KTU After TIBCO BusinessWorks™ was migrated from release 5.1.3 to release 5.2 or above, the Xpath function parse-Datetime added time zone information at the end of the datetime string. This caused release 5.4 or above to break backward compatibility with release 5.1.3. The system property com.tibco.xml.xpath.parse-dateTime.has.timezone has been added. The default value is true. Setting the value to false gives behavior consistent with BW 5.1.x.

5.5.4 1-8B1BXR The TLS_DHE_RSA_WITH_AES_128_CBC_SHA cipher suite could not be used with a non-default J2SE security provider.

5.5.4 1-8C0BOE When an application was redeployed in TIBCO Administrator, the application’s global variables were reset to the values in the EAR file that was loaded for redeployment.

5.5.4 1-8HYVND This fixed a security vulnerability. For detailed information, please contact TIBCO support.

5.5.4 1-8IKEOW The authentication plug-in wrapper that provides pre and post authentication capability forced authentication requests to be serialized. This could cause performance degradation in situations where pre or post authentication is a lengthy process. This has been fixed such that all the user authentication requests (login, verify or logout) are now executed in parallel.

Closed in Release



Closed Issues | 49

5.5.4 1-8O6UV5 The TimeOfDayForExpiry parameter is now available to control when the schedule is reset. Instead of the schedule reset always occurring at midnight GMT, the reset can occur at the time given for the TimeOfDayForExpiry parameter.

See Time of Day for Expiry Parameter in TIBCO Runtime Agent Domain Utility User’s Guide.

5.5.4 1-8U6370 The JDBC driver in TIBCO Runtime Agent 5.5.2 did not work with SQL Server 64 bit version when using XA JDBC transactions.

5.5.4 1-8QWLGR When getClob() was called on a CLOB output parameter with z/OS, the driver generated an Unsupported data conversion exception.

5.5.4 1-80LQGP When getClob() was executed with Clob output parameters, the driver generated an Unsupported data conversion exception.

5.5.4 1-5MLNKR Specifying the JmsProviderURL with a pipe symbol resulted in an exception with an invalid port error. JMS C APIs support the load balancing server URI specification only through ConnectionFactories, which TIBCO Adapter SDK code was not using.

The adapter JMS session configuration should simply provide the connection factory name. The load balance url is taken care of by the JMS server, which refers to factories.conf for the definition. The JmsProviderURL on the adapter JMS session serves only to provide the initial connection url.

5.5.4 1-8GIR2E When upgrading from TIBCO Runtime Agent 5.3, the COM, File and ActiveDatabase adapters would throw the AESDK-0151 JMS error if the JMS server was running on a non default port.

5.5.4 1-73A7CS In C++ SDK for JMS transport, a connection factory lookup was always done and this broke backward compatibility. There was no way to enable or disable the connection factory lookup. A new property has been added:

tibco.connectionfactorylookup = "on" "off"

By default, the property is set to off for backward compatibility.

5.5.4 1-8H1WG0 In Java SDK, when using the RPC Server service, the JMS session did not close properly.

5.5.4 1-7Z9VRZ Deployment over a WAN was very slow and would time out.

Closed in Release



50 | Release Notes

5.5.4 1-7Y9SKJ On HP-UX (HPPA) 64-bit machines, if the standalone TIBCO Hawk 4.7.0 product was installed with TIBCO Runtime Agent 5.4.2 and TIBCO Administrator 5.3.0, then TIBCO BusinessWorks engines could not be stopped using the TIBCO Administrator GUI. Also, machine CPU usage and partitions could not be viewed in the TIBCO Administrator GUI.

5.5.4 1-83L787 The wrap executable has been recompiled on the HP-UX PA-RISC platform so that the operating system can allocate more memory to running processes.

5.5.4 1-1AT61T On Windows 2003 Server, the value assigned to the TIB_ICU_DATA environment variable in the adapter's .tra file was not picked up at runtime.

5.5.4 1-6T6HUN On Windows XP, an error would result when publishing Japanese language data using SHIFT-JIS as the encoding value.

5.5.4 1-6VWI7T An SQL statement could not be executed using SQL DIRECT in TIBCO BusinessWorks.

5.5.4 1-6SJXK9 For multithreaded adapters, high CPU use would result when a JMS connection was lost even there was no incoming requests.

5.5.4 1-6TMU9D The space of a reply parameter (of MBinary type) was freed during a syncInvoke call, so when the reply parameter was accessed a free memory error occurred.

5.5.4 1-1Z2N4O When using an HTTP RepoURL, the C++ Adapter SDK was taking a long time to fetch instance configuration data from the TIBCO Administrator repository server.

5.5.4 1-6RB2TB The C++ Adapter SDK Base64 encoding of a binary message introduced an extra character ('\n') in the message. As a result, message decoding would fail on the Java subscriber side with a 'String index out of range' exception.

Closed in Release



Closed Issues | 51

5.5.4 1-6SAA5H If a user was given read, write and admin privileges to a folder under Application Management and attempted to configure an application under that folder, the user could not:

• see the Service Instances console for the deployed application.

• add a machine to an archive.

• add monitoring events to an archive.

5.5.4 1-30TRLT Schema with processContents = lax did not catch the errors.

5.5.4 1-4DJ3YD If you saved and closed a project for an adapter configuration such as TIBCO Adapter for MQSeries that contained a service, reopened the project and changed the transport, then saved and closed the project, the project would be corrupted when attempting to reopen it.

5.5.4 1-4MVOVE When exporting a project to a dat file using TIBCO Designer 5.2, some scalar elements were missing in the exported .dat file. As a result, an adapter such as TIBCO Adapter for COM would not start.

5.5.4 1-5K6RWL When using the XML Canon DAV Plug-in for TIBCO Designer 5.2, when no change was made after checking out resources and then synchronizing, the resources appeared as locked (non-editable). When a change was made after checking out a resource and then synchronizing, only the changed resource was editable and other resources were locked (non-editable).

5.5.4 1-5PB33C When using the XML Canon DAV Plug-in for TIBCO Designer 5.2 and adding files or folders or importing a folder that contained files, when deleting a file from TIBCO Designer and saving, a null pointer exception occurred.

5.5.4 1-5MX5YZ When using the XML Canon DAV Plug-in for TIBCO Designer 5.2 and opening a project from XML Canon and adding a library builder or deployment descriptor, then building an EAR file, when saving an error would result indicating that "somehow an unknown resource has already been added".

5.5.4 1-5PI9NW When using the XML Canon DAV Plug-in for TIBCO Designer 5.2, a project could be opened by a user who did not have permissions for the project.

Closed in Release



52 | Release Notes

5.5.4 1-6D3Q6H When an Adapter SDK JMS queue subscriber was suspended and activated again, messages pending in the JMS queue were not delivered.

5.5.4 1-6KLGK0 When an adapter used an Adapter SDK AE operation that used the TIBCO Enterprise Message Service, no reply message was received and a time-out did not occur.

5.5.4 1-6ILYCB Errors would result when adding multiple Java classes that inherited from the same class.

5.5.4 1-60H3ZX For adapters, an _SDK.ERROR.RPC.BADMSGFORMAT advisory error would result for a JMS request that contained empty value elements for a UTF-8 repository.

5.5.4 1-4ZX52C When using Domain Utility to set or change TIBCO Rendezvous parameters used by TIBCO Hawk, an alias could not be used for the service parameter.

5.5.4 1-60ZWVL When using the JMS transport and a UTF-8 repository, a deserialization error would occur if certain fields were empty.

5.5.4 1-4RIZP3 The validator would report an error if nested sequences were in a content model, even though the XML was valid.

5.5.4 1-5JB3YK When a C++ Adapter set the HTTP based repoURL and tried to communicate with READ-ONLY Administrator servers, it was throwing an exception.

5.5.4 1-5GVQ9N An adapter would crash when receiving messages from a JMS Queue where the integer type JMS property JMSXDeliveryCount was set.

5.5.4 1-5I6PB1 When a repoURL encrypted password contained more than 66 characters (prefixed by #!), an adapter would throw the error:

".\crypto\evp\evp_enc.c(261): OpenSSL internal error, assertion failed: inl > 0".

5.5.4 1-5UI0J9 Temporary consumers were not correctly deleted in case of timeout. This caused CPU utilization to go up even during idling.

5.5.4 1-404M4H A ClasscastException was thrown when you tried to export a full project to an administrator server, with a name that already existed.

Closed in Release



Closed Issues | 53

5.5.4 1-7UZLT8 In the C++ SDK, memory was utilized very rapidly when MOperationRequest::asyncInvoke() was used for RPC invocation in asynchronous mode.

5.5.4 1-8HEES0 In the C++ SDK, the data type of the uptime returned field of the TIBCO Hawk method getStatus was string.

You can now use the tibco.hawkUptimeDataType property or the -system:hawkUptimeDataType command line parameter to specify the data type. If the value of the property or command line is integer, the data type of the field is integer. Otherwise, the data type of the field is string.

5.5.4 1-7WT0AH The getProperty() method of MTree failed to get the JMS properties of the JMS session.

5.5.4 1-81OE3Q For a custom adapter when the following occurred and the user name was created with a password, a custom adapter could not connect to the EMS server even if the correct password was provided in the repository configuration in TIBCO Designer.

• JMS transport was configured

• Authentication parameter in tibemsd.conf was enabled

• JNDI lookups in the repository configuration was checked

This happened because the password was not being sent to the underlying EMS APIs correctly when creating a JMS connection.

5.5.4 1-6MCI1V After changing a deployed project’s global variables from not marked as deployable to marked as deployable and redeploying the project, the global variables were not deployable (even though they were changed as deployable).

5.5.3 1-88FNUG If TIBCO BusinessConnect was configured to use an AES encryption algorithm with strong ciphers in TIBCO BusinessConnect (AES-192 and AES-256), it would fall back to using 128-bit keys (AES-128) when encrypting messages.

5.5.2 1-6ZOKD AppManage returned the erroneous exit code FAILURE_NOT_AUTHORIZED when starting or stopping an application that did not exist.

AppManage now returns FAILURE_APPLICATION_NOT_EXIST.

Closed in Release



54 | Release Notes

5.5.2 1-6VU1DC In a user’s password contains the ’&’ character, the software returned an OperationFailedException error when deploying and undeploying an application.

5.5.2 1-6X1INZ When you executed the following command:

AppManage -batchExport -domain domain...-dir dir

and the -dir option was followed by a relative path (a path that included "./" or "../"), AppManage generated only the deployment configuration files and the AppManage.bat file but failed to generate the application archives.

5.5.2 1-70A5QI In the EMS client in tibcojms.jar, a consumer could not acknowledge a message after the consumer was closed, contrary to the JMS specification.

5.5.2 1-712I6C When AppManage was exporting deployment configuration for an EAR, and the input config.xml file contained the <daemon> element with a specified port within the <repoInstances> element, the output file failed to include this information and set the <daemon> element to the default value (tcp:7500) instead.

5.5.2 1-73J7HY When AppManage started or stopped an application that was in the undeployed state, the console output reported success of the operation whereas the operation actually failed.

AppManage now exits with a FAILURE_APPLICATION_NOT_DEPLOYED error.

5.5.2 1-75XH30 TIBCO BusinessWorks could not handle "multi-level schema redefine". At runtime, it was unable to validate an XML document if it contained an element of a redefined type that redefined yet another redefined type.

5.5.2 1-78Q547 domainutilitycmd reported that addServletEngine is not a valid task.

5.5.2 1-7A5TQ0 If the name of an Identity resource in a TIBCO Designer project contained a period (’.’), then the DAT file generated by deployment would not contain that Identity resource.

Closed in Release



Closed Issues | 55

5.5.2 1-7AYKN7 XML Turbo sometimes generated non-unique TIBCO Namespaces (namespaces whose names matched previously defined namespaces in the project).

5.5.2 1-7BXHDF The number() function in the TIBCOxml JDK accepted double or floating point suffixes (’D’, ’d’, ’F’ and ’f’), which was not adherent to the XPath specifications. For example, number(2D) returned 2 instead of NaN.

5.5.2 1-7C0ZW5 Performing two separate ACL import operations on the same domain within a short time frame sometimes caused the latter operation to fail with the following error:

"User user_name failed to lock object with name object_name. Object was locked by user_name."

5.5.2 1-7C772C When an ACL was imported into a domain and the ACL refers to resources that did not exist, AppManage did not provide any warning message to the user.

AppManage now gives a warning message that indicates a specific resource in the imported ACL list does not exist.

5.5.2 1-7FQ82G Hawk Agent did not properly handle the -ssl_no_verify_host flag in hawkagent.cfg. After an administration domain was created with TIBCO Enterprise Message Service as the message transport and with SSL enabled, if the -ssl_no_verify_host field was set to true, then Hawk Agent would not start.

5.5.2 1-7P5WVB Opening an imported XSD schema in TIBCO Designer caused a stack overflow, and consequently the relationship map did not show up.

5.5.2 1-7RO3HQ DomainSecurity.xsd did not include all the available attributes for the <AccessControlList> element.

5.5.2 1-7T5ZFF When using the EMS client in tibcojms.jar in EXPLICIT_CLIENT_ACKNOWLEDGE mode, message.acknowledge() sometimes did not acknowledge the message or acknowledged an incorrect message.

Closed in Release



56 | Release Notes

5.5.2 1-7T8HC5 In a domain that was not set up to use local application data, every time a new version of an EAR file was uploaded, its transport setting was reset to Rendezvous, even if it had been previously configured with local transport.

The software now preserves the existing transport settings when uploading EAR files.

5.5.2 1-7VEC7P When performing batch export on archives in a specified directory, AppManage would not place the exported configuration files into the specified directory if the directory name was "ears". Instead, AppManage would place the exported configuration files in a folder called "<parent_directory>.xml_files".

For example, if you executed the following command:

AppManage -batchExport -dir "c:\tibco\dev\ears"

you would find the exported configuration files in the "c:\tibco\dev.xml_files" directory.

AppManage now places exported configuration files into the "ears" directory as expected.

5.5.2 1-7VUKHB If an LDAP user’s common name (CN) contained a comma, groups associated with that user would not show up in the user’s Role Membership pane in Administrator.

5.5.2 1-7X15QA tibrvjms.jar contained an instance of the TibrvListener class which overrode the same class in tibrvnative.jar.

TibrvListener has been removed from tibrvjms.jar.

5.5.2 1-7X1IKP If an XSD contained a relative path for its schema location (either "./" or "../", the software would fail to resolve the schema reference when building the EAR file and throw a StringIndexOutOfBoundsException.

5.5.2 1-7XMKA1 If two UNIX users each set up a separate domain on the same machine, and both domains used local application data, one of the users would experience deployment failure when they are deploying the same application on the separate domains.

5.5.2 1-7Y6R2P The software’s Hawk Agent did not spawn tibhawkhma in on Linux with glibc 2.2.x.

Closed in Release



Closed Issues | 57

5.5.2 1-7ZOVEU When 64-bit Hawk microagent was used, TIBCO Administrator did not show CPU and virtual memory usage in the General tab of the machine view, and the Processes tab did not show the running processes either.

5.5.2 1-7ZVEEF On the Solaris OS, the TIBCO BusinessWorks activities “Adapter Subscriber” and “Invoke an Adapter Request-Response Service” were not able to de-serialize messages from the 64-bit UNICODE version of TIBCO Adapter for SAP R/3 when the message was in the XML wire-format (ae-xml).

5.5.2 1-80835K When the domainutilitycmd executable was used to create a new domain, it failed and threw a com.tibco.objectrepo.NotAllowedException.

5.5.2 1-80FDPQ If an LDAP server was setup to use dynamic group membership and anonymous query access was disabled, you would observe the following two behaviors:

• The LDAP users were not showing up in the User Management pane in TIBCO Administrator.

• There was a marked increase in the number of TCP connections, which were left in the TIME_WAIT state.

5.5.2 1-811MHA Idle systems that were running Linux AS4 were shown in TIBCO Administrator with CPU usage at 100%.

5.5.2 1-815K46 After the software was upgraded to release 5.5, the tibco.class.path.extended property in the .TRA files for existing domains did not include the path /tibco/tibrv/lib/tibrvj.jar as it should. The affected files are:

hawkagent_domain_name.tratibcoadmin_domain_name.tra

5.5.2 1-81E5HY When a large number of users were concurrently using TIBCO Portalbuilder, the TIBCO Administrator became unresponsive due to deadlocks between concurrent threads.

5.5.2 1-81EIWL When a large number of users were concurrently using TIBCO Administrator, threads that were waiting on the LDAP connection pool were not getting notified of available connections (they remained in WAIT state while very few connections were actually being used).

Closed in Release



58 | Release Notes

5.5.2 1-82FHNL When a UTF-8-encoded ACL was imported into a domain, multi-byte characters (for example, Chinese and Thai) were not imported properly.

5.5.2 1-830I14 If an application’s deployment configuration file contained an empty <description> or <contact> tag, you would see conflicting information on the application’s status in TIBCO Administrator after deploying it with AppManage. The Application > Application > Configuration page would show the application as "synchronized" and "success", but clicking on the application’s .PAR file would show the application as "deployable" in the Service Configuration pane.

5.5.2 1-838478

(tra)

When an upgrade is made to a deployed application using a new archive file, schema changes were not updated in the deployed application.

5.5.2 1-83QSDX Connections to SSL servers failed because SSL ciphers not included in the software’s policy file were being delivered to the servers. The software came with a limited-strength policy file, but it actually sent to the servers the complete list of ciphers covered by the unlimited-strength policy file.

NOTE: Customers who wish to use 256 AES ciphers must download an unlimited-strength policy file from their JVM vendor’s Web site and use it instead of the limited-strength policy file packaged with the software.

5.5.2 1-843S15 TIBCO BusinessWorks did not allow wildcard are anyType elements to be nilled in an XML document while the XML schema specification allowed it.

5.5.2 1-84P688 In release 5.5.1, The DAT file created for the adapter tester had different values than in previous releases for the following global variables: %%deployment%% and %%domain%%, which were not in sync with their expected values. In 5.5.1, their values were the name of the DAT file, whereas in previous releases, their values were the name of the project in TIBCO Designer.

The adapter tester’s DAT file now uses the name of the TIBCO Designer project for %%deployment%% and %%domain%%.

Closed in Release



Closed Issues | 59

5.5.2 1-86NGWV Schemas with <redefine> constructs could not be displayed correctly or edited in XSDEditor.

5.5.2 1-86AORZ Application deployment over a WAN was extraordinarily slow and eventually terminated due to timeout.

5.5.1 1-7TMJ27 Some C++ Adapters did not start-up on the Linux platform when run on TIBCO Runtime Agent 5.5.0. The Adapters would throw an exception error message similar to the following:

-Code = AESDKC-0128, Category = Unicode, Severity = errorRole, Description = Unicode conversion failure : Failed to convert type "LATIN_1" to Unicode - have you defined the env var TIB_ICU_DATA to point to the directory that contains tibicudata32.dat?, File = S/MUConverter.cpp, line = 166

5.5.1 1-1YAPA2 When using TIBCO Domain Utility to enable HTTPS with a self signed certificate and using double byte characters for entries, the characters were not handled correctly.

5.5.1 1-6XXL5V When an application was stopped in TIBCO Administrator, the error count status would return as 1, rather than 0. Because of this, TIBCO Hawk Agent would attempt to restart the application, rather then do nothing (because the application was stopped in TIBCO Administrator). This has been fixed such that when an application is stopped in TIBCO Administrator, the error count status is correctly set to 0.

5.5.1 1-79CBVH During deployment, the generated TIBCO.xml file was not saved as UTF-8. As a result, Japanese characters in the file were garbled.

5.5.1 1-7A61YQ When using TIBCO Administrator to deploy and undeploy an application (such as a TIBCO FormBuilder application), the thread count would increase as the application was deployed and undeployed. As a result, more memory was required to keep the threads alive.

5.5.1 1-7AE70X When using TIBCO Domain Utility to update a servlet engine, the update procedure did not create the TPCLlib5.x.jar file. As a result the servlet engine would not start.

Closed in Release



60 | Release Notes

5.5.1 1-7B3MG0 Using TIBCO PortalBuilder, a fully qualified domain name was required when logging into a portal. This was because the Domain field for Cookie Authentication Portal would not accept null as a value. This has been fixed such that the null value is supported in the Domain field.

5.5.1 1-7FZOI4 When using the domainutilitycmd command line tool to add custom software to an administration domain, not all constraints specified in the input XML file were checked.

5.5.1 1-7U8PHB When using the domainutilitycmd command line tool to add a custom Java adapter into an administration domain, the generated .tra file was based on the adaptercplustra.template file instead of the adaptertra.template file. As a result some Java properties were missing in the generated .tra file.

5.5.1 1-7P6VJP On Linux, an exception similar to the following appeared in the tsm.log file and the machine uptime was not reported in the TIBCO Administrator GUI.

Puma: Exception "MachineStatusHandler getMachineStartTime() failed. java.util.MissingResourceException: Can't find resource for bundle com.tibco.tra.tsm.TsmResources, key Up Time" on LINUX

5.5.1 1-7SGRJD If a password type Global Variable contained special character such as "&" in a project, it was not stored correctly in the .dat file, and on retrieval "&" became "&". The set of special characters were anything with ASCII value less than 20.

&<>'"

5.5.1 1-7T07AX Running TIBCO Domain Utility 5.5 to create the TIBCO BusinessWorks Collaborator Deployment Platform would fail.

5.5.1 1-7TKWMC While installing TIBCO BusinessWorks FormBuilder 5.2.0 in the directory pointed by the symbolic link, the CreatePlatformArchive tool would fail.

Closed in Release



Closed Issues | 61

5.5.1 1-7U8OEB The error message displayed when the TIBCO Enterprise Message Service server was configured unsuccessfully with SSL did not provide information about the underlying cause.

5.5.1 1-7EY52C The TIBCO BusinessWorks Parse XML activity didn’t release memory after the job completed.

5.5.1 1-7V50ET On a Japanese machine with MUI JA 2.0 installed, after setting the user language to English and starting TIBCO Domain Utility, the display would be in English (correct). After clicking the Main Menu button to go back to the main menu screen, Domain Utility would display in Japanese (incorrect).

5.5.1 1-7V96PE When using the AppManage utility to deploy an application, if a different user than the domain user was specified in the utility, the User Name under the History tab of the application in the TIBCO Administrator GUI would display the domain user instead of the user specified in the AppManage utility.

5.5.1 1-7WM72G The following exception would be thrown when starting TIBCO Administrator, TIBCO BusinessWorks and TIBCO Hawk Agent.

java.lang.NoSuchFieldError: _implat com.tibco.tibrv.TibrvListener.init(TibrvListener.java:72)at com.tibco.tibrv.TibrvListener.<init>(TibrvListener.java:58)at COM.TIBCO.hawk.ami.AmiSession._amiSessionInit(AmiSession.java:961)at COM.TIBCO.hawk.ami.AmiSession.<init>(AmiSession.java:78)at com.tibco.pe.hawk.EngineHawkMicroagent.<init>(EngineHawkMicroagent.java:214)at com.tibco.pe.PEMain.if(PEMain.java:314)at com.tibco.pe.PEMain.a(PEMain.java:157)at com.tibco.pe.PEMain.<init>(PEMain.java:144)at com.tibco.pe.PEMain.main(PEMain.java:82)

5.5.1 1-7XLCYO The byte order mark (BOM) was not handled correctly by the SOAP engine. This prevented a TIBCO BusinessWorks client or server from interoperating with other SOAP clients or servers that sent SOAP message with a BOM.

Closed in Release



62 | Release Notes

5.5.1 1-7Y6RD9 TIBCO Rendezvous. Fixed an incompatibility between daemons of different versions. The symptom was unexplained data loss in specific situations. Dataloss occurred only with data broadcast (using TRDP) from "older" daemons (releases 7.4.x and earlier), and received by "newer" daemons (releases 7.5.x). The trigger for data loss was a "quiet" reliability interval -- that is, if the interval elapsed without the older sender transmitting any data packets, then the newer receiver would not detect dropped packets until after the sender had discarded the data.

5.5.0 1-1F8FBI After using the RepoConvert utility to change a single-file project that contains a Message Filter into a multi-file project, the Message Filter would be lost. When opening the resulting multi-file project in TIBCO Designer, the Message Filter would appear as an unknown resource type.

5.5.0 1-638EAI When using the -encryptedPassword option in TIBCO Enterprise Message Service version 4.2.0 in an administration domain, an error similar to the following was written to Hawk.log and the Enterprise Message Service plugin microagent was not loaded by the TIBCO Hawk Agent. The un encrypted -password worked fine.

2005 Jun 20 08:53:48:240 GMT -5 HawkAgent.mako.grhq.gfs.com Error [Application] HWKAGT-060104 Error loading microagent from com.tibco.tibjms.admin.hawk.HawkController: COM.TIBCO.hawk.talon.MicroAgentException: Unrecognized option: -encryptedPassword

5.5.0 1-6O66XC When adding or editing LDAP Search Parameters and Attributes for an administration domain, a popup dialog appears. Vendor details changed in the dialog were not reflected correctly in the Search Parameters field.

5.5.0 1-6ZTA20 A JDBC query would fail when UTF8 encoding was used. An error similar to the following would occur:

BW-JDBC-100014 "JDBC error reported: (SQLState = HY000) - java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver]null" caused by: java.sql.SQLException: [tibcosoftwareinc][Oracle JDBC Driver]null

5.5.0 1-73Z1EO When redeploying adapters and processes on Windows 2000 servers, the corresponding system service would stay in Disabled status (with the delete flag set in the registry).

Closed in Release



Closed Issues | 63

5.5.0 1-750XI8 Running services deployed to certain servlet engines, for example, Tomcat 5.5 and Websphere, would display as Stopped in the TIBCO Administrator GUI.

5.5.0 1-7657Y2 The DataDirect 3.5 driver bundled in TIBCO Runtime Agent did not support Oracle 10g R2 (10.2.x.x). The DataDirect 3.6 driver bundled in Runtime Agent 5.5 supports Oracle 10g R2 (10.2.x.x).

5.5.0 1-77O6X7 When installing TIBCO Runtime Agent 5.4.1 you were prompted to update TIBCO Rendezvous 7.5.1 to version 7.5.2. If you choose NO, the Dependency Check dialog appeared to inform you that version 7.5.2 is required. The dialog has been removed and you no longer have the option not to upgrade. That is, TIBCO Rendezvous is always upgraded to version 7.5.2.

5.5.0 1-788535 The following error would appear when creating a administration domain using the domainutilitycmd script with default or non-default Rendezvous parameters:

com.tibco.objectrepo.NotAllowedException: Illegal null parameter

5.5.0 1-7BPS5Z A custom adapter could not be registered in an administration domain using the domainutilitycmd script.

5.5.0 1-7C76YH When using the ExportDomainSecurity and ImportDomainSecurity utilities, the Inherit Parent's Security Settings options (set in the TIBCO Administrator GUI) were ignored for roles.

5.5.0 1-7C7FU1 The commons-collection.jar file was not in the class path of Hawk Agent and a class not found exception resulted.

5.5.0 1-7F2908 User credentials were not checked when modifying Rendezvous parameters with the domainutilitycmd script.

5.5.0 1-7FHUYA When using the domainutilitycmd script to change domain credentials for the domain administrator, the utility did not check whether the credentials had already been changed in the TIBCO Administrator GUI. If the credentials had not been changed, the domain was left in an inconsistent state.

5.5.0 1-7FZOHD A secondary administration server could not be started from the TIBCO Administrator GUI when logged into the primary administration server.

Closed in Release



64 | Release Notes

5.5.0 1-7H43AD The status and uptime for a secondary administration server running on AIX was not displayed when viewed from the primary administrator server in the TIBCO Administrator GUI.

5.5.0 1-7DURZQ The TIBCO BusinessWorks Render XML activity would fail if the encoding was set to UTF-16.

5.5.0 1-6MVDDD CorpUserSynchronizer would fail when running against an administration domain configured to use Microsoft Active Directory that has a large number of users (for example, 100,000). To run CorpUserSynchronizer you may need to temporarily relax the server side search limit on the LDAP directory server. This is likely required when using Active Directory where the default search limit is 1000. See Searching and Active Directory Server in the TIBCO Administrator User’s Guide for details.

5.4.2 1-77LSXZ Unable to insert certain sized BLOB data into a DB2 table with the 3.5 JDBC driver.

5.4.2 1-788751 After upgrading from TIBCO PortalBuilder 5.1 to PortalBuilder 5.2 and using TIBCO Administrator to upload a PortalBuilder 5.2 EAR file, the upload would fail.

5.4.2 1-78DDVJ On AIX platforms, an HTTPS-enabled TIBCO Administrator administration server could not start.

5.4.2 1-78QKEO When upgrading TIBCO BusinessFactor, services added in a new archive were not added correctly. This caused a failure when deploying an application.

5.4.1 1-6U19NL The following message would appear when starting certain TIBCO components:

log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester).

The log4j logging mechanism is included in some components that are bundled with TIBCO Runtime Agent, but is not used. A default configuration for the unused log4j logging mechanism is now provided and the message no longer appears when starting these components.

Closed in Release



Closed Issues | 65

5.4.1 1-62CUHU When attempting to start the RepoDeleteInstance utility on Unix, the utility would fail with the following error.:

./RepoDeleteInstance: %TIBCO_TRA_HOME%/bin/repository: not found

5.4.1 1-70AF3N The java.property.logFile property allows you to change the location of the TIBCO Domain Utility log file. The property is now available on Unix platforms.

5.4.1 1-717DRV Database connections were not restored with the Oracle database server. As a result, the TIBCO Administrator GUI would display error messages about the database server not being available in some circumstances, such as listing users.

5.4.1 1-758YTN Errors resulted when executing a DB2 V8.1 stored procedure using the tibcosoftwareinc.jdbc.db2.DB2Driver driver. An exception similar to the following appeared.

<msg>"JDBC error reported: (SQLState = HY000) - java.sql.SQLException: [tibcosoftwareinc][DB2 JDBC Driver]Transliteration failed, reason: invalid UTF8 data"</msg> <msgCode>BW-JDBC-100014</msgCode> <sqlState>HY000</sqlState> <detailStr>java.sql.SQLException: [tibcosoftwareinc][DB2 JDBC Driver]Transliteration failed, reason: invalid UTF8 data</detailStr> </ns1:JDBCSQLException>

5.4.1 1-75EKKF When a new TIBCO administration domain is created, a Hawk Agent configuration file is generated in the administration domain directory. The configuration file declares the environment variable "tibco.env.LD_LIBRARY_PATH" on Unix. However, the system environment variable LD_LIBRARY_PATH was not appended.

This error affected web applications in the case where Hawk Agent started a web server (such as after a deployment). Symptoms included a failure to load application utilities due to missing libraries.

5.4.1 1-75HG1F The role path used by TIBCO PortalBuilder portal communities was not created correctly by TIBCO Runtime Agent components.

5.4.1 1-75UN9H When a TIBCO PortalBuilder application used cookie authentication, cookies for the domain were set incorrectly.

Closed in Release



66 | Release Notes

5.4.1 1-7681CT Single sign-on between TIBCO PortalBuilder 4.5.x and PortalBuilder 5.1 on cookie authenticated portals did not work correctly with web servers, such as Apache Tomcat 5.0, where embedded quotes in the cookie value were stripped off by the web server.

5.4.1 1-76CU51 Servlet engine registration would fail when running TIBCO Domain Utility in command line mode.

5.4.1 1-6X3M8J Deployment would fail if the deployment application name contained a dot (.).

5.4.1 1-739O92 In TIBCO Designer, importing two adapter configurations one after the other, would delete public scalars in the first imported adapter configuration. An error similar to the following would appear.

Schema error: unable to resolve reference to type "char.10" in namespace http://www.tibco.com/xmlns/ae2xsd/2002/05/ae/scalar/ae

To enable this fix, you must add the following property to the designer.tra file:

java.property.com.tibco.xml.schema.parse.ae.AE_CUSTOM_SCALARS=true

5.4.1 1-75XFEHH The TIBCOtsm.jar file required changes to support deployment changes for the TIBCO BusinessWorks Collaborator release 5.3.0.

5.4.1 1-74KU6M When using local as the deployment transport, if a global variable value included a space character, an error similar to the following would appear.

org.xml.sax.SAXException: fatal error at line 31, column 95, expected character (found """) (expected ";")at com.tibco.repo.RepoXMLLoader.fatalError(RepoXMLLoader.java:575) ...

5.4.0 1-6Z6UY5 When using the MigrateDomainStorage utility to migrate a file-based domain data to a database, migration would fail.

5.4.0 1-6CLBV5 After restarting the administration server, status for the TIBCO Enterprise Message Service server would display as unknown in the TIBCO Administrator GUI.

Closed in Release



Closed Issues | 67

5.4.0 1-6XMLDC The ExportDomainSecurity utility would fail when run against a large authorization domain.

5.4.0 1-71EXLF If a client machine was joined to the administration server machine using the remote Rendezvous daemon running on the server machine, AppManage -moveAppData would fail to deploy an application if it was being used to move the data storage from local to rv, and some services were deployed on the client machine.

5.4.0 1-71JK09 When the AppManage -export -ear <archive file> -out <Deployment Configuration file> command was used before creating a domain on a machine, a java.io.FileNotFoundException was thrown and the XML file was not generated.

5.4.0 1-6OV4WJ When an IBM DB2 database was used as the source of a database portlet item, the following error message could appear in the log file portal-home/logs/servlet-container/portal.log:

java.sql.SQLException: [tibcosoftwareinc][DB2 JDBC Driver][DB2]UserName.SYSUSERS IS AN UNDEFINED NAME

And you could not successfully create the portlet item.

5.4.0 1-6QCLZL The global variable DirTrace value is used to set the Engine.Log.Dir property for the BusinessWorks Engine. If this value was modified in TIBCO Designer, but not during deployment, the Engine.Log.Dir property would get the default value rather than the modified value.

5.4.0 1-6Q55AJ In a domain where the Strong Password Policy is enforced, a user is forced to change his or her password on first log-in into the TIBCO Administrator GUI. However, if the user uses an AppManage command, the message warning the user to change the password was hidden in the stack trace. This has been fixed such that the error message is visible to the user.

5.4.0 1-2556XM Runtime exceptions thrown from customer’s code would make the portal unusable. This has been fixed such that any unknown runtime exceptions from role plug-ins are now caught internally and logged and not propagated further.

Genuine runtime exceptions (RoleMembershipRuntimeException) are still thrown since applications need to know about them.

Closed in Release



68 | Release Notes

5.4.0 1-1B97WL Service level global variables at the individual engine level could not be overridden in case where the same process was deployed on multiple engines as part of a load balanced group. See the TIBCO Runtime Agent Scripting Deployment User’s Guide for details.

5.4.0 1-6J747D Local repository dat files were not cleaned up when the application’s transport was switched from local to remote (rv or https) and then redeployed.

5.4.0 1-6NJASY In case of Custom Authentication, the init() method of the plug-in was not called.

5.4.0 1-6ZVUY5 If the TIBCO Rendezvous parameters for a domain were defined using an alias, a user authentication error would occur when modifying the Super User password using TIBCO Domain Utility.

5.4.0 1-6WQR1I The Repo.logFileMaxNumber setting in tibcoadmin_<domain>.tra had no effect.

5.4.0 1-6Z04Z0 Appmanage -deploy and -undeploy would take an excessive amount of time to complete.

A new "-serialize" option has been added to AppManage that allows you to explicitly choose to serialize deployment. Once it is run once, all deployments for that application will continue to be serialized.

5.4.0 1-700G0W An incorrect instance name for the deployed application was created when the transport was changed from local to rv in a domain created as a local transport. This resulted in overwriting an application repository .dat file, if the same ear file was deployed as a different application.

5.4.0 1-6NBNX5 When using TIBCO Domain Utility to create a domain with Show Advanced selected, you can set a non default location for TRA Domain Home and Administration Domain Home. If you set a non default location by typing a pathname, and used backslashes (even on Windows platforms) deployed applications would not start.

Closed in Release



Closed Issues | 69

5.4.0 1-6OZS34 After migrating an administration domain to use TIBCO Runtime Agent 5.3, you had to reload the applications into the domain if you wanted to enable them to use the local deployment option. You can now use the -batchMoveAppData option to change transport settings in batch mode. See the TIBCO Runtime Agent Scripting Deployment User’s Guide for details.

5.3.3 1-7URNO5 The TIBCO BusinessWorks Parse XML activity did not release the memory after the job completed.

5.3.3 1-7URNPX Installation packages for all supported platforms now include the latest JRE 1.4.2 builds that include Daylight Saving Time patches for U. S. time zones for 2007.

5.3.3 1-6MNSY3 Suspending and activating a TIBCO Adapter SDK listener configured for a JMS topic would cause the adapter to crash.

5.3.3 1-7BSX6L On UNIX, the adapter crashes when a SDK listener configured for JMS queue is suspended and restarted. This has been fixed

5.3.3 1-7BSX71 When you send a few thousand messages to the RPC server in a C++ SDK based multithreaded adapter, the adapter hosting the RPC client crashes with a core dump. This happens in both synchronous and asynchronous scenarios of the RPC service.

5.3.3 1-716XYM An attempt to invoke a DB2 stored procedure on a DB2 database residing on an OS390 machine resulted in an error.

5.3.3 1-6ZVAGN The dat file generated by TIBCO Administrator at deployment for TIBCO Adapter for EJB did not include the correct administrator server settings.

5.3.3 1-712HUA TIBCO Designer 5.3 (and later) was slow and would sometimes hang when a large number of TIBCO BusinessWorks process definitions or adapter configurations (200+) were defined

• and you saved using File Sharing (especially in a mapped folder of a remote machine) or in CVS.

• while loading the project using File Sharing or the CVS option.

5.3.3 1-6X3ZAA Locally deployed .DAT files with Adapter archives did not contain the <instanceInfoProperty name="encoding"> property.

Closed in Release



70 | Release Notes

5.3.3 1-6Z4BSI When undeploying and redeploying an application, the check point table name would change for TIBCO BusinessWorks 5.1.3 and the old table would still exist in the database, but there was no way to edit it.

5.3.2 1-6MEVPH The 64 bit Xerces library was missing on Solaris.

5.3.2 1-5ZTRDK When a TIBCO BusinessWorks Collaborator archive was loaded and deployed, deployment would fail if the transport was set to local.

5.3.2 1-6B2E3I When using CVS, a folder rename in TIBCO Designer had no effect with the CVS server repository.

5.3.2 1-6MEVPH The 64 bit Xerces library was missing on Solaris.

Closed in Release



Closed Issues | 71

5.3.2 1-6O5W45 The CorpRoleSynchronizer utility and TIBCO Administrator would throw an Out of Memory error for an administration domain that was integrated with a corporate LDAP that contains a large number of groups.

When using the utility, on each machine where TIBCO Administrator is installed, modify the heap size as follows in the tibcoadmin_<DOMAIN_NAME>.tra file. This file is found under the <TIBCO_HOME>/administrator/domain/<DOMAIN_NAME>/bin folder.

java.heap.size.max=1024m

Additional Recommendations

For an administration domain that is integrated with a corporate LDAP and synchronizes with more than 5000 groups, in addition to performing the above, it is also recommended to do the following:

• Run CorpRoleSynchronizer before you start TIBCO Administrator for the first time. (Refer to the TIBCO Administrator Server Configuration Guide for information about running this utility). This ensures that the lengthy process of initial role synchronization is completed up front and Administrator is not penalized to take that load.

• In addition, avoid allowing TIBCO Administrator to automatically create roles for corporate groups and thus completely stop it from performing role synchronization. This can be done by setting the flag OFF for "Automatically create Roles for each Corporate Group" in the LDAP Settings for the administration domain (refer to the TIBCO Runtime Agent Domain Utility User’s Guide). In this case, you will need to set up the CorpRoleSynchronizer utility to run independently at periodic intervals on one of the machines.

5.3.2 1-6OEHFP Cookie authentication logout was not invalidating the session. This caused unpredictable behavior in TIBCO PortalBuilder.

5.3.2 1-6QTK5P The <xs:whiteSpace value = "collapse"/> element was broken in the validator.

5.3.2 1-6S4T3G XML file validation would fail for decimal value .00.

Closed in Release



72 | Release Notes

5.3.2 1-6S5E6H Performance was slow when using XPath step expressions with large documents.

5.3.2 1-6SV3KT Creating a new XML schema or WSDL in a project that already had schemas would fail.

5.3.2 1-6SV74L Secured properties with non latin-1 characters did not work for TIBCO PortalBuilder due to a problem in decrypting the encrypted values in the underlying library.

5.3.2 1-6U9TYK When an application was deployed to a machine with TIBCO Runtime Agent 5.3.0 installed and "local" was selected for the transport, global variables of Integer type became Boolean type.

5.3.2 1-6UKC77 In TIBCO Administrator, creating a new role when many roles already existed was very slow.

5.3.2 1-6UWZ2B A classcast exception would be thrown after using the ImportDomainSecurity utility with overwrite (in versions 5.2 or 5.3). Also, 5.1.3 clients could not use a domain that had roles imported with 5.2 or 5.3 because the standard role membership configuration class didn't exist in 5.1.

5.3.2 1-6V4UWX A java.net.ConnectException would appear in the log when creating a domain using the domain utility command line tool on any machine that did not have Internet connectivity.

Closed in Release



Closed Issues | 73

5.3.2 1-6W5K0X If the repository type for application repositories was set to "BIN" (binary) in the administrator_domain.tra file, some applications were unable to start after an Administrator server restart.

Complete the following to apply the fix to existing applications. After installing TIBCO Runtime Agent 5.3.2:

1. Use the AppManage –batchExport command to export all the existing applications in the domain to a directory in the file system.

2. Use AppManage –batchUndeploy to undeploy all the applications. Alternatively, go to the All Applications screen on the Administrator GUI and select all the applications and undeploy them.

3. Use AppManage –batchDelete to delete all the applications. Alternatively, go to the All Applications screen on the Administrator GUI and select all the applications and delete them.

4. Shut down the Administrator server.

5. Go to the <TIBCO_HOME>/administrator/domain/<DOMAIN_NAME>/data folder and delete all the application .dat files and .dat.files folders. Caution: Be very careful, not to accidentally delete the SYS_<DOMAIN_NAME>.dat and the AUTH_<DOMAIN_NAME>.dat files, as these are the domain data stores. Administrator will not work if these files are deleted.

6. Restart the Administrator server.

7. Use AppManage –batchDeploy to deploy all the applications in a batch.

5.3.2 1-6W5K20 If TIBCO Administrator crashed during deployment, and the deployment was partially complete, the application could get to a state where it could not be undeployed or deleted. The All Applications console would throw a NullPointerException and the domain would also get into an inconsistent state.

5.3.1 1-6LURF9 Using the AppManage utility, a user assigned read-only access to an application could start and stop an application even though write access is required for this privilege.

Closed in Release



74 | Release Notes

5.3.1 1-6NBBKP When using TIBCO Domain Utility to create an administration domain you could specify that a restrictive policy be used for the domain. Similarly, when using the TIBCO Administrator GUI to manage the password policy, you could modify the StrongPolicy.xml file and load it into the domain. The following features in the restrictive policy and StrongPolicy.xml file were not available. They were commented out in the StrongPolicy.xml file:

• 

• 

As a result, users were not forced to change their password on first login and passwords did not expire.

5.3.1 1-6NH7R9 The conversion from an incoming message to an XI node would sometimes return empty.

5.3.1 1-6NJWOF Users that did not exist in an administration domain (such as TIBCO PortalBuilder portal's administration domain) could not log into applications protected by a custom authentication plug-in.

5.3.1 1-6OEC6J The WSDLBuilder did not handle AESchema that referred to other AeSchema correctly. If the WSDLBuilder used an AESchema that imported other AESchema, the generated WSDL did not embed the imported AESchema correctly.

5.3.1 1-6OFDQA When adding a DTD to the TNS cache and validating, a fatal error would occur, stating the stream was closed.

5.3.1 1-6OOWRH Permissions did not work on roles with dynamic membership.

Closed in Release



Closed Issues | 75

5.3.1 1-5I2LMH On Microsoft Windows, after starting the TIBCO Hawk Agent and administration server services and then logging out of the machine, the tibhawkhma.exe service would terminate.

Because the tibhawkhma.exe service is directed as an interactive application, it catches the system LOGOFF event and exits. To instruct the tibhawkhma.exe service to run as non-interactive, the following property in the hawkagent_<domain-name>.tra file must be set:

java.property.hma.extended=--nonInteractive

This property is supported only in TIBCO Hawk 4.6. If TIBCO Runtime Agent 5.3 is run with Hawk 4.5.x, the property should be removed from the hawkagent_<domain-name>.tra file before starting the Hawk Agent. In this case, a new tibhawkhma.exe service will be spawned when you have logged back into the system.

5.3.0 1-3S82RD On HP Itanium platforms, when migrating from TIBCO Runtime Agent 5.1.3 to TIBCO Runtime Agent 5.2.0, by default, the installer did not upgrade TIBCO Rendezvous. But, because the existing TIBCO Rendezvous version did not have the latest OpenSSL libraries packaged, you had to perform a custom installation by selecting TIBCO Rendezvous so it would be re-installed with the OpenSSL libraries.

5.3.0 1-6GABD5 The TIBCOadaptermappers.jar file has been updated with the latest adcom.xsd file.

5.3.0 1-4ZX52C When using TIBCO Domain Utility to set or change TIBCO Rendezvous parameters used by TIBCO Hawk, an alias could not be used for the service parameter.

5.3.0 1-60ZWVL When using the JMS transport and a UTF-8 repository, a deserialization error would occur if certain fields were empty.

5.3.0 1-4RIZP3 The validator would report an error if nested sequences were in a content model, even though the XML was valid.

5.3.0 1-5KH9DH When configuring a Publish Rendezvous Message activity with the Content specified as "Any Element" and the Validation to "Skip", a NullPointerException resulted.

5.3.0 1-5LMCRL The logout action did not work correctly for Web Server Authentication and allowed an application to create a new Http session within the same browser session.

Closed in Release



76 | Release Notes

5.3.0 1-5RJMXP Deployment would fail on machines that were not connected to the Internet.

5.3.0 1-551CFE The adapter exited on startup on Windows XP with Service Pack 2. Windows popped up the error, "<adapter-app-name>.exe has encountered a problem and will be closed".

5.3.0 1-67ZWSM A close_notify alert sent by the Entrust server was not being acknowledged by client programs. This resulted in too many client sockets left open and the server running out of threads if a large number of requests were received.

5.3.0 1-3S82RD On HP Itanium platforms, when migrating from TIBCO Runtime Agent 5.1.3 to TIBCO Runtime Agent 5.2.0, by default, the installer did not upgrade TIBCO Rendezvous. But, because the existing TIBCO Rendezvous version did not have the latest OpenSSL libraries packaged, you had to perform a custom installation by selecting TIBCO Rendezvous so it would be re-installed with the OpenSSL libraries.

5.3.0 1-5EK536 The domain administration user’s password could be changed to null (no password) in the TIBCO Administrator GUI. Because a password is required for the domain administration user, changing it to null would cause it to become out of sync with the password set when TIBCO Domain Utility was used to create the domain, and you would be unable to restart the administration server.

5.3.0 1-5EOEGX After changing an LDAP based domain to point to a different LDAP server, restarting the administration server, and then clicking the Select LDAP Groups button from the Roles console in the TIBCO Administrator GUI, a java.lang.NullPointerException occurred.

5.3.0 1-5765ZX If an LDAP group was deleted from the LDAP directory server and you attempted to retrieve group membership for the deleted group (before TIBCO Administrator had synced with the LDAP directory), the message, "Can't connect to the LDAP server" displayed.

5.3.0 1-5FIDYI After changing an LDAP based domain to use a different base DN, restarting the administration server, and then clicking the Select LDAP Groups button from the Roles console in the TIBCO Administrator GUI, a java.lang.NullPointerException occurred.

Closed in Release



Closed Issues | 77

5.3.0 1-58OB06 For version 5.2.1, clicking the About button in the TIBCO Administrator GUI displayed the TIBCO Administrator version as 5.2.0_V35 instead of 5.2.1.

5.3.0 1-5B3FQ1 If you deployed applications using TIBCO BusinessWorks 5.2.0 and installed BusinessWorks 5.2.1, the software version was updated to 5.2.1 in all places except the service instance name, which displayed 5.2.0.

5.3.0 1-5AIDMD When using the AppManage -start command in a fault-tolerant domain where the primary administrator server was down, AppManage -start failed to start a service. An exception occurred irrespective of whether AppManage -start was run from the primary administrator server machine or the secondary administrator server machine.

5.3.0 1-56OJ4D After creating a repository-based domain and then running the MigrateDomainStorage utility to migrate the repository-based domain to an Oracle database domain, when accessing the All Services Console in the TIBCO Administrator GUI, a java.lang.NullPointerException occurred.

5.3.0 1-5723S1 When closing the TIBCO Administrator GUI (rather then logging out), after setting permissions in the User Management > Security console for an application, and then logging in again, permissions could not be set for the application. A locking error message displayed. The lock could not be broken from the Security console.

5.3.0 1-5C90KJ On Unix systems, the colon ":" path separator was not handled correctly when appending or prepending the classpath from the Prepend to Classpath and Append to Classpath fields (when editing a service instance under the Server Settings tab in the TIBCO Administrator GUI).

5.3.0 1-5GOB4X Some applications deployed with version 5.1 failed to start with version 5.2 because of an insufficient stack size. By default version 5.2 requires the stack size to be 256KB, but applications deployed with version 5.1 had the stack size set to 128KB.

5.3.0 1-2Z0OGJ The XML parser did not validate all mandatory elements and did not throw exceptions for missing elements.

Closed in Release



78 | Release Notes

5.3.0 1-2Z6I70 XML rendering created duplicate "xmlns ='' "" attributes on the same element.

5.3.0 1-5L0VXL When using the import utility to import local roles for an LDAP-based domain, the import would fail if the export file was created using the LDAP root base DN.

5.3.0 1-3RPPHY When using the import utility with the -overwrite flag, the utility failed to import when the group sync role was a member of a local role.

5.3.0 1-3RG7LV The export utility did not export intersection of role membership information correctly.

5.3.0 1-3RG7LH Users assigned super user permissions did not appear as super users when exported from one domain and imported to another.

5.3.0 1-3OZ5VX When using MoveMachine to move a client from one machine to another with the -doAdminUI option, a file not found exception resulted.

5.3.0 1-3DBF5T The "-agent_name" property in the hawkagent.cfg file was not set to the machine name entered by the user in TIBCO Domain Utility when creating a new domain.

5.3.0 1-3N202L When using TIBCO Domain Utility in command line mode and adding a JMS server a second time with the same machine name and port, no warning would display that the specified JMS server was already installed.

5.3.0 1-1L9B97 TIBCO Hawk Agent did not parse system uptime correctly.

5.3.0 1-1BMCO1 Multiple JMS Server instances with the same configuration (port, and configuration file) could be added to an administration domain. This resulted in an error when an instance started.

5.3.0 1-1BFXKL Removing and then re-adding a JMS server plug-in while the referred to tibjmsd was running resulted in a status as 'stopped' vs. 'running'. That is, the state was out of sync.

5.3.0 1-5JXE0P The MoveMachine utility did not update -agent_name <hostname> property in the hawkagent.cfg file. This caused the Hawk agent to not startup.

Closed in Release



Closed Issues | 79

5.2.1 1-4616TP When creating an administration domain with a virtual host name instead of an actual host name, the TIBCO Enterprise Message Service server could be added to the domain and TIBCO BusinessWorks processes and TIBCO adapters could be deployed in the domain. But TIBCO BusinessWorks Workflow components could not be added the domain.

5.2.1 1-4W8M4T TIBCO Hawk agent threw a java.lang.IllegalArgumentException: Field data is null exception on startup. As a result of this, the TIBCO Enterprise Message Service server was not added to the domain correctly using TIBCO Domain Utility. The status of the TIBCO Enterprise Message Service server and TIBCO BusinessWorks processes was also shown as "Unknown", due to the same reason.

5.2.1 1-3OFHH5 When initially deploying an application in a domain that used a database backend for storage, deployment would take an excessive amount of time.

5.2.1 1-3V4IK5 A server, such as a TIBCO Enterprise Message Server, could not be registered in TIBCO Domain Utility using the server's IP address.

5.2.1 1-42ADTL Authentication failed when TIBCO Runtime Agent was set up with the TIBCO Hawk Trusted security model enabled.

5.2.1 1-49NDHU When using appManage to change a non fault tolerant group to a fault tolerant group, the change failed.

5.2.1 1-4EMRYP The TIBCO Enterprise Management Advisor GUI would hang when attempting to add or delete legacy domains. This has been fixed

5.2.1 1-4EOEM1 When migrating from version 5.1 to 5.2, the migration would leave out a step required for TIBCO Enterprise Management Advisor and TIBCO BusinessFactor applications.

5.2.1 1-4FN6QD On Solaris, the TIBCO Hawk Agent would generate java.lang.ClassCastException messages every minute.

5.2.1 1-4HBD21 For TIBCO BusinessFactor, a local repository file could not be used.

5.2.1 1-4E9SHI A com.tibco.runtime.pool.ServerNotAvailableException exception was thrown indicating the database server was not available even though the database was up.

Closed in Release



80 | Release Notes

5.2.1 1-3YFN1Z If your domain had a Rendezvous network and the Hawk network parameters were different from Rendezvous, deployments would fail.

5.2.1 1-3PI974 When using a global variable as password type, changing the value during scripting deployment had no effect.

5.2.1 1-3ODVBN The sum() function threw an error message when the repeating node had a different datatype (one number and one decimal).

5.2.1 1-3Z4SAK A regular XSD expression restriction was not enforced at runtime.

5.2.1 1-4KIJI5 Xpath would throw errors when comments were included in Xpath expressions.

5.2.1 1-4MJEJA The TIBCO BusinessWorks Parse XML activity did not release the memory resulting in an OutOfMemoryError.

5.2.1 1-4RJN5 TIBCOadaptermappers.jar now includes the updated XSD file for TIBCO Adapter for MQSeries.

5.2.0 1-26G412 XML validation errors did not appear in the process stack trace.

5.2.0 1-2MD0MO A performance problem within the SOAP request-reply activity has been addressed. Performance slowed significantly as more threads were added.

5.2.0 1-2D4MPE The add-to-dateTime function returned erroneous results when the day parameter was greater than 24 regardless of the date passed in.

5.2.0 1-2DD3U0 The concat function would fail to convert to double when used similar to the following:

Double1 = concat(String1,".", String2)

where string1 ="1234"and string2 ="45"

5.2.0 1-251APQ A memory leak related the Java Method activity caused the TIBCO BusinessWorks engine to post an out of memory exception.

5.2.0 1-25TQI8 XML validation engine performance has been improved.

5.2.0 1-25Z3PV The mapper did not apply Nillable correctly to the optional XPath formula.

Closed in Release



Closed Issues | 81

5.2.0 1-1W5PQ7 The XML Transform activity, when output is in Binary mode, now honors the encoding specified in the stylesheet.

5.2.0 1-1UFJIX The XPath Formula Builder document() function does not throw a null pointer exception any more.

5.2.0 1-1VKTPQ When testing a process where an XML Render activity had no input specified, the "Unable to reparse source view error" resulted.

5.2.0 1-1WHO7I The float/double for the individual fields under the Headers field showed the correct notation when written to a file, but when the string function was used (for example, substring-after ("the Headers field"), the scientific notation (E0) displayed instead.

5.2.0 1-1X8N1R Running a transformation resulted in a java.lang.ArrayIndexOutOfBoundsException error when the number of attributes or namespaces exceeded eight.

5.2.0 1-1XHM7S If a zero-length string was mapped to an attribute in the mapper, the engine did not create the attribute as output. This was also a problem if the attribute (empty or not) was required.

5.2.0 1-1MHDRX An error occurred when using a Send HTTP Request activity that was configured to use SSL and the Identity type was Certificate/Private Key.

5.2.0 1-1R3T2Q When using HTTPS with proxy, the BW engine now works properly without throwing a 'NoRouteToHostException'.

5.2.0 1-1XXJ00 The ami_rvd_session for an existing 5.1.2 administration domain that used non-default TIBCO Rendezvous parameters was not set correctly.

5.2.0 1-1NKO45 If an application was deployed using the AppManage utility and viewed using TIBCO Administrator, sometimes the status displayed correctly as Success, but at other times displayed as Deployable (Last deploy failed).

5.2.0 1-25VJXL When using the AppManage -deploy command, if the deployment transport was specified as http in the deployment configuration file and a non-admin user was used to do the command-line deployment, an exception was thrown and the deployment was not successful.

Closed in Release



82 | Release Notes

5.2.0 1-22OJI1 A TIBCO Rendezvous license expiry warning displayed in the console when running the AppManage utility.

5.2.0 1-1WZFML For an adapter monitoring event, if a log event was configured for an adapter instance and the adapter instance used the default log file naming convention, the log event was not triggered. If the default was modified, the event worked correctly.

5.2.0 1-1Y8F3Q After upgrading to TIBCO Runtime Agent 5.1.3, any pre-5.0 C++ adapter that used the default discovery time (5 seconds) failed to deploy.

5.2.0 1-26DS76 When using the AppManage utility to do concurrent deployment in an administration domain that uses a database, some of the deployments failed because they could not find the repository server.

5.2.0 1-27ZMTL When the number of machines to which each service of an application was deployed crosses a threshold (5-6), deployment failed with an IllegalArgumentException in the case of a repository-based domain and an ArrayIndexOutOfBoundsException in the case of a database-based domain.

5.2.0 1-24SMFT When the AppManage -export -template option was used to generate a template deployment configuration file, the tags for empty fields were of the form <field/>, rather than <field></field>.

Closed in Release



Closed Issues | 83

5.2.0 1-2FA75G Some configuration settings in an existing deployment configuration file would get overwritten when a new deployment configuration file was created by exporting a newer version of the archive, using the following option:

AppManage -export -ear <new version of archive> -deployconfig <old deployment configuration file> -out <new deployment configuration file>

The configuration settings can include:

• NT Service settings

• Java settings

• Thread Count in the General settings for an existing service instance

• Product version and location information for a service to machine binding

• In the case where a process had been added to a existing process archive, the new process did not show up in the new deployment configuration file. Deploying the application with this deployment configuration file would keep the process specific settings such as MaxJobs and Activation Limit at their default values.

• In the case where a configured application contained a Service with a Log Event configured under its Monitoring tab and a value for the Match field, the exported deployment configuration file will have an empty tag for the Match field.

5.1.3 1-1N4PNK A self-signed certificate is now rejected if it is expired or if it is not present in the trusted store.

5.1.3 1-1JQFSI A message digest may now be extracted from a signed message that does not have authenticated attributes.

5.1.3 1-18MPAU The CSR Generated by TIBCO Crypto is now accepted by the Thawte CA Server.

5.1.3 1-1LGFT9 Checking a key from one security vendor against one from another vendor now works.

5.1.3 1-1MY8VJ1-1MY8UQ

Applications using TIBCO Runtime Agent now start, even if the installation path contains spaces.

Closed in Release



84 | Release Notes

5.1.3 1-1MVW6R The wrapper no longer changes ';' to ':' when setting environment variables on UNIX using "tibco.env".

If a ".tra" file uses ';' rather than ':' as a path separator on UNIX, then the file must be updated.

The wrapper now supports inclusion of "nested" .tra files using the key "tibco.include.tra." The file to be included must be an absolute path.

Example tibco.include.tra /path/to/file/to/include/file_to_include.tra

The path may include substitution variables.

Example

tibco.include.tra %TIBCO_HOME%/tra/5.1/file_to_include.tra

5.1.3 1-1ACGAC Adding an image resource of type JPEG now works.

5.1.2 1-1E9NJ5 , 8234

Illegal XML characters are now escaped using processing instructions <? tibco-char hex-val?>, so that Java and database data can be properly round-tripped through XML.

5.1.2 8089, 8186, 8188, 8216, 8217, 8218, 8220, 8243 8245, 8252, 8257, 7975, 8253

Internal defects have been fixed to support TIBCO BusinessWorks 5.1.2 Hotfix2.

• Fixed a problem where XML Schema output did not write out default values for elements

• In XML Schema—fragment of static namespace is rightly not added to the namespace cache as it cannot be picked by namespace. This fix inspects its internal fragments, which is still required.

• XML Schema <redefine> mechanism is now fully supported.

• XPath comparison fix—when an operand is a node, the XPath 1.0 rules are now followed, instead of using the Data Model XPath 2.0 comparison.

• Fixed a defect where XSLT StepExpr was not consolidating duplicate nodes.

• Fixed a runtime exception defect in XSLT top-level variable instructions.

Closed in Release



Closed Issues | 85

5.1.2 7844,8016, 8061,8131, 8146,8156, 8286,8292, 8293,8310, 8329,8334

• Back slashes in paths in import and include statements are now handled.

• Schemas including other schemas from the same directory sometimes caused the schema picker to show up. This is now fixed.

• Error alerts shown when editing a schema sometimes had the standard Java icon instead of the TIBCO Designer icon. This is now fixed.

• Fixed several typos in strings.

• TIBCO Designer no longer hangs while reopening a project with a schema selected.

5.1.2 1-18U76T Exporting a certificate in EXPORT_FORMAT_BASE64_ENCODED_X_509_WITH_NEWLINE format now works for Entrust on Solaris. Without this fix, a JMS SSL connection may fail with a message "unable to load trusted certificate number 1".

Closed in Release



86 | Release Notes

5.1.2 1-1DINOI TIBCO Enterprise for JMS 3.1.2 client libraries are included. TIBCO Enterprise for JMS 3.1.2 C client code fixes several memory leaks.

• Fixed a memory leak in the C client API associated with SSL.

• Fixed a memory leak in the C API function tibjmsMsg_CreateFromBytes().

• Fixed a timing defect associated with closing DUPS_OK sessions. Closing sessions caused the application to exit abruptly on rare occasions.

• Fixed a defect in the client library where queue browsers did not detect messages in the undelivered message queue.

• Fixed a memory leak associated with deleting temporary topics in the client library.

• Fixed a defect associated with the destination attributes sender_name and sender_name_enforced. When these properties were set, Java client receivers would throw an exception.

• Removed a dependency of the C client library on additional Solaris libraries (Solaris platforms only).

• Fixed a defect in the C client library associated with string properties of messages. If a client program received a message with string properties added another string property and sent the message again, then the send call would fail.

• Fixed a memory leak in the client library, associated with closing MsgRequestor objects.

Closed in Release



Known Issues | 87

Known Issues

The table in this section lists known issues in this release.

Change Request ID Summary/Workaround

1-AGVSZQ Summary AppManage fails for EMS SSL based domains.

Workaround Add the following line to the .tra file of AppManage, domainutility, domainutilitycmd, designer, and any new hawkagent_<domain>:

java.property.TIBCO_SECURITY_VENDOR=j2se.

Note that this will force AppManage on this machine to use j2se rather than entrust as the security vendor for all domains.

Alternatively, add the following line to the .tra files listed above: java.property.com.tibco.security.EntrustLast=true.

1-AFWVKD Summary After installing TIBCO Runtime Agent 5.6.2 on the AIX platform, buildlibrary.tra, validateproject.tra and buildear.tra still use JRE1.5:

tibco.env.LIBPATH %TPCL_HOME%/lib/httpclient_3.0:%CUSTOM_LIB_PATH%%PSP%%TRA_HOME%/hotfix/lib%PSP%%TRA_HOME%/lib%PSP%%TRA_HOME%/hotfix/icjava/6.2/lib%PSP%%TRA_HOME%/icjava/6.2/lib%PSP%%TPCL_HOME%/lib%PSP%%RV_HOME%/lib%PSP%%JVM_LIB_DIR%/%JVM_FLAVOR%%PSP%%JVM_LIB_DIR%:/tibco/infraqa/tibco/jre/1.5.0/bin/j9vm:%TPCL_HOME%/tomcat/5.5/compatible/lib:/tibco/infraqa/tibco/jre/1.6.0/lib/ppc.

Workaround This is benign behavior. No workaround is required. Alternatively, remove the line beginning tibco.env.LIBPATH from each of the 3 files.

1-AD4A1N Summary The Microsoft SQL Server JDBC Driver 2.0 fails when creating a domain when using JRE 1.6.

Workaround Add the following line to the .tra file of AppManage, domainutility, domainutilitycmd, designer, and any new hawkagent_<domain>:

java.property.TIBCO_SECURITY_VENDOR=j2se.

Note that this will force AppManage on this machine to use j2se rather than entrust as the security vendor for all domains.

Alternatively, add the following line to the .tra files listed above: java.property.com.tibco.security.EntrustLast=true.


88 | Release Notes

1-A7E59B Summary When installing TIBCO Runtime Agent 5.6.2 on the Windows platform, all tra files that should be upgraded to use JRE 1.6 via traUpgradeManager during installation are successfully updated except one tra file uninstall_admin.tra.

Workaround This is benign behavior. No workaround is required. Alternatively, manually change the reference from JRE 1.5 to 1.6.

1-A7JGXS Summary Updating tra files to use JRE 1.6.0 fails when installing the 64bit package TIB_tra-suite_5.6.2_hpux111_hppa_64.tar on the HP PA 11.23 HP 11iv2 platform.

Workaround On HP-UX, ensure that the environment variable SHLIB_PATH contains $TIBCO_HOME/jre/1.6.0/bin/hotspot/:$TIBCO_HOME/jre/1.6.0 before any TIBCO application is started. Manually run traUpgradeManager on terminal to upgrade tra files to use JRE 1.6.

1-AEZOSZ Summary During the TIBCO Runtime Agent 5.6.2 installation, the traUpgradeManager is run, which creates backup files for each tra file that is modified. However, in the case of CorpRoleSynchronizer.tra and traUpgradeManager.tra the backup file points to the new version of TIBCO Rendezvous and JRE. These backup files are not needed and both utilities will work correctly using JRE 1.6 and TIBCO Rendezvous 8.2.

Workaround To revert the two files to use TIBCO Rendezvous 1.5 and JRE 1.5, use traUpgradeManager from the command line. Specify the JRE 1.5 directory and the TIBCO Rendezvous 8.1 home directory rather than utilizing the -revert flag, which can be used for the other modified files.

1-9RDHBJ Summary TIBCO Runtime Agent 5.6.1 supports TIBCO Adapter SDK 5.4, but in the TIBCO Designer GUI, the TIBCO Adapter SDK version appears as 5.5.1.6_6 in the Runtime window.

Workaround None.



Known Issues | 89

1-9QZS5N Summary The EMS and SSL based domains with the FIPS mode fail to start the hawkagent service.

Workaround Update the hawkagent.cfg file from:...

-ssl_identity TIBCO_HOME/ems/bin/certs/client_identity.p12

#-ssl_private_key <file-name>

-ssl_password "#!zxga0q72wx3LZKuQnrnTWiZNO9FLf2UIcRSYLhtGAaA="

...

to ...

-ssl_identity TIBCO_HOME/ems/bin/certs/client_identity.p12

#-ssl_private_key <file-name>

-ssl_password "password"

...

Then restart the hawkagent service.



90 | Release Notes

1-9QRIVF Summary (AIX Only) Both the 32 and 64 bit platforms do not use the latest JRE 1.6 version.

Workaround On the 32 bit platforms, use the older JRE 1.6 version as follows:bash-3.00$ ./java -version

java version "1.6.0"

Java(TM) SE Runtime Environment (build pap3260-20071123_01)

IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20071121_15015 (JIT enabled)

J9VM - 20071121_015015_bHdSMR

JIT - r9_20071121_1330

GC - 20071031_AA)

JCL - 20071118_01

On the 64 bit platforms, change the value of the tibco.env.JVM_LIB_PATH variable to tibco.env.JVM_LIB_PATH = TIBCO_HOME/jre/1.5.0/lib/ppc64/j9vm/libjvm.so in the tra files that you are using and use the older JRE 1.6 version as follows:bash-3.00$ ./java -version

java version "1.6.0"

Java(TM) SE Runtime Environment (build pap6460-20071123_01)

IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460-20071121_15015 (JIT enabled)

J9VM - 20071121_015015_BHdSMr

JIT - r9_20071121_1330

GC - 20071031_AA)

JCL - 20071118_01

1-95P0BV Summary (UNIX Only) TIBCO Runtime Agent 5.6 cannot be installed to a folder that contains space in its name.

Workaround None.

1-95OPBC Summary (Windows Only) After installing TIBCO Runtime Agent 5.6 in a folder that contains spaces in its name, the traDBConfig utility fails to launch because the path to the traDBConfig utility cannot be found.

Workaround Manually run the traDBConfig utility.



Known Issues | 91

1-95YP6L Summary The buildear utility fails to start when TIBCO Runtime Agent 5.6 is not installed in the default location. That is because the buildear.tra file still refers to the default location: tibco.include.tra C:/tibco/designer/5.6/bin/designer.tra.

Workaround Change the default location to your installation location in the buildear.tra file.

1-9571OP Summary (Linux Only) After upgrading TIBCO Runtime Agent from 5.4 to 5.6, an exception similar to the following occurs when adding a TIBCO Enterprise Message Service server to a migrated or new domain.com.tibco.pof.entity.EntityStoreException: com.tibco.infra.repository.RepoSecuri tyException: Error authenticate user a com.tibco.infra.repository.OperationFail edException: Can not change encoding from UTF-8 to ISO8859-1 because of other existing connection with different encoding

atcom.tibco.pof.entitystore.tibrepo.TibRepoEntityStore.init(TibRepoEnti tyStore.java:359)...

atcom.tibco.pof.entitystore.tibrepo.TibRepoEntityStore.init(TibRepoEnti tyStore.java:339) ... 37 more

Workaround Open the TIBCO_HOME/tra/version/bin/domainutility.tra file, modify the variable tibco.class.path.extended.Change the directory /TIBCO_HOME/tibco/tibrv/lib to /TIBCO_HOME/tibco/tibrv/lib/tibrvj.jar.

1-95G4IT Summary In a TIBCO Runtime Agent 5.6.0 upgrade scenario with TIBCO BusinessFactor, deployment fails due to a missing entry in the hawkagent_<domain name>.tra file.

Workaround Manually add {TIBCO_HOME}/bf/<bf-version>/db/lib/classes14.jar to the tibco.class.path.extended property in the {TIBCO_HOME}/tra/domain/<domain-name>/hawkagent_<domain-name>.tra file. For example, for TIBCO BusinessFactor 5.3 installed in C:\tibco, the entry in bold font should be added to the tibco.class.path.extended property as follows:

tibco.class.path.extended=C\:/tibco/tra/5.6/hotfix/lib;C\:/tibco/bf/5.3/db/lib/classes14.jar;C\:/tibco/hawk/lib;...C\:/tibco/tpcl/5.6/tomcat/5.5/compatible/lib



92 | Release Notes

1-94X627 Summary If an application is deployed with TIBCO Runtime Agent 5.5 and then deployed with TIBCO Runtime Agent 5.6, the ehcache-1.1.jar and ehcache-1.3.0.jar files will be in the \Tomcat\shared\lib directory.

Workaround Delete the ehcache-1.1.jar file from the \Tomcat\shared\lib directory.

1-94ROZO Summary If an LDAP domain administrator user has Super User privileges, the user will not be deleted using the DeleteInvalidUser utility.

Workaround None.

1-944LKD Summary (Solaris (SPARC) Only) After installing TIBCO Runtime Agent 5.6, TIBCO Adapter projects using Enterprise Message Service as transport will not start up from TIBCO Designer and the error message "Code = AESDKC-0156, Category = JmsComm, Severity = errorRole, Description = Could not

open JMS shared library jms."displays.

Workaround Remove the libssl.so and libcrypto.so files from the TIBCO_HOME/sdk/version/lib and TIBCO_HOME/sdk/version/lib/64 directories.

1-9457DQ Summary When deleting a service for a database domain using the RepoDeleteInstance utility, the warning message "com.tibco.infra.repository.OperationFailedException: error sending instance management request: Failed in

deleteSecurityPolicyInstance" displays.

Workaround The warning can be safely ignored.

1-93332B Summary (AIX Only) After upgrading TIBCO Runtime Agent from 5.3 to 5.6, non migrated domains will not start up.

Workaround All the .tra files containing the classpath %TIBCO_HOME%/tibrv/lib or %RV_HOME%/lib need to be changed to point to a specific .jar file. You will need to choose either tibrvj.jar or tibrvjsd.jar to specify the file. On AIX with 64-bit installations, add tibrvj.jar at the end of the classpath . On AIX with 32-bit installations, add tibrvjsd.jar at the end of the classpath. See TIBCO Runtime Upgrading to 5.6 for details.



Known Issues | 93

1-93UGU3 Summary After upgrading TIBCO Runtime Agent from 5.4 or 5.5 to 5.6, the Status for the applications in a non migrated domain is UNKNOWN and machine statistics such as CPU and Memory Usage for a non migrated domain do not display inside the TIBCO Administrator GUI.

Workaround None.

1-93XSVP Summary (Windows Only) After upgrading TIBCO Runtime Agent from 5.3, 5.4, or 5.5 to 5.6, TIBCO Hawk agent in a non migrated domain will not start up and the error message "The ordinal 3879 could not be located in the dynamic link library LIBEAY32.dll." displays.

Workaround Delete the libeay32.dll and ssleay32.dll from the TIBCO_HOME/tpcl/versison/bin directory. The version is 5.3, 5.4, or 5.5,

1-931LH0 Summary (Windows Only) After installing TIBCO ActiveMatrix Adapter for Database 5.5 on top of TIBCO Runtime Agent 5.6, adbagent.exe will not start up.

Workaround Only keep the OpenSSL libraries (libeay32.dll and ssleay32.dll) in the TIBCO Rendezvous directory and remove them from the other TIBCO products directories such as TIBCO Hawk, Adapter SDK, and TPCL in the TIBCO Runtime Agent directory.

1-922R8X Summary (UNIX Only) After installing TIBCO Runtime Agent 5.6 on a machine where TIBCO Runtime Agent 5.4 or 5.3 has installed and an administrator server is running in the non migrated domains, the Domain Utility will fail to get the domain name of the current running administrator server when creating a domain using TIBCO Rendezvous as the transport type.

Workaround Open the TIBCO_HOME/administrator/domain/domain_name/bin/tibcoadmin_domain_name.tra file, modify the variable tibco.class.path.extended.Change the directory /TIBCO_HOME/tibco/tibrv/lib to /TIBCO_HOME/tibco/tibrv/lib/tibrvj.jar.

1-926WVB Summary TIBCO Runtime Agent 5.6 fails to install on a machine where a standalone TIBCO Rendezvous 8.1.0 and TIBCO Runtime Agent 5.5.4 have been installed and the error message "INTERNAL ERROR: Verification of TIBCO RV 8.1.1 installation failed. Version 8.1.1 does not match

with the version in the readme file at C:\tibco\tibrv" displays.

Workaround Upgrade TIBCO Rendezvous from 8.1.0 to 8.1.1 separately before installing TIBCO Runtime Agent 5.6.



94 | Release Notes

1-92X4KK Summary (HP-UX (PA-RISC) Only) After installing TIBCO Runtime Agent 5.6 with 64-bit package, launching Domain Utility, and clicking the Next button, the warning "could not initialize impl class com.installshield.wizard.platform.hpux.service.file.HpuxFileServ

iceImpl " displays in the console.

Workaround None

1-93L03S Summary TIBCO Rendezvous does not support OpenSSL on AIX and HP-UX platforms with the 64-bit TIBCO Runtime Agent 5.6.0 installation.

Workaround None

1-93AYKI Summary The C++ adapters using JMS do not start up on Solaris platforms with TIBCO Runtime Agent 5.6.0 installed.

Workaround Remove the libssl and libcrypto openssl libraries from the TIBCO_HOME/adapters/sdk/version/lib directory.



Known Issues | 95

1-930O5F Summary (UNIX Only) After registering TIBCO BusinessWorks Collaborator components to a domain, the TIBCOServers-Workflow_Server_Server_Name and TIBCOServers-Document_Repository_Server_Server_Name-9001 services will not start up.

Workaround If you installed 32-bit TIBCO Runtime Agent, change the JVM paths to 32-bit JVM paths in the TIBCOServers-Workflow_Server_Server_Name.tra and TIBCOServers-Document_Repository_Server_Server_Name-9001.tra files.

If you have installed 64-bit TIBCO Runtime Agent, follow these steps to fix the issue:

1. Change the JVM paths to the 64-bit JVM paths in the TIBCOServers-Workflow_Server_Server_Name.tra and TIBCOServers-Document_Repository_Server_Server_Name-9001.tra files.

2. Copy the TIBCO_HOME/tra/version/bin/wrap64 file to TIBCO_HOME/BWC/version/server/server_name/bin/ and rename wrap64 to IcTSMStartRepDaemon.

3. Copy the TIBCO_HOME/tra/version/bin/wrap64 file to the TIBCO_HOME/BWC/version/server/server_name/bin/ directory and rename wrap64 to IcTSMStartServer.

4. Modify the variable tibco.class.path.extended in the TIBCOServers-Workflow_Server_Server_Name.tra and TIBCOServers-Document_Repository_Server_Server_Name-9001.tra files.Change the directory TIBCO_HOME/tibrv/version/lib to TIBCO_HOME/tibrv/version/lib/tibrvj.jar.



96 | Release Notes

1-91R685 Summary (AIX Only) After upgrading TIBCO Runtime Agent from 5.5.2 to 5.6, the service instances in a domain can not start up.

Workaround Follow these steps:

1. Create a temporary directory, for example TIBCO_HOME/temp.

2. Navigate to TIBCO_HOME/tibrv/versison/lib and process the following commands:

mv tibrvj.jar tibrvnative.jar tibrvnativesd.jar TIBCO_HOME/tempmv TIBCO_HOME/temp/*.jar TIBCO_HOME/tibrv/versison/lib

3. Open the TIBCO_HOME/tra/domain/domain_name/application/application_name/service_instance.tra file and modify the variable tibco.env.STD_EXT_CP.Change the directory %RV_HOME%/lib to %RV_HOME%/lib/tibrvj.jar.

1-91RIPV Summary After upgrading TIBCO Runtime Agent and TIBCO Administrator from 5.5 to 5.6 on Solaris or AIX platforms, the applications deployed with version 5.5 or 5.6 fail to start up and the error message "java.lang.UnsatisfiedLinkError: Library not found: tibrvnativesd" displays.

Workaround Open the TIBCO_HOME/bw/version/bin/bwengine.tra file, modify the variable tibco.env.STD_EXT_CP.Change the directory %RV_HOME%/lib to %RV_HOME%/lib/tibrvj.jar. Then redeploy the applications.

1-940G27 Summary After upgrading TIBCO Runtime Agent from 5.4 to 5.6, the applications in the non migrated domains will not start up on Linux platforms.

Workaround Modify the tibco.class.path.extended variable by changing the directory /TIBCO_HOME/tibco/tibrv/lib to /TIBCO_HOME/tibco/tibrv/lib/tibrvj.jar in the tibcodomain_domain_name.tra, hawkagent_domain_name.tra, and AppManage.tra files.

1-848NJ1 Summary Disk Usage for a machine do not display correctly inside the TIBCO Administrator GUI on Linux platforms.

Workaround None.



Known Issues | 97

1-8SWHGP Summary TIBCO Runtime Agent 5.6 with 64-bit package can not be installed on top of an old 32-bit TIBCO Runtime Agent.

Workaround Upgrade the old 32-bit TIBCO Runtime Agent to 64-bit manually using instructions in TIBCO Runtime Agent Installation version 5.5 and install 64-bit TIBCO Runtime Agent 5.6.

1-8TMAXT Summary After installing TIBCO Runtime Agent 5.6 with 64-bit package, the TIBCO BusinessWorks service instances will not start up.

Workaround Follow these steps:

1. Copy TIBCO_HOME/tra/5.6/bin/wrap64 to TIBCO_HOME/bw/versison/bin, delete the bwengine file, and rename wrap64 to bwengine.

2. Change the 32-bit JVM path to 64-bit JVM path in the TIBCO_HOME/bw/versison/bin/bwengine.tra file.

3. Open the TIBCO_HOME/bw/versison/bin/bwengine.tra file and modify the tibco.env.STD_EXT_CP variable.Change the directory %RV_HOME%/lib to %RV_HOME%/lib/tibrvj.jar.

1-8Z133B Summary TIBCO Runtime Agent 5.5.4 Java components are compiled with JDK 1.5. This may have indirect issues with other Java version dependent software.

Workaround None.

1-8ZLV64 Summary (Linux Only) After installing TIBCO Runtime Agent 5.6 on top of TIBCO Runtime Agent 5.4, the applications in the non migrated domains will not start up.

Workaround The .tra file for the application that contains the classpath %TIBCO_HOME%/tibrv/lib or %RV_HOME%/lib needs to be changed to point to either tibrvj.jar or tibrvjsd.jar.



98 | Release Notes

1-8ZLV76 Summary After upgrading TIBCO Runtime Agent from 5.4 to 5.6, the TIBCO BusinessWorks, TIBCO Adapter for ActiveDatabase, and TIBCO Adapter for Files processes in the migrated domain will not start up on Linux and HP-UX platforms.

Workaround All the .tra files containing the classpath %TIBCO_HOME%/tibrv/lib or %RV_HOME%/lib need to be changed to point to a specific .jar file. You will need to choose either tibrvj.jar or tibrvjsd.jar to specify the file. On HP-UX with 64-bit installations, add tibrvj.jar at the end of the classpath . On Linux platforms with 64-bit and 32-bit installations, add tibrvjsd.jar at the end of the classpath. See TIBCO Runtime Upgrading to 5.6 for details.

1-8XLRMF Summary On AIX 64-bit operating systems, using 64-bit TIBCO Rendezvous over SSL is not supported.

Workaround Use 32-bit TIBCO Rendezvous.

1-8RRIMI Summary The aesend and Aelisten utilities fail to start up because of the missing xerces-c_2_1.dll file on Windows operating systems.

The aesend and Aelisten utilities fail to start up due to the missing libmaverick53.so file on UNIX operating systems.

Workaround None.

1-8QRAMV Summary (HP-UX 11i, v3 (PA-RISC) Only) TIBCO Rendezvous and TIBCO Hawk fail to uninstall because of the missing Tibuninstal.bin files under TIBCO_HOME/tibrv/version/_uninst and TIBCO_HOME/hawk/_uninst.

Workaround To uninstall TIBCO Rendezvous or TIBCO Hawk, navigate to the TIBCO_HOME/tibrv/version/_uninst or TIBCO_HOME/hawk/_uninst directory and process the following command:$ java -cp uninstaller.jar run

1-8RX3XZ Summary Some installers of TIBCO products such as TIBCO BusinessWorks, TIBCO Adapter for Files and so on fail to update the TIBCO_HOME/bw/version/bin/BuildLibrary.tra file with the classpath and palette path.

Workaround Open the TIBCO_HOME/bw/version/bin/BuildLibrary.tra file, update the variable tibco.env.CUSTOM_PALETTE_PATH according to the same variable in TIBCO_HOME/designer/version/bin/designer.tra.



Known Issues | 99

1-8ZLV4H Summary (Linux Only) After installing TIBCO Runtime Agent 5.6 on top of TIBCO Runtime Agent 5.4, you will fail to remove a TIBCO Enterprise Message Service Plug-in server from a migrated domain.

Workaround In the Encoding drop-down list, select UTF-8 when creating a domain.

1-8ZLV76 Summary After installing TIBCO Runtime Agent 5.6 on top of TIBCO Runtime Agent 5.4 on a 64 operation system, adding an Enterprise Message Service server to a domain will not start up.

Workaround Use 32-bit TIBCO Rendezvous.

1-8V8XJM Summary After installing TIBCO Runtime Agent 5.6 on top of TIBCO Runtime Agent 5.4 on a 64-bit operation system, an Enterprise Message Service server will not be added to a domain.

Workaround Use the domainutility.tra utility to add an Enterprise Message Service server to a domain.

1-8WCHYX Summary After installing TIBCO Runtime Agent 5.5.4 on top of TIBCO Runtime Agent 5.5.0 or 5.5.2 or installing TIBCO Runtime Agent 5.6, the TIBCO Adapter for ActiveDatabase applications will not start up if using HTTP to communicate with the administration server.

Workaround None.

1-75PJI7 Summary Tomcat server uses localhost name instead of virtual machine name when creating a TIBCO Administrator domain in a cluster environment. This causes a port conflict when two TIBCO Administrator servers running on the same physical node with the same http port number.

Workaround The localhost’s name used in the server.xml file must match the name of the sub-directory file under the tomcat/config/Catalina directory.



100 | Release Notes

1-8KWJMP Compatibility with TIBCO BusinessWorks, TIBCO Designer, TIBCO Hawk 4.7 and TIBCO Runtime Agent 5.5.x

When Rendezvous 8.x, TIBCO Hawk® 4.7 (or older), TIBCO Designer™ and TIBCO BusinessWorks ™ coexist on the same host computer, an OpenSSL version mismatch prevents correct operation of Rendezvous activities within BusinessWorks processes running in the Designer debugger.

Rendezvous 8.x transports require a newer version of OpenSSL, while Hawk 4.7 supplies an older version. Installing BusinessWorks modifies a directory path in designer.tra, causing Rendezvous transports to use the wrong version of OpenSSL.

Workaround

In the file designer.tra, modify the variable tibco.env.CUSTOM_PATH. Add the directory rv_8x_home/bin to the value of this path variable, ensuring that it precedes the directory tibco_home/hawk/bin.

1-8X91V9 Summary On AIX, client authentication is not supported in an EMS domain with SSL enabled.

Workaround None.

1-8A33V3 Summary When using Domain Utility, the error, The ordinal 3212 cannot be located in the dynamic link library libeay32.dll appears.

Workaround Only keep the OpenSSL libraries (libeay32.dll and ssleay32.dll) in the TIBCO Rendezvous directory and remove them from the other TIBCO products directories such as TIBCO Hawk, Adapter SDK, and TPCL in the TIBCO Runtime Agent directory.



Known Issues | 101

1-7X0T75 Summary A 64-bit AIX system running tibhawkhma is shown in TIBCO Administrator to be at 100% CPU utilization regardless of its actual CPU utilization.

Workaround Follow the instructions below to use tibhawkhma64 instead of tibhawkhma.

1. In TIBCO_HOME/hawk/bin, rename tibhawkhma (to tibhawkhma32, for example).

2. Rename tibhawkhma64 to tibhawkhma.

3. Apply the chown and chmod commands to tibhawkhma (formerly tibhawkhma64) according to the instructions in "Change TIBCO Hawk HMA Permission" in TIBCO Runtime Agent Installation.

4. Restart Hawk Agent.

1-82KRRM Summary After installation using the 64-bit installer, Hawk Agent did not spawn tibhawkhma64, but spawned tibhawkhma (the 32-bit microagent) instead.

Workaround In TIBCO_HOME/hawk/bin, rename tibhawkhma (to tibhawkhma32, for example); rename tibhawkhma64 to tibhawkhma; then restart Hawk Agent.

1-84MAHZ Summary TIBCO Installation Manager does not start on 11.23 U ia64

Workaround Start TIBCO Installation Manager manually by executing the following command in the command prompt.java -cp TIBCO_HOME/tra/5.5/lib/install/TIBCOInstallerUtility.jar:TIBCO_HOME/tpcl/5.5/lib/xmlParserAPIs.jar run -log \#

1-6PCC5L Summary When a database is taken down, but the database server is not actually stopped, the number of database connections grows while the database is unavailable, and those connections remain even after the database server becomes available again.

Workaround Increase the database re connection interval to a value that is higher than or equal to the time taken to close a connection. The re connection interval is set using the java.property.tibcoadmin.database.waitTimeoutInterval property in the administration server properties file.



102 | Release Notes

1-6OJOB9 Summary After registering the servlet engine for Weblogic clusters, the cluster name is not validated in Domain Utility.

Workaround None.

1-7MTQTD Summary On AIX 5.3 platforms, Tibuninstall.bin is not created in the _uninst directories for tra, designer, jre, and tpcl.

Workaround Uninstall tra, designer, jre or tpcl by changing directory to the corresponding product’s _uninst directory and running the following command:

java -cp uninstaller.jar run

1-7CHU1T Summary When Microsoft Active Directory 2003 is used as the LDAP server, it will thrown an exception if any query is written to return over 10,000 groups. This occurs when querying from the TIBCO Administrator GUI and CorpRoleSynchonizer.

Workaround Break the query into multiple sub queries each of which returns less than 10,000 groups.

1-7D3E78 Summary If TIBCO Runtime Agent 5.4 and Runtime Agent 5.5 are installed on the same machine, the following can occur.

When creating an administration domain using TIBCO Domain Utility that is installed with Runtime Agent 5.4, in the Administrator Configuration screen, the drop down list of TIBCO Administrator versions defaults to TIBCO Administrator 5.4. But TIBCO Administrator 5.4 is not supported for use with Runtime Agent 5.4. If you use the default, the following error will display:-- Error -- com.tibco.objectrepo.NotAllowedException: Illegal null parameterat com.tibco.objectrepo.object.ObjectProvider.getObject(ObjectProvider.java:227)....com.tibco.administrator.du.task.createdomain.CreateDomainTask.execute(CreateDomainTask.java:335)

Workaround Select TIBCO Administrator 5.3 from the Administrator Version field when creating a Runtime Agent 5.4 administration domain.

1-7PBYYZ Summary TIBCO BusinessFactor™ 5.2 (and earlier) Aggregator deployment fails in an administration domain that uses TIBCO Enterprise Message Service as the message transport.

Workaround None.



Known Issues | 103

1-77GC2G Summary TIBCO Administrator cannot reconnect to the database if the database is taken offline and then brought back online.

Note that this defect applies to taking the database offline and back online. If the tablespace is taken offline and brought back, that is handled correctly. Similarly, if the database is fully shutdown and restarted, that is also handled correctly. Note also that the Oracle Enterprise Manager web page that is used to take the database offline has a button labeled "shutdown" that actually takes the database offline.

Workaround Use Oracle Administration Assistant to select a database and choose "stop service" and then later choose "start service". TIBCO Administrator will then reconnect correctly.

If you take the individual tablespaces offline, TIBCO Administrator will then reconnect correctly.

If you shutdown the database and don't want to stop the service, then you must restart the TIBCO Administrator server.

1-3RFPXR Summary After installing TIBCO Runtime Agent 5.2 or 5.3 on a machine that has TIBCO Runtime Agent 5.1.x installed, the installer launches TIBCO Domain Utility to upgrade domains. However, the installer does not always launch TIBCO Domain Utility and does not always go to the Migration category.

Workaround Launch TIBCO Domain Utility from the command line. The utility is installed in the install-path\tibco\tra\5.5\bin folder. Choose the Migration category and click Upgrade Domains from 5.1 or 5.2 or 5.3 to 5.4.

1-751A0N Summary When installing TIBCO Runtime Agent on a Windows machine, if the Rendezvous daemon (rvd) is not shutdown prior to installation, the installer is not able to upgrade Rendezvous correctly, even after a system reboot. As a result TIBCO Administrator and TIBCO Hawk Agent will not start-up correctly.

Workaround Stop all TIBCO applications including the Rendezvous daemon and re-install TIBCO Runtime Agent 5.5. Select the Custom Install option and upgrade Rendezvous from 7.5.1 to 7.5.2.



104 | Release Notes

1-795OYR Summary On some AIX machines the TIBCO Runtime Agent installer does not create the Tibuninstall.bin file under the tra\5.5\_uninstall folder. As a result, Runtime Agent cannot be uninstalled using TIBCO Installation Manager.

Workaround Use the following command to uninstall Runtime Agent:

java -cp tibcohome\tra\5.5\_uninst\uninstaller.jar run

1-3A3B2H Summary When starting the TIBCO Hawk Agent, the microagent (tibhawkhma.exe) does not start if the administration domain is not upgraded to at least 5.2.

For example, a machine has TIBCO Runtime Agent 5.1 installed (with Hawk 4.2.1) and a Hawk Agent is running on the machine (hawkagent_domain.exe and tibhawkhma.exe). After upgrading to TIBCO Runtime Agent 5.2 (with Hawk 4.5.0), but not migrating the domain, when re-starting the Hawk Agent, the microagent (tibhawkhma.exe) does not start.

Workaround Open the TIBCO_TRA_DOMAIN_HOME\domain\hawkagent.cfg file and comment the following line:

# -log_dir "C:/tibco/tra/domain/domain/logs"

1-3OWQBV Summary If an export file created using the ExportDomainSecurity utility has two roles defined both as LDAP synchronized roles and local roles, the local role with the conflicting name doesn't get its membership set.

The problem occurs only when there are roles with the same path where one or more are LDAP synchronized roles and the other is a local role.

If the local role has at least one member role defined, the second message is logged, and the console displays an error.

If the local role doesn't have a role as a member, adding user members to the local role fails with the first message, but the second message does not display and is not flagged as an error.

Workaround None.



Known Issues | 105

1-6FJT1L Summary When using the buildear utility to create an archive file, the operation fails. An error message displays warning that certain product palettes are missing.

Workaround The product installer or the upgrade procedure for TIBCO Runtime Agent did not update the buildear.tra file. Open the designer.tra file and copy the values from the tibco.env.CUSTOM_CP_EXT and tibco.env.CUSTOM_PALETTE_PATH properties to the corresponding properties in the buildear.tra file.

1-6ZYAYD Summary If you have defined external variables using TIBCO Hawk Display and the external variables have trailing space characters, a "no valid data source" error will be generated by Hawk Display.

Workaround Remove the trailing spaces from each variable that has them.

1-7H28B3 Summary On Unix platforms, the unable to find tibrv.tkt in Path appears when starting TIBCO Hawk Agent and the administration server.

Workaround None. The message can be ignored.

1-7HWJKD Summary The files created by the generate_jars.xml ANT script are placed in the TIBCO_HOME/tra/dependency directory. If the same machine has two different versions of Runtime Agent running and servlets use different versions, they would conflict.

Workaround None.

1-7PBYZK Summary When using a TIBCO Enterprise Message Service based domain for deploying a TIBCO BusinessFactor project on a Sun One Web server, the BAM desktop does not display.

Workaround Add TIBCO_TRA_HOME/lib/TIBCOjms.jar to the JVM Path Settings->Classpath Suffix from Sun One Web Server Administrator. This change is reflected in the server.xml file of the Sun One Web Server .

Add TIBCO_TRA_HOME/lib/TIBCOjms.jar to Classpath in start.bat and shutdown .bat files in TIBCO_TRA_DOMAIN_HOME/domain-name/SunOne/bin

1-6VRS31 Summary When using ClearCase, after renaming a folder, the original folder is not deleted from the project. An error occurs when checking in the renamed folder. After closing and reopening the project, both the original folder and renamed folder exist in the project.

Workaround None.



106 | Release Notes

1-6QK23T Summary Occasionally warning messages similar to the following are written to the TIBCO Administrator or CorpRoleSynchronizer logs for an administration domain that is integrated with an LDAP directory server. The messages appear the first time Administrator or CorpRoleSynchronizer is run against a new administration domain. Warn [Role] AESDKJ-0000 [main] No Membership config defined for Role <name>.

Workaround These are harmless messages and will not affect the role synchronization process.

1-72BE7F Summary The deployment process fails when using TIBCO BusinessWorks FormBuilder. The process fails because it is unable to create a shared archive file. This occurs because the DUServletEngine.jar file is available both in the Runtime Agent lib directory and the FormBuilder lib directory.

Workaround Remove the DUServletEngine.jar file from the FormBuilder lib directory and use the CreatePlatformArchive utility (available in the FormBuilder bin directory) to create a shared archive file.

1-6EHEQF Summary On Unix systems if a service defined in the /etc/services file is not a numeric value, TIBCO Domain Utility prints an exception similar to the following in the console window and continues. The exception is harmless and can be ignored.Warn -- java.lang.NumberFormatException: For input string: "tibhawksvc". . . at java.lang.Thread.run(Thread.java:534)

Workaround None.

1-6LTX3G Summary When installing TIBCO Runtime Agent 5.2.0 or later on a machine that has Runtime Agent 5.1.3 installed, the Hawk Agents under 5.1.3 can not start HMA.

Workaround Comment out the -logdir and -rvd_session properties in the install-path/tibco/hawk/bin/hawkhma.cfg file.



Known Issues | 107

1-4KQBZ5 Summary On Windows 2003, for machines that do not have service pack 1 installed, the installer creates the vpd property files in the user’s home directory rather than c:\windows. Because Hawk Agent only searches for vpd property files under c:\windows, Hawk Agent cannot find the files and as a result, the administration domain is not updated with installed software.

Workaround Upgrade Windows 2003 with service pack 1 prior to installing TIBCO software. Or, use the following procedure after installation to copy the vpd files to c:\windows each time TIBCO software is installed.

1. After installing TIBCO software, change directory to the user’s home directory. For example:cd C:\Documents and Settings\<user-name>

2. Copy the vpd files to c:/windows. For example:copy vpd.* c:/windows

1-1OLB6D Summary Deleting a database-based domain when the database server is down takes a long time to complete.

Workaround None.

1-1U2ZU4 Summary The folder names in the installation path specified for TIBCO Runtime Agent should not contain spaces. TIBCO products cannot be deployed correctly from TIBCO Administrator if the TIBCO_HOME (established by the TIBCO Runtime Agent installation) contains spaces.

Workaround Reinstall TIBCO Runtime Agent using an installation path that does not contain spaces.



108 | Release Notes

1-5ZTRD7 Summary If TIBCO Runtime Agent 5.2 and TIBCO BusinessWorks Workflow 5.2 are installed on a cluster group node’s local drive, the workflow servers cannot be started or stopped from other nodes in the cluster group.

Workaround To workaround this issue:

1. From the first active cluster node, launch TIBCO Domain Utility and add the bundled servlet engine, workflow server, and document repository server to the domain.

2. Start TIBCO Hawk Agent from the first cluster node.

3. Move the cluster group to another cluster node.

4. From that cluster node, launch TIBCO Domain Utility and add only the bundled servlet engine with the same port as in step 1 to the domain again.

5. Stop TIBCO Hawk Agent

6. Remove the TIBCOServers.properties file from the $TIBCO_TRA_DOMAIN_HOME/$TIBCO_DOMAIN_NAME/startup directory

7. Restart TIBCO Hawk Agent.

1-5ZTRDP Summary Deployment fails if a domain is configured in a non standard location for TIBCO BusinessWorks Workflow 5.2 and it is installed in a cluster group.

Workaround None.

1-60Z4CR Summary A duplicate servlet container displays in the list of containers to be bound to a TIBCO BusinessWorks Workflow application when setting up a cluster.

Workaround None.

1-5XVR6K Summary When using TIBCO Adapter for Files in a Microsoft Windows cluster, the adapter will not start if it must access files in a directory that resides on a mapped network drive.

Workaround None.

1-5FIDY1 Summary For an LDAP based domain, after doing a manual sync or after an auto sync occurs, the administrator server log file displays the following incorrect value:"Elapsed time required in recaching of groups : [0] seconds "

Workaround None.



Known Issues | 109

1-SP2Z1 Summary On the HP-UX platform TIBCO application that use .tra files won't start and display the following error:/usr/lib/dld.sl: Can't open shared library: /tsi/ae/tools/JDK/1.3.1/h7_110/jre/lib/PA_RISC2.0/hotspot/libjvm.sl/usr/lib/dld.sl: No such file or directoryAbort(coredump)

Workaround On HP-UX, the environment variable SHLIB_PATH must contain $TIBCO_HOME/jre/1.5.0/hotspot:$TIBCO_HOME/jre/1.5.0 before the TIBCO application is started.

1-RM5U2 Summary C++ repository client applications do not provide information to the server that allows the server to validate the certificate if the client is using HTTPS for communication.

The client application is still able to authenticate itself to the server, and this authentication is enforced. Client-server communication works and will be encrypted. What is missing, is that the server can not verify that the client has an accepted certificate in addition to having the correct userid/password.

Workaround None.

1-L4VWS Summary SDK Installer: The TIBCO Runtime Agent SDK Suite installer does not upgrade the SDK components if installed over an existing TRA suite install. All components are marked as installed.

Workaround Choose the Custom Installation and ask for a Reinstallation of the "Runtime and SDK" component. This will reinstall TRA but with the SDK components.

1-K68WP Summary The TIBCO wrapper does not support multi-byte characters in command line arguments.

Workaround None.

1-2JW4IO Summary The buildear utility throws an exception if it is run over a telnet session, without setting the DISPLAY to the telnet client machine.

Workaround In the telnet window, type:

setenv DISPLAY <Telnet Client Machine>:0.0.

Then use the buildear utility. If the telnet session is from a Windows machine to a UNIX machine, you will need an X-Windows simulator on the Windows machine.



110 | Release Notes

1-6E44BH Summary When attempting a silent installation using a response file, the installation fails.

Workaround None.

1-6HJHXG Summary When creating an administration domain with Default Policy selected under Configure Password Policy and then specifying the administrator credentials without enough characters, a validation error appears with an incorrect message. The last two lines of the message should read:May contain current user ID: YesMay contain current password: Yes

Workaround None.

1-7C76WW Summary When using the ImportDomainSecurity utility to import ACLs into an administration domain, the Use intersection of role membership option (set in the TIBCO Administrator GUI) is ignored.

Workaround Use the TIBCO Administrator GUI to manually set the Use intersection of role membership option.

1-7E6RFR Summary When exporting from an administration domain integrated with an LDAP server and importing to a domain integrated with a different LDAP server, users from both LDAP directories appear, but when attempting to use a user from the non integrated LDAP server, the operation fails.

Workaround None.

1-7DRLZD Summary For an administration domain that uses TIBCO Enterprise Message Service as the message transport and is integrated with an LDAP server, LDAP groups do not display in the TIBCO Administrator GUI Roles console.

Workaround Restart the administration server and the LDAP groups will appear in the Roles console.

1-7P542L Summary When using TIBCO Domain Utility to add a machine to an administration domain that uses TIBCO Enterprise Message Service as the message transport and enabling SSL, after providing the SSL properties and clicking Next, Domain Utility freezes and is unable to continue.

Workaround Use TIBCO Domain Utility to add the machine to the domain with SSL disabled. Start Domain Utility and change the Enterprise Message Service properties to use SSL by selecting Server Setting > Change Transport Parameters.



Known Issues | 111

1-7GFBQN Summary On Microsoft Windows platforms, when the administration server is running as a service and the administration server is started from the command line, the administration server started from the command line runs as a secondary server. No message appears warning that the administration server is already running or that the server port is in use.

Workaround None.

1-638EB0 Summary TIBCO Runtime Agent installs a bundled TIBCO Hawk Agent. On Unix, even if TIBCO Enterprise Message Service has been installed before installing TIBCO Runtime Agent, if a standalone TIBCO Hawk package is not installed, EMS_ROOT=%TIBCO_EMS_HOME% in the startagent and tibhawkpassword shell scripts under TIBCO_HOME/hawk/bin are not substituted with the actual Enterprise Message Service home directory.

Workaround Edit the startagent and tibhawkpassword shell scripts with the actual Enterprise Message Service home directory.



112 | Release Notes

1-2G9JZ5 Summary When using the AppManage utility to create a new deployment configuration file and the only change to the archive is that a service inside the archive (adapter, process or formflow) has been renamed, all information pertaining to the configuration done on that service is lost in the new deployment configuration file.

For example, in the case where you have an archive file with an adapter or a process archive defined:

• You upload this archive in TIBCO Administrator and do some configuration changes on it, such as add additional machine bindings, change service level variable values, add monitoring configuration, modify service instance level settings, and so on.

• Next, you create a deployment configuration file by exporting the above application. Now you decide to change the name of the process or the adapter archive inside the enterprise archive. You then rebuild the enterprise archive.

• You then use the following command to generate a new deployment configuration file.

AppManage -export -ear new version of archive -deployconfig old deployconfig file -out new deployconfig file

Because one or more services have been renamed, the AppManage utility treats it as if a new service was added and an old service was removed. The utility has no way of knowing that an old service has been renamed. The new deployment configuration file will not have any of the configuration settings that had been done previously.

Workaround If you change the name of any service, manually modify the service name in the deployment configuration file, rather than using the AppManage utility to regenerate a deployment configuration file with the new service name.

1-26HQB9 Summary If using AppManage -deploy to deploy a large number of concurrent deployments (10 or more) on a domain that uses a database, the deployment fails.

Workaround Use AppManage -batchDeploy to deploy multiple applications in one operation.



Known Issues | 113

1-1AXM3B Summary Custom Hawk Methods sometimes do not show up in TIBCO Administrator.

TIBCO Adapter SDK requires that the property tibco.hawk.microagent.name be set to register custom hawk methods. TIBCO Administrator sets the property tibco.hawk.microagent.name when an adapter is deployed. If the property tibco.hawk.microagent.name is not set (the adapter is not deployed and the property is not set in the adapter .tra file), the observed behavior is that sometimes methods appear in the Hawk Display and other times they do not.

Workaround Deploy the adapter from TIBCO Administrator or set the property tibco.hawk.microagent.name in the adapter .tra file.

1-18UFUA Summary On Windows 2000 servers, the GUI for TIBCO Designer and Domain Utility will not launch if pcAnywhere (Symantec, Inc.) is running. In that case, processes can be seen as launched in Task Manager, but the application's GUI cannot be seen on the screen.

Solution Stop the pcAnywhere service. This is a fact of life, no fix is planned.

1-11RLN2 Summary TIBCO Runtime Agent may not be installed into a directory whose path contains double-byte characters, otherwise applications requiring Runtime Agent will not find Runtime Agent during installation.

Workaround None.

1-7HFJ6V Summary If you install TIBCO Runtime Agent on a machine as a non-root user, then change permissions on the directory where the software was installed, and attempt to install other software components on the same machine, the following error results:

"Failed to update /<dir>/tra/5.0/bin/schemas.xml. Error is Value

too large for defined data type"

Workaround Do not change permissions on the directory after the software is installed.

1-7HFJ97 Summary If a properties file is edited manually with some characters that cannot be directly represented in ISO 8859-1 character encoding, the file must be converted to ISO8859-1 encoding (for example, using Java's NATIVE2ASCII tool).

Workaround None.



114 | Release Notes

1-7HIRSO Summary File sharing violation normally occurs, if the user attempts to reinstall or uninstall the product, while the product or any of its Window services is running. The installer and uninstaller will display a Reboot Panel, if they encounter any file sharing violation. In such a case, user must select the option to reboot the system. This is because, those files that had file sharing violation are marked for delete on system reboot. If the user does not reboot the system and continues to do further installation or uninstallation, then this will result in some of the files especially jar files or dll files being deleted during the next system reboot.

Workaround Select the option to reboot the system, whenever the installer or uninstaller displays a Reboot Panel.

1-7HIRT6 Summary Sometimes the Uninstallation Summary Panel says 'Choose Finish to exit the Wizard', but only Next button is available. Selecting Next, will display the Reboot Panel. This happens only when the last panel is a Reboot Panel. The Reboot Panel is displayed, whenever the uninstaller detects a file sharing violation. You are strongly encouraged to select the Reboot option.

Workaround Select Next button and the uninstaller will display Reboot Panel.



Known Issues | 115

1-7HIRV7 Summary On HP-UX and AIX platforms, even though the correct version of TIBCO Runtime Agent version is already installed on the system, installation of a product that depends on TIBCO Runtime Agent may fail in the dependency resolution.

The TIBCO product installer maintains the registry information in the vpd.properties.tibco.systemName file. The value for systemName is determined by InetAddress.getLocalHost().getHostName(). However, the method getHostName(), returns different values based on the JRE versions used. For example, on AIX, JRE 1.3.1 returns only systemName, whereas JRE 1.4.0 returns systemName.domainName. Because of this, the installer is not able to load the correct registry file.

Workaround On Unix platforms, the installer registry file vpd.properties.tibco.systemName is located in the user's home directory.

Case 1: If the vpd.properties.tibco.systemName file exists:$ cd user's_home_directory$ ln -s vpd.properties.tibco.systemName

vpd.properties.tibco.systemName.domainName

For example:$ cd ~$ ln -s vpd.properties.tibco.upside vpd.properties.tibco.upside.tibco.com

where upside is systemName, and tibco.com is domainName

Case 2: If the vpd.properties.tibco.systemName.domainName file exists:$ cd user's_home_directory$ ln -s vpd.properties.tibco.systemName.domainName vpd.properties.tibco.systemName

For example:$ cd ~$ ln -s vpd.properties.tibco.upside.tibco.com vpd.properties.tibco.upside

where upside is systemName, and tibco.com is domainName.



116 | Appendix A Upgrading to Release 5.6 Compatibility Section Errata Pages

Appendix A Upgrading to Release 5.6 Compatibility Section Errata Pages

This appendix replaces the entire Compatibility section in Chapter 1, TIBCO Runtime Agent Upgrading to Release 5.6, July 2008.

Topics

• Compatibility on page 117


Compatibility | 117

Compatibility

The following architecture diagram shows dependencies for a few TIBCO products. Other TIBCO products depend on TIBCO Runtime Agent, but are not shown in the diagram. Note that this document does not address how to upgrade TIBCO BusinessWorks SmartMapper, TIBCO BusinessFactor, or TIBCO BusinessWorks Collaborator.

Software CompatibilityBackward compatible applications can exchange data with and use configurations of previous releases. Products dependent upon an application can continue to be used with a newer release of the application.

The following table shows the compatibility among TIBCO Administrator, TIBCO BusinessWorks, TIBCO Adapter, and TIBCO Runtime Agent on a specific machine. Yes indicates the releases are compatible. No indicates the releases are not compatible.

TIBCO Adapters

TIBCO Runtime Agent, TIBCO Designer

TIBCO PortalBuilder

TIBCO ActiveMatrix BusinessWorks

TIBCO BusinessW

orks Workflow

TIB

CO

A

dministrato

r

TIBCO Plug-ins

TIBCO Business

Factor

TIBCO Smart

Mapper

TIBCO Runtime Agent 5.3




TIBCO Administrator 5.3

Yes Yes No No


No No Yes No


118 | Appendix A Upgrading to Release 5.6 Compatibility Section Errata Pages

As shown in the table:

• TIBCO Administrator 5.3 requires TIBCO Runtime Agent 5.3, or 5.4. The installer enforces this requirement.

• TIBCO Administrator 5.4 requires TIBCO Runtime Agent 5.5. The installer enforces this requirement.

• TIBCO Administrator 5.6 requires TIBCO Runtime Agent 5.6. The installer enforces this requirement.

If administration domains already exist on a machine when you install TIBCO Runtime Agent 5.6, the TIBCO Hawk agents for these domains will continue to use existing 5.x code until you upgrade each domain use TIBCO Runtime Agent 5.6. The TIBCO Administrator 5.6 installer provides an option to upgrade the TIBCO Hawk agent to use TIBCO Runtime Agent 5.6 software for each domain.


No No No Yes

TIBCO BusinessWorks 5.1

Yes Yes Yes No


Yes Yes Yes No


Yes Yes Yes No


No No Yes Yes

TIBCO ActiveMatrix BusinessWorks 5.6

No No Yes, needs release 5.5.2 or later

Yes

TIBCO Adapter 5.x

Check the adapter’s documentation set for TIBCO Runtime Agent release requirements.






Compatibility | 119

JRE 1.6 is not compatible with all TIBCO products. Check specific TIBCO product’s documentation to verify JRE 1.6 compatibility.

Project and Domain Compatibility Forward compatible applications can exchange data with or use configuration information of newer versions of the application.

TIBCO Designer

TIBCO Designer 5.6 can open and edit projects saved by older versions of TIBCO Designer. After a project is saved by TIBCO Designer 5.6, you cannot re-open the 5.6 project with a release prior to TIBCO Designer 5.6.

TIBCO Administrator

You can use any TIBCO Administrator release to deploy applications created by any TIBCO Designer 5.x release.

• TIBCO Administrator 5.3, 5.4, or 5.6 can deploy and administer enterprise archives created in previous versions of TIBCO Administrator.

• TIBCO Administrator primary and secondary servers must be of the same release.

• TIBCO Runtime Agent 5.6 can be part of a domain where the TIBCO Administrator server is 5.3, 5.4, or 5.6.

• TIBCO Administrator 5.6 can communicate with a TIBCO Hawk Agent on another machine in the domain running TIBCO Runtime Agent 5.3, 5.4, 5.5, or 5.6.

An application configured using TIBCO Designer 5.x and deployed using previous versions of TIBCO Administrator can also be deployed using TIBCO Administrator 5.6. The domain on the client machine where the application is running can be, but does not need to be, upgraded to use TIBCO Runtime Agent 5.6. This is because TIBCO Administrator can administer domains consisting of different versions of TIBCO Runtime Agent.

TIBCO Runtime Agent

Projects that are created on different versions of TIBCO Runtime Agent can be deployed and administered by the same version of TIBCO Administrator.


120 | Appendix B traUpgradeManager Utility Errata

Appendix B traUpgradeManager Utility Errata

This appendix replaces the traUpgradeManager Utility section in Chapter 4 of the TIBCO Runtime Agent Installation documentation for Release 5.6.

Topics

• traUpgradeManager Utility, page 121


traUpgradeManager Utility | 121

traUpgradeManager Utility

The traUpgradeManager utility is used to update many elements of a TIBCO software environment:

• TIBCO products (such as TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, or TIBCO Runtime Agent)

• Deployed TIBCO ActiveMatrix BusinessWorks applications

• Domain infrastructure such as TIBCO Runtime Agent or TIBCO Administrator server

It is also used to change (both to newer and older versions):

• The TIBCO Rendezvous version

• The TIBCO Runtime Agent version. This includes updating references to TRA, JRE, and TPCL directories.

• The JRE version

Do not use the traUpgradeManager utility to upgrade a domain. See TIBCO Runtime Agent Upgrading to Release 5.6 for detailed instructions on upgrading a domain.

Also, make sure that you update the administration domain and the applications in the domain to use the same Rendezvous version.

SyntaxThe syntax for traUpgradeManager utility is :traUpgradeManager (-path a directory or file name) | -include include file [-exclude exclude file] [-traversion tra version number] [-rv rv version full path] [-jre jre home full path]) | -revert | -help

The values for the syntax are as follows.

Table 2 Values for traUpgradeManager Utility Syntax Parameters

Parameter Value

-path If a directory, do substitution for all the .tra files in this directory and all subdirectories within it; If a file name, do substitution for this file.

-include The location of a file containing one entry per line that each act as <path>.


122 | Appendix B traUpgradeManager Utility Errata

ExamplesFollowings are some examples of traUpgradeManager Utility syntax:

• To upgrade the TIBCO ActiveMatrix BusinessWorks 5.6 product to use JRE 1.6:

traUpgradeManager -path C:/tibco/bw/5.6 -jre C:/tibco/jre/1.6.0

• To upgrade all TIBCO products, all domains and all deployed applications to use JRE 1.6.0 and TIBCO Rendezvous 8.2:traUpgradeManager -path C:/tibco -jre C:/tibco/jre/1.6.0 –rv C:/tibco/tibrv/8.2

• To undo the last modification to the TIBCO ActiveMatrix BusinessWorks 5.6 product:traUpgradeManager -revert -path C:/tibco/bw/5.6

• To upgrade an individual file to use JRE 1.6:traUpgradeManager -path C:/tibco/tra/5.6/bin/DeleteInvalidUsers.tra -jre C:/tibco/jre/1.6.0

• To upgrade all TIBCO products except adapters to use JRE 1.6traUpgradeManager -path C:/tibco -jre C:/tibco/jre/1.6.0 –exclude c:/tmp/excludeList.txt

-exclude The location of a file containing one name per line which will be excluded from replacement. The name is either a directory name or a file name that resides in the location specified as the value for the -path option. Substitution will be excluded for specified file names and for all .tra files within the specified directory names and subdirectories within them.

-traversion tra version number (e.g., 5.6).

-rv The full path of rv version should be used.

-jre The location of a JRE to use. If not specified, it will use that associated with target TRA.

-revert Revert the latest substitution by removing the .tra file and rename the .bak file to replace it.

-help Print this help information, but take no action.

Table 2 Values for traUpgradeManager Utility Syntax Parameters

Parameter Value


traUpgradeManager Utility | 123

Contents of the exclude file for this example would be:

— adapter

— domain

• To upgrade TIBCO ActiveMatrix BusinessWorks 5.6 and TIBCO ActiveMatrix Adapter for File 5.6 to use JRE 1.6traUpgradeManager -path C:/tibco -jre C:/tibco/jre/1.6.0 –include c:/tmp/includeList.txt

Contents of the include file for this example would be:

— C:/tibco/bw/5.6

— C:/tibco/adapter/adfiles/5.6


124 | Appendix C License Files

Appendix C License Files

License files contain TIBCO Software Inc. End User License Agreement and Thire-Party Software License Agreements.

Topics

• TIBCO Software Inc. End User License Agreement on page 125

• Third-Party Software Notices, page 129

• Third-Party Software License Agreements, page 130


TIBCO Software Inc. End User License Agreement | 125

TIBCO Software Inc. End User License AgreementREAD THIS END USER LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED.

Upon your acceptance as indicated above, the following shall govern your use of the Software except to the extent all or any portion of the Software (a) is subject to a separate written agreement, or (b) is provided by a third party under the terms set forth in an Addenda at the end of this Agreement, in which case the terms of such addenda shall control over inconsistent terms with regard to such portion(s).

License Grant. The Software is the property of TIBCO or its licensors and is protected by copyright and other laws. While TIBCO continues to own the Software, TIBCO hereby grants to Customer a limited, non-transferable, non-exclusive, license to use the Number of Units set forth in the Ordering Document solely for Customer's internal business use.

License Term. The term of each license for the Software shall be either perpetual or on a term limited basis as set forth in the Ordering Document. If liceTIBCO Runtime Agent Release Notessed on a term limited basis, the term shall be for a period of three years commencing on the Purchase Date, and on expiration, Customer must cease using and return or destroy all copies of the Software.

Restrictions. Customer agrees not to (a) make more copies than the Number of Units (except for a reasonable number of copies for archival and disaster recovery purposes) or use any unlicensed versions of the Software; (b) provide access to the Software to anyone other than employees, contractors, or consultants under written contract with Customer agreeing to be bound by terms at least as protective of TIBCO as those in this End User License Agreement ("Authorized Users"); (c) sublicense, transfer, assign, distribute to any third party, pledge, lease, rent, or commercially share the Software or any of Customer's rights under this Agreement (for the purposes of the foregoing a change in control of Customer is deemed to be an assignment); (d) use the Software for purposes of providing a service bureau, including, without limitation, providing third-party hosting, or third-party application integration or application service provider-type services, or any similar services; (e) use the Software in connection with ultrahazardous activities, or any activity for which failure of the Software might result in death or serious bodily injury to Customer or a third party; or (f) directly or indirectly, in whole or in part, modify, translate, reverse engineer, decrypt, decompile, disassemble, make error corrections to, create derivative works based on, or otherwise attempt to discover the source code or underlying ideas or algorithms of the Software. Customer may engage in such conduct as is necessary to ensure the interoperability of the Software as required by law, provided that prior to commencing any decompilation or reverse engineering of any Software, Customer agrees to it shall observe strict obligations of confidentiality and provide TIBCO reasonable advance written notice and the opportunity to assist with and/or conduct such activity on Customer's behalf and at Customer's expense; and (g) notwithstanding the method of delivery of the Software, the scope of the licenses granted under this Agreement are limited to the Software as set forth in an Ordering Document.

Beta and Evaluation Licenses. Notwithstanding the foregoing, if the Software is being provided for demonstration, beta testing, or evaluation purposes, then Customer agrees (a) to use the Software solely for such purposes, (b) that the Software will not be used or

deployed in a production or development environment, and (c) that such use shall automatically terminate upon the earlier of thirty days from the date Customer receives the right to install the Software, or Customer's receipt of notice of termination from TIBCO.

Maintenance. Maintenance, if ordered, including first year and all subsequent years, is provided under the policies set forth in the Maintenance Program Guide in effect at the time Maintenance services are provided. The policies set forth in the Maintenance Program Guide, incorporated in this Agreement, are subject to change at TIBCO's discretion; however the level of Maintenance service provided by TIBCO will not be materially reduced during the period for which Maintenance fees have been paid by Customer. The current version of the Maintenance Program Guide can be accessed at http://www.tibco.com/services/support/default.jsp. To receive Maintenance, all Software must be properly licensed and annual Maintenance fees paid. TIBCO is not obligated to continue providing Maintenance if annual Maintenance fees have not been paid.

Services. Customer may request additional services ("Services") either in an Ordering Document, or by a separate mutually executed work order, statement of work or other work-request document incorporating the term of this End User License Agreement (each, a "Work Order"). Unless otherwise expressly agreed to in a Work Order, all Services and any work product therefrom shall be (a) performed on a time and materials basis, plus meals, lodging, travel, and other expenses reasonably incurred in connection therewith, (b) deemed accepted upon delivery, and (c) exclusively owned by TIBCO (except for Confidential Information of Customer), including all right, title and intellectual property or other right or interest therein. Each Work Order is intended to constitute an independent and distinct agreement of the parties, notwithstanding that each shall be construed to incorporate all applicable provisions of this End User License Agreement.

Limited Warranty. If Customer obtained the Software directly from TIBCO, then TIBCO warrants that for a period of thirty (30) days from the Purchase Date: (i) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (ii) the Software will substantially conform to its Documentation. This limited warranty extends only to the original Customer hereunder. Customer's sole and exclusive remedy and the entire liability of TIBCO and its licensors under this limited warranty will be, at TIBCO's option, repair, replacement, or refund of the Software and applicable Maintenance fees, in which event this End User License Agreement shall terminate upon refund thereof.

This warranty does not apply to any Software which (a) is licensed for beta, evaluation, testing or demonstration purposes for which TIBCO does not receive a license fee, (b) has been altered or modified, except by TIBCO, (c) has not been installed, operated, repaired, or maintained in accordance with instructions supplied by TIBCO, (d) has been subjected to abnormal physical or electrical stress, misuse, negligence, or accident, or (e) is used in violation of any other term of this End User License Agreement. Customer agrees to pay TIBCO for any Maintenance or Services provided by TIBCO related to a breach of the foregoing on a time, materials, travel, lodging and other reasonable expenses basis. If Customer obtained the Software from a TIBCO reseller or distributor, the terms of any warranty shall be as provided by such reseller or distributor, and TIBCO provides Customer no warranty with respect to such Software.

EXCEPT AS SPECIFIED IN THIS LIMITED WARRANTY, THE SOFTWARE, MAINTENANCE AND SERVICES ARE PROVIDED "AS IS", ALL EXPRESS OR IMPLIED CONDITIONS,


http://www.tibco.com/services/support/default.jsp

126 | TIBCO Software Inc. End User License Agreement

REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW. CERTAIN THIRD PARTY SOFTWARE MAY BE PROVIDED TO CUSTOMER ALONG WITH CERTAIN TIBCO SOFTWARE AS AN ACCOMMODATION TO CUSTOMER. THIS THIRD PARTY SOFTWARE IS PROVIDED "AS IS". CUSTOMER MAY CHOOSE NOT TO USE THIRD PARTY SOFTWARE PROVIDED AS AN ACCOMMODATION BY TIBCO. NO WARRANTY IS MADE REGARDING THE RESULTS OF ANY SOFTWARE, MAINTENANCE OR SERVICES OR THAT THE SOFTWARE WILL OPERATE WITHOUT ERRORS, PROBLEMS OR INTERRUPTIONS, OR THAT ERRORS OR BUGS IN THE SOFTWARE WILL BE CORRECTED, OR THAT THE SOFTWARE'S FUNCTIONALITY, MAINTENANCE OR SERVICES WILL MEET CUSTOMER'S REQUIREMENTS. NO TIBCO DEALER, DISTRIBUTOR, AGENT OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATIONS, EXTENSIONS OR ADDITIONS TO THIS WARRANTY.

Indemnity. If Customer obtained the Software from TIBCO directly, then TIBCO agrees at its own expense to defend or, at its option, to settle, any claim or action brought against Customer to the extent it is based on a claim that the unmodified Software infringes any patent issued by the United States, Canada, Australia, Japan, or any member of the European Union, or any copyright, or any trade secret of a third party; and TIBCO will indemnify and hold Customer harmless from and against any damages, costs and fees reasonably incurred (including reasonable attorneys' fees) that are attributable to such claim or action and which are assessed against Customer in a final judgment; provided that TIBCO is promptly notified in writing of such claim, TIBCO has the exclusive right to control such defense and/or settlement, and Customer shall provide reasonable assistance (at TIBCO's expense) in the defense thereof. In no event shall Customer settle any claim, action or proceeding without TIBCO's prior written approval. In the event of any such claim, litigation or threat thereof, TIBCO, at its sole option and expense, shall (a) procure for Customer the right to continue to use the Software or (b) replace or modify the Software with functionally equivalent software. If such settlement or modification is not commercially reasonable (in the reasonable opinion of TIBCO), TIBCO may cancel this End User License Agreement upon sixty days prior written notice to Customer, and refund to Customer the unamortized portion of the license fees paid to TIBCO by Customer based on a five-year straight-line depreciation. This Section states the entire liability of TIBCO with respect to the infringement of any intellectual property rights, and Customer hereby expressly waives any other liabilities or obligations of TIBCO with respect thereto. The foregoing indemnity shall not apply to the extent any infringement could have been avoided by use of the then-current release.

Limitation of Liability. EXCEPT AS PROVIDED UNDER INDEMNITY OR RESULTING FROM A BREACH OF CONFIDENTIALITY (THE "EXCLUDED MATTERS"), IN NO EVENT WILL EITHER PARTY OR TIBCO'S LICENSORS BE LIABLE FOR ANY LOST DATA, LOST REVENUE, LOST PROFITS, DAMAGE TO REPUTATION, BUSINESS INTERRUPTION, OR ANY OTHER INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, PUNITIVE, EXEMPLARY OR ANY SIMILAR TYPE DAMAGES ARISING OUT OF THIS AGREEMENT, THE USE OR THE INABILITY TO USE THE SOFTWARE, OR THE PROVISION OF ANY MAINTENANCE OR SERVICES, EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. EXCEPT FOR THE EXCLUDED MATTERS, IN NO EVENT SHALL A PARTY BE LIABLE TO THE OTHER, WHETHER IN CONTRACT, TORT (INCLUDING ACTIVE OR

PASSIVE NEGLIGENCE), BREACH OF WARRANTY, CLAIMS BY THIRD PARTIES OR OTHERWISE, EXCEED THE PRICE PAID BY CUSTOMER UNDER THE APPLICABLE ORDERING DOCUMENT.

THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF THE ABOVE-STATED REMEDY OR LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO CUSTOMER.

Confidentiality. "Confidential Information" means the terms of this End User License Agreement; all information marked by the disclosing party as proprietary or confidential; any provided software, related documentation or related performance test results derived by Customer; and any methods, concepts or processes utilized in provided software or related documentation. Confidential Information shall remain the sole property of the disclosing party and shall not be disclosed to any non-Authorized User of either TIBCO or Customer without the prior written consent of the disclosing party. If Confidential Information is communicated orally, such communication shall be confirmed as "Confidential" in writing within thirty days of such disclosure. The parties agree to protect the Confidential Information of the other in the same manner it protects the confidentiality of similar information and data of its own (and at all times exercising at least a reasonable degree of care). Except with respect to the Software, items will not be deemed Confidential Information if (i) available to the public other than by a breach of an agreement with TIBCO, (ii) rightfully received from a third party not in breach of any obligation of confidentiality, (iii) independently developed by one party without use of the Confidential Information of the other; (iv) known to the recipient at the time of disclosure (other than under a separate confidentiality obligation); or (v) produced in compliance with applicable law or court order, provided the other party is given reasonable notice of the same. Both parties agree to indemnify the other for any damages the other may sustain resulting from their unauthorized use and/or disclosure of the other's Confidential Information. Such damages shall include reasonable expenses incurred in seeking both legal and equitable remedies. To the extent required by law, at Customer's request, TIBCO shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of TIBCO's applicable fee. Customer agrees to observe obligations of confidentiality with respect to such information.

To the extent TIBCO is exposed to individual personal data owned or otherwise held by Customer during the provision of Services, which is subject to various data protection laws and/or regulations ("Protected Data"), TIBCO agrees to treat such Protected Data in accordance with the Customer Privacy and Security Statement set forth at http://www.tibco.com/customer_privacy_security_statement.jsp (the "Statement"). The policies and procedures set forth in the Statement as well as those set forth in the Data Protection Policy Statement at http://www.tibco.com/resources/data_protection_statement.pdf are in place to meet TIBCO's obligations for the protection, integrity and confidentiality of any Protected Data which exceed TIBCO's standard obligations to safeguard Confidential Information.

Export. Software, including technical data, is subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such regulations and agrees to obtain all necessary licenses to export, re-export, or import Software.

Government Use. If the Software, Maintenance or Services are being or have been acquired with U.S. Federal Government funds, or


http://www.tibco.com/customer_privacy_security_statement.jsp

http://www.tibco.com/resources/data_protection_statement.pdf

TIBCO Software Inc. End User License Agreement | 127

Customer is an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the Software, Maintenance or Services, or any related documentation of any kind, including technical data, or manuals, is restricted in accordance with Federal Acquisition Regulation 12.212 for civilian agencies and Defense Federal Acquisition Regulation Supplement 227.7202 for military agencies. The Software, Maintenance and Services are COMMERCIAL ITEMS AS DEFINED BY THE FEDERAL ACQUISITION REGULATION. Use of the Software, Maintenance and Services by the Government is further restricted according to the terms of this Agreement and any amendment hereto.

Orders. An Ordering Document means any purchase order, similar document or agreement requesting Software, Maintenance or Services, which shall be deemed accepted only by issuance of a TIBCO invoice and solely for purposes of administrative convenience. None of the terms of the Ordering Document (other than the Software product name, Number of Units, level of Maintenance, description of Services, and fees due in connection therewith) shall apply for any reason or purpose whatsoever, regardless of any statement on any Ordering Document to the contrary, unless countersigned by an officer of TIBCO. This Agreement constitutes the entire agreement between the parties with respect to the use of the Software, Maintenance and Services, and supersedes all proposals, oral or written, and all other representations, statements, negotiations and undertakings relating to the subject matter hereof. All orders of Software, Maintenance or Services by Customer to TIBCO shall be deemed to occur with or without reference to, under the terms of this End User License Agreement, unless expressly superseded by a signed written agreement between the parties. Neither the license to use the Software granted in this Agreement nor the obligation to pay the license fees set forth above are dependent upon the performance by any party of any Services or the supply of any other software program or product. Software shall be delivered electronically, and delivery deemed complete when the Software is made available for download by Customer.

Termination. Maintenance or Services may be terminated: (a) by either party upon a default of the other, such default remaining uncured for fifteen days from written notice from the non-defaulting party; (b) upon the filing for bankruptcy or insolvency of the other party, (c) by either party upon prior written notice at least sixty (60) days prior to the end of any annual Maintenance term; or (d) by Customer (for Services), upon ten days prior written notice or 30 days prior written notice by TIBCO. Termination of Maintenance or Services shall not terminate this End User License Agreement. Customer may terminate this End User License Agreement in its entirety at any time by destroying all copies of the Software. Upon termination or expiration of this End User License Agreement in its entirety, for any reason, Customer must cease using and return or destroy all copies of the Software. Customer's obligation to pay accrued charges and any fees due as of the date of termination, as well as the sections entitled "Confidentiality", "Limited Warranty" and "Limitation of Liability" shall survive any such termination.

Authority. You hereby represent and warrant that you have full power and authority to accept the terms of this End User License Agreement on behalf of Customer, and that Customer agrees to be bound by this End User License Agreement.

Definitions. In connection with this End User License Agreement Software product definitions are as set forth at http://tibco.com/software/productdefinitions.jsp which are hereby incorporated into the End User License Agreement and the following capitalized terms shall have the following meaning: "Customer" means the original purchaser or licensee of the Software and any permitted

successors and assigns; "Documentation" means text material that accompanies the Software on delivery, which describes how to make use of that software. "Enterprise" means an unlimited Number of Units of the Software set forth in an Ordering Document as Enterprise, to be deployed by Customer during a period of one year (or such other period of time set forth in the Ordering Document) from the Purchase Date (the "Enterprise Term"), at which time, the Number of Units then deployed in Production and Non-Production use by Customer becomes fixed and Customer may not thereafter deploy additional Units. During the Enterprise Term, Customer's right to deploy an unlimited Number of Units does not extend to any entity which acquires, is acquired by, merged into, or otherwise combined with Customer. Customer hereby agrees to provide TIBCO, within sixty (60) days after the end of the Enterprise Term, with written notice of the Number of Units deployed at the end of the Enterprise Term by Unit and License Type. In the event Customer elects to renew Maintenance (subject to the section entitled "Termination"), then during the Enterprise Term and for the first annual renewal thereafter, TIBCO agrees the annual Maintenance fee for the Software licensed on an Enterprise basis shall not increase by more than the percentage rate change in the United States Department of Labor - Consumer Price Index for All Urban Consumers (CPI-U) for the twelve month period immediately preceding the anniversary date of Maintenance. "Purchase Date" means the date the Ordering Document is accepted by TIBCO. "Project" means an unlimited Number of Units of the Software set forth in an Ordering Document as Project, to be deployed by Customer solely in connection with the description and scope of the Customer project set forth in the Ordering Document, during a period of one year (or such other time period set forth in the Ordering Document) from the Purchase Date (the "Project Term"), at which time, the Number of Units then deployed in Production and Non-Production use by Customer becomes fixed and Customer may not thereafter deploy additional Units. During the Project Term, Customer's right to deploy an unlimited Number of Units does not extend beyond the scope of the Project as set forth herein or to any entity which acquires, is acquired by, merged into, or otherwise combined with Customer. Customer hereby agrees to provide TIBCO, within sixty (60) days after the end of the Project Term, with written notice of the Number of Units deployed at the end of the Project Term by Unit and License Type. In the event Customer elects to renew Maintenance (subject to the section entitled "Termination"), then during the Project Term and for the first annual renewal thereafter, TIBCO agrees the annual Maintenance fee for the Software licensed on a Project basis shall not increase by more than the percentage rate change in the United States Department of Labor - Consumer Price Index for All Urban Consumers (CPI-U) for the twelve month period immediately preceding the anniversary date of Maintenance. "Severity" means the impact levels of an error, defect or malfunction, which under Maintenance are determined by TIBCO as follows: "Severity 1" is an emergency production situation where the Software is totally inoperable or fails catastrophically and there is no workaround; "Severity 2" is a detrimental situation (and there is no workaround) where (a) performance degrades substantially under reasonable loads causing a severe impact on use, (b) the Software is usable but materially incomplete; or (c) one or more mainline functions or commands is inoperable; "Severity 3" is where the Software is usable, but does not provide a function in the most convenient manner; and "Severity 4" is a minor problem or documentation error. "Software" means the most current, generally available object code version on all Platforms then currently available. Software does not include multiple Platforms if the software product licensed on a Platform specific basis as designated in the Software product name or as otherwise listed in an Ordering Document, including its Documentation and any subsequent Updates provided under Maintenance. For the purposes of the product definitions where "TIBCO Software" or "Licensor Software" is used it shall have the same meaning as "Software". "TIBCO" means TIBCO Software Inc.


http://tibco.com/software/productdefinitions.jsp

128 | TIBCO Software Inc. End User License Agreement

and any entities, regardless of corporate status, controlled by, controlling, or under common control with TIBCO Software Inc. "Updates" means Software bug fixes, enhancements, and updates, if and when made generally available by TIBCO. Updates provided under Maintenance, warranty or which are provided for any other reason by TIBCO, or TIBCO's authorized resellers or distributors (if applicable), are subject to the license rights, limitations and restrictions of the End User License Agreement.

Special Product Provision. Embedded/Bundled Products. Some Software embeds or bundles other Software. Use of such embedded or bundled Software is solely to enable the functionality of the Software licensed under this Agreement, and may not be used or accessed by any other Software, or for any other purpose. Bundle. A collection of Software listed in TIBCO's then current price book to be sold together under a collective name such as "XXX Bundle" which consists of X, Y and Z. The Software which comprises a Bundle must be used in accordance with any specific license restrictions imposed in this Agreement and solely in conjunction with the components of the Bundle; provided that a Bundle component may be accessed by or communicate with other Software separately licensed by Customer. In no event may the Software which comprises a Bundle be used on a standalone basis. A Bundle is sold at a discount to the cost of licensing the individual components due to the restrictions imposed on the use of the Bundle by this section and any specific license restrictions imposed by this Agreement. If the terms of this Agreement with regard to a Bundle are breached, and such breach is not cured within ten (10) days of TIBCO notifying Customer in writing of the breach, TIBCO shall be entitled to invoice Customer for the list price of the individual components of the Bundle based upon the manner in which Customer has deployed and is making use of the components. Open Source Software. If Customer uses open source software or any other third party software not supplied by TIBCO in conjunction with the Software, Customer must ensure that its use does not: (i) create, or purport to create, obligations of use with respect to the Software; or (ii) grant, or purport to grant, to any third party any rights to or immunities under TIBCO's intellectual property or proprietary rights in the Software. Customer also may not combine Software with programs licensed under the GNU General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the Software or any modifications thereto to become subject to the terms of the GPL. Third Party Software. Third Party Software means third-party software identified by its company and/or product name, the provision of which by TIBCO is made solely as an accommodation and in lieu of Customer purchasing a license to Third Party Software directly from the third party vendor.

General. All payments of fees due shall be made in U.S. dollars, net 30 from Purchase Date, or, for any other amounts coming due hereafter, net 30 from TIBCO's invoice. Fees do not include sales, use, withholding, value-added or similar taxes, and Customer agrees to pay all sales, use, value-added, goods and services, consumption, withholding, excise and any other similar taxes or government charges, exclusive of TIBCO's income tax. Customer agree to pay all reasonable costs incurred (including reasonable attorneys' fees) in collecting past due amounts. Except as set forth in the sections entitled "Limited Warranty" and "Indemnity" all fees paid under or in connection with this End User License Agreement are non-refundable and no right of set-off exists. A service charge of one and one-half percent per month will be applied to all invoices that are not paid on time. No delay in the performance of any obligation by either party, excepting all obligations to make payment, shall constitute a breach of this End User License Agreement to the extent caused by force majeure. Customer hereby grants TIBCO and its independent auditors the right to audit Customer's compliance with this End User License Agreement. If any portion of this End User License Agreement is

found to be void or unenforceable, the remaining provisions shall remain in full force and effect.

Governing Law. This End User License Agreement shall be governed by and construed in accordance with the laws of the State of California, United States of America, as if performed wholly within the state and without giving effect to the principles of conflict of law. The United Nations Convention on Contracts for the International Sale of Goods is excluded from application hereto.

Version 5.6, April 2008


Third-Party Software Notices | 129

Third-Party Software Notices

com.oreilly.servlett Library

The source code, object code, and documentation in the com.oreilly.servlet package is licensed by Hunter Digital Ventures, LLC. This Software is provided AS-IS, without warranty of any kind, either express or implied including, without limitation, any implied warranty of merchantibility and fitness for a particular purpose and any warranty of non-infringement.

DataDirect JDBC Drivers 3.7.64

Portions of this software are copyrighted by DataDirect Technologies, 1991-2002 and Copyright (c) 2001-2009 Progress Software Corporation. All rights reserved.

MX4J 3.0.1

This product includes software developed by the MX4J Product.

OpenLDAP 2.1.30OpenLDAP 2.8

Copyright© 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved.

THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE 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.

OpenSSL 0.9.8l

Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.

Simple Logging Facade for Java (SLF4J) 1.1.0

Copyright (c) 2004- 2005 SLF4J.ORG. Copyright (c) 2004-2005 QOS.ch. All rights reserved.

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 OF THIRD

PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Sun Java Runtime Environment (JRE) 1.6

As provided by Sun Microsystems additional copyright notices and license terms may be applicable to portions of the Software are set forth in the THIRDPARTYREADME.txt file.

UDD14J 2.0.3

This product includes UDD14J software which is licensed under the IBM Common Public License, v1.0. For a period of time not to exceed three years from the Purchase Date, TIBCO also offers to provide Customer, upon written request of Customer, a copy of the source code for this software.

XFire 1.1.2

Copyright (c) 2005 Envoi Solutions LLC.

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.

zlib 1.2.3

This product includes Zlib software, Copyright 1995-2003 Jean-loup Gailly and Mark Adler.

ADDENDA: Third-Party Software License Agreements


130 | Third-Party Software License Agreements

Third-Party Software License AgreementsThe following are the software licenses for the Third Party Software provided in connection with the software.

Apache Ant 1.5.3

Apache ANT Software License 1.4.1

Copyright (C) 2000-2002 The Apache Software Foundation. All rights reserved.

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

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

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

3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."

Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>

Apache Crimson 1.1.3

The Apache Crimson Software License 1.1 Copyright (c) 2001 The Apache Software Foundation. All rights reserved.





"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names "Crimson" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].



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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, Sun Microsystems, Inc., http://www.sun.com. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.

Apache Ant 1.6Apache Jakarta Commons HttpClient 2.0.2Apache Jakarta Commons HttpClient 3.0.1Apache Jakarta JSP Standard Tag Library 1.1.2Apache Jakarta Slide WebDAV client library 2.0Apache Log4J 1.2.14


Third-Party Software License Agreements | 131

Apache Log4J, v1.2.5Apache PerlTools.jar, v 1.2.0aApache Slide 2.0.0Apache Tomcat 4.1.27Apache Tomcat 5.5.27Apache Turbine, v2.1Apache Xalan-C, v 1.4.0Apache XalanJ 2.4.1Apache XercesC, v2.7.0Apache XercesJ 2.3.0Apache XML Security 1.4.2Apache Xalan-Java 2 2.6.0Apache Xerces Java 2 2.6.2Jakarta Cactus 1.6.1Jetty 6.1.3Spring 2.0EHCache 1.3.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, 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.

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

HSQLDB 1.7.3

COPYRIGHTS AND LICENSES

ORIGINAL LICENSE (a.k.a. "hypersonic_lic.txt")

For content, code, and products originally developed by Thomas Mueller and the Hypersonic SQL Group:

Copyright (c) 1995-2000, The Hypersonic SQL Group.

All rights reserved.


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

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.

Neither the name of the Hypersonic SQL Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

This software consists of voluntary contributions made by many individuals on behalf of the Hypersonic SQL Group.



For work added by the HSQL Development Group:

Copyright (c) 2001-2004, The HSQL Development Group





Neither the name of the HSQL Development Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

IBM ICU v3.2.0

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2002 International Business Machines Corporation and others


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, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

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 OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF

CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

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

All trademarks and registered trademarks mentioned herein are the property of their respective owners.

JWSDL (Java APIs for WSDL Specification) 1.5.3

Permission to copy and display the Java APIs for WSDL Specification, in any medium without fee or royalty is hereby granted, provided that you include the following on ALL copies of the Java APIs for WSDL Specification, or portions thereof, that you make:

1. A link or URL to the Java APIs for WSDL Specification at this location: http://www-124.ibm.com/developerworks/projects/wsdl4j/

2. The copyright notice as shown in the Java APIs for WSDL Specification.

Except for the limited copyright license granted above, the material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material. The material contained herein is provided on an "AS IS" basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL.

IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

The name and trademarks of the Authors may NOT be used in any manner, including advertising or publicity pertaining to the Java APIs for WSDL Specification or its contents without specific, written prior permission. Title to copyright in the Java APIs for WSDL Specification will at all times remain with the Authors.

No other rights are granted by implication, estoppel or otherwise.



libxml 2.6.9libxml 2.6.23

Except where otherwise noted in the source code (trio files, hash.c and list.c) covered by a similar licence but with different Copyright notices:

Copyright (C) 1998-2002 Daniel Veillard. All Rights Reserved.

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 DANIEL VEILLARD 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.

Except as contained in this notice, the name of Daniel Veillard shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from him.

libxml2 2.6.31

Open Source Initiative OSI - The MIT License:Licensing

Submitted by nelson on Tue, 2006-10-31 04:56. ::

The MIT License

Copyright (c) <year> <copyright holders>

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.

MX4J 3.0.1

The MX4J License, Version 1.0

Copyright (c) 2001 MX4J. All rights reserved.




3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the MX4J project." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names "MX4J" and "mx4j" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact Simone Bordet or Carlos Quiroz

5. Products derived from this software may not be called "MX4J", nor may "MX4J" appear in their name, without prior written permission of Simone Bordet.

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

This software consists of voluntary contributions made by many individuals on behalf of MX4J. For more information on MX4J, please see http://mx4j.sourceforge.net

netsnmp 5.4.1

Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001. An additional copyright section has been added as Part 4 below also under a BSD license for the work contributed by Sun Microsystems, Inc. to the project since 2003.



Code has been contributed to this project by many people over the years it has been in development, and a full list of contributors can be found in the README file under the THANKS section.

---- Part 1: CMU/UCD copyright notice: (BSD like) -----

Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

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

---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----

Copyright (c) 2001-2003, Networks Associates Technology, Inc



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

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

* Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

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

---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----

Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd.





* The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER 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.

---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----

Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Use is subject to license terms below.

This distribution may include materials developed by third parties.

Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.






* Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

---- Part 5: Sparta, Inc copyright notice (BSD) -----

Copyright (c) 2003-2006, Sparta, Inc





* Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.


---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----

Copyright (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications. All rights reserved.




* Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.


---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----

Copyright (c) Fabasoft R&D Software GmbH & Co KG, 2003 [email protected]

Author: Bernhard Penz




* The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER 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.



OpenLDAP 2.1.30OpenLDAP 2.8

The OpenLDAP Public License Version 2.8, 17 August 2003

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 in source form must retain copyright statements and notices,

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

3. Redistributions must contain a verbatim copy of this document.

The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished by a version number. You may use this Software under terms of this license revision or under the terms of any subsequent revision of the license.

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

The names of the authors and copyright holders must not be used in advertising or otherwise to promote the sale, use or other dealing in this Software without specific, written prior permission. Title to copyright in this Software shall at all times remain with copyright holders.

OpenLDAP is a registered trademark of the OpenLDAP Foundation.

Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission to copy and distribute verbatim copies of this document is granted.

OpenSSL 0.9.8dOpenSSL 0.9.8g

LICENSE ISSUES

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

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any

license issues related to OpenSSL please contact [email protected].

OpenSSL License

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

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

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




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

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

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

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

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

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

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

Original SSLeay License

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



Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]). The implementation was written so as to conform with Netscapes SSL.

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

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


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

3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young ([email protected])" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson ([email protected])"

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

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

OpenSSL 0.9.8l

OpenSSL/SSLeavy

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

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



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

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

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

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

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:www.openssl.org)"

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

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

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

Original SSLeay License

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

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




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

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

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

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


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

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

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

"This product includes cryptographic software written by Eric Young ([email protected])"

The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson ([email protected])"

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

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

Perl5 API 1.2

The Apache Software License, Version 1.1

Copyright (c) 2000 The Apache Software Foundation. All rights reserved.




3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

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



This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.

Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.

Sun Java Development Kit (JDK) 1.6.0

THIRDPARTYREADME.txt

DO NOT TRANSLATE OR LOCALIZE.



%% The following software may be included in this product: CS CodeViewer v1.0; Use of any of this software is governed by the terms of the license below:

Copyright 1999 by CoolServlets.com.

Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this program... your comments will encourage further development!

This software is distributed under the terms of the BSD License.




Neither name of CoolServlets.com nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

%% The following software may be included in this product: Crimson v1.1.1 ; Use of any of this software is governed by the terms of the license below:

The Apache Software License, Version 1.1 Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.




3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. *

4. The names "Crimson" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].



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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.

%% The following software may be included in this product: Xalan J2; Use of any of this software is governed by the terms of the license below: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/


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.






"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 owneror 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."



3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a

cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.





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





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.


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.


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.

%% The following software may be included in this product: NSIS 1.0j; Use of any of this software is governed by the terms of the license below:

Copyright (C) 1999-2000 Nullsoft, Inc.

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

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

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

3. This notice may not be removed or altered from any source distribution. Justin Frankel [email protected]"

%% Some Portions licensed from IBM are available at:

http://www.ibm.com/software/globalization/icu/

%% Portions Copyright Eastman Kodak Company 1992

%% Lucida is a registered trademark or trademark of Bigelow & Holmes in the U.S. and other countries.

%% Portions licensed from Taligent, Inc.

%% The following software may be included in this product:IAIK PKCS Wrapper; Use of any of this software is governed by the terms of the license below:

Copyright (c) 2002 Graz University of Technology. All rights reserved.

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




"This product includes software developed by IAIK of Graz University of Technology."


4. The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or promote products derived from this software without prior written permission.

5. Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name, without prior written permission of Graz University of Technology.

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

%% The following software may be included in this product: Document Object Model (DOM) v. Level 3; Use of any of this software is governed by the terms of the license below:

W3C SOFTWARE NOTICE AND LICENSE

http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231

This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.

Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the



following on ALL copies of the software and documentation or portions thereof, including modifications:

1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.

3.Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKENO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THEUSE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL ORCONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders. ____________________________________

This formulation of W3C's notice and license became active on December 31 2002. This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous grant of "use". Otherwise, this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to [email protected].

%% The following software may be included in this product: Xalan, Xerces; Use of any of this software is governed by the terms of the license below:


Copyright (c) 1999-2003 The Apache Software Foundation. All rights reserved.





"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."


4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].



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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://www.apache.org

%% The following software may be included in this product: W3C XML Conformance Test Suites v. 20020606; Use of any of this software is governed by the terms of the license below:


Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is beingprovided by the copyright holders under the following license. By obtaining,using and/or copying this work, you (the licensee) agree that you have read,understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee orroyalty is hereby granted, provided that you include the following on ALL copiesof the software and documentation or portions thereof, including modifications,that you make:



1. The full text of this NOTICE in a location viewable to users of theredistributed or derivative work.

2. Any pre-existing intellectual property disclaimers, notices, or terms andconditions. If none exist, a short notice of the following form (hypertext ispreferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright Ã½Ã½ [$date-of-software] World WideWeb Consortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/"

3. Notice of any changes or modifications to the W3C files, including thedate changes were made. (We recommend you provide URIs to the location fromwhich the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKENO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITEDTO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THATTHE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTYPATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.


The name and trademarks of copyright holders may NOT be used in advertising orpublicity pertaining to the software without specific, written prior permission.Title to copyright in this software and any associated documentation will at alltimes remain with copyright holders.

____________________________________

This formulation of W3C's notice and license became active on August 14 1998 soas to improve compatibility with GPL. This version ensures that W3C softwarelicensing terms are no more restrictive than GPL and consequently W3C softwaremay be distributed in GPL packages. See the older formulation for the policyprior to this date. Please see our Copyright FAQ for common questions aboutusing materials from our site, including specific terms and conditions forpackages like libwww, Amaya, and Jigsaw. Other questions about this notice canbe directed to [email protected].

%% The following software may be included in this product: W3C XML Schema Test Collection v. 1.16.2; Use of any of this software is governed by the terms of the license below: W3C DOCUMENT NOTICE AND LICENSE

Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved.

http://www.w3.org/Consortium/Legal/

Public documents on the W3C site are provided by the copyright holders under thefollowing license. The software or Document Type Definitions (DTDs) associatedwith W3C specifications are governed by the Software Notice. By using and/orcopying this document, or the W3C document from which this statement is linked,you (the licensee) agree that you have read, understood, and will comply withthe following terms and conditions:

Permission to use, copy, and distribute the contents of this document, or theW3C document from which this statement is linked, in any medium for any purposeand without fee or royalty is hereby granted, provided that you include thefollowing on ALL copies of the document, or portions thereof, that you use:

1. A link or URL to the original W3C document.

2. The pre-existing copyright notice of the original author, or if it doesn'texist, a notice of the form: "Copyright [$date-of-document] World Wide WebConsortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but atextual representation is permitted.)

3. If it exists, the STATUS of the W3C document.

When space permits, inclusion of the full text of this NOTICE should beprovided. We request that authorship attribution be provided in any software,documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.

No right to create modifications or derivatives of W3C documents is grantedpursuant to this license. However, if additional requirements (documented in theCopyright FAQ) are satisfied, the right to create modifications or derivativesis sometimes granted by the W3C to individuals complying with those requirements.

THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONSOR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE;THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THEIMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL ORCONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCEOR IMPLEMENTATION OF THE CONTENTS THEREOF.

The name and trademarks of copyright holders may NOT be used in advertising orpublicity pertaining to this document or its contents without specific, writtenprior permission. Title to copyright in this document will at all times remainwith copyright holders.

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

This formulation of W3C's notice and license became active on April 05 1999 soas to account for the treatment of DTDs, schema's and bindings. See the olderformulation for the policy prior to this date. Please see our Copyright FAQ forcommon questions about using materials from our site, including specific termsand conditions for packages like libwww, Amaya, and Jigsaw. Other questionsabout this notice can be directed to [email protected].

webmaster

(last updated by reagle on 1999/04/99.)



%% The following software may be included in this product: Mesa 3-D graphics library v. 5; Use of any of this software is governed by the terms of the license below:

core Mesa code include/GL/gl.h Brian Paul

Mesa GLX driver include/GL/glx.h Brian Paul

Mesa Ext registry include/GL/glext.h SGI

SGI Free B include/GL/glxext.h

Mesa license:

The Mesa distribution consists of several components. Different copyrights andlicenses apply to different components. For example, GLUT is copyrighted by MarkKilgard, some demo programs are copyrighted by SGI, some of the Mesa devicedrivers are copyrighted by their authors. See below for a list of Mesa'scomponents and the copyright/license for each.

The core Mesa library is licensed according to the terms of the XFree86copyright (an MIT-style license). This allows integration with the XFree86/DRIproject. Unless otherwise stated, the Mesa source code and documentation islicensed as follows:

Copyright (C) 1999-2003 Brian Paul All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining acopy of this software and associated documentation files (the "Software"),to deal in the Software without restriction, including without limitationthe 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 includedin all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALLBRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER INAN 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.

SGI FREE SOFTWARE LICENSE B (Version 1.1 [02/22/2000])

1. Definitions.

1.1 "Additional Notice Provisions" means such additional provisions as appear in the Notice in Original Code under the heading "Additional Notice Provisions."

1.2 "Covered Code" means the Original Code or Modifications, or any combination thereof.

1.3 "Hardware" means any physical device that accepts input, processes input, stores the results of processing, and/or provides output.

1.4 "Larger Work" means a work that combines Covered Code or portions thereof with code not governed by the terms of this License.

1.5 "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.6 "License" means this document.

1.7 "Licensed Patents" means patent claims Licensable by SGI that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.

1.8 "Modifications" means any addition to or deletion from the substance or structure of the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to the contents of a file containing Original Code and/or addition to or deletion from the contents of a file containing previous Modifications.B. Any new file that contains any part of the Original Code or previous Modifications.

1.9 "Notice" means any notice in Original Code or Covered Code, as required by and in compliance with this License.

1.10 "Original Code" means source code of computer software code that is described in the source code Notice required by Exhibit A as Original Code, and updates and error corrections specifically thereto.

1.11 "Recipient" 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 8. For legal entities, "Recipient" includes any entity that controls, is controlled by, or is under common control with Recipient. For purposes of this definition, "control" of an entity means (a) the power, direct or indirect, to direct or manage such entity, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.

1.12 "Recipient Patents" means patent claims Licensable by a Recipient that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.

1.13 "SGI" means Silicon Graphics, Inc.

1.14 "SGI Patents" means patent claims Licensable by SGI other than the Licensed Patents.2. License Grant and Restrictions.

2.1 SGI License Grant. Subject to the terms of this License and any third party intellectual property claims, for the duration of intellectual property protections inherent in the Original Code, SGI hereby grants Recipient a worldwide, royalty-free, non-exclusive license, to do the following: (i) under copyrights Licensable by SGI, to reproduce, distribute, create derivative works from, and, to the extent applicable, display and perform the Original Code and/or any Modifications provided by SGI alone and/or as part of a Larger Work; and (ii) under any Licensable Patents, to make, have made, use, sell, offer for sale, import and/or otherwise transfer the Original Code and/or any Modifications provided by SGI. Recipient accepts the terms and conditions of this License by undertaking any of the aforementioned actions. The patent license shall apply to the Covered Code if, at the time any related Modification is added, such addition of the Modification causes such combination to be covered by the Licensed Patents. The patent license in Section 2.1(ii) shall not apply to any other combinations that include the Modification. No patent license is provided under SGI Patents for infringements of SGI Patents by Modifications not provided by SGI or combinations of Original Code and Modifications not provided by SGI. 2.2 Recipient License Grant. Subject to the terms of this License and any third party intellectual property claims, Recipient hereby grants SGI and any other Recipients a worldwide, royalty-free, non-exclusive license, under any Recipient Patents, to make, have made, use, sell, offer for sale, import



and/or otherwise transfer the Original Code and/or any Modifications provided by SGI.

2.3 No License For Hardware Implementations. The licenses granted in Section 2.1 and 2.2 are not applicable to implementation in Hardware of the algorithms embodied in the Original Code or any Modifications provided by SGI .

3. Redistributions.

3.1 Retention of Notice/Copy of License. The Notice set forth in Exhibit A, below, must be conspicuously retained or included in any and all redistributions of Covered Code. For distributions of the Covered Code in source code form, the Notice must appear in every file that can include a text comments field; in executable form, the Notice and a copy of this License must appear in related documentation or collateral where the Recipient's rights relating to Covered Code are described. Any Additional Notice Provisions which actually appears in the Original Code must also be retained or included in any and all redistributions of Covered Code.

3.2 Alternative License. Provided that Recipient is in compliance with the terms of this License, Recipient may, so long as without derogation of any of SGI's rights in and to the Original Code, distribute the source code and/or executable version(s) of Covered Code under (1) this License; (2) a license identical to this License but for only such changes as are necessary in order to clarify Recipient's role as licensor of Modifications; and/or (3) a license of Recipient's choosing, containing terms different from this License, provided that the license terms include this Section 3 and Sections 4, 6, 7, 10, 12, and 13, which terms may not be modified or superseded by any other terms of such license. If Recipient elects to use any license other than this License, Recipient must make it absolutely clear that any of its terms which differ from this License are offered by Recipient alone, and not by SGI. It is emphasized that this License is a limited license, and, regardless of the license form employed by Recipient in accordance with this Section 3.2, Recipient may relicense only such rights, in Original Code and Modifications by SGI, as it has actually been granted by SGI in this License.

3.3 Indemnity. Recipient hereby agrees to indemnify SGI for any liability incurred by SGI as a result of any such alternative license terms Recipient offers.

4. Termination. This License and the rights granted hereunder will terminate automatically if Recipient breaches any term herein and fails to cure such breach within 30 days thereof. Any sublicense to the Covered Code that is properly granted shall survive any termination of this License, absent termination by the terms of such sublicense. Provisions that, by their nature, must remain in effect beyond the termination of this License, shall survive.

5. No Trademark Or Other Rights. This License does not grant any rights to: (i) any software apart from the Covered Code, nor shall any other rights or licenses not expressly granted hereunder arise by implication, estoppel or otherwise with respect to the Covered Code; (ii) any trade name, trademark or service mark whatsoever, including without limitation any related right for purposes of endorsement or promotion of products derived from the Covered Code, without prior written permission of SGI; or (iii) any title to or ownership of the Original Code, which shall at all times remains with SGI. All rights in the Original Code not expressly granted under this License are reserved.

6. Compliance with Laws; Non-Infringement. There are various worldwide laws, regulations, and executive orders applicable to dispositions of Covered Code, including without limitation export,

re-export, and import control laws, regulations, and executive orders, of the U.S. government and other countries, and Recipient is reminded it is obliged to obey such laws, regulations, and executive orders. Recipient may not distribute Covered Code that (i) in any way infringes (directly or contributorily) any intellectual property rights of any kind of any other person or entity or (ii) breaches any representation or warranty, express, implied or statutory, to which, under any applicable law, it might be deemed to have been subject.

7. Claims of Infringement. If Recipient learns of any third party claim that any disposition of Covered Code and/or functionality wholly or partially infringes the third party's intellectual property rights, Recipient will promptly notify SGI of such claim.

8. Versions of the License. SGI may publish revised and/or new versions of the License from time to time, each with a distinguishing version number. Once Covered Code has been published under a particular version of the License, Recipient may, for the duration of the license, continue to use it under the terms of that version, or choose to use such Covered Code under the terms of any subsequent version published by SGI. Subject to the provisions of Sections 3 and 4 of this License, only SGI may modify the terms applicable to Covered Code created under this License.

9. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED "AS IS." ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS ARE DISCLAIMED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. SGI ASSUMES NO RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE. SHOULD THE SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, SGI ASSUMES NO COST OR LIABILITY FOR SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY IS AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT SUBJECT TO THIS DISCLAIMER.

10. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES NOR LEGAL THEORY, WHETHER TORT (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE OR STRICT LIABILITY), CONTRACT, OR OTHERWISE, SHALL SGI OR ANY SGI LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, LOSS OF DATA, 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 SGI'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 THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO RECIPIENT.

11. Indemnity. Recipient shall be solely responsible for damages arising, directly or indirectly, out of its utilization of rights under this License. Recipient will defend, indemnify and hold harmless Silicon Graphics, Inc. from and against any loss, liability, damages, costs or expenses (including the payment of reasonable attorneys fees) arising out of Recipient's use, modification, reproduction and distribution of the Covered Code or out of any representation or warranty made by Recipient.



12. U.S. Government End Users. The Covered Code is a "commercial item" consisting of "commercial computer software" as such terms are defined in title 48 of the Code of Federal Regulations and all U.S. Government End Users acquire only the rights set forth in this License and are subject to the terms of this License.

13. Miscellaneous. This License represents the complete agreement concerning the its subject matter. If any provision of this License is held to be unenforceable, such provision shall be reformed so as to achieve as nearly as possible the same legal and economic effect as the original provision and the remainder of this License will remain in effect. This License shall be governed by and construed in accordance with the laws of the United States and the State of California as applied to agreements entered into and to be performed entirely within California between California residents. Any litigation relating to this License shall be subject to the exclusive jurisdiction of the Federal Courts of the Northern District of California (or, absent subject matter jurisdiction in such courts, the courts of the State of California), with venue lying exclusively 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 that provides that the language of a contract shall be construed against the drafter shall not apply to this License.

Exhibit A

License Applicability. Except to the extent portions of this file are made subject to an alternative license as permitted in the SGI Free Software License B, Version 1.1 (the "License"), the contents of this file are subject only to the provisions of the License. You may not use this file except in compliance with the License. You may obtain a copy of the License at Silicon Graphics, Inc., attn: Legal Services, 1600 Amphitheatre Parkway, Mountain View, CA 94043-1351, or at: http://oss.sgi.com/projects/FreeB

Note that, as provided in the License, the Software is distributed on an "AS IS" basis, with ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS DISCLAIMED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.Original Code. The Original Code is: [name of software, version number, and release date], developed by Silicon Graphics, Inc. The Original Code is Copyright (c) [dates of first publication, as appearing in the Notice in the Original Code] Silicon Graphics, Inc. Copyright in any portions created by third parties is as indicated elsewhere herein. All Rights Reserved.Additional Notice Provisions: [such additional provisions, if any, as appear in the Notice in the Original Code under the heading "Additional Notice Provisions"]

%% The following software may be included in this product: Byte Code Engineering Library (BCEL) v. 5; Use of any of this software is governed by the terms of the license below:

Apache Software License

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


Copyright (c) 2001 The Apache Software Foundation. Allrights reserved.

Redistribution and use in source and binary forms, withor without modification, are permitted provided that the followingconditions are met:

1. Redistributions of source code must retain the abovecopyright notice, this list of conditions and the followingdisclaimer.

2. Redistributions in binary form must reproduce theabove copyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.

3. The end-user documentation included with theredistribution, if any, must include the following acknowledgment:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in thesoftware itself, if and wherever such third-party acknowledgmentsnormally appear.

4. The names "Apache" and "Apache Software Foundation"and "Apache BCEL" must not be used to endorse or promoteproducts derived from this software without prior writtenpermission. For written permission, please contact [email protected].

5. Products derived from this software may not be called"Apache", "Apache BCEL", nor may "Apache" appear in their name,without prior written permission of the Apache SoftwareFoundation.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWAREFOUNDATION 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) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org.

%% The following software may be included in this product: Regexp, Regular Expression Package v. 1.2; Use of any of this software is governed by the terms of the license below: The Apache Software License, Version 1.1









4. The names "Apache" and "Apache Software Foundation" and "Apache Turbine" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache", "Apache Turbine", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.


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


%% The following software may be included in this product: CUP Parser Generator for Java v. 0.10k; Use of any of this software is governed by the terms of the license below: CUP Parser Generator Copyright Notice, License, and Disclaimer

Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided thatthe above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the names of the authors or their employersnot be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to thissoftware, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for anyspecial, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an

action of contract,negligence or other tortious action, arising out of or in connection withthe use or performance of this software.

%% The following software may be included in this product: JLex: A Lexical Analyzer Generator for Java v. 1.2.5; Use of any of this software is governed by the terms of the license below: JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.

Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright noticeappear in all copies and that both the copyright notice and this permission notice and warrantydisclaimer appear in supporting documentation, and that the name of the authors or their employersnot be used in advertising or publicity pertaining to distribution of the software withoutspecific, written prior permission.

The authors and their employers disclaim all warranties with regard to thissoftware, including all implied warranties of merchantability and fitness. In no event shall the authorsor their employers be liable for any special, indirect or consequential damages or any damageswhatsoever resulting from loss of use, data or profits, whether in an action of contract, negligenceor other tortious action, arising out of or in connection with the use or performance of thissoftware.

Java is a trademark of Sun Microsystems, Inc. References to the Java programminglanguage in relation to JLex are not meant to imply that Sun endorses this product.

%% The following software may be included in this product: SAX v. 2.0.1; Use of any of this software is governed by the terms of the license below: Copyright Status

SAX is free!

In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.

No Warranty

Because SAX is released to the public domain, there is no warranty for the design or for the software implementation, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide SAX "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 SAX is with you. Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.

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 SAX, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use SAX (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 SAX to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.

Copyright Disclaimers

This page includes statements to that effect by David Megginson, who would have been able to claim copyright for the original work.



SAX 1.0

Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of the XML-DEV mailing list, is hereby released into the public domain.

No one owns SAX: you may use it freely in both commercial and non-commercial applications, bundle it with your software distribution, include it on a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it in any other way you see fit.

David Megginson, [email protected]

1998-05-11

SAX 2.0

I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.


2000-05-05

%% The following software may be included in this product: Cryptix; Use of any of this software is governed by the terms of the license below:

Cryptix General License

Copyright Â© 1995-2003 The Cryptix Foundation Limited. All rights reserved.

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

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

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

THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) 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 OFTHE POSSIBILITY OF SUCH DAMAGE.

%% The following software may be included in this product: W3C XML Schema Test Collection; Use of any of this software is governed by the terms of the license below:

W3C® DOCUMENT NOTICE AND LICENSE

Copyright Â© 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved.





2. The pre-existing copyright notice of the original author, or if it doesn'texist, a notice of the form: "Copyright Â© [$date-of-document] World Wide WebConsortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but atextual representation is permitted.)









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


webmaster


%% The following software may be included in this product: Stax API; Use of any of this software is governed by the terms of the license below:

Streaming API for XML (JSR-173) SpecificationReference Implementation

License Agreement

READ THE TERMS OF THIS (THE "AGREEMENT") CAREFULLY BEFORE VIEWING OR USING THESOFTWARE LICENSED HEREUNDER. BY VIEWING OR USING THE SOFTWARE, YOU AGREE TO THE TERMS OF THISAGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESETERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TOALL THESE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO ORIGINAL CONTRIBUTOR, DEFINED HEREIN.

1.0 DEFINITIONS.

1.1. "BEA" means BEA Systems, Inc., the licensor of the Original Code.

1.2. "Contributor" means BEA and each entity that creates or contributes to thecreation of Modifications.

1.3. "Covered Code" means the Original Code or Modifications or the combinationof the Original Code and Modifications, in each case including portions thereof and corresponding documentation released with the source code.

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

1.5. "FCS" means first commercial shipment of a product.

1.6. "Modifications" means any addition to or deletion from the substance orstructure of either the Original Code or any previous Modifications. When Covered Code isreleased as a series of files, a Modification is:

(a) Any addition to or deletion from the contents of a file containing OriginalCode or previous Modifications.

(b) Any new file that contains any part of the Original Code or previousModifications.

1.7. "Original Code" means Source Code of computer software code ReferenceImplementation.

1.8. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,including without limitation, method, process, and apparatus claims, in any patent for whichthe grantor has the right to grant a license.

1.9. "Reference Implementation" means the prototype or "proof of concept"implementaÂtion of the Specification developed and made available for license by or on behalf of BEA.

1.10. "Source Code" means the preferred form of the Covered Code for makingmodifications to it, including all modules it contains, plus any associated documentation,interface definition files, scripts used to control compilation and installation of an Executable, orsource code differential comparisons against either the Original Code or another well known,available Covered Code of the Contributor's choice.

1.11. "Specification" means the written specification for the Streaming API forXML , Java technology developed pursuant to the Java Community Process.

1.12. "Technology Compatibility Kit" or "TCK" means the documentation, testingtools and test suites associated with the Specification as may be revised by BEA from time totime, that is provided so that an implementer of the SpecifiÂcation may determine if itsimplementation is compliant with the Specification.

1.13. "You" (or "Your") means an individual or a legal entity exercising rightsunder, and complying with all of the terms of, this Agreement or a future version of thisAgreement 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 theoutstanding shares or beneficial ownership of such entity.

2.0 SOURCE CODE LICENSE.

2.1. Copyright Grant. Subject to the terms of this Agreement, each Contributorhereby grants You a non-exclusive, worldwide, royalty-free copyright license to reproduce,prepare derivative works of, publicly display, publicly perform, distribute and sublicense theCovered Code of such Contributor, if any, and such derivative works, in Source Code andExecutable form.

2.2. Patent Grant. Subject to the terms of this Agreement, each Contributorhereby grants You a non-exclusive, worldwide, royalty-free patent license under the PatentClaims to make, use, sell, offer to sell, import and otherwise transfer the Covered Code preparedand provided by such Contributor, if any, in Source Code and Executable form. This patentlicense shall apply to the Covered Code if, at the time a Modification is added by the Contributor,such addition of the Modification causes such combination to be covered by the Patent Claims.The patent license shall not apply to any other combinations which include the Modification.

2.3. Conditions to Grants. You understand that although each Contributorgrants the licenses to the Covered Code prepared by it, no assurances are provided by anyContributor that the Covered Code does not infringe the patent or other intellectual property rights ofany other entity. Each Contributor disclaims any liability to You for claims brought by anyother entity based on infringement of intellectual property rights or otherwise. As a conditionto exercising the rights and licenses granted hereunder, You hereby assume sole responsibility to



secure any other intellectual property rights needed, if any. For example, if a thirdparty patent license is required to allow You to distribute Covered Code, it is Your responsibility to acquire that license before distributing such code.

2.4. Contributors' Representation. Each Contributor represents that to itsknowledge it has sufficient copyright rights in the Covered Code it provides , if any, to grantthe copyright license set forth in this Agreement.

3.0 DISTRIBUION RESTRICTIONS.

3.1. Application of Agreement.

The Modifications which You create or to which You contribute are governed bythe terms of this Agreement, including without limitation Section 2.0. The Source Code versionof Covered Code may be distributed only under the terms of this Agreement or a future versionof this Agreement released under Section 6.1, and You must include a copy of this Agreementwith every copy of the Source Code You distribute. You may not offer or impose any terms on anySource Code version that alters or restricts the applicable version of this Agreement or therecipients' rights hereunder. However, You may include an additional document offering theadditional rights described in Section 3.3.

3.2. Description of Modifications.

You must cause all Covered Code to which You contribute to contain a filedocumenting the changes You made to create that Covered Code and the date of any change. You mustinclude a prominent statement that the Modification is derived, directly or indirectly, fromOriginal Code provided by BEA and including the name of BEA in (a) the Source Code, and (b) inany notice in an Executable version or related documentation in which You describe the origin orownership ofthe Covered Code.

%% The following software may be included in this product: X Window System; Use of any of this software is governed by the terms of the license below:

Copyright The Open Group

Permission to use, copy, modify, distribute, and sell this software and itsdocumentation for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright noticeand this permission notice appear in supporting documentation.

The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUPBE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OFCONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of The Open Group shall not be usedin advertising or otherwise to promote the sale, use or other dealings in thisSoftware without prior written authorization from The Open Group.

Portions also covered by other licenses as noted in the above URL.

%% The following software may be included in this product: dom4j v. 1.6; Use of any of this software is governed by the terms of the license below:

Redistribution and use of this software and associated documentation

("Software"), with or without modification, are permitted provided that thefollowing conditions are met:

1. Redistributions of source code must retain copyright statements andnotices. 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/orother materials provided with the distribution.

3. The name "DOM4J" must not be used to endorse or promote products derivedfrom this Software without prior written permission of MetaStuff, Ltd. Forwritten permission, please contact [email protected].

4. Products derived from this Software may not be called "DOM4J" nor may"DOM4J" appear in their names without prior written permission of MetaStuff,Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.

5. Due credit should be given to the DOM4J Project - http://www.dom4j.org

THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS `ÀS IS'' AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FORANY 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 ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.

%% The following software may be included in this product: Retroweaver; Use of any of this software is governed by the terms of the license below:

Copyright (c) February 2004, Toby Reyelts







Neither the name of Toby Reyelts nor the names of his contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

%% The following software may be included in this product: stripper; Use of any of this software is governed by the terms of the license below:

Stripper : debug information stripper

Copyright (c) 2003 Kohsuke Kawaguchi





3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived fromthis software without specific prior written permission.

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

%% The following software may be included in this product: libpng official PNG reference library; Use of any of this software is governed by the terms of the license below:

This copy of the libpng notices is provided for your convenience. In case ofany discrepancy between this copy and the notices in the file png.h that isincluded in the libpng distribution, the latter shall prevail.

COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:

If you modify libpng you may insert additional notices immediately followingthis sentence.

libpng version 1.2.6, December 3, 2004, is Copyright (c) 2004 Glenn Randers-Pehrson, and is distributed according to the same disclaimer and license as libpng-1.2.5with the following individual added to the list of Contributing Authors

Cosmin Truta

libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following individuals added to the list of Contributing Authors

Simon-Pierre Cadieux

Eric S. Raymond

Gilles Vollant

and with the following additions to the disclaimer:

There is no warranty against interference with your enjoyment of the library or against infringement. There is no warranty that our efforts or the library will fulfill any of your particular purposes or needs. This library is provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with the user.

libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, areCopyright (c) 1998, 1999 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-0.96,with the following individuals added to the list of Contributing Authors:

Tom Lane

Glenn Randers-Pehrson

Willem van Schaik

libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (c) 1996, 1997 Andreas Dilger

Distributed according to the same disclaimer and license as libpng-0.88, with the following individuals added to the list of Contributing Authors:

John Bowler

Kevin Bracey

Sam Bushell

Magnus Holmgren

Greg Roelofs

Tom Tanner



libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.

For the purposes of this copyright and license, "Contributing Authors"is defined as the following set of individuals:

Andreas Dilger

Dave Martindale

Guy Eric Schalnat

Paul Schmidt

Tim Wegner

The PNG Reference Library is supplied "AS IS". The Contributing Authorsand Group 42, Inc. disclaim all warranties, expressed or implied, including, without limitation, the warranties of merchantability and offitness for any purpose. The Contributing Authors and Group 42, Inc. assume no liability for direct, indirect, incidental, special, exemplary,or consequential damages, which may result from the use of the PNG Reference Library, even if advised of the possibility of such damage.

Permission is hereby granted to use, copy, modify, and distribute thissource code, or portions hereof, for any purpose, without fee, subjectto the following restrictions:

1. The origin of this source code must not be misrepresented.

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

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

The Contributing Authors and Group 42, Inc. specifically permit, withoutfee, and encourage the use of this source code as a component to supporting the PNG file format in commercial products. If you use thissource code in a product, acknowledgment is not required but would be appreciated.

A "png_get_copyright" function is available, for convenient use in "about"boxes and the like:

printf("%s",png_get_copyright(NULL));

Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).

Libpng is OSI Certified Open Source Software. OSI Certified Open Source is acertification mark of the Open Source Initiative.


glennrp at users.sourceforge.net

December 3, 2004

%% The following software may be included in this product: Libungif - An uncompressed GIF library; Use of any of this software is governed by the terms of the license below:

The GIFLIB distribution is Copyright (c) 1997 Eric S. Raymond

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies 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 inall copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, 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 INTHE SOFTWARE.

%% The following software may be included in this product: Ant; Use of any of this software is governed by the terms of the license below:

License

The Apache Software License Version 2.0

The Apache Software License Version 2.0 applies to all releases of Ant startingwith ant 1.6.1 Apache License Version 2.0, January 2004

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


1. Definitions.



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







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








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












Copyright [yyyy] Apache Software Foundation




You can download the original license file here.

The License is accompanied by a NOTICE

=========================================================================== NOTICE file corresponding to the section 4 d of == == the Apache License, Version 2.0, ==== in this case for the Apache Ant distribution. ==

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

This product includes software developed by The Apache Software Foundation (http://www.apache.org/). This product includes also software developed by : - the W3C consortium (http://www.w3c.org) , - the SAX project (http://www.saxproject.org)

Please read the different LICENSE files present in the root directory of this distribution.

The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].


The Apache Software License, Version 1.1, applies to all versions of up to ant1.6.0 included.


Copyright (C) 2000-2003 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.



4. The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].




%% The following software may be included in this product: XML Resolver library; Use of any of this software is governed by the terms of the license below: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/


1. Definitions.



















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





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.









%% The following software may be included in this product: ICU4J; Use of any of this software is governed by the terms of the license below:

ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c)

1995-2003 International Business Machines Corporation and others All rightsreserved. Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the "Software"), todeal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, and/or sell copies ofthe Software, and to permit persons to whom the Software is furnished to do so,provided that the above copyright notice(s) and this permission notice appear inall copies of the Software and that both the above copyright notice(s) and thispermission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED"AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOTLIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHTHOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANYSPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTINGFROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF

CONTRACT, NEGLIGENCEOR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of acopyright holder shall not be used in advertising or otherwise to promote thesale, use or other dealings in this Software without prior written authorizationof the copyright holder.

%% The following software may be included in this product: NekoHTML; Use of any of this software is governed by the terms of the license below:

The CyberNeko Software License, Version 1.0

(C) Copyright 2002,2003, Andy Clark. All rights reserved.





"This product includes software developed by Andy Clark." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

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

5. Products derived from this software may not be called "CyberNeko", nor may "CyberNeko" appear in their name, without prior written permission of the author.

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

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

This license is based on the Apache Software License, version 1.1

%% The following software may be included in this product: Jing; Use of any of this software is governed by the terms of the license below:

Jing Copying Conditions



Copyright (c) 2001-2003 Thai Open Source Software Center Ltd



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

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

Neither the name of the Thai Open Source Software Center Ltd nor the namesof its contributors may be used to endorse or promote products derived from thissoftware without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANYDIRECT, 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 ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

%% The following software may be included in this product: RelaxNGCC; Use of any of this software is governed by the terms of the license below:

Copyright (c) 2000-2003 Daisuke Okajima and Kohsuke Kawaguchi. All rights reserved.





"This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/)."


4. The names of the copyright holders must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact the copyright holders.

5. Products derived from this software may not be called "RELAXNGCC", nor may "RELAXNGCC" appear in their name, without prior written permission of the copyright holders.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 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.

%% The following software may be included in this product: RELAX NG Object Model/Parser; Use of any of this software is governed by the terms of the license below:

The MIT License

Copyright (c)

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


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ORCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHERIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

%% The following software may be included in this product: XFree86-VidMode Extension; Use of any of this software is governed by the terms of the license below:

Version 1.1 of ProjectLicence.

Copyright (C) 1994-2004 The Project, Inc. All rights reserved.

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

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



Redistributions in binary form must reproduce the above copyrightnotice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution, and in thesame place and form as other copyright, license and disclaimer information. 3. The end-user documentation included with the redistribution, if any,must include the following acknowledgment: "This product includes softwaredeveloped by The XFree86 Project, Inc (http://www.xfree86.org/) and itscontributors", in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment may appear in the software itself, in the sameform and location as other such third-party acknowledgments. 4. Except as contained in this notice, the name of The XFree86 Project,Inc shall not be used in advertising or otherwise to promote the sale, use orother dealings in this Software without prior written authorization from TheXFree86 Project, Inc.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE XFREE86PROJECT, INC 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; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.


This is version 2003-May-08 of the Info-ZIP copyright and license.

The definitive version of this document should be available at

ftp://ftp.info-zip.org/pub/infozip/license.html indefinitely.

Copyright (c) 1990-2003 Info-ZIP. All rights reserved.

For the purposes of this copyright and license, "Info-ZIP" is defined asthe following set of individuals:

Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White

This software is provided "as is," without warranty of any kind, expressor implied. In no event shall Info-ZIP or its contributors be held liablefor any direct, indirect, incidental, special or consequential damagesarising out of the use of or inability to use this software.

Permission is granted to anyone to use this software for any purpose,

including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:

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

2. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled.

3. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s).

4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases.

%% The following software may be included in this product: XML Security; Use of any of this software is governed by the terms of the license below:

The Apache Software License, Version 1.1 PDF

Copyright (C) 2002 The Apache SoftwareFoundation.

All rights reserved. Redistribution anduse in source and binary forms, with or withoutmodification, are permitted provided that thefollowing conditions are met:

1. Redistributions ofsource code must retain the above copyrightnotice, this list of conditions and the followingdisclaimer.

2. Redistributions in binary form mustreproduce the above copyright notice, this list of conditions and the following disclaimerin the documentation and/or other materialsprovided with the distribution.

3. The end-userdocumentation included with the redistribution, if any,must include the following acknowledgment:"This product includes software developed bythe Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment mayappear in the software itself, if and wherever suchthird-party acknowledgments normally appear.

4. The names"Apache Forrest" and "Apache SoftwareFoundation" must not be used to endorse or promoteproducts

derived from this software without priorwritten permission. For written permission,please contact [email protected]. 5. Products derivedfrom this software may not be called "Apache", normay "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED`ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND



FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache SoftwareFoundation, please see http://www.apache.org.










THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 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.

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


%% The following software may be included in this product: Visual Studio. Use of any of this software is governed by the terms of the license below:

END-USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE

IMPORTANT-READ CAREFULLY: This End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation ("Microsoft) for the Microsoft software that accompanies this EULA, which includes computer software and may include associated media, printed materials, "online" or electronic documentation, and Internet-based services ("Software"). An amendment or addendum to this EULA may accompany the Software. YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE. IF YOU DO NOT AGREE, DO NOT INSTALL, COPY, OR USE THE SOFTWARE; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE (IF APPLICABLE) FOR A FULL REFUND.

MICROSOFT SOFTWARE LICENSE

1. GRANTS OF LICENSE. Microsoft grants you the rights described in this EULA provided that you comply with all terms and conditions of this EULA. NOTE: Microsoft is not licensing to you any rights with respect to Crystal Reports for Microsoft Visual Studio .NET; your use of Crystal Reports for Microsoft Visual Studio .NET is subject to your acceptance of the terms and conditions of the enclosed (hard copy) end user license agreement from Crystal

Decisions for that product.

1.1 General License Grant. Microsoft grants to you as an individual, a personal, nonexclusive license to use the Software, and to make and use copies of the Software for the purposes of designing, developing, testing, and demonstrating your software product(s), provided that you are the only individual using the Software. If you are an entity, Microsoft grants to you a personal, nonexclusive license to use the Software, and to make and use copies of the Software, provided that for each individual using the Software within your organization, you have acquired a separate and valid license for each such individual.

1.2 Documentation. You may make and use an unlimited number of copies of any documentation, provided that such copies shall be used only for personal purposes and are not to be republished or distributed (either in hard copy or electronic form) beyond your premises.

1.3 Storage/Network Use. You may also store or install a copy of the Software on a storage device, such as a network server, used only to install or run the Software on computers used by licensed end users in accordance with Section 1.1. A single license for the Software may not be shared or used concurrently by multiple end users.



1.4 Visual Studio-Effect of EULA. As a suite of development tools and other Microsoft software programs (each such tool or software program, a "Component"), Components that you receive as part of the Software may include a separate end-user license agreement (each, a "Component EULA"). Except as provided in Section 4 ("Prerelease Code"), in the event of inconsistencies between this EULA and any Component EULA, the terms of this EULA shall control. The Software may also contain third-party software programs. Any such software is provided for your use as a convenience and your use is subject to the terms and conditions of any license agreement contained in that software.

2. ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition to the rights granted in Section 1, certain portions of the Software, as described in this Section 2, are provided to you with additional license rights. These additional license rights are conditioned Everett VSPro 1 Final 11.04.02 upon your compliance with the distribution requirements and license limitations described in

Section 3.

2.1 Sample Code. Microsoft grants you a limited, nonexclusive, royalty-free license to: (a) use and modify the source code version of those portions of the Software identified as "Samples" in REDIST.TXT or elsewhere in the Software ("Sample Code") for the sole purposes of designing, developing, and testing your software product(s), and (b) reproduce and distribute the Sample Code, along with any modifications thereof, in object and/or source code form. For applicable redistribution requirements for Sample Code, see Section 3.1 below.

2.2 Redistributable Code-General. Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the object code form of any portion of the Software listed in REDIST.TXT ("Redistributable Code"). For general redistribution requirements for Redistributable Code, see Section 3.1 below.

2.3 Redistributable Code-Microsoft Merge Modules ("MSM"). Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the content of MSM file(s) listed in REDIST.TXT in the manner described in the Software documentation only so long as you redistribute such content in its entirety and do not modify such content in any way.

For all other applicable redistribution requirements for MSM files, see Section 3.1 below.

2.4 Redistributable Code-Microsoft Foundation Classes (MFC), Active Template

Libraries (ATL), and C runtimes (CRTs). In addition to the rights granted in Section 1, Microsoft grants you a license to use and modify the source code version of those portions of the Software that are identified as MFC, ATL, or CRTs (collectively, the "VC Redistributables"), for the sole purposes of designing, developing, and testing your software product(s). Provided you comply with Section 3.1 and you rename any files created by you that are included in the Licensee Software (defined below), Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the object code version of the VC Redistributables, including any modifications you make. For purposes of this section, "modifications" shall mean enhancements to the functionality of the VC Redistributables. For all other applicable redistribution requirements for VC Redistributables, see Section 3.1 below.

3. DISTRIBUTION REQUIREMENTS AND OTHER LICENSE RIGHTS AND

LIMITATIONS. If you choose to exercise your rights under Section 2, any redistribution by you is subject to your compliance with Section 3.1; some of the Redistributable Code has additional limited use rights described in Section 3.2.

3.1 General Distribution Requirements.

(a) If you choose to redistribute Sample Code, or Redistributable Code (collectively, the "Redistributables") as described in Section 2, you agree: (i) except as otherwise noted in Section 2.1 (Sample Code), to distribute the Redistributables only in object code form and in conjunction with and as a part of a software application product developed by you that adds significant and primary functionality to the Redistributables ("Licensee Software");

(ii) that the Redistributables only operate in conjunction with Microsoft Windows platforms;

(iii) that if the Licensee Software is distributed beyond Licensee's premises or externally from

Licensee's organization, to distribute the Licensee Software containing the Redistributables pursuant to an end user license agreement (which may be "break-the-seal", "click-wrap" or signed), with terms no less protective than those contained in this EULA; (iv) not to use Microsoft's name, logo, or trademarks to market the Licensee Software; (v) to display your own valid copyright notice which shall be sufficient to protect Microsoft's copyright in the Software; Everett VSPro 2 Final 11.04.02

(vi) not to remove or obscure any copyright, trademark or patent notices that appear on the Software as delivered to you; (vii) to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the Licensee Software; (viii) to otherwise comply with the terms of this EULA; and (ix) agree that Microsoft reserves all rights not expressly granted. You also agree not to permit further distribution of the Redistributables by your end users except you may permit further redistribution of the Redistributables by your distributors to your end-user customers if your distributors only distribute the Redistributables in conjunction with, and as part of, the Licensee Software, you comply with all other terms of this EULA, and your distributors comply with all restrictions of this EULA that are applicable to you.

(b) If you use the Redistributables, then in addition to your compliance with the applicable distribution requirements described for the Redistributables, the following also applies. Your license rights to the Redistributables are conditioned upon your not (i) creating derivative works of the Redistributables in any manner that would cause the Redistributables in whole or in part to become subject to any of the terms of an Excluded License; or (ii) distributing the Redistributables (or derivative works thereof) in any manner that would cause

the Redistributables to become subject to any of the terms of an Excluded License. An "Excluded License" is any license that requires as a condition of use, modification and/or distribution of software subject to the Excluded License, that such software or other software combined and/or distributed with such software be (x) disclosed or distributed in source code form; (y) licensed for the purpose of making derivative works; or (z) redistributable at no charge.

3.2 Additional Distribution Requirements for Certain Redistributable Code.



If you choose to redistribute the files discussed in this Section, then in addition to the terms of Section 3.1, you must ALSO comply with the following.

(a) Microsoft SQL Server Desktop Engine ("MSDE"). If you redistribute MSDE you agree to comply with the following additional requirements: (a) Licensee Software shall not substantially duplicate the capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, compete with same; and (b) unless Licensee Software requires your customers to license Microsoft Access in order to operate, you shall not reproduce or use MSDE for commercial distribution in conjunction with a general purpose word processing, spreadsheet or database management software product, or an integrated work or product suite whose components include a general purpose word processing, spreadsheet, or database management software product except for the exclusive use of importing data to the various formats supported by Microsoft Access. A product that includes limited word processing, spreadsheet or database components along with other components which provide significant and primary value, such as an accounting product with limited spreadsheet capability, is not considered to be a "general purpose" product.

(b) Microsoft Data Access Components. If you redistribute the Microsoft

Data Access Component file identified as MDAC_TYP.EXE, you also agree to redistribute such file in object code only in conjunction with and as a part of a Licensee Software developed by you with a Microsoft development tool product that adds significant and primary functionality to MDAC_TYP.EXE. Everett VSPro 3 Final 11.04.02

3.3 Separation of Components. The Software is licensed as a single product. Its component parts may not be separated for use by more than one user.

3.4 Benchmark Testing. The Software may contain the Microsoft .NET Framework. You may not disclose the results of any benchmark test of the .NET Framework component of the Software to any third party without Microsoft's prior written approval.

4. PRERELEASE CODE. Portions of the Software may be identified as prerelease code

("Prerelease Code"). Such Prerelease Code is not at the level of performance and compatibility of the final, generally available product offering. The Prerelease Code may not operate correctly and may be substantially modified prior to first commercial shipment. Microsoft is not obligated to make this or any later version of the Prerelease Code commercially available. The grant of license to use Prerelease Code expires upon availability of a commercial release of the Prerelease Code from Microsoft. NOTE: In the event that Prerelease Code contains a separate end-user license agreement, the terms and conditions of such end-user license agreement shall govern your use of the corresponding Prerelease Code.

5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not

expressly granted to you in this EULA. The Software is protected by copyright and other intellectual property laws and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the Software. The Software is licensed, not sold.

6. LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND

DISASSEMBLY. You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

7. NO RENTAL/COMMERCIAL HOSTING. You may not rent, lease, lend or provide commercial hosting services with the Software.

8. CONSENT TO USE OF DATA. You agree that Microsoft and its affiliates may collect and use technical information gathered as part of the product support services provided to you, if any, related to the Software. Microsoft may use this information solely to improve our products or to provide customized services or technologies to you and will not disclose this information in a form that personally identifies you.

9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Software. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for the contents of any third party sites, any links contained in third party sites, or any changes or updates to third party sites. Microsoft is not responsible for webcasting or any other form of transmission received from any third party sites. Microsoft is providing these links to third party sites to you only as a convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party site.

10. ADDITIONAL SOFTWARE/SERVICES. This EULA applies to updates, supplements, add-on components, or Internet-based services components, of the Software that Microsoft may provide to you or make available to you after the date you obtain your initial copy of the Software, unless we provide other terms along with the update, supplement, add-on component, or Internet-based services component. Microsoft reserves the right to discontinue any Internet-based services provided to you or made available to you through the use of the Software.

11. UPGRADES/DOWNGRADES

Everett VSPro 4

Final 11.04.02

11.1 Upgrades. To use a version of the Software identified as an upgrade, you must first be licensed for the software identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the software that formed the basis for your upgrade eligibility.

11.2 Downgrades. Instead of installing and using the Software, you may install and use copies of an earlier version of the Software, provided that you completely remove such earlier version and install the current version of the Software within a reasonable time. Your use of such earlier version shall be governed by this EULA, and your rights to use such earlier version shall terminate when you install the Software.

11.3 Special Terms for Version 2003 Upgrade Editions of the Software. If the Software accompanying this EULA is the version 2003 edition of the Software and you have acquired it as an upgrade from the corresponding "2002" edition of the Microsoft software product with the same product name as the Software (the "Qualifying Software"), then Section 11.1 does not apply to you. Instead, you may continue to use the Qualifying Software AND the version 2003 upgrade for so long as you continue to comply with the terms of this EULA and the EULA governing your use of the Qualifying Software. Qualifying Software does not include non-Microsoft software products.



12. NOT FOR RESALE SOFTWARE. Software identified as "Not For Resale" or "NFR," may not be sold or otherwise transfered for value, or used for any purpose other than demonstration, test or evaluation.

13. ACADEMIC EDITION SOFTWARE. To use Software identified as "Academic Edition" or "AE," you must be a "Qualified Educational User." For qualification-related questions, please contact the Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399 or the Microsoft subsidiary serving your country.

14. EXPORT RESTRICTIONS. You acknowledge that the Software is subject to U.S. export jurisdiction. You agree to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end- use, and destination restrictions issued by U.S. and other governments. For additional information see <http://www.microsoft.com/exporting/>.

15. SOFTWARE TRANSFER. The initial user of the Software may make a one-time permanent transfer of this EULA and Software to another end user, provided the initial user retains no copies of the Software. This transfer must include all of the Software (including all component parts, the media and printed materials, any upgrades (including any Qualifying Software as defined in Section 11.3), this EULA, and, if applicable, the Certificate of Authenticity). The transfer may not be an indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the Software must agree to all the EULA terms.

16. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the Software and all of its component parts.

Everett VSPro 5

Final 11.04.02

17. LIMITED WARRANTY FOR SOFTWARE ACQUIRED IN THE US AND CANADA.

Except for the "Redistributables," which are provided AS IS without warranty of any kind, Microsoft warrants that the Software will perform substantially in accordance with the accompanying materials for a period of ninety (90) days from the date of receipt.

If an implied warranty or condition is created by your state/jurisdiction and federal or state/provincial law prohibits disclaimer of it, you also have an implied warranty or condition,

BUT ONLY AS TO DEFECTS DISCOVERED DURING THE PERIOD OF THIS LIMITED WARRANTY (NINETY DAYS). AS TO ANY DEFECTS DISCOVERED AFTER THE NINETY-DAY PERIOD, THERE IS NO WARRANTY OR CONDITION OF ANY KIND.

Some states/jurisdictions do not allow limitations on how long an implied warranty or condition lasts, so the above limitation may not apply to you.

Any supplements or updates to the Software, including without limitation, any (if any) service packs or hot fixes provided to you after the expiration of the ninety day Limited Warranty period are not covered by any warranty or condition, express, implied or statutory.

LIMITATION ON REMEDIES; NO CONSEQUENTIAL OR OTHER DAMAGES. Your exclusive remedy for any breach of this Limited Warranty is as set forth below. Except for any refund elected by

Microsoft, YOU ARE NOT ENTITLED TO ANY DAMAGES, INCLUDING BUT NOT LIMITED TO CONSEQUENTIAL DAMAGES, if the Software does not meet Microsoft's Limited Warranty, and, to the maximum extent allowed by applicable law, even if any remedy fails of its essential purpose. The terms of Section 19 ("Exclusion of Incidental, Consequential and Certain Other Damages") are also incorporated into this Limited Warranty. Some states/jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to you. This Limited Warranty gives you specific legal rights. You may have other rights which vary from state/jurisdiction to state/jurisdiction. YOUR EXCLUSIVE REMEDY. Microsoft's and its suppliers' entire liability and your exclusive remedy for any breach of this Limited Warranty or for any other breach of this EULA or for any other liability relating to the Software shall be, at Microsoft's option from time to time exercised subject to applicable law, (a) return of the amount paid (if any) for the Software, or (b) repair or replacement of the Software, that does not meet this Limited Warranty and that is returned to Microsoft with a copy of your receipt. You will receive the remedy elected by Microsoft without charge, except that you are responsible for any expenses you may incur (e.g. cost of shipping the Software to Microsoft). This Limited Warranty is void if failure of the Software has resulted from accident, abuse, misapplication, abnormal use or a virus. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer, and Microsoft will use commercially reasonable efforts to provide your remedy within a commercially reasonable time of your compliance with Microsoft's warranty remedy procedures. Outside the United States or Canada, neither these remedies nor any product support services offered by Microsoft are available without proof of purchase from an authorized international source. To exercise your remedy, contact: Microsoft, Attn. Microsoft Sales Information Center/One Microsoft

Way/Redmond, WA 98052-6399, or the Microsoft subsidiary serving your country.

18. DISCLAIMER OF WARRANTIES. The Limited Warranty that appears above is the only express warranty made to you and is provided in lieu of any other express warranties or similar obligations (if any) created by any advertising, documentation, packaging, or other communications. EXCEPT FOR THE LIMITED WARRANTY AND TO THE MAXIMUM

Everett VSPro 6

Final 11.04.02

EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND ITS SUPPLIERS PROVIDE THE SOFTWARE AND SUPPORT SERVICES (IF ANY) AS IS AND WITH ALL FAULTS, AND HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY (IF ANY) IMPLIED WARRANTIES, DUTIES OR CONDITIONS OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF RELIABILITY OR AVAILABILITY, OF ACCURACY OR COMPLETENESS OF RESPONSES, OF RESULTS, OF WORKMANLIKE EFFORT, OF LACK OF VIRUSES, AND OF LACK OF NEGLIGENCE, ALL WITH REGARD TO THE SOFTWARE, AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE.



19. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

20. LIMITATION OF LIABILITY AND REMEDIES. NOTWITHSTANDING ANY DAMAGES THAT YOU MIGHT INCUR FOR ANY REASON WHATSOEVER (INCLUDING, WITHOUT LIMITATION, ALL DAMAGES REFERENCED HEREIN AND ALL DIRECT OR GENERAL DAMAGES IN CONTRACT OR ANYTHING ELSE), THE ENTIRE LIABILITY OF MICROSOFT AND ANY OF ITS SUPPLIERS UNDER ANY PROVISION OF THIS EULA AND YOUR EXCLUSIVE REMEDY HEREUNDER (EXCEPT FOR ANY REMEDY OF REPAIR OR REPLACEMENT ELECTED BY MICROSOFT WITH RESPECT TO ANY BREACH OF THE LIMITED WARRANTY) SHALL BE LIMITED TO THE GREATER OF THE ACTUAL DAMAGES YOU INCUR IN REASONABLE RELIANCE ON THE SOFTWARE UP TO THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE OR US$5.00. THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS (INCLUDING SECTIONS 17, 18, AND 19) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.

Everett VSPro 7

Final 11.04.02

21. U.S. GOVERNMENT LICENSE RIGHTS. All Software provided to the U.S.

Government pursuant to solicitations issued on or after December 1, 1995 is provided with the commercial license rights and restrictions described elsewhere herein. All Software provided to the U.S. Government pursuant to solicitations issued prior to December 1, 1995 is provided with "Restricted Rights" as provided for in FAR, 48 CFR 52.227-14 (JUNE 1987) or DFAR, 48 CFR 252.227-7013 (OCT 1988), as applicable.

22. APPLICABLE LAW. If you acquired this Software in the United States, this EULA is governed by the laws of the State of Washington. If you acquired this Software in Canada, unless expressly prohibited by local law, this EULA is governed by the laws in force in the

Province of Ontario, Canada; and, in respect of any dispute which may arise hereunder, you consent to the jurisdiction of the federal and provincial courts sitting in Toronto, Ontario. If you acquired this Software in the European Union, Iceland, Norway, or Switzerland, then

local law applies. If you acquired this Software in any other country, then local law may apply.

23. ENTIRE AGREEMENT; SEVERABILITY. This EULA (including any addendum or amendment to this EULA which is included with the Software) are the entire agreement between you and Microsoft relating to the Software and the support services (if any) and they supersede all prior or contemporaneous oral or written communications, proposals and representations with respect to the Software or any other subject matter covered by this EULA. To the extent the terms of any Microsoft policies or programs for support services conflict with the terms of this EULA, the terms of this EULA shall control. If any provision of this EULA is held to be void, invalid, unenforceable or illegal, the other provisions shall continue in full force and effect.

Si vous avez acquis votre produit Microsoft au CANADA, la garantie limitée suivante s'applique :

GARANTIE LIMITÉE

Sauf pur celles du "Redistributables," qui sont fournies "comme telles," Microsoft garantit que le Logiciel fonctionnera conformément aux documents inclus pendant une période de 90 jours suivant la date de réception.

Si une garantie ou condition implicite est créée par votre État ou votre territoire et qu'une loifédérale ou provinciale ou d'un État en interdit le déni, vous jouissez également d'une garantie ou condition implicite, MAIS UNIQUEMENT POUR LES DÉFAUTS DÉCOUVERTS DURANT LA PÉRIODE DE LA PRÉSENTE GARANTIE LIMITÉE (QUATRE-VINGT-DIX

JOURS). IL N'Y A AUCUNE GARANTIE OU CONDITION DE QUELQUE NATURE QUECE SOIT QUANT AUX DÉFAUTS DÉCOUVERTS APRÈS CETTE PÉRIODE DE QUATRE- VINGT-DIX JOURS. Certains États ou territoires ne permettent pas de limiter la durée d'une garantie ou condition implicite de sorte que la limitation ci-dessus peut ne pas s'appliquer à vous.

Tous les suppléments ou toutes les mises à jour relatifs au Logiciel, notamment, les ensembles de services ou les réparations à chaud (le cas échéant) qui vous sont fournis après l'expiration de la période de quatre-vingt-dix jours de la garantie limitée ne sont pas couverts par quelque garantie ou condition que ce soit, expresse, implicite ou en vertu de la loi.

LIMITATION DES RECOURS; ABSENCE DE DOMMAGES INDIRECTS OU AUTRES.

Votre recours exclusif pour toute violation de la présente garantie limitée est décrit ci-après.

Sauf pour tout remboursement au choix de Microsoft, si le Logiciel ne respecte pas la

Everett VSPro 8

Final 11.04.02

garantie limitée de Microsoft et, dans la mesure maximale permise par les lois applicables, même si tout recours n'atteint pas son but essentiel, VOUS N'AVEZ DROIT À AUCUNS DOMMAGES, NOTAMMENT DES DOMMAGES INDIRECTS. Les termes de la clause "Exclusion des dommages accessoires, indirects et de certains autres dommages " sontégalement intégrées à la présente garantie limitée. Certains États ou territoires ne permettent pas l'exclusion ou



la limitation des dommages indirects ou accessoires de sorte que la limitation ou l'exclusion ci-dessus peut ne pas s'appliquer à vous. La présente garantie limitée vous donne des droits légaux spécifiques. Vous pouvez avoir d'autres droits qui peuvent varier d'unterritoire ou d'un État à un autre. VOTRE RECOURS EXCLUSIF. La seule responsabilité obligation de Microsoft et de ses fournisseurs et votre recours exclusif pour toute violation de la présente garantie limitée ou pour toute autre violation du présent contrat ou pour toute autre responsabilité relative au Logiciel seront, selon le choix de Microsoft exercé de temps à autre sous réserve de toute loi applicable, a) le remboursement du prix payé, le cas échéant, pour le Logiciel ou b) la réparation ou le remplacement du Logiciel qui ne respecte pas la présente garantie limitée et qui est retourné à Microsoft avec une copie de votre reçu. Vous recevrez la compensation choisie par Microsoft, sans frais, sauf que vous êtes responsable des dépenses que vous pourriez engager (p. ex., les frais d'envoi du Logiciel à Microsoft). La présente garantie limitée est nulle si la défectuosité du Logiciel est causée par un accident, un usage abusif, une mauvaise application, un usage anormal ou un virus. Tout Logiciel de remplacement sera garanti pour le reste de la période initiale de la garantie ou pendant trente (30) jours, selon la plus longue entre ces deux périodes. À l'extérieur des États-Unis ou du Canada, ces recours ou l'un quelconque des services de soutien technique offerts par Microsoft ne sont pas disponibles sans preuve d'achat d'une source internationale autorisée. Pour exercer votre recours, vous devez communiquer avec Microsoft et vous adresser au Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399, ou à la filiale de Microsoft de votre pays.

DÉNI DE GARANTIES. La garantie limitée qui apparaît ci-dessus constitue la seule garantie expresse qui vous est donnée et remplace toutes autres garanties expresses (s'il en est) crées par une publicité, un document, un emballage ou une autre communication. SAUF EN CE QUI A TRAIT À LA GARANTIE LIMITÉE ET DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, LE LOGICIEL ET LES SERVICES DE SOUTIEN TECHNIQUE (LE CAS ÉCHÉANT) SONT FOURNIS TELS QUELS ET AVEC TOUS LES DÉFAUTS PAR MICROSOFT ET SES FOURNISSEURS, LESQUELS PAR LES PRÉSENTES DÉNIENT TOUTES AUTRES GARANTIES ET CONDITIONS EXPRESSES, IMPLICITES OU EN VERTU DE LA LOI, NOTAMMENT, MAIS SANS LIMITATION, (LE CAS ÉCHÉANT) LESGARANTIES, DEVOIRS OU CONDITIONS IMPLICITES DE QUALITÉ MARCHANDE, D'ADAPTATION À UNE FIN PARTICULIÈRE, DE FIABILITÉ OU DE DISPONIBILITÉ, D'EXACTITUDE OU D'EXHAUSTIVITÉ DES RÉPONSES, DES RÉSULTATS, DES EFFORTS DÉPLOYÉS SELON LES RÈGLES DE L'ART, D'ABSENCE DE VIRUS ET D'ABSENCE DE NÉGLIGENCE, LE TOUT À L'ÉGARD DU LOGICIEL ET DE LA PRESTATION OU DE L'OMISSION DE LA PRESTATION DES SERVICES DE SOUTIEN TECHNIQUE OU À L'ÉGARD DE LA FOURNITURE OU DE L'OMISSION DE LA FOURNITURE DE TOUS AUTRES SERVICES, RENSEIGNEMENTS, LOGICIELS, ET CONTENU QUI S'Y RAPPORTE GRÂCE AU LOGICIEL OU PROVENANT AUTREMENT DE L'UTILISATION DU LOGICIEL . PAR AILLEURS, IL N'Y A AUCUNE GARANTIE OU CONDITION QUANT AU TITRE DE PROPRIÉTÉ, À LA JOUISSANCE OU LA POSSESSION PAISIBLE, À LA CONCORDANCE À UNE DESCRIPTION NI QUANT À UNE ABSENCE DE CONTREFAÇON CONCERNANT LE LOGICIEL.

EXCLUSION DES DOMMAGES ACCESSOIRES, INDIRECTS ET DE CERTAINS AUTRES DOMMAGES. DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, EN AUCUN CAS MICROSOFT OU SES FOURNISSEURS NE SERONT RESPONSABLES DES DOMMAGES SPÉCIAUX, CONSÉCUTIFS, ACCESSOIRES OU INDIRECTS DE

Everett VSPro 9

Final 11.04.02

QUELQUE NATURE QUE CE SOIT (NOTAMMENT, LES DOMMAGES À L'ÉGARD DUMANQUE À GAGNER OU DE LA DIVULGATION DE RENSEIGNEMENTS CONFIDENTIELS OU AUTRES, DE LA PERTE D'EXPLOITATION, DE BLESSURES CORPORELLES, DE LA VIOLATION DE LA VIE PRIVÉE, DE L'OMISSION DE REMPLIR TOUT DEVOIR, Y COMPRIS D'AGIR DE BONNE FOI OU D'EXERCER UN SOIN RAISONNABLE, DE LA NÉGLIGENCE ET DE TOUTE AUTRE PERTE PÉCUNIAIRE OU AUTRE PERTE DE QUELQUE NATURE QUE CE SOIT) SE RAPPORTANT DE QUELQUEMANIÈRE QUE CE SOIT À L'UTILISATION DU LOGICIEL OU À L'INCAPACITÉ DE S'EN SERVIR, À LA PRESTATION OU À L'OMISSION DE LA PRESTATION DE SERVICES DE SOUTIEN TECHNIQUE OU À LA FOURNITURE OU À L'OMISSION DE LA FOURNITURE DE TOUS AUTRES SERVICES, RENSEIGNEMENTS, LOGICIELS, ET CONTENU QUI S'Y RAPPORTE GRÂCE AU LOGICIEL OU PROVENANT AUTREMENT DE L'UTILISATION DU LOGICIEL OU AUTREMENT AUX TERMES DE TOUTE DISPOSITION DE LA PRÉSENTE CONVENTION OU RELATIVEMENT À UNE TELLE DISPOSITION, MÊME EN CAS DE FAUTE, DE DÉLIT CIVIL (Y COMPRIS LANÉGLIGENCE), DE RESPONSABILITÉ STRICTE, DE VIOLATION DE CONTRAT OU DEVIOLATION DE GARANTIE DE MICROSOFT OU DE TOUT FOURNISSEUR ET MÊME SI MICROSOFT OU TOUT FOURNISSEUR A ÉTÉ AVISÉ DE LA POSSIBILITÉ DE TELS DOMMAGES.

LIMITATION DE RESPONSABILITÉ ET RECOURS. MALGRÉ LES DOMMAGES QUE VOUS PUISSIEZ SUBIR POUR QUELQUE MOTIF QUE CE SOIT (NOTAMMENT, MAISSANS LIMITATION, TOUS LES DOMMAGES SUSMENTIONNÉS ET TOUS LES DOMMAGES DIRECTS OU GÉNÉRAUX OU AUTRES), LA SEULE RESPONSABILITÉ DE MICROSOFT ET DE L'UN OU L'AUTRE DE SES FOURNISSEURS AUX TERMES DE TOUTE DISPOSITION DE LA PRÉSENTE CONVENTION ET VOTRE RECOURS EXCLUSIF À L'ÉGARD DE TOUT CE QUI PRÉCÈDE (SAUF EN CE QUI CONCERNETOUT RECOURS DE RÉPARATION OU DE REMPLACEMENT CHOISI PAR MICROSOFT À L'ÉGARD DE TOUT MANQUEMENT À LA GARANTIE LIMITÉE) SELIMITE AU PLUS ÉLEVÉ ENTRE LES MONTANTS SUIVANTS : LE MONTANT QUE VOUS AVEZ RÉELLEMENT PAYÉ POUR LE LOGICIEL OU 5,00 $US. LES LIMITES,

EXCLUSIONS ET DÉNIS QUI PRÉCÈDENT (Y COMPRIS LES CLAUSES CI-DESSUS), S'APPLIQUENT DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, MÊME SI TOUT RECOURS N'ATTEINT PAS SON BUT ESSENTIEL.

À moins que cela ne soit prohibé par le droit local applicable, la présente Convention est régie par les lois de la province d'Ontario, Canada. Vous consentez à la compétence des tribunaux fédéraux et provinciaux siégeant à Toronto, dans la province d'Ontario.

Au cas où vous auriez des questions concernant cette licence ou que vous désiriez vous mettre en rapport avec Microsoft pour quelque raison que ce soit, veuillez utiliser l'information contenue dans le Logiciel pour contacter la filiale de Microsoft desservant votre pays, ou visitez Microsoft sur le World Wide Web à http://www.microsoft.com.

The following MICROSOFT GUARANTEE applies to you if you acquired this Software in any other country:

Statutory rights not affected -The following guarantee is not restricted to any territory and does not affect any statutory rights that you may have from your reseller or from Microsoft if you acquired the Software directly from Microsoft. If you acquired the Software or any support



services in Australia, New Zealand or Malaysia, please see the "Consumer rights" section below.

Everett VSPro 10

Final 11.04.02

The guarantee -The Software is designed and offered as a general-purpose software, not for any user's particular purpose. You accept that no Software is error free and you are strongly advised to back-up your files regularly. Provided that you have a valid license, Microsoft guarantees that a) for a period of 90 days from the date of receipt of your license to use the Software or the shortest period permitted by applicable law it will perform substantially in accordance with the written materials that accompany the Software; and b) any support services provided by Microsoft shall be substantially as described in applicable written materials provided to you by Microsoft and Microsoft support engineers will use reasonable efforts, care and skill to solve any problem issues. In the event that the Software fails to comply with this guarantee, Microsoft will either (a) repair or replace the Software or (b) return the price you paid. This guarantee is void if failure of the Software results from accident, abuse or misapplication. Any replacement Software will be guaranteed for the remainder of the original guarantee period or 30 days, whichever period is longer. You agree that the above guarantee is your sole guarantee in relation to the Software and any support services.

Exclusion of All Other Terms -To the maximum extent permitted by applicable law and subject to the guarantee above, Microsoft disclaims all warranties, conditions and other terms, either express or implied (whether by statute, common law, collaterally or otherwise) including but not limited to implied warranties of satisfactory quality and fitness for particular purpose with respect to the Software and the written materials that accompany the Software. Any implied warranties that cannot be excluded are limited to 90 days or to the shortest period permitted by applicable law, whichever is greater.

Limitation of Liability -To the maximum extent permitted by applicable law and except as provided in the Microsoft Guarantee, Microsoft and its suppliers shall not be liable for any damages whatsoever (including without limitation, damages for loss of business profits, business interruption, loss of business information or other pecuniary loss) arising out of the use or inability to use the Software, even if Microsoft has been advised of the possibility of such damages. In any case Microsoft's entire liability under any provision of this Agreement shall be limited to the amount actually paid by you for the Software. These limitations do not apply to any liabilities that cannot be excluded or limited by applicable laws.

Consumer rights -Consumers in Australia, New Zealand or Malaysia may have the benefit of certain rights and remedies by reason of the Trade Practices Act and similar state and territory laws in Australia, the Consumer Guarantees Act in New Zealand and the Consumer Protection Act in Malaysia in respect of which liability cannot lawfully be modified or excluded. If you acquired the Software in New Zealand for the purposes of a business, you confirm that the Consumer Guarantees Act does not apply. If you acquired the Software in Australia and if Microsoft breaches a condition or warranty implied under any law which cannot lawfully be modified or excluded by this agreement then, to the extent permitted by law, Microsoft's liability is limited, at Microsoft's option, to: (i) in the case of the Software: a) repairing or replacing the Software; or b) the cost of such repair or replacement; and (ii) in the case of support services: a) re-supply of the services; or b) the cost of having the services supplied again.

Everett VSPro 11

Final 11.04.02

Should you have any questions concerning this EULA, or if you desire to contact Microsoft for any reason, please use the address information enclosed in this Software to contact the Microsoft subsidiary serving your country or visit Microsoft on the World Wide Web at http://www.microsoft.com.

Everett VSPro 12

Final 11.04.02

%% The following software may be included in this product: zlib; Use of any of this software is governed by the terms of the license below:

zlib.h -- interface of the 'zlib' general purpose compression library version 1.1.3, July 9th, 1998

Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software

in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler [email protected] [email protected]

The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format

%% The following software may be included in this product: Mozilla Rhino. Use of any of this software is governed by the terms of the license below:

The contents of this file are subject to the Netscape 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/NPL/

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 Rhino code, released May 6, 1999.

The Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by Netscape are Copyright (C) 1997-2000 Netscape Communications Corporation. All Rights Reserved.

Contributor(s):



Kemal Bayram

Patrick Beard

Norris Boyd

Igor Bukanov, [email protected]

Brendan Eich

Ethan Hugg

Roger Lawrence

Terry Lucas

Mike McCabe

Milen Nankov

Attila Szegedi, [email protected]

Ian D. Stewart

Andi Vajda

Andrew Wason

%% The following software may be included in this product: Apache Derby. Use of any of this software is governed by the terms of the license below:

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/


1. Definitions.
















(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







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.






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.


THIRDPARTYREADME.txt

DO NOT TRANSLATE OR LOCALIZE.

%% The following software may be included in this product: CS CodeViewer v1.0; Use of any of this software is governed by the terms of the license below:

Copyright 1999 by CoolServlets.com.

Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this program... your comments will encourage further development!

This software is distributed under the terms of the BSD License.




Neither name of CoolServlets.com nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.



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

The following software may be included in this product: Crimson v1.1.1 ; Use of any of this software is governed by the terms of the license below:

The Apache Software License, Version 1.1 Copyright (c) 1999-2000 The Apache Software Foundation. All rights * reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:




4. The names "Crimson" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business

Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see <http://www.apache.org/>./

The following software may be included in this product: Xalan J2; Use of any of this software is governed by the terms of the license below:

Apache License

Version 2.0, January 2004



1. Definitions.









"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 owneror 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."









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.





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.









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.

%% The following software may be included in this product: NSIS 1.0j; Use of any of this software is governed by the terms of the license below:

Copyright (C) 1999-2000 Nullsoft, Inc.

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



3. This notice may not be removed or altered from any source distribution. Justin Frankel [email protected]"

%% Some Portions licensed from IBM are available at:

http://www.ibm.com/software/globalization/icu/

%% Portions Copyright Eastman Kodak Company 1992

%% Lucida is a registered trademark or trademark of Bigelow & Holmes in the U.S. and other countries.

%% Portions licensed from Taligent, Inc.

%% The following software may be included in this product:IAIK PKCS Wrapper; Use of any of this software is governed by the terms of the license below:

Copyright (c) 2002 Graz University of Technology. All rights reserved.





"This product includes software developed by IAIK of Graz University of Technology."


4. The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or promote products derived from this software without prior written permission.

5. Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name, without prior written permission of Graz University of Technology.

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

The following software may be included in this product: Document Object Model (DOM) v. Level 3; Use of any of this software is governed by the terms of the license below:


http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231

This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.

Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications:


2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the

W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.

3.Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKENO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THEUSE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.




The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

____________________________________

This formulation of W3C's notice and license became active on December 31 2002. This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous grant of "use". Otherwise, this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and

OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to [email protected].

%% The following software may be included in this product: Xalan, Xerces; Use of any of this software is governed by the terms of the license below: /* The Apache Software License, Version 1.1 Copyright (c) 1999-2003 The Apache Software Foundation. All rights * reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:




4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].


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

OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://www.apache.org

%% The following software may be included in this product: W3C XML Conformance Test Suites v. 20020606; Use of any of this software is governed by the terms of the license below:


Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is beingprovided by the copyright holders under the following license. By obtaining,using and/or copying this work, you (the licensee) agree that you have read,understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee orroyalty is hereby granted, provided that you include the following on ALL copiesof the software and documentation or portions thereof, including modifications,that you make:

1. The full text of this NOTICE in a location viewable to users of theredistributed or derivative work.

2. Any pre-existing intellectual property disclaimers, notices, or terms andconditions. If none exist, a short notice of the following form (hypertext ispreferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright Ã½Ã½ [$date-of-software] World WideWeb Consortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/"

3. Notice of any changes or modifications to the W3C files, including thedate changes were made. (We recommend you provide URIs to the location fromwhich the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKENO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITEDTO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THATTHE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTYPATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.




The name and trademarks of copyright holders may NOT be used in advertising orpublicity pertaining to the software without specific, written prior permission.Title to copyright in this software and any associated documentation will at alltimes remain with copyright holders.

____________________________________

This formulation of W3C's notice and license became active on August 14 1998 soas to improve compatibility with GPL. This version ensures that W3C softwarelicensing terms are no more restrictive than GPL and consequently W3C softwaremay be distributed in GPL packages. See the older formulation for the policyprior to this date. Please see our Copyright FAQ for common questions aboutusing materials from our site, including specific terms and conditions forpackages like libwww, Amaya, and Jigsaw. Other questions about this notice canbe directed to [email protected].

%% The following software may be included in this product: W3C XML Schema Test Collection v. 1.16.2; Use of any of this software is governed by the terms of the license below: W3C DOCUMENT NOTICE AND LICENSE

Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved.





2. The pre-existing copyright notice of the original author, or if it doesn'texist, a notice of the form: "Copyright [$date-of-document] World Wide WebConsortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but atextual representation is permitted.)







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


webmaster


%% The following software may be included in this product: Mesa 3-D graphics library v. 5; Use of any of this software is governed by the terms of the license below:

core Mesa code include/GL/gl.h Brian Paul

Mesa GLX driver include/GL/glx.h Brian Paul

Mesa Ext registry include/GL/glext.h SGI

SGI Free B include/GL/glxext.h

Mesa license:

The Mesa distribution consists of several components. Different copyrights andlicenses apply to different components. For example, GLUT is copyrighted by MarkKilgard, some demo programs are copyrighted by SGI, some of the Mesa devicedrivers are copyrighted by their authors. See below for a list of Mesa'scomponents and the copyright/license for each.

The core Mesa library is licensed according to the terms of the XFree86copyright (an MIT-style license). This allows integration with the XFree86/DRIproject. Unless otherwise stated, the Mesa source code and documentation islicensed as follows:

Copyright (C) 1999-2003 Brian Paul All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining acopy of this software and associated documentation files (the "Software"),to deal in the Software without restriction, including without limitationthe 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 includedin all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALLBRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER INAN 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.

SGI FREE SOFTWARE LICENSE B (Version 1.1 [02/22/2000])

1. Definitions.

1.1 "Additional Notice Provisions" means such additional provisions as appear in the Notice in Original Code under the heading "Additional Notice Provisions."

1.2 "Covered Code" means the Original Code or Modifications, or any combination thereof.

1.3 "Hardware" means any physical device that accepts input, processes input, stores the results of processing, and/or provides output.

1.4 "Larger Work" means a work that combines Covered Code or portions thereof with code not governed by the terms of this License.

1.5 "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.6 "License" means this document.

1.7 "Licensed Patents" means patent claims Licensable by SGI that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.

1.8 "Modifications" means any addition to or deletion from the substance or structure of the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to the contents of a file containing Original Code and/or addition to or deletion from the contents of a file containing previous Modifications.B. Any new file that contains any part of the Original Code or previous Modifications.

1.9 "Notice" means any notice in Original Code or Covered Code, as required by and in compliance with this License.

1.10 "Original Code" means source code of computer software code that is described in the source code Notice required by Exhibit A as Original Code, and updates and error corrections specifically thereto.

1.11 "Recipient" 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 8. For legal entities, "Recipient" includes any entity that controls, is controlled by, or is under common control with Recipient. For purposes of this definition, "control" of an entity means (a) the power, direct or indirect, to direct or

manage such entity, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.

1.12 "Recipient Patents" means patent claims Licensable by a Recipient that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.

1.13 "SGI" means Silicon Graphics, Inc.

1.14 "SGI Patents" means patent claims Licensable by SGI other than the Licensed Patents.2. License Grant and Restrictions.

2.1 SGI License Grant. Subject to the terms of this License and any third party intellectual property claims, for the duration of intellectual property protections inherent in the Original Code, SGI hereby grants Recipient a worldwide, royalty-free, non-exclusive license, to do the following: (i) under copyrights Licensable by SGI, to reproduce, distribute, create derivative works from, and, to the extent applicable, display and perform the Original Code and/or any Modifications provided by SGI alone and/or as part of a Larger Work; and (ii) under any Licensable Patents, to make, have made, use, sell, offer for sale, import and/or otherwise transfer the Original Code and/or any Modifications provided by SGI. Recipient accepts the terms and conditions of this License by undertaking any of the aforementioned actions. The patent license shall apply to the Covered Code if, at the time any related Modification is added, such addition of the Modification causes such combination to be covered by the Licensed Patents. The patent license in Section 2.1(ii) shall not apply to any other combinations that include the Modification. No patent license is provided under SGI Patents for infringements of SGI Patents by Modifications not provided by SGI or combinations of Original Code and Modifications not provided by SGI. 2.2 Recipient License Grant. Subject to the terms of this License and any third party intellectual property claims, Recipient hereby grants SGI and any other Recipients a worldwide, royalty-free, non-exclusive license, under any Recipient Patents, to make, have made, use, sell, offer for sale, import and/or otherwise transfer the Original Code and/or any Modifications provided by SGI.

2.3 No License For Hardware Implementations. The licenses granted in Section 2.1 and 2.2 are not applicable to implementation in Hardware of the algorithms embodied in the Original Code or any Modifications provided by SGI .

3. Redistributions.

3.1 Retention of Notice/Copy of License. The Notice set forth in Exhibit A, below, must be conspicuously retained or included in any and all redistributions of Covered Code. For distributions of the Covered Code in source code form, the Notice must appear in every file that can include a text comments field; in executable form, the Notice and a copy of this License must appear in related documentation or collateral where the Recipient's rights relating to Covered Code are described. Any Additional Notice Provisions which actually appears in the Original Code must also be retained or included in any and all redistributions of Covered Code.

3.2 Alternative License. Provided that Recipient is in compliance with the terms of this License, Recipient may, so long as without derogation of any of SGI's rights in and to the Original Code, distribute the source code and/or executable version(s) of Covered Code under (1) this License; (2) a license identical to this License but for only such changes as are necessary in order to clarify Recipient's role as licensor of Modifications; and/or (3) a license of Recipient's choosing, containing terms different from this License, provided that the license terms include this Section 3 and Sections 4, 6, 7, 10, 12, and 13, which terms may not be modified or superseded by any other terms of



such license. If Recipient elects to use any license other than this License, Recipient must make it absolutely clear that any of its terms which differ from this License are offered by Recipient alone, and not by SGI. It is emphasized that this License is a limited license, and, regardless of the license form employed by Recipient in accordance with this Section 3.2, Recipient may relicense only such rights, in Original Code and Modifications by SGI, as it has actually been granted by SGI in this License.

3.3 Indemnity. Recipient hereby agrees to indemnify SGI for any liability incurred by SGI as a result of any such alternative license terms Recipient offers.

4. Termination. This License and the rights granted hereunder will terminate automatically if Recipient breaches any term herein and fails to cure such breach within 30 days thereof. Any sublicense to the Covered Code that is properly granted shall survive any termination of this License, absent termination by the terms of such sublicense. Provisions that, by their nature, must remain in effect beyond the termination of this License, shall survive.

5. No Trademark Or Other Rights. This License does not grant any rights to: (i) any software apart from the Covered Code, nor shall any other rights or licenses not expressly granted hereunder arise by implication, estoppel or otherwise with respect to the Covered Code; (ii) any trade name, trademark or service mark whatsoever, including without limitation any related right for purposes of endorsement or promotion of products derived from the Covered Code, without prior written permission of SGI; or (iii) any title to or ownership of the Original Code, which shall at all times remains with SGI. All rights in the Original Code not expressly granted under this License are reserved.

6. Compliance with Laws; Non-Infringement. There are various worldwide laws, regulations, and executive orders applicable to dispositions of Covered Code, including without limitation export, re-export, and import control laws, regulations, and executive orders, of the U.S. government and other countries, and Recipient is reminded it is obliged to obey such laws, regulations, and executive orders. Recipient may not distribute Covered Code that (i) in any way infringes (directly or contributorily) any intellectual property rights of any kind of any other person or entity or (ii) breaches any representation or warranty, express, implied or statutory, to which, under any applicable law, it might be deemed to have been subject.

7. Claims of Infringement. If Recipient learns of any third party claim that any disposition of Covered Code and/or functionality wholly or partially infringes the third party's intellectual property rights, Recipient will promptly notify SGI of such claim.

8. Versions of the License. SGI may publish revised and/or new versions of the License from time to time, each with a distinguishing version number. Once Covered Code has been published under a particular version of the License, Recipient may, for the duration of the license, continue to use it under the terms of that version, or choose to use such Covered Code under the terms of any subsequent version published by SGI. Subject to the provisions of Sections 3 and 4 of this License, only SGI may modify the terms applicable to Covered Code created under this License.

9. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED "AS IS." ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS ARE DISCLAIMED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. SGI ASSUMES NO RISK AS TO THE QUALITY AND PERFORMANCE

OF THE SOFTWARE. SHOULD THE SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, SGI ASSUMES NO COST OR LIABILITY FOR SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY IS AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT SUBJECT TO THIS DISCLAIMER.

10. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES NOR LEGAL THEORY, WHETHER TORT (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE OR STRICT LIABILITY), CONTRACT, OR OTHERWISE, SHALL SGI OR ANY SGI LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, LOSS OF DATA, 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 SGI'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 THAT EXCLUSION AND LIMITATION MAY NOT APPLY TO RECIPIENT.

11. Indemnity. Recipient shall be solely responsible for damages arising, directly or indirectly, out of its utilization of rights under this License. Recipient will defend, indemnify and hold harmless Silicon Graphics, Inc. from and against any loss, liability, damages, costs or expenses (including the payment of reasonable attorneys fees) arising out of Recipient's use, modification, reproduction and distribution of the Covered Code or out of any representation or warranty made by Recipient.

12. U.S. Government End Users. The Covered Code is a "commercial item" consisting of "commercial computer software" as such terms are defined in title 48 of the Code of Federal Regulations and all U.S. Government End Users acquire only the rights set forth in this License and are subject to the terms of this License.

13. Miscellaneous. This License represents the complete agreement concerning the its subject matter. If any provision of this License is held to be unenforceable, such provision shall be reformed so as to achieve as nearly as possible the same legal and economic effect as the original provision and the remainder of this License will remain in effect. This License shall be governed by and construed in accordance with the laws of the United States and the State of California as applied to agreements entered into and to be performed entirely within California between California residents. Any litigation relating to this License shall be subject to the exclusive jurisdiction of the Federal Courts of the Northern District of California (or, absent subject matter jurisdiction in such courts, the courts of the State of California), with venue lying exclusively 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 that provides that the language of a contract shall be construed against the drafter shall not apply to this License.

Exhibit A

License Applicability. Except to the extent portions of this file are made subject to an alternative license as permitted in the SGI Free Software License B, Version 1.1 (the "License"), the contents of this file are subject only to the provisions of the License. You may not use this file



except in compliance with the License. You may obtain a copy of the License at Silicon Graphics, Inc., attn: Legal Services, 1600 Amphitheatre Parkway, Mountain View, CA 94043-1351, or at: http://oss.sgi.com/projects/FreeB

Note that, as provided in the License, the Software is distributed on an "AS IS" basis, with ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS DISCLAIMED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.Original Code. The Original Code is: [name of software, version number, and release date], developed by Silicon Graphics, Inc. The Original Code is Copyright (c) [dates of first publication, as appearing in the Notice in the Original Code] Silicon Graphics, Inc. Copyright in any portions created by third parties is as indicated elsewhere herein. All Rights Reserved.Additional Notice Provisions: [such additional provisions, if any, as appear in the Notice in the Original Code under the heading "Additional Notice Provisions"]

%% The following software may be included in this product: Byte Code Engineering Library (BCEL) v. 5; Use of any of this software is governed by the terms of the license below:

Apache Software License

/

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


Copyright (c) 2001 The Apache Software Foundation. Allrights reserved.

Redistribution and use in source and binary forms, withor without modification, are permitted provided that the followingconditions are met:

1. Redistributions of source code must retain the abovecopyright notice, this list of conditions and the followingdisclaimer.

2. Redistributions in binary form must reproduce theabove copyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.

3. The end-user documentation included with theredistribution, if any, must include the following acknowledgment:

"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in thesoftware itself, if and wherever such third-party acknowledgmentsnormally appear.

4. The names "Apache" and "Apache Software Foundation"and "Apache BCEL" must not be used to endorse or promoteproducts derived from this software without prior writtenpermission. For written permission, please contact [email protected].

5. Products derived from this software may not be called"Apache", "Apache BCEL", nor may "Apache" appear in their name,without prior written permission of the Apache SoftwareFoundation.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS

FOR A PARTICULAR PURPOSEARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWAREFOUNDATION 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) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

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

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org. /










THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 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.

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


%% The following software may be included in this product: CUP Parser Generator for Java v. 0.10k; Use of any of this software is governed by the terms of the license below: CUP Parser Generator Copyright Notice, License, and Disclaimer

Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided thatthe above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting documentation, and that the names of the authors or their employersnot be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to thissoftware, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for anyspecial, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract,negligence or other tortious action, arising out of or in connection withthe use or performance of this software.

%% The following software may be included in this product: JLex: A Lexical Analyzer Generator for Java v. 1.2.5; Use of any of this software is governed by the terms of the license below: JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.

Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright noticeappear in all copies and that both the copyright notice and this permission notice and warrantydisclaimer appear in supporting documentation, and that the name of the authors or their employersnot be used in advertising or publicity pertaining to distribution of the software withoutspecific, written prior permission.

The authors and their employers disclaim all warranties with regard to thissoftware, including all implied warranties of merchantability and fitness. In no event shall the authorsor their employers be liable for any special, indirect or consequential damages or any damageswhatsoever resulting from loss of use, data or profits, whether in an action of contract, negligenceor other tortious action, arising out of or in connection with the use or performance of thissoftware.

Java is a trademark of Sun Microsystems, Inc. References to the Java programminglanguage in relation to JLex are not meant to imply that Sun endorses this product.

%% The following software may be included in this product: SAX v. 2.0.1; Use of any of this software is governed by the terms of the license below: Copyright Status

SAX is free!

In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.

No Warranty

Because SAX is released to the public domain, there is no warranty for the design or for the software implementation, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide SAX "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 SAX is with you. Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.

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 SAX, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use SAX (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 SAX to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.

Copyright Disclaimers

This page includes statements to that effect by David Megginson, who would have been able to claim copyright for the original work.

SAX 1.0

Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of the XML-DEV mailing list, is hereby released into the public domain.

No one owns SAX: you may use it freely in both commercial and non-commercial applications, bundle it with your software distribution, include it on a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it in any other way you see fit.


1998-05-11

SAX 2.0

I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.


2000-05-05

%% The following software may be included in this product: Cryptix; Use of any of this software is governed by the terms of the license below:



Cryptix General License

Copyright Â© 1995-2003 The Cryptix Foundation Limited. All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions aremet:

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

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

THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) 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 OFTHE POSSIBILITY OF SUCH DAMAGE.

%% The following software may be included in this product: W3C XML Schema Test Collection; Use of any of this software is governed by the terms of the license below:

W3C® DOCUMENT NOTICE AND LICENSE

Copyright Â© 1994-2002 World Wide Web Consortium, (Massachusetts Institute ofTechnology, Institut National de Recherche en Informatique et en Automatique,Keio University). All Rights Reserved.





2. The pre-existing copyright notice of the original author, or if it doesn'texist, a notice of the form: "Copyright Â© [$date-of-document] World Wide WebConsortium, (Massachusetts Institute of Technology, Institut National deRecherche en Informatique et en Automatique, Keio University). All RightsReserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but atextual representation is permitted.)







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


webmaster


%% The following software may be included in this product: Stax API; Use of any of this software is governed by the terms of the license below:

Streaming API for XML (JSR-173) Specification

Reference Implementation

License Agreement

READ THE TERMS OF THIS (THE "AGREEMENT") CAREFULLY BEFORE VIEWING OR USING THESOFTWARE LICENSED HEREUNDER. BY VIEWING OR USING THE SOFTWARE, YOU AGREE TO THE TERMS OF THISAGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESETERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TOALL THESE TERMS, PROMPTLY RETURN THE



UNUSED SOFTWARE TO ORIGINAL CONTRIBUTOR, DEFINED HEREIN.

1.0 DEFINITIONS.

1.1. "BEA" means BEA Systems, Inc., the licensor of the Original Code.

1.2. "Contributor" means BEA and each entity that creates or contributes to thecreation of Modifications.

1.3. "Covered Code" means the Original Code or Modifications or the combinationof the Original Code and Modifications, in each case including portions thereof and corresponding documentation released with the source code.

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

1.5. "FCS" means first commercial shipment of a product.

1.6. "Modifications" means any addition to or deletion from the substance orstructure of either the Original Code or any previous Modifications. When Covered Code isreleased as a series of files, a Modification is:

(a) Any addition to or deletion from the contents of a file containing OriginalCode or previous Modifications.

(b) Any new file that contains any part of the Original Code or previousModifications.

1.7. "Original Code" means Source Code of computer software code ReferenceImplementation.

1.8. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,including without limitation, method, process, and apparatus claims, in any patent for whichthe grantor has the right to grant a license.

1.9. "Reference Implementation" means the prototype or "proof of concept"implementaÂtion of the Specification developed and made available for license by or on behalf of BEA.

1.10. "Source Code" means the preferred form of the Covered Code for makingmodifications to it, including all modules it contains, plus any associated documentation,interface definition files, scripts used to control compilation and installation of an Executable, orsource code differential comparisons against either the Original Code or another well known,available Covered Code of the Contributor's choice.

1.11. "Specification" means the written specification for the Streaming API forXML , Java technology developed pursuant to the Java Community Process.

1.12. "Technology Compatibility Kit" or "TCK" means the documentation, testingtools and test suites associated with the Specification as may be revised by BEA from time totime, that is provided so that an implementer of the SpecifiÂcation may determine if itsimplementation is compliant with the Specification.

1.13. "You" (or "Your") means an individual or a legal entity exercising rightsunder, and complying with all of the terms of, this Agreement or a future version of thisAgreement 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 theoutstanding shares or beneficial ownership of such entity.

2.0 SOURCE CODE LICENSE.

2.1. Copyright Grant. Subject to the terms of this Agreement, each Contributorhereby grants You a non-exclusive, worldwide, royalty-free copyright license to reproduce,prepare derivative works of, publicly display, publicly perform, distribute and sublicense theCovered Code of such Contributor, if any, and such derivative works, in Source Code andExecutable form.

2.2. Patent Grant. Subject to the terms of this Agreement, each Contributorhereby grants You a non-exclusive, worldwide, royalty-free patent license under the PatentClaims to make, use, sell, offer to sell, import and otherwise transfer the Covered Code preparedand provided by such Contributor, if any, in Source Code and Executable form. This patentlicense shall apply to the Covered Code if, at the time a Modification is added by the Contributor,such addition of the Modification causes such combination to be covered by the Patent Claims.The patent license shall not apply to any other combinations which include the Modification.

2.3. Conditions to Grants. You understand that although each Contributorgrants the licenses to the Covered Code prepared by it, no assurances are provided by anyContributor that the Covered Code does not infringe the patent or other intellectual property rights ofany other entity. Each Contributor disclaims any liability to You for claims brought by anyother entity based on infringement of intellectual property rights or otherwise. As a conditionto exercising the rights and licenses granted hereunder, You hereby assume sole responsibility to secure any other intellectual property rights needed, if any. For example, if a thirdparty patent license is required to allow You to distribute Covered Code, it is Your responsibility to acquire that license before distributing such code.

2.4. Contributors' Representation. Each Contributor represents that to itsknowledge it has sufficient copyright rights in the Covered Code it provides , if any, to grantthe copyright license set forth in this Agreement.

3.0 DISTRIBUION RESTRICTIONS.

3.1. Application of Agreement.

The Modifications which You create or to which You contribute are governed bythe terms of this Agreement, including without limitation Section 2.0. The Source Code versionof Covered Code may be distributed only under the terms of this Agreement or a future versionof this Agreement released under Section 6.1, and You must include a copy of this Agreementwith every copy of the Source Code You distribute. You may not offer or impose any terms on anySource Code version that alters or restricts the applicable version of this Agreement or therecipients' rights hereunder. However, You may include an additional document offering theadditional rights described in Section 3.3.

3.2. Description of Modifications.

You must cause all Covered Code to which You contribute to contain a filedocumenting the changes You made to create that Covered Code and the date of any change. You mustinclude a prominent statement that the Modification is derived, directly or indirectly, fromOriginal Code provided by BEA and including the name of BEA in (a) the Source Code, and (b) inany notice in an Executable version or related



documentation in which You describe the origin orownership ofthe Covered Code.

%% The following software may be included in this product: X Window System; Use of any of this software is governed by the terms of the license below:

Copyright The Open Group

Permission to use, copy, modify, distribute, and sell this software and itsdocumentation for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright noticeand this permission notice appear in supporting documentation.


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUPBE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OFCONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of The Open Group shall not be usedin advertising or otherwise to promote the sale, use or other dealings in thisSoftware without prior written authorization from The Open Group.

Portions also covered by other licenses as noted in the above URL.

%% The following software may be included in this product: dom4j v. 1.6; Use of any of this software is governed by the terms of the license below:

Redistribution and use of this software and associated documentation

("Software"), with or without modification, are permitted provided that thefollowing conditions are met:

1. Redistributions of source code must retain copyright statements andnotices. 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/orother materials provided with the distribution.

3. The name "DOM4J" must not be used to endorse or promote products derivedfrom this Software without prior written permission of MetaStuff, Ltd. Forwritten permission, please contact [email protected].

4. Products derived from this Software may not be called "DOM4J" nor may"DOM4J" appear in their names without prior written permission of MetaStuff,Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.

5. Due credit should be given to the DOM4J Project - http://www.dom4j.org

THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS `ÀS IS'' AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS

FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FORANY 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 ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights Reserved.

%% The following software may be included in this product: Retroweaver; Use of any of this software is governed by the terms of the license below:

Copyright (c) February 2004, Toby Reyelts





Neither the name of Toby Reyelts nor the names of his contributors may be used to endorse or promote products derived from this software without specific prior written permission.

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

%% The following software may be included in this product: stripper; Use of any of this software is governed by the terms of the license below:

Stripper : debug information stripper

Copyright (c) 2003 Kohsuke Kawaguchi







3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived fromthis software without specific prior written permission.

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

%% The following software may be included in this product: libpng official PNG reference library; Use of any of this software is governed by the terms of the license below:

This copy of the libpng notices is provided for your convenience. In case ofany discrepancy between this copy and the notices in the file png.h that isincluded in the libpng distribution, the latter shall prevail.

COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:

If you modify libpng you may insert additional notices immediately followingthis sentence.

libpng version 1.2.6, December 3, 2004, is Copyright (c) 2004 Glenn Randers-Pehrson, and is distributed according to the same disclaimer and license as libpng-1.2.5with the following individual added to the list of Contributing Authors

Cosmin Truta

libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following individuals added to the list of Contributing Authors

Simon-Pierre Cadieux

Eric S. Raymond

Gilles Vollant

and with the following additions to the disclaimer:

There is no warranty against interference with your enjoyment of the library or against infringement. There is no warranty that our efforts or the library will fulfill any of your particular purposes or needs. This library is provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with the user.

libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, areCopyright (c) 1998, 1999 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-0.96,with the following individuals added to the list of Contributing Authors:

Tom Lane


Willem van Schaik

libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (c) 1996, 1997 Andreas Dilger

Distributed according to the same disclaimer and license as libpng-0.88, with the following individuals added to the list of Contributing Authors:

John Bowler

Kevin Bracey

Sam Bushell

Magnus Holmgren

Greg Roelofs

Tom Tanner

libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.

For the purposes of this copyright and license, "Contributing Authors"is defined as the following set of individuals:

Andreas Dilger

Dave Martindale

Guy Eric Schalnat

Paul Schmidt

Tim Wegner

The PNG Reference Library is supplied "AS IS". The Contributing Authorsand Group 42, Inc. disclaim all warranties, expressed or implied, including, without limitation, the warranties of merchantability and offitness for any purpose. The Contributing Authors and Group 42, Inc. assume no liability for direct, indirect, incidental, special, exemplary,or consequential damages, which may result from the use of the PNG Reference Library, even if advised of the possibility of such damage.

Permission is hereby granted to use, copy, modify, and distribute thissource code, or portions hereof, for any purpose, without fee, subjectto the following restrictions:

1. The origin of this source code must not be misrepresented.

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

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



The Contributing Authors and Group 42, Inc. specifically permit, withoutfee, and encourage the use of this source code as a component to supporting the PNG file format in commercial products. If you use thissource code in a product, acknowledgment is not required but would be appreciated.

A "png_get_copyright" function is available, for convenient use in "about"boxes and the like:

printf("%s",png_get_copyright(NULL));

Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).

Libpng is OSI Certified Open Source Software. OSI Certified Open Source is acertification mark of the Open Source Initiative.


glennrp at users.sourceforge.net

December 3, 2004

%% The following software may be included in this product: Libungif - An uncompressed GIF library; Use of any of this software is governed by the terms of the license below:

The GIFLIB distribution is Copyright (c) 1997 Eric S. Raymond

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies 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 inall copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, 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 INTHE SOFTWARE.

%% The following software may be included in this product: Ant; Use of any of this software is governed by the terms of the license below:

License

The Apache Software License Version 2.0

The Apache Software License Version 2.0 applies to all releases of Ant startingwith ant 1.6.1

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.



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.





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] Apache Software Foundation 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./

You can download the original license file here.

The License is accompanied by a NOTICE

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

== NOTICE file corresponding to the section 4 d of ==

== the Apache License, Version 2.0, ==

== in this case for the Apache Ant distribution. ==

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

This product includes software developed by

The Apache Software Foundation (http://www.apache.org/).

This product includes also software developed by :

- the W3C consortium (http://www.w3c.org) ,

- the SAX project (http://www.saxproject.org)

Please read the different LICENSE files present in the root directory of this distribution.

The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].


The Apache Software License, Version 1.1, applies to all versions of up to ant1.6.0 included.

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



======================== The Apache Software License, Version 1.1 ============================================================================ Copyright (C) 2000-2003 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org./

%% The following software may be included in this product: XML Resolver library; Use of any of this software is governed by the terms of the license below:

Apache License




1. Definitions.



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









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



licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.





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













%% The following software may be included in this product: ICU4J; Use of any of this software is governed by the terms of the license below:

ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c)

1995-2003 International Business Machines Corporation and others All rightsreserved. Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the "Software"), todeal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, and/or sell copies ofthe Software, and to permit persons to whom the Software is furnished to do so,provided that the above copyright notice(s) and this permission notice appear inall copies of the Software and that both the above copyright notice(s) and thispermission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED"AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOTLIMITED TO



THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHTHOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANYSPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTINGFROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCEOR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of acopyright holder shall not be used in advertising or otherwise to promote thesale, use or other dealings in this Software without prior written authorizationof the copyright holder.

%% The following software may be included in this product: NekoHTML; Use of any of this software is governed by the terms of the license below:

The CyberNeko Software License, Version 1.0

(C) Copyright 2002,2003, Andy Clark. All rights reserved.





"This product includes software developed by Andy Clark."


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

5. Products derived from this software may not be called "CyberNeko", nor may "CyberNeko" appear in their name, without prior written permission of the author.

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

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

This license is based on the Apache Software License, version 1.1

%% The following software may be included in this product: Jing; Use of any of this software is governed by the terms of the license below:

Jing Copying Conditions

Copyright (c) 2001-2003 Thai Open Source Software Center Ltd



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

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

* Neither the name of the Thai Open Source Software Center Ltd nor the namesof its contributors may be used to endorse or promote products derived from thissoftware without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANYDIRECT, 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 ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


Copyright (c) 2000-2003 Daisuke Okajima and Kohsuke Kawaguchi.






"This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/)."




4. The names of the copyright holders must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact the copyright holders.

5. Products derived from this software may not be called "RELAXNGCC", nor may "RELAXNGCC" appear in their name, without prior written permission of the copyright holders.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 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.

%% The following software may be included in this product: RELAX NG Object Model/Parser; Use of any of this software is governed by the terms of the license below:

The MIT License

Copyright (c)

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


THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ORCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHERIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

%% The following software may be included in this product: XFree86-VidMode Extension; Use of any of this software is governed by the terms of the license below:

Version 1.1 of ProjectLicence.

Copyright (C) 1994-2004 The Project, Inc. All rights reserved.

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

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

2. Redistributions in binary form must reproduce the above copyrightnotice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution, and in thesame place and form as other copyright, license and disclaimer information. 3. The end-user documentation included with the redistribution, if any,must include the following acknowledgment: "This product includes softwaredeveloped by The XFree86 Project, Inc (http://www.xfree86.org/) and itscontributors", in the same place and form as other third-party acknowledgments.Alternately, this acknowledgment may appear in the software itself, in the sameform and location as other such third-party acknowledgments.

4. Except as contained in this notice, the name of The XFree86 Project,Inc shall not be used in advertising or otherwise to promote the sale, use orother dealings in this Software without prior written authorization from TheXFree86 Project, Inc.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE XFREE86PROJECT, INC 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; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.


This is version 2003-May-08 of the Info-ZIP copyright and license.

The definitive version of this document should be available at ftp://ftp.info-zip.org/pub/infozip/license.html indefinitely.

Copyright (c) 1990-2003 Info-ZIP. All rights reserved.

For the purposes of this copyright and license, "Info-ZIP" is defined asthe following set of individuals:

Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen,

Paul von Behren, Rich Wales, Mike White



This software is provided "as is," without warranty of any kind, expressor implied. In no event shall Info-ZIP or its contributors be held liablefor any direct, indirect, incidental, special or consequential damagesarising out of the use of or inability to use this software.

Permission is granted to anyone to use this software for any purpose,

including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:

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

2. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled.

3. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s).

4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases.

%% The following software may be included in this product: XML Security; Use of any of this software is governed by the terms of the license below:

The Apache Software License, Version 1.1 PDF

Copyright (C) 2002 The Apache SoftwareFoundation.

All rights reserved. Redistribution anduse in source and binary forms, with or withoutmodification, are permitted provided that thefollowing conditions are met:

1. Redistributions ofsource code must retain the above copyrightnotice, this list of conditions and the followingdisclaimer.

2. Redistributions in binary form mustreproduce the above copyright notice, this list of conditions and the following disclaimerin the documentation and/or other materialsprovided with the distribution.

3. The end-userdocumentation included with the redistribution, if any,must include the following acknowledgment:"This product includes software developed bythe Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment mayappear in the software itself, if and wherever suchthird-party acknowledgments normally appear.

4. The names"Apache Forrest" and "Apache SoftwareFoundation" must not be used to endorse or promoteproducts

derived from this software without priorwritten permission. For written permission,please contact [email protected]. 5. Products derivedfrom this software may not be called "Apache", normay "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED`ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache SoftwareFoundation, please see http://www.apache.org.












THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 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.

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


%% The following software may be included in this product: Visual Studio. Use of any of this software is governed by the terms of the license below:

END-USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE

IMPORTANT-READ CAREFULLY: This End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation ("Microsoft) for the Microsoft software that accompanies this EULA, which includes computer software and may include associated media, printed materials, "online" or electronic documentation, and Internet-based services ("Software"). An amendment or addendum to this EULA may accompany the Software. YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE. IF YOU DO NOT AGREE, DO NOT INSTALL, COPY, OR USE THE SOFTWARE; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE (IF APPLICABLE) FOR A FULL REFUND.

MICROSOFT SOFTWARE LICENSE

1. GRANTS OF LICENSE. Microsoft grants you the rights described in this EULA provided that you comply with all terms and conditions of this EULA. NOTE: Microsoft is not licensing to you any rights with respect to Crystal Reports for Microsoft Visual Studio .NET; your use of Crystal Reports for Microsoft Visual Studio .NET is subject to your acceptance of the terms and conditions of the enclosed (hard copy) end user license agreement from Crystal

Decisions for that product.

1.1 General License Grant. Microsoft grants to you as an individual, a personal, nonexclusive license to use the Software, and to make and use copies of the Software for the purposes of designing, developing, testing, and demonstrating your software product(s), provided that you are the only individual using the Software. If you are an entity, Microsoft grants to you a personal, nonexclusive license to use the Software, and to make and use copies of the Software, provided that for each individual using the Software within your organization, you have acquired a separate and valid license for each such individual.

1.2 Documentation. You may make and use an unlimited number of copies of any documentation, provided that such copies shall be used only for personal purposes and are not to be republished or distributed (either in hard copy or electronic form) beyond your premises.

1.3 Storage/Network Use. You may also store or install a copy of the Software on a storage device, such as a network server, used only to install or run the Software on computers used by licensed end users in accordance with Section 1.1. A single license for the Software may not be shared or used concurrently by multiple end users.

1.4 Visual Studio-Effect of EULA. As a suite of development tools and other Microsoft software programs (each such tool or software program, a "Component"), Components that you receive as part of the Software may include a separate end-user license agreement (each, a "Component EULA"). Except as provided in Section 4 ("Prerelease Code"), in the event of inconsistencies between this EULA and any Component EULA, the terms of this EULA shall control. The Software may also contain third-party software programs. Any such software is provided for your use as a convenience and your use is subject to the terms and conditions of any license agreement contained in that software.

2. ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition to the rights granted in Section 1, certain portions of the Software, as described in this Section 2, are provided to you with additional license rights. These additional license rights are conditioned

Everett VSPro 1

Final 11.04.02

upon your compliance with the distribution requirements and license limitations described in Section 3.

2.1 Sample Code. Microsoft grants you a limited, nonexclusive, royalty-free license to: (a) use and modify the source code version of those portions of the Software identified as

"Samples" in REDIST.TXT or elsewhere in the Software ("Sample Code") for the sole purposes of designing, developing, and testing your software product(s), and (b) reproduce and distribute the Sample Code, along with any modifications thereof, in object and/or source code form. For applicable redistribution requirements for Sample Code, see Section 3.1 below.

2.2 Redistributable Code-General. Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the object code form of any portion of the Software listed in REDIST.TXT ("Redistributable Code"). For general redistribution requirements for Redistributable Code, see Section 3.1 below.

2.3 Redistributable Code-Microsoft Merge Modules ("MSM"). Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the content of MSM file(s) listed in REDIST.TXT in the manner described in the Software documentation only so long as you redistribute such content in its entirety and do not modify such content in any way.

For all other applicable redistribution requirements for MSM files, see Section 3.1 below.

2.4 Redistributable Code-Microsoft Foundation Classes (MFC), Active Template Libraries (ATL), and C runtimes (CRTs). In addition to the rights granted in Section 1,



Microsoft grants you a license to use and modify the source code version of those portions of the Software that are identified as MFC, ATL, or CRTs (collectively, the "VC Redistributables"), for the sole purposes of designing, developing, and testing your software product(s). Provided you comply with Section 3.1 and you rename any files created by you that are included in the Licensee Software (defined below), Microsoft grants you a limited, nonexclusive, royalty-free license to reproduce and distribute the object code version of the VC Redistributables, including any modifications you make. For purposes of this section, "modifications" shall mean enhancements to the functionality of the VC Redistributables. For all other applicable redistribution requirements for VC Redistributables, see Section 3.1 below.

3. DISTRIBUTION REQUIREMENTS AND OTHER LICENSE RIGHTS AND

LIMITATIONS. If you choose to exercise your rights under Section 2, any redistribution by you is subject to your compliance with Section 3.1; some of the Redistributable Code has additional limited use rights described in Section 3.2.

3.1 General Distribution Requirements.

(a) If you choose to redistribute Sample Code, or Redistributable Code (collectively, the "Redistributables") as described in Section 2, you agree: (i) except as otherwise noted in Section 2.1 (Sample Code), to distribute the Redistributables only in object code form and in conjunction with and as a part of a software application product developed by you that adds significant and primary functionality to the Redistributables ("Licensee Software");

(ii) that the Redistributables only operate in conjunction with Microsoft Windows platforms;

(iii) that if the Licensee Software is distributed beyond Licensee's premises or externally from Licensee's organization, to distribute the Licensee Software containing the Redistributables pursuant to an end user license agreement (which may be "break-the-seal", "click-wrap" or signed), with terms no less protective than those contained in this EULA; (iv) not to use Microsoft's name, logo, or trademarks to market the Licensee Software; (v) to display your own valid copyright notice which shall be sufficient to protect Microsoft's copyright in the Software;

Everett VSPro 2

Final 11.04.02

(vi) not to remove or obscure any copyright, trademark or patent notices that appear on the Software as delivered to you; (vii) to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the Licensee Software; (viii) to otherwise comply with the terms of this EULA; and (ix) agree that Microsoft reserves all rights not expressly granted.

You also agree not to permit further distribution of the Redistributables by your end users except you may permit further redistribution of the Redistributables by your distributors to your end-user customers if your distributors only distribute the Redistributables in conjunction with, and as part of, the Licensee Software, you comply with all other terms of this EULA, and your distributors comply with all restrictions of this EULA that are applicable to you.

(b) If you use the Redistributables, then in addition to your compliance with the applicable distribution requirements described for the

Redistributables, the following also applies. Your license rights to the Redistributables are conditioned upon your not (i) creating derivative works of the Redistributables in any manner that would cause the Redistributables in whole or in part to become subject to any of the terms of an Excluded License; or (ii) distributing the Redistributables (or derivative works thereof) in any manner that would cause the Redistributables to become subject to any of the terms of an Excluded License. An "Excluded License" is any license that requires as a condition of use, modification and/or distribution of software subject to the Excluded License, that such software or other software combined and/or distributed with such software be (x) disclosed or distributed in source code form; (y) licensed for the purpose of making derivative works; or (z) redistributable at no charge.

3.2 Additional Distribution Requirements for Certain Redistributable Code.

If you choose to redistribute the files discussed in this Section, then in addition to the terms of Section 3.1, you must ALSO comply with the following.

(a) Microsoft SQL Server Desktop Engine ("MSDE"). If you redistribute MSDE you agree to comply with the following additional requirements: (a) Licensee Software shall not substantially duplicate the capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, compete with same; and (b) unless Licensee Software requires your customers to license Microsoft Access in order to operate, you shall not reproduce or use MSDE for commercial distribution in conjunction with a general purpose word processing, spreadsheet or database management software product, or an integrated work or product suite whose components include a general purpose word processing, spreadsheet, or database management software product except for the exclusive use of importing data to the various formats supported by Microsoft Access.

A product that includes limited word processing, spreadsheet or database components along with other components which provide significant and primary value, such as an accounting product with limited spreadsheet capability, is not considered to be a "general purpose" product.

(b) Microsoft Data Access Components. If you redistribute the Microsoft Data Access Component file identified as MDAC_TYP.EXE, you also agree to redistribute such file in object code only in conjunction with and as a part of a Licensee Software developed by you with a Microsoft development tool product that adds significant and primary functionality to MDAC_TYP.EXE.

Everett VSPro 3

Final 11.04.02

3.3 Separation of Components. The Software is licensed as a single product. Its component parts may not be separated for use by more than one user.

3.4 Benchmark Testing. The Software may contain the Microsoft .NET Framework.

You may not disclose the results of any benchmark test of the .NET Framework component of the Software to any third party without Microsoft's prior written approval.

4. PRERELEASE CODE. Portions of the Software may be identified as prerelease code ("Prerelease Code"). Such Prerelease Code is not at the level of performance and compatibility of the final, generally available product offering. The Prerelease Code may not operate



correctly and may be substantially modified prior to first commercial shipment. Microsoft is not obligated to make this or any later version of the Prerelease Code commercially available. The grant of license to use Prerelease Code expires upon availability of a commercial release of the Prerelease Code from Microsoft. NOTE: In the event that Prerelease Code contains a separate end-user license agreement, the terms and conditions of such end-user license agreement shall govern your use of the corresponding Prerelease Code.

5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to you in this EULA. The Software is protected by copyright and other intellectual property laws and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the Software. The Software is licensed, not sold.

6. LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND

DISASSEMBLY. You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

7. NO RENTAL/COMMERCIAL HOSTING. You may not rent, lease, lend or provide commercial hosting services with the Software.

8. CONSENT TO USE OF DATA. You agree that Microsoft and its affiliates may collect and use technical information gathered as part of the product support services provided to you, if any, related to the Software. Microsoft may use this information solely to improve our products or to provide customized services or technologies to you and will not disclose this information in a form that personally identifies you.

9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Software. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for the contents of any third party sites, any links contained in third party sites, or any changes or updates to third party sites. Microsoft is not responsible for webcasting or any other form of transmission received from any third party sites. Microsoft is providing these links to third party sites to you only as a convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party site.

10. ADDITIONAL SOFTWARE/SERVICES. This EULA applies to updates, supplements, add-on components, or Internet-based services components, of the Software that Microsoft may provide to you or make available to you after the date you obtain your initial copy of the Software, unless we provide other terms along with the update, supplement, add-on component, or Internet-based services component. Microsoft reserves the right to discontinue any Internet-based services provided to you or made available to you through the use of the Software.

11. UPGRADES/DOWNGRADES

Everett VSPro 4

Final 11.04.02

11.1 Upgrades. To use a version of the Software identified as an upgrade, you must first be licensed for the software identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the software that formed the basis for your upgrade eligibility.

11.2 Downgrades. Instead of installing and using the Software, you may install and use copies of an earlier version of the Software, provided that you completely remove such earlier version and install the current version of the Software within a reasonable time. Your use of such earlier version shall be governed by this EULA, and your rights to use such earlier version shall terminate when you install the Software.

11.3 Special Terms for Version 2003 Upgrade Editions of the Software. If the Software accompanying this EULA is the version 2003 edition of the Software and you have acquired it as an upgrade from the corresponding "2002" edition of the Microsoft software product with the same product name as the Software (the "Qualifying Software"), then Section 11.1 does not apply to you. Instead, you may continue to use the Qualifying Software AND the version 2003 upgrade for so long as you continue to comply with the terms of this EULA and the EULA governing your use of the Qualifying Software. Qualifying Software does not include non-Microsoft software products.

12. NOT FOR RESALE SOFTWARE. Software identified as "Not For Resale" or "NFR," may not be sold or otherwise transfered for value, or used for any purpose other than demonstration, test or evaluation.

13. ACADEMIC EDITION SOFTWARE. To use Software identified as "Academic Edition" or "AE," you must be a "Qualified Educational User." For qualification-related questions, please contact the Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399 or the Microsoft subsidiary serving your country.

14. EXPORT RESTRICTIONS. You acknowledge that the Software is subject to U.S. export jurisdiction. You agree to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end- use, and destination restrictions issued by U.S. and other governments. For additional information see <http://www.microsoft.com/exporting/>.

15. SOFTWARE TRANSFER. The initial user of the Software may make a one-time permanent transfer of this EULA and Software to another end user, provided the initial user retains no copies of the Software. This transfer must include all of the Software (including all component parts, the media and printed materials, any upgrades (including any Qualifying Software as defined in Section 11.3), this EULA, and, if applicable, the Certificate of Authenticity). The transfer may not be an indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the Software must agree to all the EULA terms.

16. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the Software and all of its component parts.

Everett VSPro 5

Final 11.04.02

17. LIMITED WARRANTY FOR SOFTWARE ACQUIRED IN THE US AND CANADA.

Except for the "Redistributables," which are provided AS IS without warranty of any kind, Microsoft warrants that the Software will perform substantially in accordance with the accompanying materials for a period of ninety (90) days from the date of receipt.

If an implied warranty or condition is created by your state/jurisdiction and federal or state/provincial law prohibits disclaimer of it, you also



have an implied warranty or condition, BUT ONLY AS TO DEFECTS DISCOVERED DURING THE PERIOD OF THIS LIMITED WARRANTY (NINETY DAYS). AS TO ANY DEFECTS DISCOVERED AFTER THE NINETY-DAY PERIOD, THERE IS NO WARRANTY OR CONDITION OF ANY KIND.

Some states/jurisdictions do not allow limitations on how long an implied warranty or condition lasts, so the above limitation may not apply to you. Any supplements or updates to the Software, including without limitation, any (if any) service packs or hot fixes provided to you after the expiration of the ninety day Limited Warranty period are not covered by any warranty or condition, express, implied or statutory.

LIMITATION ON REMEDIES; NO CONSEQUENTIAL OR OTHER DAMAGES. Your exclusive remedy for any breach of this Limited Warranty is as set forth below. Except for any refund elected by Microsoft, YOU ARE NOT ENTITLED TO ANY DAMAGES, INCLUDING BUT NOT LIMITED TO CONSEQUENTIAL DAMAGES, if the Software does not meet Microsoft's Limited Warranty, and, to the maximum extent allowed by applicable law, even if any remedy fails of its essential purpose. The terms of Section 19 ("Exclusion of Incidental, Consequential and Certain Other Damages") are also incorporated into this Limited Warranty. Some states/jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to you. This Limited Warranty gives you specific legal rights. You may have other rights which vary from state/jurisdiction to state/jurisdiction. YOUR EXCLUSIVE REMEDY. Microsoft's and its suppliers' entire liability and your exclusive remedy for any breach of this Limited Warranty or for any other breach of this EULA or for any other liability relating to the Software shall be, at Microsoft's option from time to time exercised subject to applicable law, (a) return of the amount paid (if any) for the Software, or (b) repair or replacement of the Software, that does not meet this Limited Warranty and that is returned to Microsoft with a copy of your receipt. You will receive the remedy elected by Microsoft without charge, except that you are responsible for any expenses you may incur (e.g. cost of shipping the Software to Microsoft). This Limited Warranty is void if failure of the Software has resulted from accident, abuse, misapplication,

abnormal use or a virus. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer, and Microsoft will use commercially reasonable efforts to provide your remedy within a commercially reasonable time of your compliance with Microsoft's warranty remedy procedures. Outside the United States or Canada, neither these remedies nor any product support services offered by Microsoft are available without proof of purchase from an authorized international source. To exercise your remedy, contact: Microsoft, Attn. Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399, or the Microsoft subsidiary serving your country.

18. DISCLAIMER OF WARRANTIES. The Limited Warranty that appears above is the only express warranty made to you and is provided in lieu of any other express warranties or similar obligations (if any) created by any advertising, documentation, packaging, or other communications. EXCEPT FOR THE LIMITED WARRANTY AND TO THE MAXIMUM Everett VSPro 6

Final 11.04.02

EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND ITS SUPPLIERS PROVIDE THE SOFTWARE AND SUPPORT SERVICES (IF ANY) AS IS AND WITH ALL FAULTS, AND HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY (IF ANY) IMPLIED WARRANTIES, DUTIES

OR CONDITIONS OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF RELIABILITY OR AVAILABILITY, OF ACCURACY OR COMPLETENESS OF RESPONSES, OF RESULTS, OF WORKMANLIKE EFFORT, OF LACK OF VIRUSES, AND OF LACK OF NEGLIGENCE, ALL WITH REGARD TO THE SOFTWARE, AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE.

19. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATION, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

20. LIMITATION OF LIABILITY AND REMEDIES. NOTWITHSTANDING ANY DAMAGES THAT YOU MIGHT INCUR FOR ANY REASON WHATSOEVER (INCLUDING, WITHOUT LIMITATION, ALL DAMAGES REFERENCED HEREIN AND ALL DIRECT OR GENERAL DAMAGES IN CONTRACT OR ANYTHING ELSE), THE ENTIRE LIABILITY OF MICROSOFT AND ANY OF ITS SUPPLIERS UNDER ANY PROVISION OF THIS EULA AND YOUR EXCLUSIVE REMEDY HEREUNDER (EXCEPT FOR ANY REMEDY OF REPAIR OR REPLACEMENT ELECTED BY MICROSOFT WITH RESPECT TO ANY BREACH OF THE LIMITED WARRANTY) SHALL BE LIMITED TO THE GREATER OF THE ACTUAL DAMAGES YOU INCUR IN REASONABLE RELIANCE ON THE SOFTWARE UP TO THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE OR US$5.00. THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS (INCLUDING SECTIONS 17, 18, AND 19) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.

Everett VSPro 7

Final 11.04.02

21. U.S. GOVERNMENT LICENSE RIGHTS. All Software provided to the U.S. Government pursuant to solicitations issued on or after December 1, 1995 is provided with the commercial license rights and restrictions described elsewhere herein. All Software provided to the U.S. Government pursuant to solicitations issued prior to December 1, 1995 is provided with "Restricted Rights" as provided for in FAR, 48



CFR 52.227-14 (JUNE 1987) or DFAR, 48 CFR 252.227-7013 (OCT 1988), as applicable.

22. APPLICABLE LAW. If you acquired this Software in the United States, this EULA is governed by the laws of the State of Washington. If you acquired this Software in Canada, unless expressly prohibited by local law, this EULA is governed by the laws in force in the Province of Ontario, Canada; and, in respect of any dispute which may arise hereunder, you consent to the jurisdiction of the federal and provincial courts sitting in Toronto, Ontario. If you acquired this Software in the European Union, Iceland, Norway, or Switzerland, then local law applies. If you acquired this Software in any other country, then local law may apply.

23. ENTIRE AGREEMENT; SEVERABILITY. This EULA (including any addendum or amendment to this EULA which is included with the Software) are the entire agreement between you and Microsoft relating to the Software and the support services (if any) and they supersede all prior or contemporaneous oral or written communications, proposals and representations with respect to the Software or any other subject matter covered by this EULA. To the extent the terms of any Microsoft policies or programs for support services conflict with the terms of this EULA, the terms of this EULA shall control. If any provision of this EULA is held to be void, invalid, unenforceable or illegal, the other provisions shall continue in full force and effect.

Si vous avez acquis votre produit Microsoft au CANADA, la garantie limitée suivante s'applique :

GARANTIE LIMITÉE

Sauf pur celles du "Redistributables," qui sont fournies "comme telles," Microsoft garantit que le Logiciel fonctionnera conformément aux documents inclus pendant une période de 90 jours suivant la date de réception.

Si une garantie ou condition implicite est créée par votre État ou votre territoire et qu'une loifédérale ou provinciale ou d'un État en interdit le déni, vous jouissez également d'une garantie ou condition implicite, MAIS UNIQUEMENT POUR LES DÉFAUTS DÉCOUVERTS DURANT LA PÉRIODE DE LA PRÉSENTE GARANTIE LIMITÉE (QUATRE-VINGT-DIX JOURS). IL N'Y A AUCUNE GARANTIE OU CONDITION DE QUELQUE NATURE QUECE SOIT QUANT AUX DÉFAUTS DÉCOUVERTS APRÈS CETTE PÉRIODE DE QUATRE- VINGT-DIX JOURS. Certains États ou territoires ne permettent pas de limiter la durée d'une garantie ou condition implicite de sorte que la limitation ci-dessus peut ne pas s'appliquer à vous.

Tous les suppléments ou toutes les mises à jour relatifs au Logiciel, notamment, les ensembles de services ou les réparations à chaud (le cas échéant) qui vous sont fournis après l'expiration de la période de quatre-vingt-dix jours de la garantie limitée ne sont pas couverts par quelque garantie ou condition que ce soit, expresse, implicite ou en vertu de la loi.

LIMITATION DES RECOURS; ABSENCE DE DOMMAGES INDIRECTS OU AUTRES.

Votre recours exclusif pour toute violation de la présente garantie limitée est décrit ci-après.

Sauf pour tout remboursement au choix de Microsoft, si le Logiciel ne respecte pas la Everett VSPro 8

Final 11.04.02

garantie limitée de Microsoft et, dans la mesure maximale permise par les lois applicables, même si tout recours n'atteint pas son but essentiel, VOUS N'AVEZ DROIT À AUCUNS DOMMAGES, NOTAMMENT DES DOMMAGES INDIRECTS. Les termes de la clause "Exclusion des dommages accessoires, indirects et de certains autres dommages " sontégalement intégrées à la présente garantie limitée. Certains États ou territoires ne permettent pas l'exclusion ou la limitation des dommages indirects ou accessoires de sorte que la limitation ou l'exclusion ci-dessus peut ne pas s'appliquer à vous. La présente garantie limitée vous donne des droits légaux spécifiques. Vous pouvez avoir d'autres droits qui peuvent varier d'unterritoire ou d'un État à un autre. VOTRE RECOURS EXCLUSIF. La seule responsabilité obligation de Microsoft et de ses fournisseurs et votre recours exclusif pour toute violation de la présente garantie limitée ou pour toute autre violation du présent contrat ou pour toute autre responsabilité relative au Logiciel seront, selon le choix de Microsoft exercé de temps à autre sous réserve de toute loi applicable, a) le remboursement du prix payé, le cas échéant, pour le Logiciel ou b) la réparation ou le remplacement du Logiciel qui ne respecte pas la présente garantie limitée et qui est retourné à Microsoft avec une copie de votre reçu. Vous recevrez la compensation choisie par Microsoft, sans frais, sauf que vous êtes responsable des dépenses que vous pourriez engager (p. ex., les frais d'envoi du Logiciel à Microsoft). La présente garantie limitée est nulle si la défectuosité du Logiciel est causée par un accident, un usage abusif, une mauvaise application, un usage anormal ou un virus. Tout Logiciel de remplacement sera garanti pour le reste de la période initiale de la garantie ou pendant trente (30) jours, selon la plus longue entre ces deux périodes. À l'extérieur des États-Unis ou du Canada, ces recours ou l'un quelconque des services de soutien technique offerts par Microsoft ne sont pas disponibles sans preuve d'achat d'une source internationale autorisée. Pour exercer votre recours, vous devez communiquer avec Microsoft et vous adresser au Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 98052-6399, ou à la filiale de Microsoft de votre pays.

DÉNI DE GARANTIES. La garantie limitée qui apparaît ci-dessus constitue la seule garantie expresse qui vous est donnée et remplace toutes autres garanties expresses (s'il en est) crées par une publicité, un document, un emballage ou une autre communication. SAUF EN CE QUI A TRAIT À LA GARANTIE LIMITÉE ET DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, LE LOGICIEL ET LES SERVICES DE SOUTIEN TECHNIQUE (LE CAS ÉCHÉANT) SONT FOURNIS TELS QUELS ET AVEC TOUS LES DÉFAUTS PAR MICROSOFT ET SES FOURNISSEURS, LESQUELS PAR LES PRÉSENTES DÉNIENT TOUTES AUTRES GARANTIES ET CONDITIONS EXPRESSES, IMPLICITES OU EN VERTU DE LA LOI, NOTAMMENT, MAIS SANS LIMITATION, (LE CAS ÉCHÉANT) LESGARANTIES, DEVOIRS OU CONDITIONS IMPLICITES DE QUALITÉ MARCHANDE, D'ADAPTATION À UNE FIN PARTICULIÈRE, DE FIABILITÉ OU DE DISPONIBILITÉ, D'EXACTITUDE OU D'EXHAUSTIVITÉ DES RÉPONSES, DES RÉSULTATS, DES EFFORTS DÉPLOYÉS SELON LES RÈGLES DE L'ART, D'ABSENCE DE VIRUS ET D'ABSENCE DE NÉGLIGENCE, LE TOUT À L'ÉGARD DU LOGICIEL ET DE LA PRESTATION OU DE L'OMISSION DE LA PRESTATION DES SERVICES DE SOUTIEN TECHNIQUE OU À L'ÉGARD DE LA FOURNITURE OU DE L'OMISSION DE LA FOURNITURE DE TOUS AUTRES SERVICES, RENSEIGNEMENTS, LOGICIELS, ET CONTENU QUI S'Y RAPPORTE GRÂCE AU LOGICIEL OU PROVENANT AUTREMENT DE L'UTILISATION DU LOGICIEL . PAR AILLEURS, IL N'Y A AUCUNE GARANTIE OU CONDITION QUANT AU TITRE DE PROPRIÉTÉ, À LA JOUISSANCE OU LA POSSESSION PAISIBLE, À LA CONCORDANCE À UNE DESCRIPTION NI QUANT À UNE ABSENCE DE CONTREFAÇON CONCERNANT LE LOGICIEL.



EXCLUSION DES DOMMAGES ACCESSOIRES, INDIRECTS ET DE CERTAINS AUTRES DOMMAGES. DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, EN AUCUN CAS MICROSOFT OU SES FOURNISSEURS NE SERONT RESPONSABLES DES DOMMAGES SPÉCIAUX, CONSÉCUTIFS, ACCESSOIRES OU INDIRECTS DE

Everett VSPro 9

Final 11.04.02

QUELQUE NATURE QUE CE SOIT (NOTAMMENT, LES DOMMAGES À L'ÉGARD DUMANQUE À GAGNER OU DE LA DIVULGATION DE RENSEIGNEMENTS CONFIDENTIELS OU AUTRES, DE LA PERTE D'EXPLOITATION, DE BLESSURES CORPORELLES, DE LA VIOLATION DE LA VIE PRIVÉE, DE L'OMISSION DE REMPLIR TOUT DEVOIR, Y COMPRIS D'AGIR DE BONNE FOI OU D'EXERCER UN SOIN RAISONNABLE, DE LA NÉGLIGENCE ET DE TOUTE AUTRE PERTE PÉCUNIAIRE OU AUTRE PERTE DE QUELQUE NATURE QUE CE SOIT) SE RAPPORTANT DE QUELQUEMANIÈRE QUE CE SOIT À L'UTILISATION DU LOGICIEL OU À L'INCAPACITÉ DE S'EN SERVIR, À LA PRESTATION OU À L'OMISSION DE LA PRESTATION DE SERVICES DE SOUTIEN TECHNIQUE OU À LA FOURNITURE OU À L'OMISSION DE LA FOURNITURE DE TOUS AUTRES SERVICES, RENSEIGNEMENTS, LOGICIELS, ET CONTENU QUI S'Y RAPPORTE GRÂCE AU LOGICIEL OU PROVENANT AUTREMENT DE L'UTILISATION DU LOGICIEL OU AUTREMENT AUX TERMES DE TOUTE DISPOSITION DE LA PRÉSENTE CONVENTION OU RELATIVEMENT À UNE TELLE DISPOSITION, MÊME EN CAS DE FAUTE, DE DÉLIT CIVIL (Y COMPRIS LANÉGLIGENCE), DE RESPONSABILITÉ STRICTE, DE VIOLATION DE CONTRAT OU DEVIOLATION DE GARANTIE DE MICROSOFT OU DE TOUT FOURNISSEUR ET MÊME SI MICROSOFT OU TOUT FOURNISSEUR A ÉTÉ AVISÉ DE LA POSSIBILITÉ DE TELS DOMMAGES.

LIMITATION DE RESPONSABILITÉ ET RECOURS. MALGRÉ LES DOMMAGES QUE VOUS PUISSIEZ SUBIR POUR QUELQUE MOTIF QUE CE SOIT (NOTAMMENT, MAISSANS LIMITATION, TOUS LES DOMMAGES SUSMENTIONNÉS ET TOUS LES DOMMAGES DIRECTS OU GÉNÉRAUX OU AUTRES), LA SEULE RESPONSABILITÉ DE MICROSOFT ET DE L'UN OU L'AUTRE DE SES FOURNISSEURS AUX TERMES DE TOUTE DISPOSITION DE LA PRÉSENTE CONVENTION ET VOTRE RECOURS EXCLUSIF À L'ÉGARD DE TOUT CE QUI PRÉCÈDE (SAUF EN CE QUI CONCERNETOUT RECOURS DE RÉPARATION OU DE REMPLACEMENT CHOISI PAR MICROSOFT À L'ÉGARD DE TOUT MANQUEMENT À LA GARANTIE LIMITÉE) SELIMITE AU PLUS ÉLEVÉ ENTRE LES MONTANTS SUIVANTS : LE MONTANT QUE VOUS AVEZ RÉELLEMENT PAYÉ POUR LE LOGICIEL OU 5,00 $US. LES LIMITES, EXCLUSIONS ET DÉNIS QUI PRÉCÈDENT (Y COMPRIS LES CLAUSES CI-DESSUS), S'APPLIQUENT DANS LA MESURE MAXIMALE PERMISE PAR LES LOIS APPLICABLES, MÊME SI TOUT RECOURS N'ATTEINT PAS SON BUT ESSENTIEL.

À moins que cela ne soit prohibé par le droit local applicable, la présente Convention est régie par les lois de la province d'Ontario, Canada. Vous consentez à la compétence des tribunaux fédéraux et provinciaux siégeant à Toronto, dans la province d'Ontario.

Au cas où vous auriez des questions concernant cette licence ou que vous désiriez vous mettre en rapport avec Microsoft pour quelque raison que ce soit, veuillez utiliser l'information contenue dans le Logiciel pour contacter la filiale de Microsoft desservant votre pays, ou visitez Microsoft sur le World Wide Web à http://www.microsoft.com.

The following MICROSOFT GUARANTEE applies to you if you acquired this Software in any other country:

Statutory rights not affected -The following guarantee is not restricted to any territory and does not affect any statutory rights that you may have from your reseller or from Microsoft if you acquired the Software directly from Microsoft. If you acquired the Software or any support services in Australia, New Zealand or Malaysia, please see the "Consumer rights" section below.

Everett VSPro 10

Final 11.04.02

The guarantee -The Software is designed and offered as a general-purpose software, not for any user's particular purpose. You accept that no Software is error free and you are strongly advised to back-up your files regularly. Provided that you have a valid license, Microsoft guarantees that a) for a period of 90 days from the date of receipt of your license to use the Software or the shortest period permitted by applicable law it will perform substantially in accordance with the written materials that accompany the Software; and b) any support services provided by Microsoft shall be substantially as described in applicable written materials provided to you by Microsoft and Microsoft support engineers will use reasonable efforts, care and skill to solve any problem issues. In the event that the Software fails to comply with this guarantee, Microsoft will either (a) repair or replace the Software or (b) return the price you paid. This guarantee is void if failure of the Software results from accident, abuse or misapplication. Any replacement Software will be guaranteed for the remainder of the original guarantee period or 30 days, whichever period is longer. You agree that the above guarantee is your sole guarantee in relation to the Software and any support services.

Exclusion of All Other Terms -To the maximum extent permitted by applicable law and subject to the guarantee above, Microsoft disclaims all warranties, conditions and other terms, either express or implied (whether by statute, common law, collaterally or otherwise) including but not limited to implied warranties of satisfactory quality and fitness for particular purpose with respect to the Software and the written materials that accompany the Software. Any implied warranties that cannot be excluded are limited to 90 days or to the shortest period permitted by applicable law, whichever is greater.

Limitation of Liability -To the maximum extent permitted by applicable law and except as provided in the Microsoft Guarantee, Microsoft and its suppliers shall not be liable for any damages whatsoever (including without limitation, damages for loss of business profits, business interruption, loss of business information or other pecuniary loss) arising out of the use or inability to use the Software, even if Microsoft has been advised of the possibility of such damages. In any case Microsoft's entire liability under any provision of this Agreement shall be limited to the amount actually paid by you for the Software. These limitations do not apply to any liabilities that cannot be excluded or limited by applicable laws.

Consumer rights -Consumers in Australia, New Zealand or Malaysia may have the benefit of certain rights and remedies by reason of the Trade Practices Act and similar state and territory laws in Australia, the Consumer Guarantees Act in New Zealand and the Consumer Protection Act in Malaysia in respect of which liability cannot lawfully be modified or excluded. If you acquired the Software in New Zealand for the purposes of a business, you confirm that the Consumer Guarantees Act does not apply. If you acquired the Software in Australia and if Microsoft breaches a condition or warranty implied under any law which cannot lawfully be modified or excluded by this agreement then, to the extent permitted by law, Microsoft's liability is



limited, at Microsoft's option, to: (i) in the case of the Software: a) repairing or replacing the Software; or b) the cost of such repair or replacement; and (ii) in the case of support services: a) re-supply of the services; or b) the cost of having the services supplied again.

Everett VSPro 11

Final 11.04.02

Should you have any questions concerning this EULA, or if you desire to contact Microsoft for any reason, please use the address information enclosed in this Software to contact the Microsoft subsidiary serving your country or visit Microsoft on the World Wide Web at http://www.microsoft.com.

Everett VSPro 12

Final 11.04.02

%% The following software may be included in this product: zlib; Use of any of this software is governed by the terms of the license below:

zlib.h -- interface of the 'zlib' general purpose compression library version 1.1.3, July 9th, 1998






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

Jean-loup Gailly Mark Adler

[email protected] [email protected]

The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format

%% The following software may be included in this product: Mozilla Rhino. Use of any of this software is governed by the terms of the license below: The contents of this file are subject to the Netscape 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/NPL/ 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 Rhino code, released May 6, 1999. The Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by Netscape are Copyright (C)

1997-2000 Netscape Communications Corporation. All Rights Reserved. Contributor(s): Kemal Bayram Patrick Beard Norris Boyd Igor Bukanov, [email protected] Brendan Eich Ethan Hugg Roger Lawrence Terry Lucas Mike McCabe Milen Nankov Attila Szegedi, [email protected] Ian D. Stewart Andi Vajda Andrew Wason/

%% The following software may be included in this product: Apache Derby. Use of any of this software is governed by the terms of the license below:

Apache License




1. Definitions.




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




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





(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




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.














Sun Microsystems, Inc. Binary Code License Agreement for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6

Sun Microsystems, Inc. Binary Code License Agreement for the JAVA 2 PLATFORM STANDARD EDITION RUNTIME ENVIRONMENT 5.0 SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE.

W3C IPR Software, v.5.3.2

W3C® SOFTWARE NOTICE AND LICENSE

Copyright © 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:


2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

3.Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.


____________________________________

This formulation of W3C's notice and license became active on August 14 1998 so as to improve compatibility with GPL. This version ensures that W3C software licensing terms are no more restrictive than GPL and consequently W3C software may be distributed in GPL packages. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to [email protected].

webmaster

(last updated $Date: 2002/02/13 14:08:32 $)

UDD14J 2.0.3

IBM Public License Version 1.0

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

1. DEFINITIONS

"Contribution" means: in the case of International Business Machines Corporation ("IBM"), the Original Program, and in the case of each Contributor, changes to the Program, and 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 IBM and any other 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.



"Original Program" means the original version of the software accompanying this Agreement as released by IBM, including source code, object code and documentation, if any.

"Program" means the Original Program and Contributions.

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

2. GRANT OF RIGHTS

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.

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.

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.

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:

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

its license agreement:

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;

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

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

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:

it must be made available under this Agreement; and

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

Each Contributor must include the following in a conspicuous location in the Program:

Copyright (C) 1996, 1999 International Business Machines Corporation and others. All Rights Reserved.

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

IBM may publish new versions (including revisions) of this Agreement from time to time. 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. No one other than IBM has the right to modify this Agreement. 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 © 2004 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. Contact our Board for further donation information.

X Open ICU 1.4.1.2

COPYRIGHT AND PERMISSION NOTICECopyright (c) 1999,2000,2001 Compaq Computer CorporationCopyright (c) 1999,2000,2001 Hewlett-Packard CompanyCopyright (c) 1999,2000,2001 IBM CorporationCopyright (c) 1999,2000,2001 Hummingbird Communications Ltd.Copyright (c) 1999,2000,2001 Silicon Graphics, Inc.Copyright (c) 1999,2000,2001 Sun Microsystems, Inc.Copyright (c) 1999,2000,2001 The Open GroupAll rights reserved.

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, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

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 OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

X Window System is a trademark of The Open Group.

OSF/1, OSF/Motif and Motif are registered trademarks, and OSF, the OSF logo, LBX, X Window System, and Xinerama are trademarks of the Open Group. All other trademarks and registered trademarks mentioned herein are the property of their respective owners.



W3C IPR Software, v. 5.3.2

Copyright © 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/

This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright © [$date-of-software] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"

Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.


____________________________________

This formulation of W3C's notice and license became active on August 14 1998 so as to improve compatibility with GPL. This version ensures that W3C software licensing terms are no more restrictive than GPL and consequently W3C software may be distributed in GPL packages. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to [email protected].

webmaster

(last updated $Date: 2002/02/13 14:08:32 $)

zlib, v1.1.4

Zlib License, v 1.1.4

zlib.h — interface of the 'zlib' general purpose compression library version 1.1.4, March 11th, 2002






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

Jean-loup Gailly <[email protected]>Mark Adler <[email protected]>

The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format).


http://www.w3.org/

http://www.lcs.mit.edu/


http://www.inria.fr/


http://www.keio.ac.jp/


http://www.w3.org/

http://www.w3.org/







http://www.w3.org/Consortium/Legal/copyright-software-19980519.html

http://www.w3.org/Consortium/Legal/copyright-software-19980519.html

http://www.w3.org/Consortium/Legal/IPR-FAQ.html



mailto:[email protected]

http://www.w3.org/Help/Webmaster.html

Date post:	08-Nov-2014
Category:	Documents
Upload:	adam-smith
View:	455 times
Download:	1 times