IBM Support

Deprecated and removed features in IBM DataPower Gateway products

Question & Answer


Question

What features are deprecated or removed in 10.6 and earlier IBM® DataPower firmware? This document lists the features that are deprecated and removed in 10.6 and earlier of DataPower firmware. Features that are deprecated or removed in one release continue to be deprecated or removed in the current and later releases. Alternatives are provided, when available.

Cause

Due to evolving technology, the DataPower firmware is updated, which can change the required configuration of objects.

Answer


If a feature is listed as deprecated, IBM reserves the right to remove this capability in a later product release. A feature is generally not removed after announcement of deprecation until at least two major releases or one full year, whichever time period is longer. IBM reserves the right to remove a feature immediately when warranted. Migrate your existing configuration to use the alternative.



10.6 deprecated and removed features

No features are deprecated or removed in 10.6.0.


10.5 deprecated and removed features


10.5 deprecated features

Feature Alternative Additional information
10.5.1: Objects that integrate with IBM MQ servers that are not running version 9 or later. Use objects that integrate with IBM MQ servers that are running version 9 or later.
10.5.1: Conformance validator utility None
10.5.0.6 (10.5.1): WebGUI Use the new UI
10.5.0.6 (10.5.1): API probe settings. Use probe settings. API probe settings and the new probe settings share the same configuration.
10.5.0.6 (10.5.1): API probe property in gateway-peering manager. Use probe settings.
10.5.0.3: The following gateway-peering properties.
  • Primary count
  • Peers in a peer group
  • Nodes in a cluster
  • Auto-manage nodes
  • TLS among peers or nodes
  • Identification and validation credentials
Where applicable, the property is moved to the gateway-peering group.
10.5.0.3: Send a test message tool Use a third-party application like Postman.

10.5 removed features

Feature Alternative Deprecated since version
10.5.4: WebGUI Use the new UI 10.5.0.6 (10.5.1)
10.5.0.13 (10.6.0.1): SQL data source Connection password property. Migrate to the Connection password alias. property. 7.2
10.5.0.13 (10.6.0.1): SQL data source password command. Migrate to the password-alias command. 7.2
10.5.0.0: The b2bp-archive-purge-now command. The purge-b2bp-all and purge-b2bp-gateway commands. 10.5
10.5.0.0: The Archive-purge transactions action. Purge B2B Transaction Data action. 10.5
10.5.0.0: Microsoft Internet Explorer to access the DataPower GUI. Another supported browser. 10.5
10.5.0.0: Restrict a privileged user to specific domains. None. 10.5

10.0 deprecated and removed features


10.0 deprecated features

Feature Alternative Additional information
10.0.4: Rate limit API action Add a rate limit assembly action where rate limits use the limits defined in the API plan.
10.0.4: Extension Functions in XML manager None
10.0.2: Allow WebSocket upgrade in invoke assembly action Add a WebSocket upgrade assembly action to the assembly.
10.0.1.1: Restrict to HTTP/1.0 in invoke assembly action Use the HTTP version to server property to set the protocol version. When set to HTTP/2, whether to require HTTP/2.
10.0.1.1: Restrict to HTTP/1.0 Policy in User Agent HTTP version policy
10.0.0.0: Suppress identical events for a defined duration in a log target. None
10.0.0.0: Secure Gateway Client None
10.0.0.0: Cloud Gateway Service None
10.0.0.0: Cloud Connector Service None

10.0 removed features

Feature Alternative Deprecated since version
10.0.4: Extension Functions in XML manager None 10.0.4
10.0.0.0: Debian firmware images for DataPower for Linux. None 10.0.0.0

2018.4 and earlier deprecated features

Feature Alternative Additional information
2018.4.1.4: The compatibility mode property for the API Connect Gateway Service. Migrate your API Connect integration to use the API Gateway service instead of the Multi-Protocol Gateway service. For more information, see the API Porting Notes wiki. When the compatibility mode is set to V5, the DataPower service used is the Multi-Protocol Gateway. When not set to V5, the DataPower service used is the API Gateway.
2018.4.1.1: Key and certificate aliases for a gateway-peering instance. Edit the configuration for each gateway-peering instance to assign identification credentials that reference the required key and certificate aliases.
7.5: The smtp protocol identifier to connect to remote SMTP servers. Use the dpsmtp or dpsmtps protocol identifier.
7.2: SSL Proxy Profile and Crypto Profile Use SSL Client Profile, SSL Server Profile, and SSL SNI Server Profile For more information, see Migration from SSL Proxy Profile.
7.2: Password Password Alias For more information, see Migration from passwords to password aliases.
7.2: Load balancer groups LDAP and IMS Connect health checks Load balancer group TCP health check The TCP health check has all of the same capabilities of the LDAP and IMS Connect health checks.

[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"ARM Category":[{"code":"a8m50000000L0rqAAC","label":"DataPower"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
28 August 2024

UID

swg21634531