Communication Interfaces: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
(Die Seite wurde neu angelegt: „de:Kommunikation_/_Schnittstellen (work in progress) = HVS32 = == Automatik-Polling == *HVS32 default interface == Interak…“) |
|||
| Zeile 3: | Zeile 3: | ||
(work in progress) | (work in progress) | ||
| − | = HVS32 = | + | = HVS32 Processing-Interfaces = |
| + | Please note: all descriptions are just examples. Field names, -length, format are open to customization. Due to a data evaluator, we are able to map your fields to our database structure. | ||
| + | Except Automatic-Polling SOAP/REST - these interfaces are fixed and can not easily be customized! | ||
| − | == | + | === Automatic-Polling === |
| − | *[[ | + | *[[HVS32_File_Interface_(Polling)|File (CSV, SDF, etc.)]] |
| + | *[[HVS32_REST_Interface_(Polling)|REST]] | ||
| + | *[[HVS32_SOAP_Interface_(Polling)|SOAP]] | ||
| + | *[[HVS32_ODBC_Interface_(Polling)|ODBC]] | ||
| + | *[[HVS32_JDBC_Interface_(Polling)|JDBC]] | ||
| + | *[[HVS32_SAP_RFC_Interface_(Polling)|SAP RFC]] | ||
| + | *[[HVS32_SAP_IDOC_Interface_(Polling)|SAP IDOC]] | ||
| + | *[[HVS32_Ehrhardt_%2B_Partner_LFS_Interface_(Polling)|Ehrhardt + Partner LFS]] | ||
| − | == | + | === Interactive === |
| − | *[[ | + | *[[HVS32_File_Interface_Deliverydata_(Interactive)|File (Deliverydata)]] |
| − | *[[ | + | *[[HVS32_File_Interface_Addressdata_(Interactive)|File (Addressdata)]] |
| + | *[[HVS32_SOAP_Interface_(Interactive)|SOAP]] | ||
| + | *[[HVS32_JDBC_Interface_(Interactive)|JDBC]] | ||
| + | *[[HVS32_SAP_RFC_Interface_(Interactive)|SAP RFC]] | ||
| − | = | + | = Sonstige Schnittstellen = |
| − | + | *[[Statusdaten_Export_Default_Interface|StatusEventMessage - Manager (SEM)]] | |
| − | |||
| − | *[[ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Version vom 24. April 2020, 16:26 Uhr
(work in progress)
HVS32 Processing-Interfaces
Please note: all descriptions are just examples. Field names, -length, format are open to customization. Due to a data evaluator, we are able to map your fields to our database structure. Except Automatic-Polling SOAP/REST - these interfaces are fixed and can not easily be customized!