DIVE Platform

DIVE: Data Integration and Visibility Engine

The modern operational layer for enterprises running IBM Sterling B2B Integrator — visibility, governance, administration, and day-to-day operational control.

Overview

What DIVE is

DIVE is a self-hosted operational platform that runs alongside IBM Sterling B2B Integrator. It does not replace the execution engine and it does not sit in the data path. IBM Sterling B2B Integrator continues to receive, transform, route, and deliver files exactly as it does today. DIVE reads what those processes record, presents it in a modern interface, and gives operations teams a governed place to administer partners, flows, protocol profiles, and security assets.

The problem DIVE addresses is operational rather than functional. Mature IBM Sterling B2B Integrator environments accumulate hundreds of partner-specific business processes, mailbox structures, and routing rules. Answering a simple question — did the file arrive, and if not, where did it stop — often means console access, database queries, or a request to the one person who knows. DIVE puts that answer in a browser.

Capabilities

What the platform covers

DIVE groups the daily work of a B2B operations team into six areas.

Operational visibility

File and transfer activity searchable by producer, consumer, flow, tag, protocol, receive status, delivery status, and time window, with the outcome of every delivery attempt.

Monitoring and exceptions

Volume and health trends, delivery outcomes over a selected period, ranked failure categories with their underlying error signatures, and an exceptions queue for abnormal behaviour.

Administration

Partner records, flow definitions, protocol profiles, code lists, and notification configuration managed through a single governed interface rather than scattered console screens.

Governance

Versioned flow definitions with effective-from dates, attributable changes, and a registry that shows what is active in the environment right now.

Role-based access

Local accounts with administrator, standard user, and partner user roles, so support staff can investigate without holding full platform credentials.

Partner and flow management

Partner onboarding, routing, schedules, and protocol configuration handled as configuration against reusable patterns instead of a new business process for every partner.

How DIVE fits with IBM Sterling B2B Integrator

DIVE is deployed inside your environment, on your infrastructure. The agent component reads operational data on a schedule and streams it to the DIVE application; it is read-only and no transferred files pass through it. If DIVE is stopped, IBM Sterling B2B Integrator continues to run and you lose visibility rather than transfers.

That boundary is deliberate. Enterprises running regulated file exchange cannot accept a new component in the critical path, and DIVE is designed so adoption carries no delivery risk. IBM Sterling B2B Integrator Ecosystem Services explains the services that surround an implementation.

Protocols and components in scope

DIVE manages configuration and visibility for the transports enterprises already run on IBM Sterling B2B Integrator.

  • SFTP, FTP and FTPS partner exchange
  • AS2 messaging with signed payloads and MDN handling
  • HTTP and REST-based delivery endpoints
  • Mailbox routing and store-and-forward exchange
  • Local and network filesystem pickup and delivery
  • IBM Connect:Direct managed routing
  • AS2 and SSL certificates, PGP keys, and SSH keys as governed security assets

Inside DIVE

The running product.

Illustrative DIVE interfaces, captured in the Cognitrix demo environment. Partner names, file names and identifiers are redacted; everything else is the shipping product.

DIVE File Insights screen: search filters for time window, business context and delivery status, above a results table of file transfers
File InsightsSearch by producer, consumer, flow, tag, protocol, receive and delivery status, or time window. Select a record and replay or redeliver it.
DIVE Flows Directory listing versioned transfer flows with source partner, transfer type, route count and status
Flows DirectoryVersioned flows with source partner, push or pull, route count, status, and effective-from date.
DIVE protocol profile cards for SFTP, FTP, HTTP, AS2, Mailbox, FileSystem and Connect:Direct
Protocol profilesSFTP, FTP, HTTP, AS2, Mailbox, FileSystem and Connect:Direct configured as reusable profiles instead of per-partner BPML.
DIVE Security Asset Studio cards for AS2 certificates, SSL certificates, PGP keys and SSH keys
Security assetsAS2 and SSL certificates, PGP keys and SSH keys onboarded as governed assets with SFG-backed validation.

Request a DIVE Demo

Tell us your IBM Sterling B2B Integrator version, deployment model, and partner count, and we will focus the session on your environment.