News
Abstract
IBM® API Connect V10.0.1.2-ifix2 is now available. This update includes important internal development and field reported fixes.
Content
IBM® API Connect v10.0.1.2-ifix2 delivers enhanced capabilities for the market-leading IBM® API Management solution. In addition to the ability to deploy in complex, multi-cloud topologies, this update introduces more upgrade capability from v2018.
For more information about API Connect v10.0.1.2-ifix1, see API Connect IBM® Knowledge Center "What's New"
Read the following section for special updates regarding upgrading from earlier versions of API Connect v10
- Special note when API Connect v10 is deployed that uses Virtual Appliances (OVAs) on VMware: v10.0.1.2-ifix2 includes virtual appliances with a newer version of the operating system that does not allow for in-place upgrade of the virtual appliances. If you are performing a fresh installation of v10, it is highly recommended you begin with v10.0.1.2-ifix2. New v10.0.1.2-ifix2 virtual appliances must be deployed after you upgrade from any previous v10.x.x.x (except v10.0.1.2 and v10.0.1.2-ifix1) level deployed on VMware. This procedure must be completed to move your product data.
- Special note when API Connect is deployed on OpenShift v4.x: Due to changes in Kubernetes operator, a workaround is needed after v10.0.1.0 to v10.0.1.2-ifix2 upgrade. This workaround has no downtime. See IBM® Knowledge Center page. This method is also applicable for IBM® Cloud Pak for Integration clients upgrading from version 2020.3.1 (API Connect v10.0.1.0) to 2020.4.1 EUS, which allows upgrade of API Connect to v10.0.1.2-ifix2. See the following IBM® Knowledge Center page. If you are already on v10.0.1.2-ifix2, this issue is not seen. If you are not on OpenShift, this issue is not applicable.
- Special note: For more information about upgrading from v10.0.1.2 to v10.0.1.2-ifix2, see following links
- Upgrade from v10.0.1.2 to v10.0.1.2-ifix2 on VMware
- Upgrade API Connect from v10.0.1.2 to v10.0.1.2-ifix2 on native Kubernetes
- Upgrade API Connect from v10.0.1.2 to v10.0.1.2-ifix2 on OpenShift
For clients upgrading from API Connect v2018.4.1.15
- For deployments on Kubernetes: An in-place upgrade path is available. To upgrade to v10.0.1.2-ifix2, v2018 must first be at v2018.4.1.15, and Kubernetes must be at a version supported by v10.0.1.2-ifix2 (see system requirements in IBM® Compatibility Reports.). See details here
- New: For deployments on VMware: A side-by-side upgrade path is available, where data is backed up from v2018 virtual appliances (OVAs) and restore data into new v10.0.1.2-ifix2 virtual appliances (OVAs) must be deployed separately. During the upgrade process, v2018 virtual appliances must be powered off. The gateways might not be powered off during the upgrade process of Manager, Portal, and Analytics subsystems. To upgrade to v10.0.1.2-ifix2, v2018 must first be at v2018.4.1.15. See the IBM® Knowledge Center page for full upgrade instructions. More storage is required on v2018 OVAs during the upgrade process to perform the backup. See requirements here
Note: Upgrade from v10.0.1.2-ifix2 to v10.0.2.0 is not supported
API Connect v10.0.1.2-ifix2 contains the following field reported APARs:
| APAR | Summary | |
| LI81307 | UPGRADE SERVER SSH KEY TO BE MORE THAN 1024 BITS | |
| LI81533 | RETIRING OR REMOVING A PRODUCT FROM APIC MANAGER UI DOES NOT DELETE API FROM THE PORTAL | |
| LI81721 | DUPLICATE APPROVAL EMAILS SENT TO ORG OWNER FOR CANCELED SUBSCRIPTION APPROVAL WHEN CATALOG HAS A SPACE | |
| LI81851 | CREATE AN APPLICATION DIALOG TITLE IS NOT TRANSLATED IN THE PORTAL | |
| LI81853 | TEST CONNECTION FOR EMAIL SERVER SENDS BLANK PASSWORD ON EDIT | |
| LI81882 | PORTAL SESSION IS VALID EVEN AFTER THE BROWSER IS RESTARTED | |
| LI81898 | CP4I APIC 10.0.1.0 - AUTOMATIC TLS SECRET REFRESH DID NOT WORK - CERTS EXPIRED AFTER 90 DAYS | |
| LI81906 | 2 GWS IS ASSOCIATED WITH OTHER ANALYTICS SERVICE, IS TIED TO THE SAME CATALOG, BUT ANALYTICS DATA IS DISPLAYED ON PORTAL. | |
| LI81912 | INCOMPATIBILITY OF CATALOG BASED API PROPERTIES COMPARED TO VERSION 5 | |
| LI81917 | API NOT MASKING PERSONAL DATA | |
| LI81932 | SITE MISSING ON PORTAL SYSTEM RESTORE | |
| LI81938 | CANNOT DISABLE APPLICATION ON APIM | |
| LI81943 | CREDENTIALS CREATION FAILING WHEN APP NAME IN ID FORMAT | |
| LI81944 | MIGRATION UTILITY - ADD TOGGLE FOR V5 REQUEST.HEADERS | |
| LI81855 | THE VALUE OF CATALOG PROPERTY CANNOT BE EDITED AFTER CREATING | |
| LI81858 | JSONWEBTOKEN MODULE DOES NOT TAKE INTO ACCOUNT OF THE JWKS -> X5C FORMAT | |
| LI81890 | CONSUMER ORG INVITATION LOGIN FAILURE - OIDC USER REGISTRY | |
| LI81895 | 'RESEND INVITE' FAILS TO SEND ON CONSUMER ORGANIZATION | |
| LI81966 |
THE 'DEVELOP' PAGE IS NOT AUTOMATICALLY UPDATED WITH USER CHANGES.
|
|
| LI81990 |
PRODUCTS (SUBSCRIPTIONS) NOT LOADING PROPER NUMBERS AT FIRST
|
|
| LI81936 |
|
|
| LI81964 |
NATS-STREAMING-OPERATOR CONTINUOUSLY FAILING TO SCALE STANCLUSTER TO 3 PODS
|
|
| LI81989 |
API CONNECT ANALYTICS - RETENTION/ROLLOVER CRON JOB FAILING
|
|
| LI82002 |
OOM WHEN RUNNING PORTAL SITE CONTENT REFRESH WHERE DUPLICATE USERS ARE PRESENT.
|
|
| LI82003 |
OCP UPGRADE OF APICONNECT FROM 10.0.1.0 TO 10.0.1.1 GETS STUCK
|
|
| LI82008 |
SITE RESTORE FAILS DUE TO THE MAX_ALLOWED_PACKET LIMIT
|
|
| LI82009 |
RENEW CERTS STEPS CONFUSING
|
|
| LI82041 | CREATING A (SOAP PROXY) USING IBM® API CONNECT FROM MULTIPART WSDL FILE VIA API MANAGER ISSUED AND ERROR | |
| LI82013 | Docker CVE-2021-21284 CVE-2021-21285 | |
| LI82026 | OpenSSL CVE-2020-1971 | |
| LI82047 |
PGBOUNCER CANNOT START DUE TO DNS SERVER ISSUES.
|
|
| LI82014 | Node.js CVEs | |
| LI82062 | ABILITY TO DISABLE DEBUG LOGGING IN IBM-APICONNECT OPERATOR POD IN V10.0.1.2 | |
| LI82102 | API DEFINITION MAY BECOME UNUSABLE WHEN UPGRADING FROM V2018 TO V10 | |
| LI82056 | Performing more than 1 restore causing WAL files to grow and eventually fill up the disk | |
| LI82059 | APIS MAY FAIL AFTER UPGRADE FROM V2018 TO V10 | |
| LI82080 | REGEX PATTERNS INCORRECTLY MODIFIED DURING UPGRADE FROM 2018 TO V10 | |
| LI82099 |
DOUBLE QUOTES PRESENT WITH ESCAPE SLASHES
|
|
| LI82128 |
CONVERSION OF OAUTH PROVIDER FAILS, CAUSING APIS IN CATALOG NOT TO APPEAR IN THE GATEWAY
|
|
| LI81973 | ERROR "413: REQUEST ENTITY TOO LARGE" OCCURS WHILE UPLOADING A CUSTOM THEME ONTO DEVPORTAL VIA CLI | |
| LI82164 | HA MODE STUCK IN "PROGRESSING TO ACTIVE" IN ACTIVE NODE | |
| LI82126 | MIGRATION TOOL ERROR BUT CONTINUE ON INVALID $REF | |
| LI82133 | MIGRATION OF API WITHOUT DEFAULT PROPERTIES FAILS TO PUBLISH | |
| LI82132 | MIGRATION ARCHIVE:PUSH COMMAND FAILS FOR SOAP-BASED APIS WHEN WSDL ZIP CONTAINS UNEXPECTED FILES | |
| LI82095 | ERROR WHILE REGISTERING DEV PORTAL SERVICE IN CLOUD MANAGER UI. |
Downloads:
Full installation files for IBM® API Connect 10.0.1.2-ifix2 can be downloaded from Fix Central :
| Description – Filename | Date Published |
|
IBM® API Connect v10.0.1.2-ifix2 Analytics for VMWare
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Local Test Environment
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Local Test Environment for Linux
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Local Test Environment for OSX
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Local Test Environment for Windows
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 for Containers
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Operator Release Files for Containers
|
23 March 2021 |
| IBM® API Connect v10.0.1.2-ifix2 Operator Upgrade Release Files for Containers apiconnect-operator-upgrade-release-files_10.0.1.2-ifix2.zip |
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Install Assist for Linux®
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Install Assist for Mac
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Install Assist for Windows
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Management for VMWare
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Developer Portal for VMWare
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit for Linux®
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit Designer with Loopback for Linux®
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit Designer with Loopback for Mac
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit Designer with Loopback for Windows
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit with Loopback for Linux®
|
23 March 2021 |
| IBM® API Connect v10.0.1.2-ifix2 Toolkit with Loopback for Mac toolkit-loopback-mac_10.0.1.2-ifix2.zip |
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit with Loopback for Windows
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit for Mac
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Toolkit for Windows
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Analytics Upgrade File
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Management Server Upgrade File
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Portal Upgrade File
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 script and assets required for v10->v10.0.1.2 side-by-side upgrades
|
23 March 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 scripts and assets required for v2018->v10.0.1.20-ifix1 side-by-side upgrades
|
06 May 2021 |
|
IBM® API Connect v10.0.1.2-ifix2 Security Signature Bundle File
|
06 May 2021
|
API Connect v10.0.1.1 Migration Utility
| Description – Filename | Date Published |
|
IBM® API Connect Migration Utility v10.0.1.2
|
25 June 2021 |
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000L0rvAAC","label":"API Connect"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
22 July 2021
UID
ibm16445859