BackendObjectTransmitterEx
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 | Here you can specify a set of variables which are then available to the BackendObjectRetrieverEx (eg individual DB_connection strings, etc.). It is also possible to refer to system partner variables by placing a '$' in front of them. If you define e.g. the variable with key eBiss.DbAdapter.ConnectionString as value $DB_Test, then the value of the variable DB_Test of the main location of the default system partner is used or if UseDefaultSystemPartnerVariables is set to no, the variable of the message system partner. |
| 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 .