The Programs listed below are licensed under the following terms and conditions in addition to those of the International Program License Agreement.
Program Name: IBM InfoSphere Warehouse 9.7.3c, Enterprise Edition
Program Number: 5724-E34
The Program is licensed as a multi-product package and includes the Supporting Programs identified below. Licensee is authorized to install and use such Supporting Programs only to support Licensee's use of the Principal Program under this Agreement and within the limits of the Proofs of Entitlement for the Program (unless broader rights are provided elsewhere in this License Information document). The phrase "to support Licensee's use" would include only those uses that are necessary or otherwise directly related to a licensed use of the Principal Program or another Supporting Program. The Supporting Programs may not be used for any other purpose. Licensee is not authorized to transfer or remarket the Supporting Programs separate from the Principal Program. A Supporting Program may be accompanied by license terms, and those terms, if any, apply to Licensee's use of that Supporting Program. In the event of conflict, the terms in this License Information document supersede the Supporting Program's terms. When Licensee's right to use the Program expires or terminates, Licensee must discontinue use, destroy or promptly return all copies of the Supporting Programs to the party from whom Licensee acquired the Program. If Licensee downloaded the Supporting Programs, Licensee should contact the party from whom Licensee acquired the Program. If Licensee wishes to license the Supporting Programs for any use beyond the limits set forth above, please contact an IBM Sales Representative or the party from whom Licensee acquired the Program to obtain the appropriate license.
The following are Supporting Programs licensed with the Program:
IBM DB2 18.104.22.168, Enterprise Server Edition
- IBM Database Add-ins for Visual Studio 9.7.4
- IBM Data Server Driver for JDBC and SQLJ 3.62
- IBM Data Server Driver for JDBC and SQLJ 4.12
- IBM Data Server Drivers for ODBC and CLI 9.7.4
- IBM Data Server Driver Package 9.7.4
- IBM Global Security Toolkit 8.0
- IBM Enterprise Content Management Text Search 1.0
- IBM Omnifind Yahoo! Edition 8.4.2
- IBM Java SDK 6.0/1.6 GA
- IBM UIMA Java SDK (IUJS) 2.3
- IBM LanguageWare 22.214.171.124
- IBM SDK/Runtime Environment, Java(TM) 2 Technology Edition 6.0
- IBM Tivoli Directory Server 6.2 - Client Only (component)
- IBM Tivoli Composite Application Manager for Applications 6.2 (DB2 Agent component)
- IBM Tivoli Monitoring for Databases: DB2 Agent (component)
- IBM Tivoli Storage Manager for Advanced Copy Services 6.1 (component)
- IBM Tivoli System Automation for Multiplatforms 126.96.36.199
- IBM Tivoli System Automation for Multiplatforms 3.2
- Platform Integration Toolkit 2.2
IBM Tivoli System Automation for Multiplatforms 3.1
IBM Tivoli System Automation for Multiplatforms 3.2.1
IBM WebSphere Application Server 7.0
IBM InfoSphere Federation Server 9.7 (component)
IBM LanguageWare 6.1
IBM WebSphere MQ 7.0.1
IBM DB2 Performance Expert for Linux, UNIX, and Windows 3.2.2
IBM InfoSphere Optim Performance Manager 5.1 for DB2 for Linux, UNIX, and Windows, Extended Edition
IBM Data Studio full client 3.1
IBM Data Studio administration client 3.1
IBM Data Studio web console 3.1
IBM Mashup Center 2.0
IBM Cognos Business Intelligence 10.1
Processor Value Unit (PVU)
Processor Value Unit (PVU) is a unit of measure by which the Program can be licensed. The number of PVU entitlements required is based on the processor technology (defined within the PVU Table by Processor Vendor, Brand, Type and Model Number at http://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html) and the number of processors made available to the Program. IBM continues to define a processor, for the purpose of PVU-based licensing, to be each processor core on a chip. A dual-core processor chip, for example, has two processor cores.
Licensee can deploy the Program using either Full Capacity licensing or Virtualization Capacity (Sub-Capacity) licensing according to the Passport Advantage Sub-Capacity Licensing Terms (see webpage below). If using Full Capacity licensing, Licensee must obtain PVU entitlements sufficient to cover all activated processor cores* in the physical hardware environment made available to or managed by the Program, except for those servers from which the Program has been permanently removed. If using Virtualization Capacity licensing, Licensee must obtain entitlements sufficient to cover all activated processor cores made available to or managed by the Program, as defined according to the Virtualization Capacity License Counting Rules at http://www.ibm.com/software/lotus/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html.
* An Activated processor core is a processor core that is available for use in a physical or virtual server, regardless of whether the capacity of the processor core can be or is limited through virtualization technologies, operating system commands, BIOS settings, or similar restrictions.
Terabyte is a unit of measure by which the Program can be licensed. A Terabyte is 2 to the 40th power bytes. Licensee must obtain an entitlement for each Terabyte of storage available to the Program.
1. Additional Charge Metric Details
If Licensee has acquired the Program based on the Terabyte charge metric, instead of the entitlements required for the Program directly, Licensee must obtain Terabyte entitlements for this Program sufficient to cover the terabytes of user data as reported by the Program. Licensee must also have the user data spread across two or more active data partitions.
2. Usage Restrictions
2.1 High Availability/Failover Configurations
After the server is fully licensed, it can be used to service user workload. In High Availability configurations this server is called a Primary server; additional servers acting as backups are called Standby servers that may be deployed in Hot, Idle/Warm or Cold configurations. Licensee must acquire a correct number of PVU or Terabyte license entitlements in addition to the PVU or Terabyte license entitlements Licensee obtained for the Primary server.
In a Hot Standby configuration, the Program is operational on all servers to service user transactions or queries. Because each of the Hot Standby servers is used to operate the Program for user transactions or queries before and after a failure, the Program must be fully licensed on all Hot Standby Servers. If Licensee enables the High Availability Disaster Recovery (HADR) Reads on Standby component on the standby server, the standby server accepts clients connections and allows query executions. This standby server is considered a Hot Standby server when HADR Reads on Standby component is enabled, thus the standby server must be fully licensed.
If Licensee is licensing under the Processor Value Unit charge metric, then in Hot Standby, Licensee must license the Program for the number of Processor Value Units that apply to the processors attached or available to all Hot Standby server(s). For example, consider an environment with two servers, one Primary server with four processors and one Hot Standby server with two processors. This environment must be licensed for the Processor Value Units that apply to all six processors (four for the Primary server and two for the Hot Standby server).
If Licensee is licensing under the Terabyte charge metric, then Licensee is not entitled to the HADR Reads on Standby functionality.
In an Idle/Warm Standby configuration, Idle/Warm Standby servers have the Program installed, however, they do not have the Program operational to service user transactions or query workloads. A server is considered Idle/Warm if the HADR Reads on Standby component is disabled and the server is used exclusively for administrative actions that assist in failover scenarios such as having a database in rollforward pending state to support log shipping, or in making a flash copy of a DB2 database and then performing a database backup of this copy on another server, or in keeping a standby database synchronized using the HADR component.
If Licensee is licensing under the Processor Value Unit charge metric, Licensee must license the Program for 100 Processor Value Units per Idle/Warm Standby system, regardless of the number of processors attached or available to the Idle/Warm Standby system. For example, consider disaster recovery configuration consisting of two systems. The Primary system consists of a Primary server and four additional servers. The Idle/Warm Standby system consists of 5 servers. This environment must be licensed for the Processor Value Units that apply to the five servers that comprise the Primary system (i.e. the Primary server and 4 additional servers) plus an additional 100 Process Value Units for the Idle/Warm Standby system.
If Licensee is licensing under the Terabyte charge metric, Licensee must license the Program for one Terabyte license for each Idle/Warm Standby system. For example, consider disaster recovery configuration consisting of two systems. The Primary system consists of a Primary server and four additional servers. The Idle/Warm Standby system consists of 5 servers. This environment must be licensed for the Terabytes that apply to the five servers that comprise the Primary system (i.e. the Primary server and 4 additional servers) plus an additional Terabyte license for the Idle/Warm Standby system.
If Licensee is licensing under the Terabyte charge metric, then Licensee is not entitled to the HADR functionality.
In a Cold Standby configuration, Cold Standby servers may have the Program installed, however, they do not have the Program powered on. A server is considered Cold if, to use it, Licensee must run the command "db2start" to instantiate the DB2 data server. There are no charges for the Program on Cold Standby servers.
3. Supporting Program Restrictions
3.1 IBM DB2 Enterprise Server Edition (DB2 ESE)
3.1.1 Homogeneous Replication Feature for DB2 Enterprise Server Edition
Licensee is authorized to use the Homogeneous Replication Feature for DB2 Enterprise Server Edition ("Homogeneous Replication Feature"), at no additional charge, only for queue-based replication functionality to replicate data between two DB2 for Linux, Unix and Windows (LUW) data servers. Licensee must obtain additional PVU license entitlements for the Homogeneous Replication Feature: (a) for each data server on which the Program is installed that replicates with more than one IBM DB2 LUW data server; and (b) for each data server on which the Program is installed that replicates with one or more IBM DB2 for z/OS data servers. Any other use of the Homogeneous Replication Feature requires that Licensee acquire a full license entitlement to an IBM InfoSphere Data Replication product.
3.1.2 Licensee is not authorized to use the following DB2 features without additional licenses:
- IBM DB2 Geodetic Data Management Feature
- IBM DB2 SQL Skin Feature for applications compatible with Sybase ASE
3.1.3 Host Connections
Restrictions on the use of DB2 with mainframe and iSeries data sources:
DB2 connect component
The DB2 connect component included with the DB2 ESE program is not licensed for use with DB2 for z/OS and OS/390, DB2 Server for VSE & VM, and DB2 for iSeries data servers. If users need to connect to any of the above mentioned DB2 data servers, a separate PoE for a DB2 Connect program must be acquired.
IBM Data Server Driver for JDBC and SQLJ
The IBM Data Server Driver for JDBC and SQLJ included with the DB2 ESE program is not licensed for use with DB2 for z/OS and OS/390, DB2 Server for VSE & VM, and DB2 for iSeries data servers. If users need to connect to any of the above mentioned DB2 data servers, a separate PoE for a DB2 Connect program must be acquired.
3.1.4 DB2 ESE program components
The DB2 ESE program contains components which are provided to support Licensee's authorized use of the DB2 ESE program on server machines within Licensee's organization. If Licensee wants to perform multiple installations and/or distribution of these components, Licensee must contact IBM or its reseller to obtain the appropriate licenses. The following are the exceptions:
DB2 clients and documentation
DB2 clients and documentation are provided with this DB2 ESE program. Licensee may make copies of these clients and documentation in support of Licensee's authorized use of the DB2 ESE program within Licensee's organization.
DB2 application drivers
The IBM Data Server Driver for JDBC and SQLJ is provided with this DB2 ESE program . Licensee may make copies of these drivers in support of Licensee's authorized use of the DB2 ESE program within Licensee's organization.
3.2 DB2 Connect Components
This Program includes portions of DB2 Connect technology. Licensee is authorized to install and use these components only in conjunction with the Program for single access by the SQL Warehousing Tool (SQW) to DB2 data on System z or System i platforms. DB2 Connect technology component are to be used only by the internal components of the Program and may not be used by applications or tools other than the SQL Warehousing Tool (SQW).
Licensee's use of DB2 Connect technology is subject to the terms and conditions of the license agreement which accompanies the components except as limited in this license. DB2 Connect technology may not be used for any other purpose. Please contact Licensee's DB2 Reseller if Licensee's needs exceed this license agreement, to obtain a full DB2 Connect license.
3.3 InfoSphere Federation Server
This Program uses components from InfoSphere Federation Server. Licensee is authorized to use these components only in conjunction with the Program for single access by the SQL Warehousing Tool (SQW) to supported relational data sources that require access through InfoSphere Federation Server as well as for access to federated data in Oracle, DB2 and Informix databases, excluding access to any other database and use with data replication. Licensee must also license DB2 Connect to access DB2 for z/OS and DB2 for i. Access to other databases requires that Licensee acquire a fully licensed copy of an IBM InfoSphere Federation Server product. Combining federation with data replication, including SQL Replication, requires that Licensee acquire a fully licensed copy of an IBM InfoSphere Data Replication product.
3.4 IBM Mashup Center
The use of IBM Mashup Center is included in this Program. IBM Mashup Center consists of two offerings: IBM Lotus Mashups (the "Mashup Program") and IBM InfoSphere MashupHub (the "Data Feed Program").
Licensee may only use the Data Feed Program to deliver feeds from data sources managed by the Program and a maximum of two other underlying relational SQL based data stores in support of the Program data source for read only purposes. Additionally, the Licensee may not publish non-Program data to interfaces beyond the Mashup Program. Additionally, the Licensee can configure policies on the feeds within the Data Feed Program for permissions and caching purposes and active content filtering, but Licensee may not configure any other Mashup Center component policies for other purposes without obtaining a separate entitlement, for example for enabling: (a) feed filtering policies to create global or element filters, (b) IP address authorization to allow or deny access based on IP addresses, or (c) rate limiting to limit the number of requests allowed per minute.
3.5 IBM Cognos Business Intelligence
- Use Metric: Authorized User
- Entitlement: 5
Authorized User is a unit of measure by which the Supporting Program can be licensed. An Authorized User is a unique person who is given access to the Supporting Program. The Supporting Program may be installed on any number of computers or servers and each Authorized User may have simultaneous access to any number of instances of the Supporting Program at one time. Licensee must obtain separate, dedicated entitlements for each Authorized User accessing the Supporting Program in any manner directly or indirectly (for example: via a multiplexing program, device, or application server) through any means. An entitlement for an Authorized User is unique to that Authorized User and may not be shared, nor may it be reassigned other than for the permanent transfer of the Authorized User entitlement to another person.