GLU Transaction Pattern

In the Integration Builder, the process of adding transactions is facilitated through the ‘Transactions Panel.’ When you select ‘Add Transaction,’ the Integration Builder generates a standardized transaction ‘Pattern’ that is universally applicable to all transactions.

All GLU.Ware transactions adhere to this consistent and repeating ‘Pattern.’ Each transaction is structured or ‘anchored’ by the API definition, encompassing the Inbound API Request received from an Initiating System, followed by the API Response that the GLU.Engine sends back to that Initiating System.

The next step involves the use of the Orchestration Manager to specify the actions that the GLU.Engine should perform with the API Request payload upon reception. To enhance the orchestration configuration, the ‘Add Endpoint’ button can be utilized to incorporate different ‘legs’ into the configuration.

Note: This orchestrates the outgoing request in the applicable format expected by the third party being integrated to.

When you click the ‘Add Endpoint’, the configuration pattern for Outbound Connectors is automatically pre-populated. This approach guides users through the orchestration configuration by streamlining the input of necessary configurations for each Outbound Request and Response to the Endpoints that are included in the configuration.

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

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