Usually the data for creating customer-relevant content is not centrally available, but is distributed across numerous data sources within the company (CRM, product databases, process control, input management, etc.). In order to generate high-quality customer communication, it is crucial to draw on all data sources available in the company. For this reason, the interface strategy of Series M/ aims to integrate the system seamlessly into the IT landscape in order to be able to communicate with all relevant surrounding systems.
Therefore, the technical connection is aligned with the standard of the service-oriented architectures SOA. This means: clear separation of business logic, data storage and document creation. In this way the products of the M/ series can be made available as company-wide available services. Entrepreneurial independence and flexibility are maintained. Just like a carabiner, two separate elements are connected at the defined interface with pinpoint accuracy and reliability - and can be easily released again if required.
Below are some important interfaces in the context of document creation with M/TEXT TONIC.
Java API and web services. External applications such as business applications call M/TEXT to initiate document processes, provide templates and documents with data, etc.
Java Authentication and Authorization Service (JAAS) as a special Java interface for connecting Single Sign-On systems
M/TEXT interface for calling external resources, for example to obtain additional data at runtime (online and batch)