Web Transaction Framework
A lightweight IBM i (AS/400), iSeries component that simplifies outbound API calls via major integration platforms such as MuleSoft or Confluent.
Automatically manage low level communications with no API or Data Queue Development required on IBM i
Offload API heavy lifting to your Integration platform
The Web Transaction Framework (webTF) is an add-on component that can optionally be used with the infoConnect for implementing outbound IBM i -> MuleSoft -> external integration use cases. The component is included free of charge with a subscription purchase and is available for trial with any Infoview IBM i integration product.
Some of the use cases where webTF could be a good fit:
- Requesting shipping quotas and delivery dates
- Running real time credit applications
- Checking if a customer is already in an existing customer data platform
External messaging to the desired integration platform
Web Transactional Framework Mechanics
All interactions with the external APIs are offloaded from the IBM i (AS/400) to MuleSoft, Confluent, or other similar integration platforms. The webTF communicates with these integration platforms via a pair of data queues (request and response) and places new transactions/messages into request DQ then waits for the response DQ with the same transaction ID. Only the integration between IBM i and desired middleware platform needs to be configured to create and process the transaction via data queues.
webTF: IBM i Web Transaction Framework for Outbound API Communication and External Messaging
Offload All Outbound API Complexity From IBM i to Your Integration Platform Automatically
webTF handles the low-level communications required for IBM i programs to initiate outbound calls to external REST APIs and messaging platforms, without any API or data queue development on the IBM i side. It works by placing outbound transactions into a request data queue and listening on a matching response data queue using the same transaction ID. MuleSoft, Confluent, Kafka, and similar platforms handle the actual API interaction, keeping the IBM i entirely free of web services complexity. Configuration, transaction tracking, exception logging, and Splunk or Elastic stack integration are all managed through the product UI.
Real-World IBM i Outbound API Scenarios
webTF is the right fit when IBM i business logic needs to call an external service in real time during a transaction, and the IBM i team should not be responsible for managing that API connection directly. Common scenarios include requesting shipping quotes and delivery dates from logistics providers, running real-time credit applications against external financial platforms, and checking whether a customer already exists in a customer data platform or CRM before creating a new record. Each scenario runs through the webTF data queue mechanism with full transaction logging and exception visibility built in.
Included Free With Any infoConnect Subscription
webTF is provided at no additional cost with the purchase of any Infoview infoConnect product subscription, including infoConnect for MuleSoft, Kafka, and infoConnect Hub, and is valid for the full subscription term. It is delivered as a SAVF file, installed directly on the IBM i server, and typically deployed within hours. Reference project source code, a user manual, and demo applications are available to accelerate first use case implementation. Infoview’s professional services team is available for IBM i configuration, middleware flows, and full use case rollout.
Frequently Asked Questions
Looking to increase communication from us to you
-
What differentiates the webTF from a change data capture component?
The webTF is a free product given to customers who purchase a subscription for a connector product.
The webTF focuses on outbound messages from the IBM i to other software applications. infoCDC is an optional add-on that provides real-time codeless integration and data replication solutions.
-
Does the webTF reside directly on the IBM i?
The component is installed on the applicable IBM i server(s) and is delivered in a SAVF file featuring all required objects -
How long does it take to deploy and get the webTF up and running?
Typical implementation includes hours or days. Customers can reference our demo applications to rapidly roll out their own use cases.
Infoview Professional Services team is available to quickly implement the first few use cases both on IBM i and Mulesoft / Kafka / other integration platforms
-
What visibility is provided on transactions processed by webTF?
The following tables provide a seamless view of transactions processed
1. Transaction Types (TRNTYPES) defines transaction types
2. Transaction Header (TRNHDR) details of transaction results
3. Transaction Log (TRNLOG) log details of transactions
Product Features
Below are some examples where real time outbound API calls deliver better customer experiences or improve the process quality and operational efficiency:
- Simple extensible developer-friendly framework built with native IBM i stack
- Automatically manages low-level communications with MuleSoft or similar platforms with no API or Data Queue development required on IBM i
- Easy configuration and management of all outbound API integrations within the product UI
- Transaction tracking and exception logging details can be streamed into log aggregation, alerting, and monitoring platforms such as Splunk or Elastic stack
Subscription Models, Delivery, and Support
- Standard:During the entirety of the subscription term, support will be provided entailing product deployment, error/bug resolution, best practice advice, as well as subsequent product releases
- Priority:Expedited incident resolution, bug fixes, and small enhancements. Unused support hours can be rolled over for the following month.
- Priority 24×7: Support engineer available for incident resolution during standard business hours and on-call rotations for all nights/weekends/holidays. Unused support hours are rolled over to the following month.
- Dedicated 24×7: A dedicated support engineer is online and ready to jump in at any point in time, day or night. Time outside incident resolution can be used for any additional project work.