The integration engine
Runs the flows: receives, transforms, routes and delivers the messages.
VOGO eBS Integrator
Enterprise Service Bus Integrator — the layer through which applications exchange data without being linked directly to each other: it receives the message, transforms it, sends it where it belongs and checks that it arrived.
Installed at the organisation. A new link between two systems is built once, in the integrator, not in each application.
Every data exchange becomes an integration flow: where the message comes from, what shape it has, how it is transformed and where it goes. The registry, the archive, accounting, human resources and the portal are no longer linked directly to each other.
The integrator speaks each system’s protocols — REST, SOAP, files on SFTP, message queues, databases — and converts between them, including the old government services that require SOAP or signed files.
A message that does not arrive is not lost: it is retried automatically, by rules, and one that cannot be delivered goes to a review queue or opens a ticket. The console shows the state of the flows and connectors at every moment.
Connect. Transform. Deliver. Follow up.
Each data exchange described once: the source, the transformation, the destination and the delivery rules.
REST, SOAP, SFTP and files, JMS, Kafka, databases through JDBC, e-mail and the common systems.
JSON, XML, CSV and custom formats, with field mapping and validation of each message.
The message reaches the right destination by type, value or business rule.
Daily synchronisations, file transfers and periodic reporting, by calendar.
Automatic retry on failure, a queue for undelivered messages and error handling per flow.
Data exchange with government services and other institutions, without code in the applications.
The state of each flow and connector, messages, errors and durations, in the VOGO console.
Platform events — document registered, new request, payment — start the flows, without repeated polling.
A message that cannot be delivered opens a ticket in VOGO eBS Service Desk, with the flow and the error.
APIs built in the integrator are published and secured through VOGO eBS API Gateway.
Connector passwords and keys are kept in the VOGO vault, not in the flow configuration.
Support, updates and training are provided by VOGO, as the product’s manufacturer.
Runs the flows: receives, transforms, routes and delivers the messages.
The links with external systems, on each one’s protocol.
Scheduled flows: synchronisations, file transfers and reporting.
Undelivered messages, retried automatically or sent for review.
Flows, connectors and errors, in a Romanian-language web console.
The product uses as mature open-source libraries: WSO2 Micro Integrator.
It is the VOGO system integration product: the links between the organisation’s applications, government services and partners go through a single layer, which transforms, routes, delivers and follows every message.
The integrator connects systems to each other and transforms the data between them. API Gateway publishes the APIs to consumers and controls who calls them. Together: the integrator builds the service, the gateway exposes it.
Yes. VOGO eBS Integrator is an integrated product, developed, licensed and supported by VOGO, with VOGO modules, console and support. The product uses as mature open-source libraries: WSO2 Micro Integrator.
On premise, in the organisation’s infrastructure, on virtual machines or in containers. The exchanged data never leaves it.
Request a demo on your organisation’s integrations.
Note: The services are provided in line with the European DNSH principle – “Do No Significant Harm”, in accordance with Article 17 of Regulation (EU) 2020/852 on the establishment of a framework to facilitate sustainable investment and with the European Commission’s technical guidance on the application of the DNSH principle, C/2023/111.