File Events
Solace Micro-Integration for File Events provides integration of file-based data with Solace Event Brokers.
The micro-integration event enables files by turning file data into event messages either for ingestion into a Solace broker, or from a broker to a file. This means files can participate in message-based application patterns.
This 2-way integration is configured via “workflows” in your micro-integration instance. A workflow is a source-to-processing-to-target data pipeline configured within the micro-integration runtime. Each workflow (you can have up to 20 defined per Micro-Integration runtime instance), defines a source (e.g. a file on an SFTP server), any header processing necessary for the target, and a target destination (e.g. a Solace topic). When active, events will stream across these Workflows.
For file to file transfers, check out our File-to-File Micro-Integration.
For integrating with files directly from Solace Cloud, take a look at our dedicated Micro-Integration for SFTP.
For a self-service governance management console, see our File Mesh Manager solution.
Features & Use Cases
The Micro-Integration is available as:
- A runnable package based on a Java JAR file including a start script
- A container image suitable for running in a container runtime such as Docker or Podman
The PubSub+ Micro-Integration for Files is a “self-contained Micro-Integration” from Solace. All self-contained Micro-Integrations share a common architecture and provide a number of enterprise services to the Micro-Integrations such as:
- A local management server accessible over HTTP(s) and JMX exposing endpoints for:
- Health check
- Metrics monitoring
- Log file access
- Workflow adminstration (start & stop workflows)
- A common set of configuration options for:
- logging – log levels, log file size, archive and rollover rules, appenders to export to other log services
- security setup for management endpoints – authentication and authorization to the endpoints, TLS for HTTPS endpoints
- Various runtime deployment options:
- Standalone
- Active_Standby – for redundancy (you can have more than 1 standby instance)
- Active_Active – for horizontal scaling (where the source of data will support multiple active consumers such as a non-exclusive queue in PubSub+)