Within the Integration Builder use the Orchestration Manager section in ‘Green’ of the Transaction pattern to define the downstream Receiving System transaction step or steps for each transaction being configured. There is no limit to the number of receiving systems that can be addressed within the definition of a single transaction.
Each step in the flow to a downstream system is defined by the Request that the GLU.Engine will deliver and the Response it will receive via the pre-defined Receiving System Connector.
Each such step has several possible configuration fields:
Flow Code
Used by Handlers to redirect the flow of a transaction (to specific Flow Code). Thus, the flow of any orchestration is not necessarily sequential in line with the sequence of that the transactions steps with Receiving Systems are defined in the Console. In the example above ‘db1’ is the assigned Flow Code.
Exclude from Build
This can be used to stop the connection defined by this Flow Code from appearing in the build. If this is ticked then this connector will not be included in build and it will not be possible to route to this flow code. It should be used when building a GLU.Engine and the connector is not needed in this version. Also if this is selected it will mean the connector will not be included in the GLU billing.
Async
If selected, this route will be performed asynchronously to other routes. By default, all routes are performed synchronously. Note: The Flow between routes can be altered with the use of Handlers – Flows marked as ‘Async’ will be invoked irrespective of any Handlers.
Process
An orchestration can be marked as ‘Process’. This is an orchestration that just handles logic and routing through the user of 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.
