Introduction to Connectors

GLU.Engines employ the concept of Connectors. Connectors can be one of three types:

  1. Inbound Connectors are consumed by Initiating Systems that send messages to the GLU.Engine – these your GLU.Engine API’s.
  2. Outbound Connectors are used by the GLU.Engine to initiate messages / calls to downstream Receiving Systems.
  3. Inbound/Outbound Connectors are interfaces that can serve as a bi-directional interface to the GLU.Engine. This type is applicable in particular to certain technologies such as ISO8583.

GLU.Ware supports an ever expanding list of protocols and their associated payloads including TCP/IP, HTTP, SMTP, FTP, SOAP, REST, ISO8583, ISO20022 – SWIFT MX, ISO15022 – SWIFT MT, MML, GraphQL, FTP, SAP AMQP – Rabbit MQ, AMQP – Apache MQ, SMPP/SMPPS, LDAP and various Database Connectors including MySQL, Oracle, MS SQL, BD2, PostgreSQL and Cassandra.

The GLU.Engine is able to transform any supported Protocol to any other supported Protocol. It does this by un-marshalling all payload attributes received into a ‘GLU Object Model’ maintained within the GLU.Engine and it then Marshalls those attributes to outbound payloads using protocol specific content types as required.

The diagram below illustrates a Digital Channel Platform being an Initiating System will consume an Inbound Connector (API) on the GLU.Engine. The downstream ‘Receiving Systems’ (Business Systems, Scoring Systems, Regulatory Systems and CBS) are all accessed via Outbound Connectors (or if ISO8582 is employed an Inbound/Outbound Connector).

Source Systems that originate transactions, consume the Inbound (‘API’) Connector exposed on the GLU.Engine. The Outbound Connectors on the GLU.Engine will ‘consume’ the interface (or API) that downstream or Target systems expose.

There can be multiple Target systems in any flow but there is only ever one Source System for a particular transaction. During configuration of any Connector Interface on the GLU.Console, the user will define if the Connector being configured is an ‘Inbound’, ‘Outbound’ or ‘Both’. This categorisation is important in that it presents specific parameters and variables that vary between the ‘API’ and ‘Connector’ Interface contexts.

Was this article helpful?

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

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