11.0.0.5 update

Author: IBMRob

CHANGELOG.md

@@ -0,0 +1,38 @@
+# Change log
+
+## 11.0.0.5 (2019-07-x)
+
+**Breaking changes**:
+* When using MQ, the UID of the mqm user is now 888.  You need to run the container with an entrypoint of `runmqserver -i` under the root user to update any existing files.
+* MQSC files supplied will be verified before being run. Files containing invalid MQSC will cause the container to fail to start
+
+**Other changes**:
+* Security fixes
+* Web console added to production image
+* Container built on RedHat host (UBI)
+* Includes MQ 9.1.2
+* Supports configuring agent files
+* Supports installing additional config files using extensions.zip
+
+## 11.0.0.3 (2019-02-04)
+
+**Breaking changes**:
+NONE
+
+**Other changes**:
+* Provides samples for building image with MQ Client
+* Code to generate RHEL based images
+* Fix for overriding the hostname and port for RestAPI in the UI / Swagger Docs.
+
+## 11.0.0.2 (2018-11-20)
+
+**Breaking changes**:
+NONE
+
+**Other changes**:
+* Updated to support 11.0.0.2 runtime
+* Updated to support ICP platform
+
+## 11.0.0.0 (2019-10-08)
+
+* Initial version

LICENSE

@@ -1,11 +1,11 @@
-The translated license terms can be viewed here: https://www-03.ibm.com/software/sla/sladb.nsf/searchlis/?searchview&searchorder=4&searchmax=0&query=(App+Connect+Enterprise+V11.0.0.4)
+The translated license terms can be viewed here: https://www-03.ibm.com/software/sla/sladb.nsf/searchlis/?searchview&searchorder=4&searchmax=0&query=(App+Connect+Enterprise+V11.0.0.5)
 
 LICENSE INFORMATION
 
 The Programs listed below are licensed under the following License Information terms and conditions in addition to the Program license terms previously agreed to by Client and IBM. If Client does not have previously agreed to license terms in effect for the Program, the International Program License Agreement (Z125-3301-14) applies.
 
 Program Name (Program Number):
-IBM App Connect Enterprise V11.0.0.4 (5724-J05)
+IBM App Connect Enterprise V11.0.0.5 (5724-J05)
 
 The following standard terms apply to Licensee's use of the Program.
 
@@ -19,7 +19,7 @@ Program's specifications can be found in the collective Description and Technica
 
 Prohibited Uses
 
-Licensee may not use or authorize others to use the Program, alone or in combination with other services or products, in support of any of the following high risk activities: design, construction, control, or maintenance of nuclear facilities, mass transit systems, air traffic control systems, automotive control systems, weapons systems, or aircraft navigation or communications, or any other activity where program failure could give rise to a material threat of death or serious personal injury.
+Licensee may not use or authorize others to use the Program if failure of the Program could lead to death, bodily injury, or property or environmental damage.
 
 Bundled Programs
 
@@ -40,6 +40,7 @@ Supporting Programs:
 - IBM WebSphere Adapter for Siebel Business Applications V7.5
 - IBM MQ Advanced V9.0
 - IBM Data Server Driver Package V11.1
+- IBM MQ Advanced V9.1
 
 Non-Production Limitation
 
@@ -65,16 +66,17 @@ Note: IBM may provide limited support for some Separately Licensed Code. If such
 
 The following are Separately Licensed Code:
 The Program includes some or all of the following licensed to you as Separately Licensed Code.
-1. CC-BY-3.0 - spdx-exceptions(node) V2.1.0, posix-character-classes V0.1.1
-2. CC0-1.0 - spdx-license-ids(node) V3.0.0 , lodash.fill 3.4.0, lodash.intersection 4.4.0, lodash.partialright 4.2.1
+1. CC-BY-3.0 - spdx-exceptions(node) , spdx-expression-parse
+2. CC0-1.0 - spdx-license-ids(node)  , lodash.fill , lodash.intersection , lodash.partialright , libnpx make-fetch-happen spdx-license-ids spdx-license-ids
 3. Ubuntu
 4. Red Hat Enterprise Linux (RHEL)
+5.Red Hat Universal Base Image v7.0
 ===================================================================
-1. spdx-exceptions(node) V2.1.0, posix-character-classes V0.1.1
+1. spdx-exceptions(node) , spdx-expression-parse
 License for CreativeCommons-by-3.0
 ===================================================================
 ===================================================================
-2. spdx-license-ids(node) V3.0.0,  lodash.fill 3.4.0, lodash.intersection 4.4.0, lodash.partialright 4.2.1
+2.  spdx-license-ids(node)  , lodash.fill , lodash.intersection , lodash.partialright , libnpx make-fetch-happen spdx-license-ids spdx-license-ids
 License for Creative Commons CC0-1.0
 ===================================================================
 ===================================================================
@@ -86,6 +88,12 @@ When IBM App Connect  Enterprise is provided in a container format, license info
 =========================================================================
 When IBM App Connect  Enterprise is provided in a container format, license information for Red Hat Enterprise Linux packages may be found in /usr/share/doc/${package}
 =========================================================================
+5.Red Hat Universal Base Image v7.0
+=========================================================================
+Red Hat Universal Base Image v7.0 has been taken under EULA > https://www.redhat.com/licenses/eulas
+
+The Program maybe provided with third party software programs subject to their own license terms. The license terms either accompany the third party software programs or, in some instances, may be viewed at > https://access.redhat.com/containers/
+=========================================================================
 
 Redistributables
 
@@ -128,9 +136,9 @@ Licensee can deploy the Program using either Full Capacity licensing or Virtuali
 
 Virtual Processor Core
 
-Virtual Processor Core is a unit of measure by which the Program can be licensed. A Physical 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 (for example, a blade or a rack-mounted device) that has the required components is considered itself a separate Physical Server. A Virtual Server is either a virtual computer created by partitioning the resources available to a Physical Server or an unpartitioned Physical Server. A Processor Core (commonly called a processor or CPU) is a functional unit within a computing device that interprets and executes instructions. A Processor Core consists of at least an instruction control unit and one or more arithmetic or logic unit. A Virtual Processor Core is a Processor Core in an unpartitioned Physical Server, or a virtual core assigned to a Virtual Server. Licensee must obtain entitlement for each Virtual Processor Core made available to the Program.
+Virtual Processor Core is a unit of measure by which the Program can be licensed. 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 (for example, a blade or a rack-mounted device) that has the required components is considered itself a separate Server. A Virtual Server is either a virtual computer created by partitioning the resources available to a physical Server or an unpartitioned physical Server. A Processor Core is a functional unit within a computing device that interprets and executes instructions. A Processor Core consists of at least an instruction control unit and one or more arithmetic or logic unit. A Virtual Processor Core is a Processor Core on a Virtual Server created by partitioning the resources available to a physical Server or an unpartitioned physical Server. Licensee must obtain entitlement for each Virtual Processor Core made available to the Program.
 
-For each Physical Server, Licensee must have sufficient entitlements for the lesser of 1) the sum of all available Virtual Processor Cores on all Virtual Servers made available to the Program or 2) all available Processor Cores on the Physical Server.
+For each physical Server, Licensee must have sufficient entitlements for the lesser of 1) the sum of all available Virtual Processor Cores on all Virtual Servers or 2) all available Processor Cores on the physical Server.
 
 In addition to the above, the following terms apply to Licensee's use of the Program.
 
@@ -142,17 +150,9 @@ Use of the Program and Components when used for Development and Functional Test
 
 Under Development and Functional Test use, the Program or components can only be deployed as part of Licensee's internal development, unit, and functional testing environments. In functional test environments the developer can integrate their code with that of others on shared use machines, and that code can be tested in a test harness. Functional testing is limited to ensuring that the Program can be used to connect to local or remote endpoints, and that a sample of data sent between those endpoints is processed correctly. Licensee is not authorized to use the Program or components for system test, meaning integrated code is tested as a product, processing production workloads, simulating production workloads or testing the scalability of any code, application or system. 
 
-Idle Standby configurations 
-
- "Idle Standby" configuration is one where a copy of the Program is installed on a server which forms part of a high availability solution and is the server to which the Program will fail over in the event that the copy of the Program on the active server ceases to be usable. A server is only considered "idle" if, until a failover takes place, it is used exclusively for administrative actions that assist in failover scenarios. 
-
-If the Program is used in an Idle Standby configuration with the Program's multi-instance mode , then a copy of the Program may reside for backup purposes on an Idle Standby server, and started, but must remain "idle" and not be used to carry out productive work of any kind unless the active server fails over on to the Idle Standby server, in which event the Idle Standby copy may be used to carry out productive work during the period of failover. 
-
-If the Program is used in an Idle Standby configuration with other High Availability systems, then a copy of the Program may reside for backup purposes on an Idle Standby server but not started (and therefore not be used to carry out productive work of any kind), but will be started automatically by the High Availability components in the event of the active server failing, in which event the Idle Standby copy may be used to carry out productive work during the period of failover.
-
 2. Operation mode
 
-The Program is capable of running in different operational modes, with associated restrictions , which are detailed in the "Operation Modes" and the "Restrictions that apply in each operation mode" sections of the Program's Knowledge Center, which is provided by IBM in the English, Brazilian Portuguese, German, Japanese and Spanish languages. The term Execution Group (used below) is defined in the "Technical Overview" section of the Program's Knowledge Center.
+The Program is capable of running in different operational modes, with associated restrictions, which are detailed in the "Operation Modes" and the "Restrictions that apply in each operation mode" sections of the Program's Knowledge Center, which is provided by IBM in the English, Brazilian Portuguese, German, Japanese and Spanish languages. The term Execution Group (used below) is defined in the "Technical Overview" section of the Program's Knowledge Center.
 
 In Standard mode, all features are enabled for use with a single Execution Group. The number of message flows that Licensee can deploy is unlimited.
 
@@ -174,9 +174,11 @@ IBM MQ
 - Entitlement: Ratio 1 VPC/1 VPC 
 - Entitlement: Ratio 1 PVU /1 PVU
 
+"Ratio n/m" means that Licensee receives some number ('n') entitlements of the indicated metric for the Supporting or Bundled Program for every specified number ('m') entitlements of the specified metric for the Program as a whole. The specified ratio does not apply to any entitlements for the Program that are not of the required metric type. The number of entitlements for the Supporting or Bundled Program is rounded up to a multiple of 'n'. For example, if a Program includes 100 PVUs for a Supporting or Bundled Program for every 500 PVUs obtained of the Principal Program and Licensee acquires 1,200 PVUs of the Program, Licensee may install the Supporting or Bundled Program and have processor cores available to or managed by it of up to 300 PVUs. Those PVUs would not need to be counted as part of the total PVU requirement for Licensee's installation of the Program on account of the installation of the Supporting or Bundled Program (although those PVUs might need to be counted for other reasons, such as the processor cores being made available to other components of the Program, as well).
+
 4. Bundled Program details
 
-App Connect Professional 
+IBM App Connect Professional 
 - Entitlement: Ratio 1 VPC/1 VPC 
 - Entitlement: Ratio 1 PVU /1 PVU
 
@@ -190,10 +192,9 @@ Licensee may not exploit any distributable Microsoft Code (i.e., source code and
 
 The Program contains sample source code that is derived from the distributable Microsoft Code in source code form. Licensee must not include any such sample source code derived from distributable Microsoft Code in any malicious, deceptive or unlawful program.
 
-L/N:  L-DFOX-B5NGLP
-D/N:  L-DFOX-B5NGLP
-P/N:  L-DFOX-B5NGLP
-
+L/N:  L-DFOX-BC9LDF
+D/N:  L-DFOX-BC9LDF
+P/N:  L-DFOX-BC9LDF
 
 International Program License Agreement