Hier finden Sie eine Auswahl aktueller Lizenztexte zu den IBM Informix Produkten.
Lizenzierung kann im Detail ein kompliziertes, aber auch ein lohnendes Thema sein.
Die richtige Lizenzierung schafft Sicherheit für die Anwendung und Kostenvorteile in der Nutzung.
Ob für bestehende oder geplante Installationen, gerne beraten wir Sie bei Lizenzfragen zu Informix.
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 Informix Growth Edition V11.50xC7
Program Number: 5725-A40
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. The terms of this Agreement may replace or modify the license terms for the Supporting Programs. In the event of conflict, these terms supersede the terms of the license agreement which accompanies the Supporting Programs. 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 Informix Client SDK V3.50 5724-C23
IBM WebSphere Application Server V7.0
Separately Licensed Code
The provisions of this paragraph do not apply to the extent they are held to be invalid or unenforceable under the law that governs this license. Each of the components listed below is considered "Separately Licensed Code". IBM Separately Licensed Code is licensed to Licensee under the terms of the applicable third party license agreement(s) set forth in the NON_IBM_LICENSE file(s) that accompanies the Program. Notwithstanding any of the terms in the Agreement, or any other agreement Licensee may have with IBM, the terms of such third party license agreement(s) governs Licensee's use of all Separately Licensed Code unless otherwise noted below.
Future Program updates or fixes may contain additional Separately Licensed Code. Such additional Separately Licensed Code and related licenses are listed in another NON_IBM_LICENSE file that accompanies the Program update or fix. Licensee acknowledges that Licensee has read and agrees to the license agreements contained in the NON_IBM_LICENSE file(s). If Licensee does not agree to the terms of these third party license agreements, Licensee may not use the Separately Licensed Code.
For Programs acquired under the International Program License Agreement ("IPLA") or International Program License Agreement for Non Warranted Program ("ILAN") and Licensee is the original licensee of the Program, if Licensee does not agree with the third party license agreements, Licensee may return the Program in accordance with the terms of, and within the specified time frames stated in, the "Money-back Guarantee" section of the IPLA or ILAN IBM Agreement.
Note: Notwithstanding any of the terms in the third party license agreement, the Agreement, or any other agreement Licensee may have with IBM:
(a) IBM provides this Separately Licensed Code to Licensee WITHOUT WARRANTIES OF ANY KIND;
(b) IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SEPARATELY LICENSED CODE;
(c) IBM is not liable to Licensee, and will not defend, indemnify, or hold Licensee harmless for any claims arising from or related to the Separately Licensed Code; and
(d) IBM is not liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages including, but not limited to, lost data, lost savings, and lost profits, with respect to the Separately Licensed Code.
Notwithstanding these exclusions, in Germany and Austria, IBM's warranty and liability for the Separately Licensed Code is governed only by the respective terms applicable for Germany and Austria in IBM license agreements.
Note: IBM may provide limited support for some Separately Licensed Code. If such support is available, the details and any additional terms related to such support will be set forth in the License Information document.
The following are Separately Licensed Code:
AGS Server Studio and Sentinel Release 7
A Client Device is a single user computing device that requests the execution of or receives for execution a set of commands, procedures, or applications from another computer system that is typically referred to as a server or is otherwise managed by the server. Multiple Client Devices may share access to a common server. A Client Device generally has some processing capability or is programmable to allow a user to do work. Examples include, but are not limited to appliances, automated teller machines, cash registers, disk drives, desktop computers, kiosks, notebook computers, personal digital assistant, point-of-sale terminals, tape drives, and technical workstations. Licensee must obtain entitlements for every Client Device which runs, uses services provided by, or otherwise accesses the Program and for every other computer or server on which the Program is installed.
Install is a unit of measure by which the Program can be licensed. An Install is an installed copy of the Program on a physical or virtual disk made available to be executed on a computer. Licensee must obtain an entitlement for each Install of the Program.
A "Socket" is electronic circuitry that accepts a processor chip. A "processor chip" is electronic circuitry containing one or more processor cores that plugs into a Socket. A "processor core" is a functional unit within a computing device that interprets and executes program instructions, and consists of at least an instruction control unit and one or more arithmetic or logic units.
Level of Use
Licensee's use of a Program may not exceed the level defined by the number of use authorizations Licensee has acquired, as evidenced in Licensee's Proof of Entitlement (PoE). Each version of the Program is available for licensing in accordance with one or more of the following levels of use:
1) Charge Metrics
The IBM Informix Growth Edition V11.50 is available for licensing on a Limited Use Socket, Processor Value Unit, Concurrent Session, or Authorized User Single Install charge metric basis, as specified below.
Consult Licensee's Proof of Entitlement (PoE) to determine which charge metric terms apply to the Program Licensee has licensed. The charge metric is specific to the part number that has been purchased.
1.1) The following applies to any version of an IBM Informix Growth Edition Program when used solely in a development environment.
If the Program is used only in a development environment, there is no minimum Authorized User Single Install or Concurrent Session license entitlement requirement. Licensee must only acquire entitlements to the actual number of Authorized Users Single Install or Concurrent Sessions Licensee uses. Use in a development environment is limited to the purposes of developing, evaluating, demonstrating, and testing application programs, and for no other purpose.
1.2) Authorized User Single Install - If Licensee acquires a Program based on this Charge Metric, then the terms of this Section apply.
Licensee must acquire a separate Authorized User Single Install license entitlement for each Authorized User of the Program accessing each individual Install.
Authorized User Single Install is a unit of measure by which the Program can be licensed. An Authorized User is a unique person who is given access to the Program. An Install is an installed copy of the Program on a physical or virtual disk made available to be executed on a computer. The Program may be installed on any number of computers or servers, but if the Authorized User has accessed or has access to more than one Install of the Program, the Authorized User requires a separate entitlement for each such Install. Licensee must obtain separate, dedicated entitlements for each Authorized User accessing the Program on each Install 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.
A Client Device is considered a separate Authorized User of the Program and requires an entitlement as if that Client Device were a person.
1.3) Concurrent Session - If Licensee acquires a Program based on this Charge Metric, then the terms of this Section apply.
A Concurrent Session is a logical connection made between each database instance created by an Install and a Client Device. Each such connection is counted as a Concurrent Session whether or not it is actually in use and regardless of the duration of the connection and/or period(s) of activity. If an individual end user establishes multiple connections, each one is counted as a separate Concurrent Session, even if they share a common physical pathway. From the day Licensee began using the Program, the highest number of connections ever established at any time for each database instance created by an Install will be counted for purposes of determining the total Concurrent Session entitlements required. Licensee must acquire entitlements for the greatest number of logical connections ever established at any time for all database instances created by each Install. See the example below.
Each logical connection made between a Client Device and a copy of a database instance created by an Install is counted as a Concurrent Session for which an entitlement is required. For example, if there are two (2) different Installs and each creates two (2) separate database instances and a single Client Device is connected to each database instance on both Installs, then four (4) Concurrent Sessions have been established and a PoE must be acquired for each of them. As a further example, if four database instances are created by two (2) different Installs and a single Client Device is connected, directly or indirectly, to each of the four (4) database instances of the Program, then eight (8) Concurrent Sessions have been established and a PoE must be acquired for each of them.
Licensee must obtain separate, dedicated entitlements for each Concurrent Session that has been or is in existence. An entitlement for a Concurrent Session is unique to that Client Device and a specific database instance created for an Install and may not be shared, nor may it be reassigned other than for the permanent replacement of that Client Device with another Client Device.
Each logical connection from a Client Device made, directly or indirectly, to a database instance created for an Install, through the Intranet (connections from within Licensee's Enterprise) or through the Internet (connections from outside Licensee's Enterprise) is counted as a separate Concurrent Session and a separate entitlement (PoE) must be acquired for such Concurrent Session.
A PoE is required for each Concurrent Session established to access the Program or any Program component either directly or indirectly through any means. An example of "indirect" access would be through a multiplexing program, Client Device, or application server. The number of connections is not reduced by any program, Client Device, or machine, such as a front-end server, application server, or multiplexer, which may be used to connect, manage, and/or concentrate the logical connections.
For example, if Licensee installs one or more copies of the Program on each of three (3) Installs and from the day Licensee begins using the Program, the greatest number of Concurrent Sessions ever established on the total Program instances on Install 1 was twelve (12), on Install 2 was seventy (70), and on Install 3 was eighty-nine (89), then Licensee must acquire, and pay for, PoE entitlements for one hundred and seventy-one (171) Concurrent Sessions, even if the number of Licensee's logical connections decreases over time (e.g, logical connections are reduced to the following: Install 1: 12; Install 2: 56; Install 3: 80). Of course, Licensee may subsequently again increase Licensee's total number of logical connections to one hundred-seventy-one (171) without needing to acquire additional Concurrent Session entitlements; provided that Licensee does not increase the number of logical connections on any one of the Installs beyond the highest number of logical connections ever previously established on that Install. In this example, Licensee could again increase the logical connections on Install 2 up to 70, and could increase the logical connections on Install 3 up to 89, without needing to acquire additional Concurrent Session entitlements. However, if Licensee increased the number of logical connections on Install 1 to 25, even though the number of logical connections on Installs 2 and 3 remained at 56 and 80, respectively, Licensee would need to acquire an additional 13 Concurrent Session entitlements for Install 1 (bringing Licensee's total entitlements to one hundred and eighty-four (184)). Concurrent Sessions are not equivalent to concurrent users.
Each batch process being executed at the same time is also considered to be a Concurrent Session.
Licensee must acquire a separate Concurrent Session license entitlement for each Concurrent Session as described above.
1.4) Limited Use Socket (LU Socket)
The LU Socket charge metric is only available to the Informix Growth Edition.
This Program is licensed on a Limited Use Socket ("LU Socket") basis as follows. Licensee must: (1) acquire one LU Socket entitlement for each Socket on the Install on which the Program is installed; and (2) comply with the resource use restrictions further defined below in this License Information.
Limited Use Socket (LU Socket) is a unit of measure by which the Program can be licensed. A Limited Use Socket is an electronic circuitry that accepts a processor chip that meets the maximum processor cores per socket authorized use terms and conditions in the IBM Express and Middleware Licensing Guide . A Server is a physical computer that is comprised of processing units, memory, and input/output capabilities and that executes requested procedures, commands, or applications for one or more users or client devices. Where racks, blade enclosures, or other similar equipment is being employed, each separable physical device (e.g., a blade or a rack-mounted device) that has the required components is considered itself a separate Server. A processor chip is electronic circuitry containing one or more processor cores that plugs into a Socket. A processor core is a functional unit within a computing device that interprets and executes program instructions, and consists of at least an instruction control unit and one or more arithmetic or logic units. Licensee must obtain entitlements for each Socket on the Server on which the Program is installed.
If the Program is eligible for sub-capacity licensing, Licensee may be permitted to license less than all Sockets on the Server. Sub-capacity licensing terms, conditions and eligibility requirements for LU Socket-charged programs are described in the Sub-capacity Guide . If Licensee's use of the Program is not eligible for sub-capacity licensing based on these terms and conditions, Licensee must acquire LU Socket entitlements for all Sockets on the Server on which the Program is installed. The LU Socket entitlements are specific to the Program and may not be exchanged, interchanged, or aggregated with LU Socket entitlements of another software program.
1.5) Processor Value Unit
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.
2) Informix Growth Edition Program Usage Restrictions
The following restrictions apply to licenses to Informix Growth Edition V11.50 Program.
2.1) Install Limitation - If Licensee licenses the Program on a LU Socket basis, Licensee may not install or use the Program on a physical server machine that has a capacity of more 4 Sockets and may only utilize up to a total of 16 processor cores.
If Licensee licenses the Program on a PVU, Concurrent Session or Authorized User Single Install basis, Licensee may not install or use the Program on an Install that has more 4 Sockets and may only utilize up to a total of 16 processor cores.
Where a physical, logical, or virtual partition is used, it must be created with an approved IBM eligible partitioning technology. See list of eligible technologies in: ftp://ftp.software.ibm.com/software/passportadvantage/SubCapacity/Eligible_Virtualization_Technology.pdf
2.2) The total amount of resources allocated to a given Informix Install, including all database instances managed by the Install, cannot exceed:
2.2.1 Install processor limit 4 sockets, total 16 cores (equivalent to 16 CPUVPs)
2.2.2 - Install Memory Allocation Limit - total of sixteen (16) Gigabytes of memory allocated (as reflected in the SHMTOTAL tunable parameters of the Program) to support use of all instances of the Program on a single Install. The sum total of all SHMTOTAL parameters set within all instances of the Program in an Install may not exceed 16 Gigabytes of allocated memory, regardless of the amount of physical memory in the physical server.
2.3) Licensee may use the Enterprise Replication (ER) in any mode, as either admin nodes or leafnodes.
2.4) Licensee may use the Program up to total a of three (3) Primary and Secondary Install nodes, in any combination of primary and secondary Install nodes using: High-availability Data Replication (HDR), Remote Secondary Server (RSS) and Shared Disk Secondary (SDS). Secondary Install nodes may perform both read and write queries and operations.
2.5) Under a license to the Informix Growth Edition Program, Licensee is not entitled to use any of the following functions:
2.5.1 - DBSpace Prioritization during backup/restore
2.5.2 - Recovery Time Objective Policy
2.5.3 - Private Memory Cache for VP
2.5.4 - Direct I/O for Cooked Files
2.5.5 - I-STAR
2.5.6 - Parallel query
2.5.7 - High Performance Loader
2.5.8 - Parallel index build
2.5.9 - Parallel backup/restore
2.5.10 - Table/Index/DBSpace partitioning
2.5.11 - Column level encryption
2.5.12 Compression (e.g., the Storage Optimization Feature)
2.7) When using Informix clustering secondary configurations for High-availability Data Replication (HDR), Remote Secondary Server (RSS), or Shared Disk Secondary (SDS), the following applies.
2.7.1 There are no additional charges for the Program placed on standby secondary Install(s) in Cold or Warm standby configurations.
2.7.2 Licensee must acquire sufficient Informix Growth Edition entitlements for each standby secondary Install when used in a Hot standby configuration.
For definition of Cold, Warm, and Hot standby, see http://www-03.ibm.com/software/sla/sladb.nsf/pdf/policies/$file/Feb-2003-IPLA-backup.pdf
3) Program Components
The Program is made up of components, and use of any component is use of the Program. Therefore, for example, if Licensee uses one component of IBM Informix on one Install, and another of its components on another Install, both Installs must be fully licensed. The number of LU Socket, PVU, Authorized User Single Install or Concurrent Session authorizations required for IBM Informix is the total of the number of entitlements (LU Sockets, Authorized Users Single Install or Concurrent Sessions) required for each of its components and all components must be licensed on the same charge metric.
3.1) The following is an exception: Licensee may, without requiring additional authorizations, install each of the following three components on additional Installs in support of Licensee's authorized use of the Program within Licensee's Enterprise: IBM Informix Connect Runtime, Informix ODBC, and IBM Informix JDBC. However, Licensee must have sufficient LU Socket, PVU, Authorized User Single Install, or Concurrent Session authorizations for the Program to provide for the use of these components.
The IBM Informix Connect Runtime component may only be used for production, and may not be used for, or in conjunction with, product or program development.
4) Separate Informix Client SDK (CSDK) program
A copy of Informix CSDK program is provided along with the Program. The Informix CSDK is available for use with this Program at no additional charge but is offered with no Subscription and Support (S&S). To obtain support for the Informix CSDK, Licensee must purchase a separate Informix CSDK entitlement (PoE) and remain current with support S&S for the Informix CSDK.
Pursuant to the Informix CSDK program license agreement which Licensee must accept before use upon installation, the IBM Informix JDBC Embed SQL runtime libraries included the CSDK may not be used in production mode.
Licensee must purchase a separate entitlement (PoE) when using Informix JDBC Embed SQL runtime libraries in a production environment.
5) Informix Version to Version Upgrade Support
In order to facilitate version to version upgrade from an older Informix version to one of these Programs, Licensee may install and operate both the older version and the Program for a single period of 180 days while they are in development and test stage of a transition. Licensee must be current on the Subscription and Support (S&S) of the product to which Licensee is upgrading.
6) The following terms apply to the SNMP Research Intl EMANATE modules: Master Agent for 32-bit Red Hat Linux WS 3 (XS6), 64-bit Red Hat Linux 4 WS (Opteron); Subagent Development Kit for 32-bit Red Hat Linux WS 3 (X86), 64-bit Red Hat Linux 4 WS Opteron) modules:
Licensee may not reverse engineer or decompile the modules, except as allowable by applicable law.
Licensee may load, store, create and list the modules.
Licensee may not copy, modify or distribute the modules.
Licensee may only use the modules in conjunction with the Program.