Integration Namespaces

Within an Integration Namespace, APIs (provided by other solutions in the Solution Designer or external APIs) can be made usable. An Integration Namespace supports the Business Analyst and the Solution Developer to call operations of the referenced API and to map the response to the ubiquitous language of the solution.

After providing the OpenAPI Specification (as JSON or YAML), the platform will create a type-safe interface for the Operations defined in the OpenAPI Specification. This allows developers to program against the API as if it was a service locally defined in the solution. In addition, the platform abstracts common components such as API URL, path- and query-parameters away, so that the developer only needs to provide the parameter values and (optionally) a request body in order to invoke the operation

To use the operations, a REST-Integration service and its related Input- and Output-Entities must be modeled in the Integration Namespace. Inside the service, the developer can call the operations and the mapping from the Input-Entity to the parameters or request bodies and from the response to the Output-Entity of a service takes place.

The entities in the integration namespace can be used as ‘known-entity’ of an External Entity in the Domain-Namespace