IBM API Connect V2018.4.1.17-ifix2 is now available

API Connect v2018.4.1.17-ifix1.0 contains the following field reported and security APARs:

API Connect v2018.4.1.17-ifix2.0 contains the following field reported and security APAR:

*** 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.17-ifix2:

When upgrading to Version 2018.4.1.17-ifix2, 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.17-ifix2 (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.17-ifix2:

IBM API Connect 2018.4.1.17 is fix pack to a Long-Term Supported (LTS) release.  API Connect 2018.4.1.17 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.17-ifix2 and the IBM API Connect 2018.4.1.17-ifix2 Toolkit files can be downloaded from Fix Central :

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 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

What is Fix Central (FC)?