Available modules by product

Different DataPower® products have different add-on modules.

Module management differs on DataPower Gateway for Developers and when the platform is docker.

You cannot activate modules on DataPower Gateway for Developers.
When the platform is docker, you cannot re-enable a feature unless you activate the appropriate module again. For more information, see Managing add-on features for a DataPower Docker image.

The following table lists whether a package is available from IBM® Passport Advantage® to activate the features in a module. If the table states that modules are activated, you might need to disable them to match the business goals in development, test, and production environments. These tools are available from IBM Fix Central.

Table 1. Available modules for DataPower products
Module	DataPower Gateway appliance	DataPower Gateway production edition	DataPower Gateway nonproduction edition	DataPower Gateway developers edition	DataPower Gateway for Developers ¹
Application Optimization Module	Yes	Yes	Activated	Activated	Activated
B2B Module ²	Yes	Yes	Activated	Activated	Activated
Integration Module ²	Yes	Yes	Activated	Activated	Activated
Tenant Module	Yes	No	No	No	No
TIBCO EMS Module ³	Yes	Yes	Yes	No	No
Transformation Extender Module	Yes	Yes	Yes	No	No

¹

DataPower Gateway for Developers is a no-cost product without IBM Support and does not support module management. You can obtain IBM Support in one of the following ways.

Purchase the conversion tool from IBM Passport Advantage.
Purchase a supported edition from IBM Passport Advantage.

²

The module contains the Extended Oracle support for the Database Connectivity (DCO-Oracle) feature that you can manage separately from the Database Connectivity (DCO) feature.

³

The module is not available for the X4 (5207) appliance.

Application Optimization Module

The Application Optimization Module contains the Application Optimization (AppOpt) feature that provides dynamic load distribution to manage front and back workloads in a balanced manner.

The key benefits are as follows.

Self-balanced standby to distribute incoming requests to multiple DataPower products without an external load balancer. This distribution paradigm improves performance and availability and includes full failover.
Intelligent load distribution to optimize request routing to application servers. Requests are routed to servers to optimize usage and response time.
Integrate with z/OS® Sysplex Distributor. The Sysplex Distributor Target Control Service establishes control connections with the z/OS Sysplex Distributor that allow the z/OS Sysplex Distributor to balance workload across multiple DataPower products. When the platform is docker or linux, integration with z/OS Sysplex Distributor is not available. Use of the Sysplex Distributor Target Control Service is deprecated.

The controls to self-balance incoming requests are part of the configuration of standby control for network interfaces. In self-balancing mode, two or more DataPower products distribute load among themselves. The active member manages all TCP connections to virtual IP addresses. When a client initiates a new TCP connection, the active member selects a member, possibly itself, to act as the connection endpoint. The active member tracks member capabilities to distribute traffic. The selected member completes the establishment of the connection. The active member forwards all segments of the TCP connection to the member that is acting as the connection endpoint.

Intelligent server load distribution covers various configurations and integrations.

Intelligent load distribution uses a load balancer group and enhances server load distribution by dynamically adapting the workload across application servers based on server-feedback. Intelligent load distribution uses metadata about membership, weight of members, and session affinity. Integration requires that the application or file server produces an XML representation of the server topology.
Session affinity for a load balancer group overrides the distribution algorithm to provide continuity between an application server and a client within a session. With session affinity, all client requests that are in a session are forwarded to a specific application server. For some applications to work correctly, the application requires session affinity between the client and the application server. Session affinity enhances application performance by using in-memory caching, not a database. Session affinity uses cookies to track session information that can maintain login credentials.
The weighted least connection algorithm in a load balancer group imposes a weight infrastructure to least connections for application servers.
On Demand Router (ODR) that routes and distributes traffic to WebSphere® Application Server Network Deployment clusters. ODR supports advanced routing features that include application awareness, dynamic server weight changes, high availability, application edition routing, and maintenance mode routing.

For more information about the functions that are provided with the Application Optimization Module, see the following topics.

B2B Module

The B2B Module adds the following support.

The B2B gateway that exchanges messages between B2B trading partners.
B2B transaction processing with AS1, AS2, AS3, ebXML, POP, and SMTP protocols.
B2B protocol policy enforcement, access control, message filtering, and data security.
EDI, XML, and binary payload routing.
Profile management of trading partners and full features interface for B2B configuration and transaction viewing.
Any-to-any processing. Binary processing support is available with the Binary processing (DataGlue) feature, which does not include support for the binary processing of Transformation Extender maps. The binary processing support of Transformation Extender maps requires the Transformation Extender Module.
Database connectivity with support for complex Oracle data types and extended Oracle support. You separately manage the Extended Oracle support for the Database Connectivity (DCO-Oracle) feature from the Database Connectivity (DCO) feature. When the platform is docker, the Database Connectivity feature and the Extended Oracle support for the Database Connectivity feature are never available. In other words, you can manage connections to any SQL data source except IMS, but you can never have support for complex Oracle data types or extended Oracle support.

If you add the B2B Module and you did not initially configure the RAID volume for B2B storage, you must reinitialize the RAID to have two partitions.

Note: For DataPower Gateway for Docker, support is for only standard Docker, not through container-orchestration systems such as Kubernetes (k8s) for the following reasons.

B2B requires RAID for message persistence.
B2B high availability (HA) is a two-system active-passive configuration that depends on RAID.
B2B HA is always active-passive and is incompatible with a container-orchestration system. If implemented with a container-orchestration system, the resultant confutation is an incompatible active-active configuration.

Integration Module

The Integration Module adds the following support.

Any-to-any processing. Binary processing support is available with the Binary processing (DataGlue) feature, which does not include support for the binary processing of Transformation Extender maps. The binary processing support of Transformation Extender maps requires the Transformation Extender Module.
Database connectivity with support for complex Oracle data types and extended Oracle support. You separately manage the Extended Oracle support for the Database Connectivity (DCO-Oracle) feature from the Database Connectivity (DCO) feature. When the platform is docker, the Database Connectivity feature and the Extended Oracle support for the Database Connectivity feature are never available. In other words, you can manage connections to any SQL data source except IMS, but you can never have support for complex Oracle data types or extended Oracle support.
IMS integration with the IMS feature.

Tenant Module

The Tenant Module supports the creation of two tenants and the installation of their initial firmware image. Tenants provide runtime-isolation and upgrade flexibility among API Connect and traditional DataPower workloads without business disruption. Because tenants use a different firmware image, you must download tenant-specific firmware images from IBM Fix Central to manage the firmware version on tenants.

For more information about tenants, see Tenants.

TIBCO EMS Module

The TIBCO EMS Module contains the TIBCO EMS feature and enables the DataPower product to send messages to and receive messages from TIBCO Enterprise Management Service servers.

Transformation Extender Module

The Transformation Extender Module contains the IBM Transformation Extender feature and enables the DataPower product to process binary messages for maps that you created with IBM Sterling® Transformation Extender Design Studio.

Important: To process binary messages, you also require the binary processing support that is available with the Binary processing (DataGlue) feature that is available in either the B2B Module or the Integration Module. Therefore, you cannot purchase and use the Transformation Extender Module without purchasing either the B2B Module or the Integration Module.