Přeskočit na hlavní obsah

Integration platform overview

Concept​

General architecture concepts of integration platform.

Terms

  • External Apps - an external application is an existing application integrated with AVAplace platform and running outside of the platform
    • Cloud application - application is running in external cloud environment, e.g. SaaS application
    • On-premise installation - application is installed and running on customer's site, e.g. ERP system
  • Native Apps - a native application running natively on AVAplace platform, developed using AVA application development SDK

Platform integration

Partner's eco-system​

Partner's eco-system provides hosting for partner's external applications, deployment infrastructure and AVAplace integration solutions.
Integration solution for external application can choose from gRPC or Webhook technologies served by MessageGateway platform service to consume messages from message bus.

Platform eco-system​

Platform eco-system provides hosting for native platform applications and services and for native business applications. All these applications and services are developed and deployed to AVAplace platform using AVA application development SDK (i.e. AppTemplate in .NET, UI kit in Angular, Dev-Ops). The native applications can be developed by development partners, see How to enlist and develop AVAnative application.
Integration solution is embedded into application using SDK and the native application running on AVAplace platform is using message broker directly to publish and consume messages from message bus

Basic methods of communication​

  1. The message consumer (message bus) providing notifications to registered subscribers
    The external message consumer is using gRPC or Webhook technologies served by MessageGateway platform service.
    • The gRPC technology is recommended for integration solutions based on .NET, because nuget package for gRPC consumer is provided, see documentation.
    • The Webhook technology is recommended for other technologies due to its simplicity, see documentation.
    • Note: The native message consumer is supported only for native applications running on AVAplace platform, see documentation.
  2. The REST API client to call APIs of platform services
  • Standard REST API calls to platform services using HTTP methods (GET, POST, PUT, PATCH, DELETE), see documentation.
  • The standard OAuth/OIDC authentication is supported. See documentation.

Integration processes​

Business integration process​

The Business Integration process provides automation of order approval and deployment of external cloud applications to the customer.
Important: The application usage data from partners utilizing their Pay-as-you-go billing model is obligatory for both types (i.e. native and external) of application.

The integration solution is based upon combination of two basic methods of communication:

  1. The message consumer providing notifications to registered subscribers, e.g. to consume order released notification to approve order and start deployment of purchased application.
  2. The REST API client to call APIs of platform services, e.g. to get order details and to control the order status flow of purchased application using PlatformStore.Order API.

Business integration

Data integration process​

The Data Integration process provides automation of data transfer between external and native applications and ERP systems using Virtual Data Models (VDM).

The integration solution is based upon combination of two basic methods of communication:

  1. The message consumer providing notifications to registered subscribers, e.g. to consume data changes notification to query data and update them in purchased application.
  2. The REST API client to call APIs of platform services, e.g. to consume or publish synchronized data of purchased application using data integration orchestrator (i.e. DataService API).

Data integration