Content relevant to the customer can only be created by drawing on all data sources available to the company. That's why the Series M/ interface strategy is based on comprehensive connection to existing systems. The goal is
The technical connections are made using the Service Oriented Architecture principle, or SOA. This ensures a clear divide between business logic, data storage, and document creation while maintaining company flexibility. It works like Velcro: two elements meet and match up exactly at the defined interface, creating a reliable connection, but can be separated again at any time as required.
The interfaces required for further optimization and output processes are called together with M/OMS. Here we are dealing with interfaces for document creation using M/TEXT.
External applications open M/TEXT using the Java API and webservice interfaces, for example, in order to provide templates and documents with data. Data transfer preferably takes place using XML data streams.
At the same time, M/TEXT is able to open external resources during document creation, for example in order to call up any extra data required.