Possible ways of integration with external systems

Introduction

The AMAGE system allows integration with external information systems. These IT systems can be both systems used internally by our client. Whether it is financial and accounting systems (Finance), or ERP type information management systems, but also domain solutions.

These systems can be divided into two groups, i.e. systems that receive information from the AMAGE system and systems that provide information to the AMAGE system. Through integration mechanisms, we enable communication and data exchange. This is important because due to the ongoing digitization of IT solutions in enterprises, IT systems cannot exist independently. Information exchange between individual management systems/domains is required.

The AMAGE system enables simple exchanges with the participation of the client’s employees - it is the simplest and fastest data exchange mechanism. This requires somehow generating data in one system and then transferring them via some file format (xls, csv, xml) to the AMAGE system. The solution is not very automatic, but in many cases it allows for quick data exchange.

In further steps (or when the Client’s IT departments operate effectively), enable the implementation of activities automatically. This article is only an introduction informing about possible ways of implementing integration. From the simplest technically (not necessarily organizationally) to fully automated exchanges with high possibilities of interaction between individual IT systems. Each of these solutions represents possible steps to take, but it is not the only one. The AMAGE team always tries to work out the best possible solution with the client so that the effect is visible as quickly as possible.

Possible solutions

Integration into external systems can be implemented in several ways.

  • Manual data integrations (flat cvs/txt files)

  • Flat file automation (ftp/webdav)

  • Flat file automation (email)

  • Automation of flat files (email)

  • Integration via WebServices communication (REST/SOAP)

  • Integration through communication of external data integrators

Manual data integrations

Data integration through manual user operations on two systems. Export of data in the source system in the form of an xls/csv/xml file, e.g. for one or more deliveries. In the target system, data import from the transferred data files. Potential errors signaled to the user.

Flat file automation (ftp/webdav)

Automation of manual transfer by automatically sending files when they are generated (trigger) on the source system to an external data resource in the target system (e.g. ftp server). Files sent in a fixed format (csv/xls/xml) and automatically imported by the target system. Potential errors reported in integration logs available to system administrators.

Flat file automation (email)

Automate manual transfer by scanning incoming mail/handling outgoing mail. A message generated automatically when the document is created (trigger) in the source system. Generating email messages with file attachments. Files sent in a fixed format (csv/xls/xml) and automatically imported by the target system. Potential errors reported in integration logs available to system administrators.

Automation of flat files (email)

Automation of manual transfer by integrating exchange tables on SQL RDBMS servers. A message generated automatically when the document is created (trigger) in the source system. Generating entries in exchange tables for the target system. The target system periodically scans the exchange tables and imports the data. Potential errors reported in integration logs available to system administrators.

Integration through WebServices communication

Dedicated integration interfaces such as REST/SOAP communication with definable data structures. Own communication servers. Operation of both two WebServices servers (source system + target system) and asynchronous communication, and one WebServices server (source system OR target system) and communication of one of the parties in the polling mechanism. Possibility to use additional authorization servers to conduct transactions (tokens/oauth, etc.). Possibility of using formats developed in manual data exchange or dedicated data structures as content, including the use of EDI communication standards.

Integration through communication of external data integrators/integration systems

Integration via dedicated data buses (integration bus, etc.). The use of messages specific to given solutions, e.g. SAP PI or the use of open message standards such as EDI. Implementation is always agreed between both parties.

The Howto is based on system version 1.17.0.2 (03.2022) and presents features that may not be available in your system. Ask AMAGE about making this functionality available.
Due to ongoing development of the system, some screens or configuration files may look slightly different, but will still retain the full functionality described here. This does not affect the core functionality described in this document.