Integration of an own application
What is an application and where are applications installed? After having answered those fundamental questions, we will present the different integration scenarios in the following.
There are three scenarios:
- Software as a Service (SaaS): The application is provided as SaaS and used stand-alone, i.e. isolated from other applications
- Enterprise Application Integration (EAI): The application is provided as SaaS and interacts with other applications via a standardized interface (logistics mall BUS)
- Logistics Mall Apps (Apps): Single apps run within the logistics mall infrastructure and make use of a customer-wide data repository. Apps can be combined using the logistics mall process designer.
Szenarien im Vergleich
Die Tabelle zeigt einen Vergleich der einzelnen Szenarien
|Software as a Service SaaS||Enterprise Application Integration EAI||Logistics Mall Apps|
|Description||The application is provided as SaaS and used stand-alone, i.e. isolated from other applications||The application is provided as SaaS and interacts with other applications via a standardized interface (logistics mall BUS)||Single apps run within the logistics mall infrastructure and make use of a customer-wide data repository. Apps can be combined using the logistics mall process designer.|
|Suitable application types|
|Suitable hosting options|
Integration of an application via the logistics mall BUS
This article describes how to integrate an application (e.g. a warehouse management system) with another application via the logistics mall BUS.
This scenario is an “application integration scenario”. Other scenarios are described in the article “Integration scenarios”.
- What is an application?
- Where are applications installed?
An application has to meet the following requirements:
- The application is a user application or a service application
- The application is mall-hosted or cloud-hosted
- The application is already integrated as software as a service, see software as a service scenario
Integration at a glance
This scenario is based on the software as a service scenario. The tasks described in the respective article must be completed first.
The following tasks are:
- Describing the use case of the integration
- Implementing BOD receiving interface(s)
- Implementing BOD transfer interface(s)
Use case of the integration
At first, the use case in which the application shares messages with other applications is described.
BOD receiving interface
In the context of the logistics mall, a message is a business object document or in other words an XML or JSON formatted data structure that contains a business object (e.g. a stock list, shipment, invoice…). Business object documents are shared via REST web services.
For every BOD type the application receives, the application must provide an REST web service. The specification is:
void : <http_url> ( parameter)
http_url: the http URL of the REST service, e.g.
parameter: BOD<Verb,Type> a BOD with verb PROCESS and existing BO type.
The parameter is transferred by means of a POST request.
BOD transfer interface
For every type of BOD an application wants to send, the application calls up a web service provided by the logistics mall BUS and defined analogue to the above-mentioned description.
The logistics mall BUS controls the reception and redirection of BODs between the different applications.