Standard Process

The data created by Lobster_data can be output via different types of Response Routes. For each profile, any number of Response Routes can be defined. Each of the possible Response Route types can also occur multiple times.

However, a profile does not necessarily need to have a Response Route. This might, for example, be the case if either the Integration Unit already handles all the outputs or the data is only written to a database during the mapping process. The type of a Response Route determines how (e.g. via which network protocol) the file is sent to a target system.

For each Response Route, the content type (i.e. the output format of the transmitted file) can be set individually. This allows a profile job to pass the same data in multiple formats to different destinations, for example, saving it as a CSV file locally and sending it as an XML file (created with the XMLMemSaveTemplateParserUnit) to a server and also sending the input file (as received) to another destination. A postexecuter can be configured for each Response Route, with which the output file can be additionally manipulated.

Important note: All Response Routes are usually executed once per job, but you also have the option to do that once per record. See also sections Parsing and When Does the Parser Start a New Record?

States of Response Routes, Dependencies of Response Routes and State of Phase 6

Each individual Response Route has a state. Via these states, dependencies between Response Routes can be defined (e.g. Response Route 2 should only be executed if Response Route 1 was successful) and the states of all Response Routes determine the overall state of phase 6.

Postexecution