The BackendObjectTransmitter provides documents and extracted items (e.g., articles) to external components for further processing (e.g., to a WWS).
Name | Meaning |
---|---|
Type | Type of the job step. |
Name | Name of the job step that will appear in the job designer |
Description | Optional description for the job step. |
DokumentStateToSet | Status that a transferred document gets. |
NewBackendWriterForEachCall | Flag |
UseDefaultSystemPartnerVariables | Flag |
Variables | A number of variables can be specified here, e.g. a DB_connection. If the value begins with a $, the value of a node variable or a variable of the standard system partner or of the system partner of the message is determined. For example, the value $Db_Connection_FB leads to a search for the node variable “Db_Connection_FB”; if this is not defined, the variable is searched for in the standard system partner in case UseDefaultSystemPartnerVariables is set, otherwise the variable is searched for in the system partner of the message. |
BackendType | Depending on the document to be booked by the external system, the corresponding backend type must be set. e.g. Checkers for articles, delivery note books for Despatch Advice etc. |
DebugTrace | Flag. Enables or disables additional debugging information. In this case, detailed SQL statements. |
Note: If messages which are transferred to a host system with the BackendObjectTransmitterEx are also to be containerized in a message box for informative purposes, one uses an EntityMessageCreator in addition to the BackendObjectTransmitter. This also requires that a suitable Containerizer is present for the INHOUSE Entity Types .