Modern enterprise systems demand fast, reliable communication across multiple channels such as email, SMS, and FTP. Yet many IBM i environments remain isolated - requiring external middleware or separate servers to handle communications, introducing latency and operational overhead. The Communication feature within the Sitemule Platform solves this by embedding multi‑channel communication services natively on IBM i. This ensures messages, files, and alerts flow through the same trusted environment as your business logic - enhancing performance, reliability, and system responsiveness.

Architecture and Core Design Principles

Architecture: The Communication subsystem lives inside the Sitemule Platform runtime on IBM i, executing as ILE service programs or native jobs. It incorporates email (SMTP/POP/IMAP), SMS interfaces via SMPP or gateway APIs, and FTP/FTPS servers directly on the IBM i TCP/IP stack. By hosting all communication‑engines within the same OS and runtime context as ERP logic, the feature avoids cross‑tier hops and external dependencies.

Design Rationale: The rationale emphasizes “single‑platform execution” to preserve performance and governance. Rather than exporting spool files to separate mail servers or staging files on external FTP hosts, the system keeps everything internal - maintaining transactional integrity, security context, and audit trails. This mirrors modern IBM i design patterns that favour native integration and minimal middleware.

Data Flow: A business event triggers a message (for example: an invoice generation in RPG). The Platform runtime immediately routes this into the communication service, which formats the payload as an email or SMS, optionally attaches files, and dispatches it. The service then logs the message event in Db2 for i, updates job statuses, and if configured, triggers follow‑up FTP transfers. The flow is end‑to‑end inside IBM i - no external routers, separate mail farms, or detached file servers.

Integration within Sitemule Platform

Within the Sitemule Platform ecosystem, the Communication feature is a shared service layer used by modules like Workspace, Hub, and Assist. When the Hub module exchanges data with external partners, the communication layer issues FTP‑based file shipments or SMS alerts directly from IBM i. When Assist detects an anomaly, the monitoring service triggers an email and SMS via the same runtime. These modules rely on the common runtime core, meaning the communication engine reuses session, security, and logging contexts rather than deploying standalone components. This shared architecture delivers consistent performance and simplifies operational governance.

Technical Benefits and Performance

Performance: Because all communications execute within IBM i itself, the latencies associated with external mail relays or FTP servers are eliminated. Internally dispatching email or SMS jobs reduces round‑trip delays and keeps workloads within the TCP/IP stack of IBM i.

Maintainability: With pre‑built integration into the Platform console, administrators configure email templates, SMS gateways, or FTP endpoints without deploying separate mail servers or custom scripts. Updates are managed via the Platform interface and versioned alongside other modules.

Scalability: The service supports high volumes of outbound messages, large batch FTP transfers, and simultaneous channel operations. By leveraging IBM i job pools and built‑in spool management, the system scales alongside your core ERP environment rather than requiring separate infrastructure.

Security: Running inside IBM i means communications inherit the native authority, journaling, and object‑level controls of the system. Whether an email carries a spool file or an SMS transmits an alert, the message generation remains subject to the same audit and permission framework as your business logic.

Compatibility and Interoperability

The Communication feature integrates seamlessly with IBM i assets such as Db2 for i, ILE RPG programs, and CL jobs. For example, an RPG routine can call a service program within the Platform that sends a notification. The system supports JSON payloads over REST, enabling external systems to trigger messages via HTTP. It also supports FTP and secure FTPS protocols, allowing files to be exchanged between IBM i and Windows or Unix partners. Output formats such as PDF, TIFF, CSV - generated by ERP logic - can be attached directly to outgoing emails without external conversion tools. This interoperability ensures both legacy and modern endpoints are fully supported.

Use Case

Problem: A manufacturing company running an IBM i ERP must notify customers and partners whenever a production batch completes. They previously relied on manual ticketing and external mail servers, causing delays and errors.

Implementation: The company deploys the Communication feature of Sitemule Platform. Upon batch completion, an RPG program triggers a service call which dispatches emails with PDF reports, sends SMS alerts to mobile contacts, and uploads feed files via FTP to partner systems - all executed natively on IBM i.

Result: Message dispatch times dropped from minutes to seconds, manual processes were eliminated, and error rates in partner synchronization fell by 90%. All communications remained within the IBM i environment, preserving control and reducing external operational overhead.

Related Features

The Communication service complements the Native IBM i Integration feature by ensuring that message dispatch and file exchange also occur on IBM i, not in separate middleware. It also aligns with Monitoring & Alerting, as those alerts may trigger or be delivered through the communication engine.

By embedding high‑performance communication channels - email, SMS, FTP - directly into IBM i, the Sitemule Platform enables real‑time data exchange and operational responsiveness without external dependencies. This reduces latency, simplifies infrastructure, and maintains full system control.
See the business value of this feature.