Real Time Component

Web Service component

Designing synchronous and real-time data exchanges


The Web Service component of Stambia is the best way to simplify the management of web services in data integration projects, providing a high level of productivity and performance with an amazing simplicity.

With the same agility as the other Stambia components, the web service component is directly usable and offers a high level of productivity due to the model driven approach of Stambia and the use of native standards for any type of web services (SOAP, REST, XML or JSON formats).

With its approach based on preconfigured models (templates), this component can be adapted to the needs of each client and thus bring the best solution to any project.


Native reverse engineering

Stambia allows to reverse or describe any type of web service based on a WSDL or WADL format, or using associations with existing technologies such as XML or JSON.

The resulting metadata will include the entire description of the web service (Ports, operations, input/output description, exceptions…).

The principle of Stambia is to allow recovery of all native metadata to simplify the standard exploitation of each technology.


Invocation of existing web services

The mappings can use web services to gather information from the web or from internal third party applications. The Stambia approach of the mappings will simplify the way to use web services. The user can focus on the business rules and forget the technical complexity of the service. A simple Drag & Drop to instantiate the use of the web service will be enough.


Publication of Web Services

The Stambia Web Service Connector allows you to publish Web services graphically, with no line of code.

The Stambia Processes can be published as web services with a simple click.

Web Services are published in the SOAP or REST standard and may contain complex inputs or outputs.

These inputs / outputs are defined by a simple drag & drop into the process which is being published.

The web services published by Stambia are WSI-Compliant.


Use cases

This component can be used to expose (publish) Information System data (master data, Business Intelligence data, etc.) for internal or external applications requiring synchronous or real-time exchanges, and also in order to be called by common schedulers.

  • Publishing information for a partner, supplier or customer may be done in a few minutes without the need to write code or complex programs.
  • Collecting data from cloud applications becomes simple and performant.
  • Designing new e-commerce solutions is now easy.


Change Data Capture

Follow the evolution of your data


The Change Data Capture component simplifies the management of change detections in databases. Change detection is essential for certain data integration projects, providing performance gains and improved flow of information exchange.

With the same agility as the other Stambia components, the Change Data Capture component is directly usable and offers a high level of productivity due to the model driven approach of Stambia and the use of native "transactional or redo log" files of databases or the use of simple triggers.

The approach through Stambia templates (models of processes) offers a high level of flexibility, and allows to answer any specific project needs.



Types of captures


When provided by database vendors, Stambia uses the standard API functions to read data from the transactional or redo log files. This is the case for technologies such as Oracle, Microsoft SQL Server or Postgre SQL

In other cases Stambia uses triggers to detect changes in source tables.

The changes can automatically be written into a staging area in order to be read by the mappings or the replication templates.

Starting the CDC

Starting the capture doesn’t require code or complex parameters. The user can start it by selecting the tables to capture and instanciating the appropriate CDC template, depending on the underlying technology.


Using CDC in mappings

Mappings can directly use the captured data by simply choosing the « use CDC » option of the source table. In that case, instead of using the source, the mapping will switch to the CDC table automatically prepared by the capture process.


Using the replication template

The replication component of Stambia allows to quickly replicate the captured data towards a third party database.

This can be done with simple parameters and with no complex designs.

The Stambia universal mappings can also be used to complete and adapt the replication process in case there is a need to implement business specificities.

This component is optimized for each source and target database, even in case of heterogenous databases. This brings the best level of performance.


Subscribers functionality

Furthermore, the Change Data Capture templates can manage multiple subscribers. This is particularly useful when an organization needs to use modifications in a source for multiple targets. For example, a modification in the CRM application can be sent to the datawarehousing database, and at the same time into an ERP or specific application.

Events detection

Make your Information System responsive and agile

To provide greater fluidity in the information system, it is important to be able to react to different events that occur within the IT infrastructure.

Stambia provides all the components necessary to establish exchanges based on change detection.


Stambia provides many event detection objects such as :

  • File detection
  • FTP file detection
  • Email detection
  • New data in a table
  • New data in a JMW queue/topic
  • Specific scripts