Integration
Was this helpful?
Was this helpful?
The digiRunner platform provides robust integration capabilities, enabling it to function as a proxy or router for API requests. This integration architecture allows seamless connections between API consumers (such as applications and web clients) and backend servers, as well as core systems. The architecture supports secure data transfer, access control, and load balancing, offering flexible options for data formats and protocols.
In this mode, digiRunner acts as a proxy for API consumers, such as web or mobile applications, to connect to backend services securely.
Register Target APIs: The backend server APIs are registered on digiRunner to make them accessible to the applications.
Client Account Creation: Set up a client account on digiRunner to represent applications that will be consuming these APIs.
API Grouping: Organize registered APIs into API groups to streamline management and authorization.
Authorization: The API groups are authorized for the client accounts, allowing specific applications or API consumers to access designated APIs on the backend server.
API consumers (web or mobile apps) initiate requests with tokens, which pass through the firewall to the API Gateway in digiRunner.
The API Gateway processes and routes these requests to the correct backend APIs, as per the defined API group and client permissions.
In this mode, digiRunner acts as a router, facilitating secure communication between servers, including communication with core systems using various protocols.
Server-to-Server API Communication: The platform enables direct server-to-server API requests, providing an API key for secure access.
Protocol Support: digiRunner supports multiple protocols (e.g., HTTP, SOAP, MQ) for compatibility with diverse core systems and legacy environments.
API requests from the client (API consumer) are forwarded through digiRunner to different core system hosts.
Depending on the host and data requirements, the requests are routed with the appropriate protocol (e.g., JSON over HTTP, XML over SOAP, or Telex over MQ).
The API Gateway securely routes data across different systems, ensuring data reaches the correct endpoint in a compatible format.
In the dAAPR configuration, digiRunner can simultaneously serve as both a proxy and a router, allowing it to handle a variety of integration patterns between clients, servers, and core systems.
Client to Server: As a proxy, digiRunner manages token-based API requests from applications and routes them to the appropriate backend API.
Server to Server: As a router, digiRunner manages API key-based communication between servers and core systems, supporting multiple protocols for interoperability.
API requests with tokens are processed by the API Gateway for client-to-server interactions, while API key-based requests manage server-to-server interactions.
Requests can be routed to different hosts based on protocol requirements, facilitating flexible data exchange across various systems.
This dual configuration is ideal for environments requiring both client-server and server-server data communication, offering comprehensive integration capabilities.
