Skip to content

ws-Modul - preprocess - postprocess

ws-Modul - preprocess - postprocess

Annotations

The name "ws-module" stands for "web service module", but in ADIB there are also special modules / functions behind it, such as e.g.

  • Contentserv exports
  • ADIB portal creation

The Use-Cases page shows special cases that explain this peculiarity. What sounds complicated is actually quite simple and obvious in practice:

  • Should data be exported from Contentserv and e.g. be written to a csv file, so select
    • Module "CS-elasticsearch csv-export" as ws-module (or web service)
    • Modulates "Excel" destination
  • If you would like to generate an (ADIB) portal from a MySQL database table, select:
    • Module "MySQL" as source
    • "Source2Edit Portal" module as a web service

In these cases, the "ws module" takes the position of the source or destination.

ws-module

The ws-module (webservice module) has a certain special position, since it can be connected to a source (and then acts as a destination) and can itself be a data source that is connected to a target (i.e. destination module). In order to specify the web service more precisely, also specify the "web service template", which contains important information about the selected web service. You receive ready-made standard web services via the corresponding license components - such as e.g. for Shopware or for Salesforce CommerceCloud.

Example: You would like to send the data from your Navision system to your Shopware eShop on a regular basis. To do this, select the entry "SW-Articles/Variants" as wsModule.

Depending on the selected module (e.g. web service general), different (connection) parameters must then be entered so that ADIB knows how to access the data.

The following ws modules are available:

  • Contentserv area
    • CS elastic search csv export
      • The "Contentserv lightning export" module for PIM
    • CS elastic search csv export DAM
      • The "Contentserv lightning export" module for DAM
    • CS-elasticsearch2database
      • Exports the data from Contentserv to a database to be defined
    • CS-elasticsearch2Search-Portal
      • Creates a complete search-portal and renders all data from Contentserv to be accessible via this portal
    • CS-elasticsearch2Edit-Portal
      • Creates a complete edit-portal and renders all data from Contentserv to be accessible via this portal
      • Users can change data - that will be written back to the Contentserv system on a regular basis (i.e. every hour, every day,...)

      • INFO: In this case, just select the ws module. No source or destination module is required! The database is defined via the parameters in this ws module. * Shopware area * SW articles/variants * Shopware module in the area of ​​article/variant creation (the origin of the article must be defined as srcModule). * SW Cust/Orders * Shopware module in the Customers / Orders environment (the destination of the customer data or orders must be defined as destModule). * Web services area (general) * Webservice-General * A "generic" web service module: here you can define the structure of the web service to be addressed. * ElasticSearch * Solr * ADIB Portals section * CS-elasticsearch ElasticForms edit portal * Direct creation of an ADIB portal with editing options from Contentserv *

        INFO: In this case, just select the ws module. No source or destination module is required! * CS-elasticsearch Elasticforms Search Portal * Direct creation of an ADIB portal without editing option from Contentserv *

        INFO: In this case, just select the ws module. No source or destination module is required! * ElasticForms Search Portal * Source2Edit portal * Creation of an ADIB portal with editing option from the defined source (source module) * Source2Search portal * Creation of an ADIB portal without editing option from the defined source (source module) * Area special mappings / data structure transformations * Flex mapping * SAP Mara import

Pre-process

A pre-process is a process that takes place before the actual application integration.

The following pre-processes are available:

  • FTP/SFTP
  • Prepare file with timestamp
  • Rsync
  • SCP

Post-process

A post-process is a process that takes place after the actual application integration.

Example 1: You would like to be informed by email when a current product data export has been sent out to your customers.

Example 2: You export the list of customers' open items from your SAP system. The data should then be transmitted to the customer's system via SCP.

The following post processes are available:

  • Archive file after import: automatic renaming of file names
  • e-mail: Sending a confirmation e-mail after successful completion of the data integration
  • Replace pattern in file: Subsequent modification of the content of files (with freely definable searches - replace)
  • FTP/SFTP: Copy files to a foreign server via FTP/SFTP protocol.
  • Rsync: Synchronize orders.
  • SCP: Copy files to a foreign server using the SCP protocol.