News
Abstract
IBM® API Connect v10.0.1.7 is now available.
Content
IBM® API Connect v10.0.1.7 delivers enhanced capabilities for the market-leading IBM® API Management solution. This update includes important internal development and field reported fixes as defined below.
For more information about API Connect v10.0.1.7, see API Connect IBM® Knowledge Center "What's New"
For licensing updates, see licensing updates note here
For new deployments: You can do a full installation that uses 10.0.1.7
When upgrading from API Connect v10.0.1.2 or greater on VMware:There are no special considerations required. Apply 10.0.1.7. Follow the instructions here. The steps apply when upgrading from v10.0.1.2 (with or without ifixes) to v10.0.1.7.
When upgrading from API Connect v10.0.1.1 or earlier: Read the following section:
- Special note when API Connect v10.0.1.1 or earlier is deployed that uses Virtual Appliances (OVAs) on VMware: v10.0.1.6 includes virtual appliances with a newer version of the operating system that requires a version migration to new virtual appliances. This procedure must be completed to move your product data. If the deployment is on v10.0.1.2 or greater this method does not apply. If you are performing a fresh installation of v10, it is highly recommended you begin with the latest delivery of v10.
- Special note when API Connect v10.0.1.1 or earlier is deployed on OpenShift v4 or any other Kubernetes platforms: Due to changes in Kubernetes operator, you must first upgrade to 10.0.1.2-ifix2, and then apply v10.0.1.5. Find information on upgrading to v10.0.1.2-fix2
Read the following section for special updates regarding moving from API Connect v2018 to v10:
- Upgrading from API Connect v2018 to v10 can be accomplished using specific combinations of v2018.4.1.17 or above and v10.0.1.x.
- For deployments on Kubernetes: An in-place upgrade path is available. To move to v10.0.1.5, v2018 must first be at v2018.4.1.17 or above, and Kubernetes must be at a version supported by v10.0.1.5 (see system requirements in IBM® Compatibility Reports.). See details here
- For deployments on VMware: A version migration path is available, where data is backed up from v2018 virtual appliances (OVAs) and data is restored into new v10.0.1.5 virtual appliances (OVAs) deployed separately. During the migration process, v2018 virtual appliances must be powered off. The gateways may remain powered on during the upgrade process of Manager, Portal, and Analytics subsystems. To move to v10.0.1.5, v2018 must first be at v2018.4.1.17 or above. See the IBM® Knowledge Center page for detailed instructions. More storage is required on v2018 OVAs during the upgrade process to perform the backup. See requirements here
- Find planning and overview materials related to moving from v2018 to v10 at API Connect: Upgrade Central
API Connect v10.0.1.7 contains all field APARs included in v10.0.1.6 as well as the following field reported APARs:
| APAR | Summary |
| LI82082 | ERRONEOUS ERROR MESSAGES ARE OUTPUT REGULARLY IN OVA SYSLOG |
| LI82424 | 403 ERROR WHILE ADDING CUSTOM ROLE FOR THE CONSUMER ORGANIZATION |
| LI82488 | GATEWAYSCRIPT V1.0.0 POLICY ON API GATEWAY MAY SET THE CONTENT TYPE TO UNKNOWN |
| LI82496 | EDIT SECURITY REQUIREMENTS OF AN OAUTH SECURITY SCHEME REMOVES SELECTED SCOPES |
| LI82515 | FOR V5C GATEWAY AFTER MIGRATION FROM V5 TO V10 THE NAME IN SSLCLIENTPROFILE FOR URLOPEN MODULE NO LONGER WORKS |
| LI82528 | V5 EMULATED POLICY FAILS WHEN NULL CONTEXT VARIABLES ARE PRESENT |
| LI82537 | INVOKE_1.5.0 AND PROXY_1.5.0 POLICIES GENERATE A PARSE FAILURE FOR HTML RESPONSES |
| LI82541 | EMULATED V5 POLICY WILL FAIL WITH AN XML PARSING ISSUE IF AN API PROPERTY HAS A SPECIAL XML CHARACTER |
| LI82542 | NVOKE_1.5.0 POLICY MAY NOT RETURN A RESPONSE ERROR PAYLOAD WHEN THE TARGET SERVER WAS NOT REACHABLE |
| LI82544 | INVOKE AND PROXY 150 DO NOT UPDATE MESSAGE.STATUS WHEN SPECIFYING AN RESPONSE OBJECT VARIABLE |
| LI82546 | API SUBSCRIPTION ISSUE DUE TO NAME MISMATCH- CHARACTER LIMITATION |
| LI82551 | STAN CLUSTER POD IN COMPLETED STATE |
| LI82552 | CLIENT-ID HEADER NOT SENT TO INVOKE_1.5.0 OR PROXY_1.5.0 POLICY BACKEND SERVER IN SOME INSTANCES |
| LI82562 | THE ACTIVATION SLIDER CONTROL DOESN'T SHOW UP IN API EDITOR WITHOUT GIVEN USER PERMISSION "PRODUCT:MANAGE" AT ORG LEVEL |
| LI82564 | MANAGEMENT-APIM POD MAY CRASH IF THE AUDIT ENDPOINT IS UNREACHABLE |
| LI82568 | SYSLOG AUDIT MESSAGES ARE INCORRECTLY TRANSLATED |
| LI82569 | WHEN IDG IS RESTARTED, DIFFERENT AUTHENTICATION URL REGISTRIES ARE REFLECTED IN IDG1, IDG2, AND IDG3. |
| LI82571 | DEVELOPER PORTAL (ADMIN) RESTART OCCURS UNEXPECTEDLY. |
| LI82572 | SEND TASK GOES TO FAILED STATE ON 500 DATABASE ERROR |
| LI82574 | APIC V10 - GUI FORM BLOCKS CONFIGURATION |
| LI82578 | V5 AND V5C APIS WITH A PROXY POLICY WILL EXECUTE POST PROXY POLICIES IF AN EXCEPTION IS THROWN BEFORE THE PROXY POLICY |
| LI82579 | TESTING XML FILE VALIDATION AGAINST AN XSD FAILS VALIDATION AS THE SCHEMA IS NOT RECOGNIZED. |
| LI82584 | USE OF DEFAULT VALUE FOR AN OPTIONAL PARAMETER IS NEVER ALLOWED TO BE EMPTY IN TRY IT |
| LI82595 | SWITCH POLICY WITH MANY CONDITIONS MAY EXHAUST CALL DEPTH LIMITS |
| LI82596 | PORTAL-TUNNEL PODS SHOULD NOT WRITE TO THEIR ROOT FILESYSTEM |
| LI82597 | PUBLISHING AN ALREADY PUBLISHED PRODUCT WITH SUBSCRIPTION (WITHOUT KEEPING SUBSCRIPTIONS) LEADS TO AN INCORRECT GATEWAY SNAPSHOT |
| LI82598 | BASICAUTH USER INPUT FAILS DUE TO SPECIAL CHARACTERS USING PORTAL TRY IT |
| LI82601 | CAN'T IDENTIFY USERS IN UI WHEN A UUID IS USED FOR USERNAME |
| LI82603 | LAZY MATCHING WHEN LOOKING FOR AN API IN MORE THAN ONE PRODUCT. |
| LI82604 | EXPLORER USERS SHOULD BE ABLE TO CHOOSE WHICH EXAMPLE TO DISPLAY WHEN MULTIPLE EXAMPLES ARE PROVIDED |
| LI82606 | APICONNECT-WSDL: MAX CALL STACK EXCEEDED IN TOBUFFER |
| LI82607 | DESIGNER ISSUE: APPLICATION AUTHENTICATION / CORS SETTINGS ARE NOT GETTING SAVED |
| LI82608 | NAME VALUE PAIRS IN QUERY PARAMETERS DON'T ALWAYS INCLUDE THE NAME |
| LI82609 | DELETE USER VIA API/CLI FROM APIM DOESN'T UPDATE THE PORTAL, APIM NEEDS TO SEND WEBHOOKS TO PORTAL |
| LI82613 | DUPLICATE FIELDS IN PORTAL TEST TOOL FOR ENUM PARAMETER WITH SCHEMA OF TYPE BOOLEAN |
| LI82615 | THE S3 BACKUP CODE DOESN'T WORK WITH A CUSTOM PORT. |
| LI82617 | ON DEVELOPER PORTAL CHANGE PASSWORD LOGS OUT USERS IF AN INCORRECT PASSWORD IS ENTERED |
| LI82618 | V10 PORTAL SUBSYSTEM REPEATEDLY PROGRESSING TO PASSIVE |
| LI82620 | IN API MANAGER, SUBSCRIPTION APPROVAL TASKS DOES NOT CORRECTLY DISPLAY PRODNAME, VERSION, PLAN, APPNAME, USERNAME, AND ORGNAME |
| LI82621 | OVERRIDE_PROVIDER_TTL OPTION FOR OIDC USER REGISTRY DOES NOT WORK |
| LI82622 | API ASSEMBLY DOESN'T POPULATE CATALOG TLS CLIENT PROFILES |
| LI82629 | RETRIEVING WSDL FOR API FROM PORTAL RETURNS ISO-8859 ENCODING |
| LI82630 | DRUPAL CORE OPTIONAL LOGIN FORM BLOCK DOESN'T ALLOW APIC LOGIN |
| LI82632 | ENCRYPT APP CREDENTIALS IN URL INSTEAD OF BASE64 ENCODE |
| LI82635 | GENERATED GATEWAYSCRIPT FOR MULTI-LINE CONDITIONALS IS INVALID IN SOME CASES |
| LI82640 | APPLICATION AUTHENTICATION SOURCE ERROR IN API MANAGER |
| LI82646 | UI ERROR WHEN CLICKING APPLICATION AUTHENTICATION |
| LI82703 | APIC MIGRATION V5 TO V10 CAUSED MANY API FAILED WITH MAPPING ISSUE |
| LI82673 | AMU PUSHES ALL CATALOGS WITH NAME STARTING AS ONE SELECTED WITH --CATALOGS FLAG |
| LI82453 | VIEW ENDPOINT IS WRONG IN THE MANAGER PORTAL |
| LI82828 | API PROTECTION FEATURE CHECKING IS NOT WORKING PROPERLY WHEN V5 AND V6 GATEWAYS ARE CONFIGURED IN A CATALOG |
Downloads:
Full installation files for IBM® API Connect v10.0.1.7 can be downloaded with proper entitlement from Fix Central.
| Description – Filename | Date Published |
|
IBM® API Connect Analytics v10.0.1.7 for VMWare
|
24 Jun 2022 |
|
IBM® API Connect Local Test Environment v10.0.1.7
|
24 Jun 2022 |
|
IBM® API Connect Local Test Environment v10.0.1.7 for Linux
|
24 Jun 2022 |
|
IBM® API Connect Local Test Environment v10.0.1.7 for OSX
|
24 Jun 2022 |
|
IBM® API Connect Local Test Environment v10.0.1.7 for Windows
|
24 Jun 2022 |
|
IBM® API Connect v10.0.1.7 for Containers
|
24 Jun 2022 |
|
IBM® API Connect Operator Release Files v10.0.1.7 for Containers
|
24 Jun 2022 |
| IBM® API Connect Operator Upgrade Release Files v10.0.1.7 for Containers apiconnect-operator-upgrade-release-files_10.0.1.7.zip |
24 Jun 2022 |
|
IBM® API Connect Install Assist v10.0.1.7 for Linux®
|
24 Jun 2022 |
|
IBM® API Connect Install Assist v10.0.1.7 for Mac
|
24 Jun 2022 |
|
IBM® API Connect Install Assist v10.0.1.7 for Windows
|
24 Jun 2022 |
|
IBM® API Connect Management v10.0.1.7 for VMWare
|
24 Jun 2022 |
|
IBM® API Connect Developer Portal v10.0.1.7 for VMWare
|
24 Jun 2022 |
|
IBM® API Connect Toolkit v10.0.1.7 for Linux®
|
24 Jun 2022 |
|
IBM® API Connect Toolkit Designer with Loopback v10.0.1.7 for Linux®
|
24 Jun 2022 |
|
IBM® API Connect Toolkit Designer with Loopback v10.0.1.7 for Mac
|
24 Jun 2022 |
|
IBM® API Connect Toolkit Designer with Loopback v10.0.1.7 for Windows
|
24 Jun 2022
|
|
IBM® API Connect Toolkit with Loopback v10.0.1.7 for Linux®
|
24 Jun 2022 |
| IBM® API Connect Toolkit with Loopback v10.0.1.7 for Mac | 24 Jun 2022 |
| IBM® API Connect Toolkit with Loopback v10.0.1.7 for Windows | 24 Jun 2022 |
|
IBM® API Connect Toolkit v10.0.1.7 for Mac
|
24 Jun 2022 |
|
IBM® API Connect Toolkit v10.0.1.7 for Windows
|
24 Jun 2022 |
|
IBM® API Connect Analytics v10.0.1.7 Upgrade File
|
24 Jun 2022 |
|
IBM® API Connect Management Server Upgrade File v10.0.1.7
|
24 Jun 2022 |
|
IBM® API Connect v10.0.1.7 Portal Upgrade File
|
24 Jun 2022 |
| IBM® API Connect script and assets required for v10->v10.0.1.7 side-by-side upgrades v10_ova_dr_files_10.0.1.7.tgz |
24 Jun 2022 |
| IBM® API Connect scripts and assets required for v2018->v10.0.1.7 side-by-side upgrades v2018_ova_upgrade_files_10.0.1.7.tgz |
24 Jun 2022 |
|
IBM® API Connect Security Signature Bundle File v10.0.1.7
|
24 Jun 2022 |
API Connect v10.0.1.7-R0 Migration Utility
| Description – Filename | Date Published |
|
IBM® API Connect Migration Utility v10.0.1.7-R1
|
16 Aug 2022 |
IBM API Connect Control Plane for OVA upgrades
When upgrading on VMWare the following Control Plane files may be required to be downloaded and installed to bring Kubernetes to a supported release level. For more details, see Step 4 of the Upgrade Instructions in the API Connect IBM Documentation.
When upgrading on VMWare the following Control Plane files may be required to be downloaded and installed to bring Kubernetes to a supported release level. For more details, see Step 4 of the Upgrade Instructions in the API Connect IBM Documentation.
| Description – Filename | Date Published |
|
IBM API Connect 10.0.4.0-ifix1 Control Plane File for OVA (optional)
|
3 Jun 2022 |
[{"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:
27 September 2023
UID
ibm16598487