GLU Transaction Pattern

Within the Integration Builder, one uses the ‘Transactions Panel’ to Add Transactions. By clicking on ‘Add Transaction’, the Integration Builder will automatically create the Transaction ‘Pattern’ that is applicable to all Transactions.

Stp 01.png

All GLU.Ware Transactions follow this standardised repeating ‘Pattern’ whereby each transaction is defined or ‘anchored’ by the API definition. This comprises of the Inbound API Request that comes from any particular Initiating System, followed by the API Response that the GLU.Engine will return to that Initiating System.

Thereafter the Orchestration Manager is used to define what the GLU.Engine should do with the API Request payload once it has been received. Use the ‘Add Endpoint’ button to add ‘legs’ to your Orchestration configuration.

When you click ‘Add Endpoint’ the configuration pattern for Outbound Connectors is pre-populated for you. In this way the user is guided through the configuration of the Orchestration legs by populating the required configurations for each Outbound Request and Response to Endpoints that have been added to your configuration.

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

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