In the Integration Builder, navigate to the Orchestration Manager section highlighted in green within the Transaction pattern. Here, you define the downstream steps for each transaction being configured, allowing you to interact with multiple receiving systems as needed.
Each step in the flow to a downstream system is defined by the Request that the GLU.Engine will send and the Response it will receive via the pre-configured Receiving System Connector.
Each step has several possible configuration fields:
Flow Code
- Used by Handlers to redirect the transaction flow to specific Flow Codes.
- This allows for non-sequential orchestration flow, independent of the sequence in which transaction steps with receiving systems are defined in the Console.
- Example: ‘db1’ is assigned as the Flow Code.
Exclude from Build
- This enables exclusion of the connection defined by this Flow Code from the build. It’s important to note that if this option is selected you won’t be able to route to Flow Code via this build.
- It’s useful when building a GLU.Engine and the connector is not needed in the current version.
- If ticked, the connector will not be included in the build or GLU billing.
Async
- If selected, the route will be executed asynchronously alongside other routes.
- By default, all routes are performed synchronously.
- Note: The flow between routes can be altered using Handlers, but routes marked as ‘Async’ will be invoked regardless of Handlers.
Process
- Marking an orchestration as ‘Process’, indicates that it will solely handle logic and routing via Handlers.
- There is no outbound request and response available on a Process orchestration.
Is StreamCall
This process is in Beta development with GLU.Ware team. Further descriptions will follow in later releases of GLU.Ware, however if you are interested in using streaming connectors please speak to GLU support.
Connector
- Refers to possible pre-defined Connectors for the Receiving System.
These configuration fields provide flexibility and control over the orchestration flow, allowing you to tailor the behaviour of each transaction steps to meet your specific integration requirements.
