Skip to main content

47 docs tagged with "integration"

View All Tags

Apache Camel - basics

Apache Camel integrations are defined within your application's jvm/{app-name}-script-config/{app-name}-camel.kts file.

Apache Camel - introduction

The Genesis low-code platform supports the use of Apache Camel in order to integrate with external systems, using its plethora of components.

Apache Camel - testing

To create integration tests for your Apache Camel routes, you need to create service tests by extending the AbstractGenesisTestSupport class and specifying the relevant application-name-camel.kts file as the scriptFileName.

Custom endpoints - configuring runtime

Gpal custom endpoints require no configuration beyond the web-handler.kts file. No modifications to the processes.xml file are required. Files will be picked up automatically by the Genesis Router from the /script folders.

Custom endpoints - examples

The example below is a collection of custom endpoints supporting SAML authentication. The LoginPostEndPoint, LoginUrlRequestEndPoint, LogoutEndPoint, and MetadataEndPoint all extend this AbstractSamlEndPoint.

Data Pipeline - introduction

Genesis Data Pipelines enable you to stream data into and out of your Genesis application. If you are looking to integrate your application with an external database or file system, this module should be your first consideration. If Data Pipeline does not offer you the solution you need, we suggest using Apache Camel to create the integration.

DB streaming out - introduction

The GenesisToDb module enables you to stream data from the Genesis low-code platform to classic RDBMS databases, such as Oracle or MSSQL.

Excel - functions

The following Excel functions are currently supported by ExcelToGenesis.

Excel - reference

The Genesis low-code platform enables you to convert existing Excel spreadsheets into Genesis data models.

FIX Gateway

This page shows you how to create a Gateway to connect to a remote system using the FIX (Financial Information eXchange) protocol.

FIX Gateways customisation

While the standard architecture of the FIX gateway is more than sufficient for most use cases, it is not ideal for more demanding architectures.


The FIX Xlator is a plugin for the Streamer and Streamer client, which enables type-safe handling of FIX messages. It also gives access to a set of vital integration features, such as FIXIN, EXECUTIONREPORT and CUSTOM_FIX.

Gateways and Streamers - introduction

If your application needs to integrate with external systems through a gateway, you need to be able to interpret incoming messages in the format of the external system. Equally, you need to be able to reformat information from your Genesis application when you send messages out to that system.

Integration testing

GenesisJunit is only available from version 8 of the Genesis Server Framework (GSF).

Notify - Genesis Screen

The Genesis platform provides a mechanism for creating pop-up toast notifications on screen in the app. Any notifications sent to the Genesis Screen Gateway will be sent as a toast pop-up notification.

Notify - Symphony

Symphony is a secure instant messaging service focused on financial companies.

Open API

Open API support was introduced in version 7.0 of the Genesis platform.

REST endpoints - introduction

The Genesis low-code platform automatically exposes all the resources you have configured as REST endpoints via the Genesis Router. Unless configured otherwise, all requests require a valid SESSIONAUTHTOKEN HTTP header. A SESSIONAUTHTOKEN is retrieved after successful user authentication.

REST endpoints - testing

The REST Endpoints created by the Genesis low-code platform reflect your application's business logic. These endpoints can be configured through the Genesis Router.