News
Abstract
IBM API Connect V2018.4.1.9-ifix1 is now available. This update includes important internal development and 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 2018.4.1.9-ifix1 update includes important internal development and field reported fixes.
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.9-ifix1 for VMWare (.OVA) deployments. You cannot upgrade your API Connect topology to 2018.4.1.9-ifix1 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.9-ifix1 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.9-ifix1 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Knowledge Center.
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 Knowledge Center for more information on this and new features included in API Connect v2018.4.1.9-ifix1.
API Connect v2018.4.1.9 contains the following field reported APARs:
APAR | Summary |
LI80983 | INCORRECT API CALL ROUTING DUE TO SYNC ISSUE IN CATALOG BETWEEN MANAGER AND GATEWAY |
LI81089 | MAP POLICY UI MAY SHOW DUPLICATE SCHEMAS THAT SHOW DUPLICATE MAPPING WIRES |
LI81105 | RESTRICT ROLE BY IP IS NOT WORKING IN DEV PORTAL |
LI81112 | CHANGING A DRUPAL ROLE NAME DOESNT UPDATE THE ACTIONS MENU ON THE PEOPLE LIST PAGE |
LI81114 | LAST PAGE OF APPLICATION LIST DOES NOT SHOW END OF LIST WHEN PRESENTED BY MULTIPLE PAGES |
LI81128 | REPLACING A PRODUCT WITH ANOTHER ONE WHICH CONTAINS A DIFFERENT CUSTOM VISIBILITY RESULT IN 504 (TIMEOUT) AND 409 (LOCK) ERRORS |
LI81130 | PERFORMANCE OF EXPLORER WITH LARGE COMPLEX RESPONSE IN PORTAL AND CHROME |
LI81131 | DUPLICATE PARAMETERS IN PATH AFTER IMPORTING REST API |
LI81133 | UI NOT CONFORMING TO THE YAML SPEC WHEN CREATING A NEW PARAMETER |
LI81135 | GROUP BY SUMMARY SHOWS SUMMARY AND PATH IN WHEN GROUPED BY TAGS IS ALSO SELECTED |
LI81137 | ANALYTICS NOT WORKING, RETURNING AUTHENTICATION ERROR, INVALID COOKIE |
LI81138 | ADD OPTION TO PORTAL TO HIDE X-CLIENT-CERTIFICATE HEADER WHEN USING MTLS |
LI81141 |
CERTIFICATES NOT REMOVED FROM CRYPTO VALIDATION CREDENTIALS IN DATAPOWER WHEN UPDATING TRUSTSTORE IN API CONNECT CLOUD ADMIN
|
LI81142 | OPEN API VALIDATION ERRORS OF AN API IN PORTAL EXTRA 'VALUE' GETS ADDED TO SWAGGER DEFINITION |
LI81143 | ACCESS-CONTROL-ALLOW-ORIGIN HEADER CONTAINS WILDCARD |
LI81146 | MAP SET ACTION WITH A DEFAULT OF NULL DOES NOT USE THE API PROPERTY TO ENABLE NULL MAPPED VALUES |
LI81150 | CLOUD MANAGER REGISTER SERVICE PAGE UI DOESN'T ALLOW ENDPOINTS THAT TRAILING WITH NUMBERS |
LI81151 | API CONFIGURATION OBJECTS NOT CLEANED UP FROM GATEWAY SERVER UNDER CERTAIN CIRCUMSTANCES |
LI81159 | A CONNECTIONERROR ON A PROXIED WEB SERVICE REQUEST WILL NOT RETURN AN ERROR RESPONSE |
LI81163 | REMOTE CODE EXECUTION VULNERABILITY IN PHP7 CVE-2019-11043 |
LI81168 | MAP POLICIES CREATED BY MIGRATION FROM APIM V4 TO API CONNECT V5 MAY NOT MAP ARRAYS IN SOME CASES |
LI81170 | PATHS ORDER IS CHANGED ON UPDATING PATH |
LI81173 | EMAIL SUBSCRIBERS FROM DEVELOPER PORTAL FAILS |
LI81176 | 204 RESPONSE WITH NO PAYLOAD GETS PARSE ERROR WHEN RESPONSE INCLUDES CONTENT-TYPE |
LI81177 | METHOD NOT ALLOWED ERROR HAS NO LOGGING INDICATING THE FAILING REQUEST URI |
LI81188 | DEVELOPER PORTAL EXPLORER NOT SCROLLING BACK TO TOP WHEN SWITCHING BETWEEN OPERATIONS OF AN API |
LI81190 | CALLING API WITHOUT "ACCEPT" HEADER DATAPOWER API GATEWAY ERROR RESPONSE DOESN'T HONOR THE PRODUCES PROPERTY DEFINED IN SWAGGER |
LI81192 |
WEBFORM MODULES' EMAIL FUNCTION DOESN'T WORK AFTER UPGRADE
|
LI81194 | TARGET SERVICE ADDED TO EXISTING API ALWAYS CREATED AS DATAPOWER-GATEWAY |
LI81195 | USERS IN API MANAGER WITH VIEWER ROLE ABLE TO ADD API AND PRODUCT |
LI81209 | WRONG GERMAN TRANSLATION FOR "EXAMPLE REQUEST" IN API DESCRIPTION |
LI81239 | API USING PATCH VERB MAY FAIL IN DEVELOPER PORTAL |
LI81249 | UPGRADE TO 2018.4.1.8 MAY FAIL WITH ENOBUFS ERROR |
LI81261 | API MANAGER UI SLOWNESS WHEN LISTING CONSUMER ORGANIZATIONS AND APPLICATIONS |
LI81262 | SLOW SYSTEMS ALONG WITH LOTS OF USER ACTIVITY CAN CAUSE SERVICES TO GET OR REMAIN OUT OF SYNC |
LI81314 |
KUBERNETES VULNERABILITY CVE-2019-11251
|
LI81317 | DEVELOPER PORTAL EMAIL SUBSCRIBERS 'ALL USERS' OPTION RETURN ERROR: THE WEBSITE ENCOUNTERED AN UNEXPECTED ERROR |
API Connect v2018.4.1.9-ifix1 contains the following field reported APARs:
APAR | Summary |
LI80875 | INTERMITTENT 504 ERRORS AFTER ONE NODE IN A MANAGEMENT CLUSTER GOES DOWN |
LI81185 | DEPRECATED PRODUCT AND SUBSCRIPTION DISAPPEAR FROM PORTAL UI |
LI81236 | API MANAGEMENT SERVER WEBHOOKS CAN REMAIN STUCK PREVENTING THE SYNCHRONIZATION TO DATAPOWER GATEWAY AND/OR DEVELOPER PORTAL |
LI81246 | PARAMETER FORMAT ATTRIBUTES ARE INCORRECTLY DELETED BY DESIGNER AFTER CLICK SAVE |
LI81247 | API CONNECT DEVELOPER PORTAL: THE CSYNC2 SQLITE DATABASES NEED OCCASIONAL VACUUMING |
LI81274 | APIC DEVELOPER PORTAL DRUPAL VULNERABILITIES |
LI81279 | API MANAGER DEVELOPER SECTION SHOWS LAST MODIFIED DATE AS CURRENT TIME FOR APIS AND PRODUCTS |
LI81281 | THE DEVELOPER PORTAL BLOCKS THE LOAD BALANCER IP ADDRESS |
LI81294 | MISSING TRANSLATIONS IN PORTAL |
LI81295 | GOLANG VULNERABILITIES |
LI81299 | UPGRADE FAILURE ON PORTAL DUE TO PROBLEM SITE |
LI81316 | AFTER UPGRADE TO 2018.4.1.9, API DESIGNER MIGHT FAIL TO LOGIN TO API MANAGER |
LI81340 | IN API MANAGER APPLICATIONS TAB, THE CONSUMER ORGANIZATION FIELD NO LONGER THERE AFTER UPGRADE TO 2018.4.1.9 |
LI81424 | MYSQL UPDATE |
*** 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 Knowledge Center: What's new in this release.
Important notes on upgrading to 2018.4.1.9-ifix1:
When upgrading to Version 2018.4.1.9-ifix1 or later, 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.
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.9 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Knowledge Center.
Support lifecycle policy for IBM API Connect Version 2018.4.1.9-ifix1:
IBM API Connect 2018.4.1.9-ifix1 is fix pack to a Long-Term Supported (LTS) release. API Connect 2018.4.1.9-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.9-ifix1 and the IBM API Connect 2018.4.1.9-ifix1 Toolkit files can be downloaded from Fix Central :
Description – Filename | Date Published |
IBM API Connect Management V2018.4.1.9-ifix1 Containers
|
31 January 2020 |
IBM API Connect Developer Portal V2018.4.1.9-ifix1 Containers
|
31 January 2020 |
IBM API Connect Analytics V2018.4.1.9-ifix1 Containers
|
31 January 2020 |
IBM API Connect Management V2018.4.1.9-ifix1 for VMWare
|
31 January 2020 |
IBM API Connect Developer Portal V2018.4.1.9-ifix1 for VMWare
|
31 January 2020 |
IBM API Connect Analytics V2018.4.1.9-ifix1 for VMWare
|
31 January 2020 |
IBM API Connect Installation Assist V2018.4.1.9-ifix1 for Linux®
|
31 January 2020 |
IBM API Connect Installation Assist V2018.4.1.9-ifix1 for Mac
|
31 January 2020 |
IBM API Connect Installation Assist V2018.4.1.9-ifix1 for Windows
|
31 January 2020 |
IBM API Connect Toolkit V2018.4.1.9-ifix1 for Linux®
|
31 January 2020 |
IBM API Connect Toolkit V2018.4.1.9-ifix1 for Mac
|
31 January 2020 |
IBM API Connect Toolkit V2018.4.1.9-ifix1 for Windows
|
31 January 2020 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.9-ifix1 for Linux®
|
31 January 2020 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.9-ifix1 for Mac
|
31 January 2020 |
IBM API Connect Toolkit Designer with Loopback V2018.4.1.9-ifix1 for Windows
|
31 January 2020 |
IBM API Connect V2018.4.1.9-ifix1Analytics.OVA Upgrade File
|
31 January 2020 |
IBM API Connect V2018.4.1.9-ifix1 Management Server.OVA Upgrade File
|
31 January 2020 |
IBM API Connect V2018.4.1.9-ifix1 Developer Portal.OVA Upgrade File
|
31 January 2020 |
IBM DataPower Gateway for Docker Production Edition v2018.4.1.9 idg_dk2018419.lts.prod.tar.gz |
13 December 2019 |
IBM DataPower Gateway for Docker Non-Production Edition v2018.4.1.9 idg_dk2018419.lts.nonprod.tar.gz |
13 December 2019 |
Kubernetes DataPower Monitor v2018.4.1.9
|
13 December 2019 |
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 Knowledge Center -- Installing API Connect
IBM API Connect Control Plane for OVA upgrades
When upgrading from v2018.4.1.5 or v2018.4.1.6 to v2018.4.1.9, on VMWare only, a Control Plane file 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 Knowledge Center.
Description – Filename | Date Published |
IBM API Connect 1.14.0 Control Plane File for OVA (optional)
|
13 December 2019 |
ICP Installation Files for API Connect v2018.4.1.9
Description – Filename | Date Published |
IBM API Connect ICP Enterprise V2018.4.1.9-ifix1 IBM_API_Connect_ICP_Enterprise_2018.4.1.9-ifix1.0.zip |
5 February 2020 |
IBM API Connect ICP Professional V2018.4.1.9-ifix1 IBM_API_Connect_ICP_Professional_2018.4.1.9-ifix1.0.zip |
5 February 2020 |
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 Knowledge Center
Description – Filename | Date Published |
IBM API Connect Local Test Environment apic-lte-2018.4.1.9-ifix1.0.zip |
31 January 2020 |
Was this topic helpful?
Document Information
Modified date:
12 May 2020
UID
ibm11128723