Get advice

Integration with 1C systems
through the exchange microservice

Connect 1C to the data bus faster and easier through a ready-made exchange microservice. It uses OData, so it is compatible with any 1C configuration. It does not require improvements on the part of the service and does not download 1C even with a large amount of data transferred.

Discuss the task

You'll also get

Comparison table
types of integrations

We are launching integrations for business

Retail

Production

Construction

Fintech

logistic

Medicine

Pharmaceutical industry

Many others

Advantages of connecting 1C to ESB through the exchange microservice

Easy to connect. The microservice consists of separate ETL connectors for 1C. To connect, just specify in the configuration settings which objects to send to or receive from the 1C system. It does not require improvements from 1C.

Without the risk of a vendor lock. The risk of a vendor lock is excluded, because the microservice is based on popular Opensource tools (MuleSoft, WSO2, Talend, etc.).

1C integration with any services. You can set up an exchange between two 1C's. ESB also allows you to connect services from any vendor to exchange with 1C.

Suitable for cloud 1C. Easily connect even 1C cloud solutions to the exchange via the service's API.

Compatible with all configurations. The exchange microservice uses the standard OData exchange mechanism.

Does not load 1C. Microexchange service Does not load 1C even with a large amount of data exchanged.

Any data transformation logic for 1C is available with ESB integrations

Data transfer
with the “link” type

To transfer an object with the “link” type, you need to make sure that all directories are created in the consumer system. Otherwise, the object will be created broken or the stream will give an error. 

Our connectors check whether the system contract is being fulfilled (completeness, correctness).  Only when all conditions are met will the message be sent to the consumer

Assembling the object
from several tables

Object information can be stored  from several sources. You need to request information on each source and combine it for submission. 

Our solution allows aggregating object data. For example, collect “orders” and “payments” separately (from different sources) and transfer them as “orders with payments”.

Delete a record
from the tabular part of the object

Such a record is not registered for the 1C exchange. The receiver system must know this feature of 1C and calculate changes on its own.

Our connectors can check deletion from the table. If the deletion took place, they are marked in the vault. Consumers don't have to do calculations.

A snapshot of current prices

1C does not provide a snapshot of current prices. The consumer must determine for himself which price from the entire register (past, present, future) is relevant.

Using storage, we calculate current prices so that any consumer system can pick them up without unnecessary logic.

Eliminate data loss when exchanging between systems

Проблема
При обмене “точка-точка” в момент отказа одной из систем данные могут теряться: одна система считает сообщение переданным, когда вторая его не получила.

The problem

When exchanging point-to-point when one of the systems fails data may be lost: one system considers a message to have been transmitted when the other has not received it.

Решение
Мы настраиваем интеграции так, что при обрыве связи сообщение считается необработанным и будет передано в следующем проходе.

Solution

We set up integrations so that when communication is broken the message is considered unprocessed and will be handed over in the next aisle.

Change some IT systems without changing others

Проблема
При старом подходе источник отдает данные, как есть. Потребитель должен преобразовать их под свой формат. При такой схеме любое изменение в источнике повлечет каскад изменений всех связанных потоков данных.

The problem

With the old approach, the source gives the data as it is. The consumer must convert them to their own format. Under this scheme, any change in the source will entail a cascade of changes in all related data streams.

Решение
Изменение ERP или любой другой системы не вызовет доработок всех связанных систем.  Если система изменится, это затронет только коннекторы “источник-хранилище”. Для всех потребителей все останется без изменения.

Solution

A change in ERP or any other system will not cause improvements to all related systems.  If the system changes, it's will only affect source-storage connectors. For all consumers, everything will remain the same.

Reduce the load on systems without improvements and increasing resources

Проблема
Одни и те же данные нужны разным системам. Потребители дублируют запросы в систему-источник, что увеличивает нагрузку. Если в компании есть одна система для хранения основных данных, она будет получать огромное число запросов. Часто это старая монолитная система, которую в будущем бизнес хочет заменить.

The problem

Different systems need the same data. Consumers duplicate requests to the source system, which increases the load. If The company has one system for storing basic data; it will receive a huge number of requests. This is often an old monolithic system that businesses want to replace in the future.

Решение
Потребители обращаются в хранилище. Нагрузка на основной источник снижается без доработок самой системы и увеличения ресурсов. Когда придет время заменить старую систему на несколько новых сервисов, нужно будет изменить потоки “источник-хранилище”. Изменения не затронут множества потребителей.

Solution

Consumers go to the vault. The load on the main source is reduced without improving the system itself and increasing resources. When it comes time to replace the old system with several new services, you'll need to change the source-storage streams. Many consumers will not be affected by the changes.

Eliminate data loss during exchange

Change some IT systems without changing others

Reduce the load  on systems

Discuss the task

Get a free consultation with an expert

Submit a request

We will define the boundaries of the problem that causes losses to businesses

We will develop possible solutions and tools for their implementation

We will define the implementation plan and the next steps

You can implement this solution with us, another integrator or your team

Our approach
and benefits

Risk Free. If you are unhappy with the result, you don't have to pay for the work. We specify this clause in the contract.

Alienation. We don't hold customers hostage. All our solutions are easy to share with your team or another contractor.

Efficient IT. For us, IT is effective when it brings results for business and ensures a high rate of change.

Expertise. 400+ successfully launched integrations on various tools (Kafka, MuleSoft, WSO2, etc.).

Control. Each integration we have launched is under the control of the monitoring system.

They trust us

Any data transformation logic for 1C is available with ESB integrations

Data transferwith the “link” type

Assembling the objectfrom several tables

Delete a recordfrom the tabular part of the object

A snapshot of current prices

Eliminate data loss when exchanging between systems

The problem

Solution

Change some IT systems without changing others

The problem

Solution

Reduce the load on systems without improvements and increasing resources

The problem

Solution

Get a free consultation with an expert

They trust us

KT.Team Maxxium

KT.Team La Nature

KT.Team St Gobain

KT.Team Твое

KT.Team SQ 2

KT.Team SQ 1

KT.Team Norgau

KT.Team Музторг

Рабочая тетрадь Саблуков

Рабочая тетрадь Серветников

KT.Team Brandly

KT.Team Трансатлантик

KT.Team FML

Рабочая тетрадь Шилов

We have implemented a scalable service bus for ATIMO

We provided Polaris with the ability to easily bring new products to marketplaces

We have developed a targeted system integration scheme. We implemented ESB technology and launched 48 streams

Integration of Talend ESB into the IT infrastructure of a logistics company

We redesigned the IT architecture and drew up a roadmap for its transformation

We helped to reduce the load and scale system throughput

Work with product data has been automated for the Fix Price network

Get a comparison table of integration types

Typical work scheme

1. Designing a low coupled architecture

The transition plan, taking into account business features

2. Migrating the streams that are most relevant to you

Solving 80% of data exchange problems between systems

3. Migrating the rest of the streams to fill the data warehouse

A single mechanism for exchanging the entire enterprise and the completeness of data for analytics

Business solutions based on Data Warehouse data

Cases

Integration of the IT infrastructure of an e-commerce project with marketplaces using the WSO2 ESB service bus

Integration of Talend ESB into the IT infrastructure of a logistics company

Implementation of the Talend ESB service bus into the project's IT architecture

Let's discuss your project

Data transfer
with the “link” type

Assembling the object
from several tables

Delete a record
from the tabular part of the object

Eliminate data loss when exchanging between systems

The transition plan, taking into account
business features