Release 11.1.0

Highlights

Changed Items

• Enhancements to API Monetization

  API Monetization allows package subscriptions to use any IAM policy without disrupting the existing Identity & Authorize policy configured at the API level, such as JWT or OAUTH.

• Deploying Consumer Applications

  Enhancements to deploying consumer applications allows customers to promote OAuth2 strategies with additional options to control the overwriting of client IDs and secrets or the refreshing of client secrets.

Deprecated Items

The following Destinations are deprecated and will be removed in future releases:

• Centrasite
• Email

Usage Notes

This section provides any additional information that you need, to work with IBM webMethods API Gateway.

• IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. Click here for information on the available products and also the underlying infrastructure provider in each region. For details about the IP addresses for IBM webMethods API Gateway in all regions, see IBM webMethods iPaaS page.

• Information on major releases, hotfixes, and patch releases including the latest statistics on cloud environments availability, incident history, and planned maintenance events are available on the Service Status page.

• Do not provide values starting with a dot (.), in any of the fields in API Gateway UI and in key values when making API calls from a REST client.

The link provided in the Documentation section of the API details tab can be accessed using API gateway internal users credentials and cannot be accessed using SSO user credentials.

The following functionalities have certain restrictions in IBM webMethods API Gateway instance on cloud:

• API support
  webSocket API is not supported.

• Policy support
  

  • Custom filter is not supported for a rule configuration under Threat Protection policy

  • The following policies are not supported in a cloud instance as they are relevant only for an on premise deployment:

    • Enable JMS/AMQP
    • JMS/AMQP Routing
    • JMS/AMQP Properties
    • Authorize User
    • Invoke webMethods IS
      
      

• Policy Properties support
  The following policy properties are not supported in API Cloud API Gateway instance:

  • Audit Log, JDBC, Digital Events, and SNMP destinations are not available in the following policies:

    • Log Invocation
    • Monitor Performance
    • Monitor SLA
    • Traffic Optimization
      
      

  • Kerberos Token Authentication property is not available in the Inbound Authentication - Transport policy

  • The following properties are not available in the Inbound Authentication - Message policy:

    • Validate SAML Audience URL
    • Require SAML Token under Token Assertions
      
      

  • The Run as user property is not available in the following policies:

    • IS Service alias
    • Request Transformation
    • Response Transformation
    • Conditional Error Processing
      
      

  • Administration support

    • Access URLs Tenants can access the API Cloud API Gateway instance (both the UI and runtime invocation) only using the URL provided by IBM. This implies the following restrictions for the tenant:
      • Ports section is not available since they cannot be manipulated.
      • Load Balancer URLs section is not available since they cannot be manipulated.
        
        

  • Cache configuration support is not available.

  • Licensing support is not available

  • Clustering configuration support is not available.

  • Messaging is not available.

  • Web services is not available.

  • Master password management is not supported.

  • Application logs section that contains configuring aggregation of logs is not supported.

  • Destinations
    The following destinations have restrictions in API Cloud API Gateway instance:

    • Audit Log, Database, Digital Event Services (DES) and third party SNMP server are not available since they are relevant only for on premise cases.
    • Developer Portal settings are auto populated and disabled when Developer Portal is provisioned as part of the API Cloud.
    • For an Email destination, only templates can be configured since API Gateway Cloud instance has a predefined email server that cannot be changed.
      
      

  • Settings

    • Outbound Proxy section is not available under General configuration as it is relevant only for an on premise deployment.
    • Kibana port cannot be updated as it is predefined and SAML SSO section is not available under the system settings section.
      
      

  • Few Extended settings are not available.

  • System Information in the About page is not included.

• The Send Digital Events notification setting under Quota management is not available.

• Analytics support

  • Runtime event data cannot be archived or restored in API Cloud API Gateway instance.
  • Cache statistics is not available.
  • Application logs are not available.
    
    

• Custom Import - JMS settings and JNDI settings is not available as they are not applicable for Cloud.

• Connectivity

  • Service development is not possible in API Gateway cloud, that is, Designer cannot be connected in API Cloud API Gateway instance.
  • Integration Server console cannot be accessed. This means that all the configurations including logging is not available
  • Reverse Invoke from an on premise instance is not supported.
  • Paired gateway setup is not supported in a cloud instance. Advanced Edition is the default hosted solution.
    
    

• Payload - The maximum payload size limit for API Gateway calls is 30MB by default for paid tenants and 20MB for free forever tenants.

• Searching payload content - You must define custom fields for transactional events to search request and response payloads. Searching payload content without custom fields is not supported.