Data Processing and Back-End Integration

The Data Orchestration Engine (DOE) processes all data exchanged between the back-end system and the receivers (such as mobile devices). Depending from where the data comes (back end or client devices), the DOE processes the data by calling a set of predefined services. The concept of how the DOE processes the data is explained in this section.

Back-end systems are the source and target of data, which need to be exchanged with the client devices. So, you must know the concept of how to integrate the data objects in the DOE with the back-end data. This is also explained in this section.

Listed below are the conceptual topics covered in data processing and back-end integration:

• Flow definitions

  A flow definition is made up of flow blueprints, which specifies the services to be called to process a data object.

  More information: Flow Definition

• Flow blueprints

  Each flow blueprint defines a logically irreducible processing scenario such as back-end inbound initial load, outbound client with confirmation, and so on. This topic lists the different flow blueprints provided in the DOE.

  More information: Available Flow Blueprints

• Custom Service

  Predefined flow blueprints that contain standard services are provided in the DOE. However, to add additional services, based on your requirements, you must define custom services.

  More information: Custom Service

• Back-end adapters

  To connect the back-end systems and the data objects in the DOE, you use connectors called back-end adapters. Back-end adapters of type BAPI Wrappers can be used to connect to back-end systems.

  More information: Back-End Adapter