1. Home
  2. GLU.Guide
  3. New to GLU.Ware
  4. GLU.Engine – Introduction

GLU.Engine – Introduction

The GLU.Engine™ connects Initiating Systems to Receiving Systems. It exposes APIs as ‘Incoming Connectors’ that Initiating System connect to and it handles the downstream connections to the required Receiving Systems via ‘Outbound Connectors’. These connections may simply be for the distribution of records or data from one system to one or more downstream systems, or they may perform potentially complex orchestration and routing of transactions between multiple systems. Based on the configuration applied in the GLU.Console, each GLU.Engine performs the required Protocol Translation between Initiating Systems and Receiving Systems. Parameter Validation on all inbound messages can be applied so as to filter out spurious messages; thus protecting the downstream ecosystem from unnecessary load.


Orchestration rules can be attached to any received payload (Inbound API Requests or Receiving System API Responses). There is no limit to the number or Handlers that can be attached to any flow, this enables the GLU.Engine to perform riche transaction flow Orchestrations by running these in-flight rules to determine the routes that individual messages follow based on their respective parameter payloads.


Enrichment of message parameter sets is achieved by adding static or derived parameters within the GLU.Engine or from data received from any step in the flow.


Each GLU.Engine is SDLC Aware meaning that the SDLC stage (e.g. Test, Pre-Prod, Production) for which it has been built has embedded within it the network connection configurations necessary to seamlessly exchange messages between the correct end-point systems. Monitoring hooks enable monitoring data to be presented on the GLU.Console and a detailed Audit History of every GLU.Engine build process is retained on record in the GLU.Console. The GLU.Engine supports the transfer of messages securely using SSL and various End-Point Validation methods (e.g. Basic, OAuth, OAuth2) are supported. Additionally, anti-tamper hash value validations are supported.




Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies