The Document type Custom class allows you to directly forward your data to an Integration Unit without Mapping. Phases 2 and 3 are then deactivated. This allows you to use functionalities like input agents, responses, partner channels, and logging in the Control Center when you implement your own data processing operations.
In addition to the existing Integration Unit classes, we provide a programming interface (API) that also allows you to develop your own Integration Units in Java.
Configuration in Phase 2, which determines the format of the input data. The document type determines how the parser reads the data and transfers it to the source tree. Examples: EDIFACT, XML, JSON, CSV, X12.
The core task of Phase 3. Mapping transfers data from the source structure to the target structure according to defined rules. In the process, fields can be transformed, functions can be called, and values can be calculated.
Central operational overview of the Lobster Data Platform. The Control Center displays running jobs, successful jobs, and error logs. Administrators use it to monitor operations, intervene in running jobs, and restart failed jobs.