News
Abstract
IBM API Connect V2018.4.1.16-ifix1 is now available. This update includes an important security update and no field reported fixes.
Content
IBM API Connect 2018.x delivers enhanced capabilities for the market-leading IBM API Management solution. In addition to the ability to deploy in complex, multi-cloud topologies, this version provides enhanced experiences for developers and cloud administrators at organizations.
The API Connect v2018.4.1.16-ifix1 update includes important security fixes. See the "What's New" topic in the API Connect IBM Documentation for more information on what's included in API Connect v2018.4.1.16.
- A special note regarding a lack of a fix pack 14: IBM API Connect v2018.4.1.14 was skipped purely from a numbering perspective to resume the synchronized releases between IBM API Connect and IBM DataPower Gateway.
Please read the following section for special updates regarding upgrading from earlier versions of API Connect v2018.4.1.x and for customers looking to upgrade to API Connect v10.0.1.x
- A special note on upgrades from prior versions of API Connect v2018.4.1.x: API Connect v2018.4.1.5 is now a prerequisite for API Connect v2018.4.1.16 for VMWare (.OVA) deployments. You cannot upgrade your API Connect topology to 2018.4.1.16 without first being at least at the v2018.4.1.5 level. Again, this restriction applies only to VMWare (.OVA) deployments only of IBM API Connect v2018.4.1.9. This is due to the level of Kubernetes deployed with the VMWare (.OVA) installation of IBM API Connect v2018.4.1.16 and restrictions around skipping levels of Kubernetes when upgrading. Additionally, a Control Plane file is required if you are upgrading from v2018.4.1.5 or v2018.4.1.6 to v2018.4.1.16 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Documentation.
- An additional note on upgrade procedures for DataPower Gateway high-availability clusters. The upgrade procedure for DataPower Gateway has new steps for upgrading high-availability clusters, to ensure that a single gateway is running as primary for all gateway-peering definitions, and that the primary gateway is upgraded last. See the "What's New" topic in the API Connect IBM Documentation for more information on this and new features included in API Connect v2018.4.1.16.
- Customers seeking to upgrade to API Connect v10.0.1.x: The supported upgrade path for API Connect v2018.4.1.x to API Connect v10.0.1.x on Kubernetes is documented in IBM Documentation. See also API Connect Upgrade Central: v2018 to v10
API Connect v2018.4.1.16 contains the following field reported APARs:
APAR | Summary |
LI81293 | NO WAY TO ADD THE USER'S DEFINED PARAMETER TO A PATH IN V2018 |
LI81441 | INCONSISTENCIES IN SUBSCRIBER_EVENTS TABLES BREAK SYNCHRONISATION |
LI81592 | $REF IN API PARAMETERS IS SHOWN AS A BLANK ENTRY IN API DESIGN VIEW |
LI81616 | DOUBLE QUOTES IN EXAMPLE DEFINITION ARE SHOWN WITH BACKSLASHES IN THE DEVELOPER PORTAL EXPLORER |
LI81750 | API MANAGER'S API ASSEMBLE TEST TOOL WRONGLY APPEND EXTRA TEXT IN THE "SCOPE" PARAMETER'S VALUE |
LI81796 | API DESIGNER GENERATES DUPLICATE ENTRIES FOR PATH PARAMETERS |
LI81841 | ERRONEOUS ERROR MESSAGES ARE OUTPUT REGULARLY IN OVA SYSLOG |
LI81860 | SPORADICALLY FAILING CLOUD-BACKUP (API-MANAGER) BECAUSE "FILE CHANGED AS WE READ IT" |
LI81890 | CONSUMER ORG INVITATION LOGIN FAILURE - OIDC USER REGISTRY |
LI81921 | Use relative paths for tokenurls (and other internal endpoints) |
LI81923 | API EDITOR WITHIN API MANAGER INCORRECTLY DISPLAYS A WARNING STATING CERTAIN POLICES ARE INVALID |
LI81935 | The server API hostname is included in the portal error message. |
LI81937 | PORTAL SUBSYSTEMS FAIL TO START ON OVA VERSION WITH 2 CPU |
LI81941 | PROPERTY "NAME" IN PLAN CONFIG IS CREATED AUTOMATICALLY WHEN EDITING A PLAN |
LI81952 | AFTER UPGRADE FROM V10.0.1.0 TO V10.0.1.1, THE WRONG TRANSLATION IS SHOWN IN THE PORTAL" |
LI81953 | PORTAL DB NOT CLEANING GCACHE PAGE FILES IN RARE CIRCUMSTANCES |
LI81974 | UPGRADE TO 2018.4.1.15 FAILED FOR ANALYTICS |
LI81978 | MANAGEMENT SUBSYSTEM UPGRADE MAY FAILS DURING APIM SCHEMA UPGRADE STEP |
LI81992 | FIX DEVELOPER PORTAL TO DISPLAY PATH ALIAS FOR PRODUCT OR API |
LI81996 | MAP POLICY IN A CATCH CONSUMING XML INPUT DOES NOT DETECT THE PROPER CONTENT TYPE |
LI82002 | OOM WHEN RUNNING PORTAL SITE CONTENT REFRESH WHERE DUPLICATE USERS ARE PRESENT. |
LI82008 | SITE RESTORE FAILS DUE TO THE MAX_ALLOWED_PACKET LIMIT |
LI82011 | STACK OVERFLOW OCCURS WHEN QUERY PARAM VALUE MATCHES THE VARIABLE NAME ITS TRYING TO RESOLVE |
LI82014 | Node.js CVE-2020-8265 CVE-2020-8287 CVE-2020-1971 |
API Connect v2018.4.1.16-ifix1.0 contains the following security related APAR:
APAR | Summary |
LI81879 | MYSQL UPDATES |
LI82120 | DRUPAL CORE - CRITICAL - CROSS-SITE SCRIPTING - SA-CORE-2021-002 |
*** Please note that links to some security related APARs may not be available in the table above. This is intentional for security purposes. ***
Database technology used in this release:
IBM API Connect relies on SQL and no-SQL database technology to provide persistent storage of objects required for the function of the product. Database technology requires fast and reliable storage and in the case of a highly available configuration, the database must perform adequately in a clustered configuration.
GlusterFS: Testing of IBM API Connect when using GlusterFS has shown that GlusterFS does not provide the speed or reliability for any of the database technologies used in IBM API Connect and thus should not be considered for use as the clustered storage facility with this product.
AWS EBS: IBM API Connect deployed on Kubernetes in EC2 instances on AWS should make use of the AWS EBS storage solution with GP2 or IO1 type.
We advise all users of prior version of API Connect v2018.x to install this update to take advantage of the fixes.
For more information about this release, see API Connect IBM Documentation: What's new in this release.
Important notes on upgrading to 2018.4.1.16-ifix1:
When upgrading to Version 2018.4.1.16-ifix1, you must complete a manual backup just before starting the upgrade. The manual backup is required because the upgrade can take an extended period of time. See Requirements for upgrading on VMware and Requirements for upgrading on Kubernetes.
- Starting with IBM API Connect Version 2018.4.1.11, writable LDAP user registries can be used only for onboarding and authenticating Developer Portal users. A writable LDAP user registry cannot be used to authenticate Cloud Manager and API Manager users. If you already have a writable LDAP user registry for use with the Cloud Manager or the API Manager, you must update the registry to be read-only by changing the User Managed property to be false.
- Starting with IBM API Connect Version 2018.4.1.9iFix1, after completion of the upgrade, some tasks may have stopped running. See Requirements for upgrading on VMware and Requirements for upgrading on Kubernetes describing action to take.
Finally, a Control Plane file is required if you are upgrading from v2018.4.1.5 or v2018.4.1.6 to v2018.4.1.16 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Documentation.
Support lifecycle policy for IBM API Connect Version 2018.4.1.16-ifix1:
IBM API Connect 2018.4.1.16-ifix1 is fix pack to a Long-Term Supported (LTS) release. API Connect 2018.4.1.16-ifix1 is a recommended product level for which support, including defect and security updates, will be provided through cumulative, in-place fix packs until the effective end of service (EOS) date for IBM API Connect 2018.4.1.x. An LTS release is intended for customers that may need a longer-term deployment for their environment. For more information, see IBM API Connect v2018.x Support Lifecycle.
Downloads:
Full installation files for IBM API Connect 2018.4.1.16-ifix1.0 and the IBM API Connect 2018.4.1.16-ifix1.0 Toolkit files can be downloaded from Fix Central :
Description – Filename | Date Published |
IBM API Connect Management V2018.4.1.16-ifix1.0 Containers
|
4 June 2021 |
IBM API Connect Developer Portal V2018.4.1.16-ifix1.0 Containers
|
4 June 2021 |
IBM API Connect Analytics V2018.4.1.16-ifix1.0 Containers
|
4 June 2021 |
IBM API Connect Management V2018.4.1.16-ifix1.0 for VMWare
|
4 June 2021 |
IBM API Connect Developer Portal V2018.4.1.16-ifix1.0 for VMWare
|
4 June 2021 |
IBM API Connect Analytics V2018.4.1.16-ifix1.0 VMWare
|
4 June 2021 |
IBM API Connect Installation Assist V2018.4.1.16-ifix1.0 for Linux®
|
4 June 2021 |
IBM API Connect Installation Assist V2018.4.1.16-ifix1.0 for Mac
|
4 June 2021 |
IBM API Connect Installation Assist V2018.4.1.16-ifix1.0 for Windows
|
4 June 2021 |
IBM API Connect Toolkit V2018.4.1.16-ifix1.0 for Linux®
|
4 June 2021 |
IBM API Connect Toolkit V2018.4.1.16-ifix1.0 for Mac
|
4 June 2021 |
IBM API Connect Toolkit V2018.4.1.16-ifix1.0 for Windows
|
4 June 2021 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.16-ifix1.0 for Linux®
|
4 June 2021 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.16-ifix1.0 for Mac
|
4 June 2021 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.16-ifix1.0 for Windows
|
4 June 2021 |
IBM API Connect V2018.4.1.16-ifix1.0Analytics.OVA Upgrade File
|
4 June 2021 |
IBM API Connect V2018.4.1.16-ifix1.0 Management Server.OVA Upgrade File
|
4 June 2021 |
IBM API Connect V2018.4.1.16 Developer Portal.OVA Upgrade File
|
4 June 2021 |
IBM DataPower Gateway for Docker Production Edition v2018.4.1.16 idg_dk20184116.lts.prod.tar.gz |
2 April 2021 |
IBM DataPower Gateway for Docker Non-Production Edition v2018.4.1.16 idg_dk20184116.lts.nonprod.tar.gz |
2 April 2021 |
Kubernetes DataPower Monitor v2018.4.1.16
|
2 April 2021 |
Security Signature Bundle File for API Connect v2018.4.1.16-ifix1.0 Files
|
4 June 2021 |
Ensure that you have read and understood the installation instructions for OVAs and Containers before downloading and by using the installation files. You can find detailed installation instructions in IBM API Connect Documentation -- Installing API Connect
IBM API Connect Control Plane for OVA upgrades
When upgrading from v2018.4.1.5 through v2018.4.1.8, on VMWare only, one or more Control Plane files must be downloaded and installed to bring Kubernetes to a supported release level. For more details, see Step 5 of the Upgrade Instructions in the API Connect IBM Documentation.
Description – Filename | Date Published |
IBM API Connect 1.14.0 Control Plane File for OVA (optional)
|
2 March 2020 |
IBM API Connect 1.15.0 Control Plane File for OVA (optional)
|
2 March 2020 |
IBM API Connect 1.16.0 Control Plane File for OVA (optional)
|
4 September 2020 |
IBM API Connect 1.17.0 Control Plane File for OVA (optional)
|
1 Feb 2021 |
IBM API Connect 1.18.0 Control Plane File for OVA (optional)
|
2 April 2021 |
IBM API Connect Local Test Environment is now available
The IBM API Connect Local Test Environment allows you to test APIs on your local machine, without the need to connect to an API Connect management server. For more details, see the IBM Documentation
Description – Filename | Date Published |
IBM API Connect Local Test Environment apic-lte-2018.4.16-161.zip |
2 April 2021 |
Was this topic helpful?
Document Information
Modified date:
24 August 2021
UID
ibm16439555