Versions Compared

Old Version 13

changes.mady.by.user Alexandra Aldea

Saved on

compared with

New Version 14

changes.mady.by.user Felix Janssen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example for configuring the connection: 

Code Block
languagetext
titleapplication-external-flow.properties
blueriq.connection.<connection-name>.external-flow.project = projectname // the REQUIRED name of the project that contains the flow to be started
blueriq.connection.<connection-name>.external-flow.version = 0.0-Trunk // the REQUIRED  version of the project that contains the flow to be started
blueriq.connection.<connection-name>.external-flow.flow = flowname // the REQUIRED  name of the flow to be started
blueriq.connection.<connection-name>.external-flow.channel = channel // the OPTIONAL name of the channel be started
blueriq.connection.<connection-name>.external-flow.baseurl =http https://<external-url>:<port>/Runtime/server // the OPTIONAL URL of the external host where the target project is on (if omitted the same server is assumed).

Alternatively, since Blueriq 12.9, it is possible to indicate a shortcut. The shortcut should be defined for the target runtime.

Code Block
languagetext
titleapplication-external-flow.properties
blueriq.connection.<connection-name>.external-flow.shortcut-name = myShortcut
blueriq.connection.<connection-name>.external-flow.channel = channel
blueriq.connection.<connection-name>.external-flow.baseurl = https://<external-url>:<port>/Runtime/server

When both a project/version/flow and a shortcut are configured, the shortcut takes precedence.


Info

The connection name, namely <connection-name> in the example above, needs to match the result of the evaluated expression from the AQ_ExternalFlow container implementation.