Middleware4j: Difference between revisions
No edit summary |
Updated by push_wiki.py |
||
| Line 1: | Line 1: | ||
{{ | '''Middleware4j''' is a file-based message transformation and routing engine developed as a companion to [[Commander4j]]. It has no dependencies on Commander4j and can be used independently for any system integration requirement. | ||
Its primary purpose is to link systems that use incompatible data formats. It monitors directories for incoming files, transforms them using configurable XSLT stylesheets, and delivers the results to one or more output destinations in the required format — running continuously in the background as a service. | |||
For a full explanation of how the application works, see [[Overview_Middleware4j]]. | |||
== Getting Started == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[Overview_Middleware4j]] || What Middleware4j does and how it works | |||
|- | |||
| [[Downloads]] || Download the latest release | |||
|- | |||
| [[Installation_Middleware4j]] || How to install and deploy as a Windows service | |||
|} | |||
== User Guide == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[Maps]] || Configuring transformation pipelines (the core concept) | |||
|- | |||
| [[Connectors]] || Available input and output connector types | |||
|- | |||
| [[Middleware4j_Example_Configuration]] || Complete worked configuration example | |||
|- | |||
| [[EMAIL]] || Email connector and SMTP configuration | |||
|} | |||
== Connector Reference == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[ASCII]] || Fixed-column flat file input and output | |||
|- | |||
| [[CSV]] || Delimiter-separated file input and output | |||
|- | |||
| [[XML]] || XML document input and output with XSLT transformation | |||
|- | |||
| [[RAW]] || Copy or move files without transformation | |||
|- | |||
| [[EMAIL]] || Send files as email attachments or receive via email | |||
|- | |||
| [[SOCKET]] || Transmit data to devices over TCP/IP | |||
|- | |||
| [[PDF_PRINT]] || Automatically print PDF files to a named printer queue | |||
|} | |||
[[Category:Middleware4j]] | |||
Latest revision as of 12:17, 1 April 2026
Middleware4j is a file-based message transformation and routing engine developed as a companion to Commander4j. It has no dependencies on Commander4j and can be used independently for any system integration requirement.
Its primary purpose is to link systems that use incompatible data formats. It monitors directories for incoming files, transforms them using configurable XSLT stylesheets, and delivers the results to one or more output destinations in the required format — running continuously in the background as a service.
For a full explanation of how the application works, see Overview_Middleware4j.
Getting Started
| Overview_Middleware4j | What Middleware4j does and how it works |
| Downloads | Download the latest release |
| Installation_Middleware4j | How to install and deploy as a Windows service |
User Guide
| Maps | Configuring transformation pipelines (the core concept) |
| Connectors | Available input and output connector types |
| Middleware4j_Example_Configuration | Complete worked configuration example |
| Email connector and SMTP configuration |
Connector Reference
| ASCII | Fixed-column flat file input and output |
| CSV | Delimiter-separated file input and output |
| XML | XML document input and output with XSLT transformation |
| RAW | Copy or move files without transformation |
| Send files as email attachments or receive via email | |
| SOCKET | Transmit data to devices over TCP/IP |
| PDF_PRINT | Automatically print PDF files to a named printer queue |