What's new in Version 10.0.8.1

What's new for Developers

AI Gateway functionality on DataPower® API Gateway

Enabling this feature activates AI Gateway policies on the DataPower API Gateway, allowing you to create REST proxies that utilize the AI Gateway to control access to AI models. For more information, see Using the AI Gateway to support APIs for AI applications.

Local Test Environment updates

• You can now configure the toolkit credentials for the Local Test Environment by using the following command:

  apic client-creds:set ~/.apic-lte/credentials.json

• You can now launch the API Designer user interface by using the following command:

  APIC_DESIGNER_CREDENTIALS=~/.apic-lte/credentials.json <path-to-designer>

For more information, see Starting the Local Test Environment and Preparing an API for testing in the Local Test Environment

Language configuration for CLI command outputs

You can now set the language for CLI command outputs by using the --lang flag. This flag allows you to receive command outputs in your preferred language from a list of supported languages. For more information, see Setting the language.

Bulk import feature for AsyncAPIs from EEM

A bulk import feature is now available, enabling users to select and import multiple AsyncAPI definitions from Event Endpoint Manager (EEM) into API Connect. For more information, see Importing an AsyncAPI from Event Endpoint Management.

Improved UI notifications for product publishing

Enhanced the notifications for product publishing. Previously, a plain text message appeared. Now, the notification includes visual symbols to indicate the status of the publishing process. For more information, see Publishing a draft product.

What's new for API product managers

Analytics client dashboard includes longitude and latitude

The map of IP addresses in the client dashboard now shows the longitude and latitude, in addition to the geohash.

Analytics consumption report

A new API consumption report is available from the Cloud Manager and API Manager UIs. The consumption report contains the same data as the consumption dashboard, and can be used to report usage for consumption-based licensing. For more information, see Counting total API calls.

Governance service updates

The following governance service updates are now available.

• Product scanning. You can now run governance scans on the products in your catalogs and spaces, to validate the products that they contain, as well as running scans on the APIs. For more information, see Scanning your catalogs and spaces.
• Tags in API rulesets. You can now add one or more tags to your governance service API rulesets. If you have matching tags in both your APIs and rulesets, then the appropriate rulesets are pre-selected for your validation scans, and the governance process can be run more quickly and effectively. For more information, see Configuring governance in the Cloud Manager and Configuring governance in the API Manager.

The Config Sync feature is no longer a Technology Preview

The Config Sync feature is fully released and supported. See Using Config Sync to replicate consumer-side catalog data.

Config Sync records the number of resources that are processed during a synchronization in the analytics subsystem. The results can be viewed in the consumption dashboard. For users on call volume licensing, the amount of data that is synchronized is converted to API calls and is included in your call volume license.

What's new for API consumers

New analytics charts in the Developer Portal

The Developer Portal analytics view has two new charts at both application and consumer organization scope:

• Top APIs over time.
• Top products over time.

New features in Consumer Catalog

The Consumer Catalog now supports local user registry or OIDC user registry, the ability to view analytics for an application, and the ability to delete consumer accounts. For more information, see Consumer Catalog and Developer Portal considerations

What's new for Developer Portal site administrators

Limiting API details visibility for non-authenticated users

In the previous releases, both the authenticated and non-authenticated users can view all the API details if the respective API product is viewable. Now, you can limit the API details visibility for non-authenticated users by selecting the Show API details to anonymous users setting in the Developer Portal. For more information, see Configuring the API details visibility for non-authenticated users.

Additional options for selecting email recipients in the Portal mailing wizard

The Portal users can now select a consumer organization or groups of consumer organizations in mailing wizard. For more information, see Emailing consumer organizations.

Admin Portal updated to Drupal 10.3

The Admin Portal has been updated to Drupal 10.3 which uses a new Admin navigation. The portal tutorials and other Drupal admin related docs are updated to reflect the new Admin navigation.

What's new for DevOps

Support for restricted pod security enforcement using namespace labels

API Connect 10.0.8.1 on Kubernetes now supports deploying subsystems in namespaces configured with the "enforce=restricted" policy.

Replicating analytics data to a 2DCDR warm-standby data center

If you have a two data center warm-standby deployment, you can configure the analytics subsystem in your active data center to offload incoming API event records to the analytics subsystem in your warm-standby data center. For more information, see Replicating analytics data to a 2DCDR warm-standby data center.

Automated API behavior testing: Smart generation and Autotest assist are now available in API Connect on Kubernetes and OpenShift Container Platform

Beginning with API Connect 10.0.8.1, the Smart generation and Autotest assist features of the Automated API behavior testing application are available in API Connect when deployed on Kubernetes or OpenShift Container Platform. These test features are not available when you deploy API Connect on VMware.

For instructions on enabling these features on Kubernetes or OpenShift Container Platform, see the "Enabling Autotest Assist Smart Generation" section of Installing the Automated API behavior testing application.

Analytics data retention period defined by deployment profile

The default retention period of analytics data was set to 30 days for one replica profiles and 90 days for three replica profiles. In V10.0.8.1, the default retention period is set according the analytics deployment profile:

Table 1. Default analytics retention periods

Profile	Retention (days)
n1xc2.m16	3
n1xc4.m32	30
n1xc6.m48	45
n3xc4.m16 - DEPRECATED	2
n3xc4.m32	30
n3xc6.m48	45
n3xc8.m64	45

Analytics offload support for two parallel pipelines

In previous releases, all analytics offload targets were configured in spec.external.offload and run in series. A second pipeline configuration section (spec.external.offload2) is added in V10.0.8.1, which runs in parallel. For more information about analytics offload, see Offload to third-party systems.

Ability to increase analytics Logstash persistent queue size

A new ingestion.queue.defaultQueueSize property is added to the analytics subsystem. Users can increase the queue size following the steps here: Logstash persistent queue.

Filter apicup certs list output for user-facing endpoints and credentials

Two new arguments are added to apicup certs list:

• apicup certs list --endpoints outputs only user-facing endpoint certificates.
• apicup certs list --creds outputs only credentials and encryption secrets.

Update to Ubuntu Linux on VMware

The Ubuntu Linux version is upgraded to from v20.04 to v22.04. Extra upgrade steps are required, see Upgrading management, portal, and analytics on VMware.

Cert-manager is upgraded to version 1.12.13

API Connect 10.0.8.1 uses cert-manager 1.12.13. If your environment requires a manual installation or upgrade of cert-manager, the instructions are included as part of the API Connect installation and upgrade procedures.

Support for API Connect operator at different version from API Connect subsystems

You can now run the API Connect operator at a different version from the API Connect subsystems. See the supported combinations in the installation documentation for your platform Kubernetes, OpenShift, and Cloud Pak for Integration.