Guide – How To Start – Flogo – Event Processing System on Ubuntu 18.04

Flogo is an ultra-light ecosystem for building event-driven apps. The notion of triggers and actions are leveraged to process incoming events. An action, a common interface, exposes key capabilities such as application integration, stream processing, etc.

This is a quick deployment and ready-to-run image.
Simple and rapid installation. Easy to maintain.

Connection and Configuration of Flogo Server on Ubuntu

Important notice: Since there is no authorization in the portal, we strongly recommend you to open a firewall on port 3303 only for your IP address where you came from.

Go to http:\\%vm_ip%:3303.

Click “New”.

Click “Create an action”.

Enter “Action name” and click “Create”.

Click on the created flow.

Flogo is an event-driven framework. A trigger is the entry-point for events to, as the name implies, trigger the functionality of your app. The trigger is responsible for accepting the incoming event and invoking one or more defined actions (flows). To add a trigger, click on the “+” icon on the left hand side of the screen and select the Receive HTTP Message trigger.

Click on the gray panel “Input/Output”.

In the Input tab, you need to configure the input parameter we will use later:

Parameter name: name
Type: string

The response to the HTTP request will be a message and the HTTP status code, and to be able to send data back you’ll need to have Output parameters. From the screen where you are now, select the Output tab and configure two parameters:

Parameter name: code
Type: integer

Click on the “+” sign to add a new parameter

Parameter name: message
Type: any

Now it is time to configure the trigger to listen to HTTP messages. To start, click on the trigger and a new dialog will open with a bunch of options in the active Trigger settings tab. In this dialog you’ll have to provide:

Port: The port on which your app will listen (set this to 9233)
Method: The HTTP method that will trigger this flow (set this to GET)
Path: The path that will route the messages to this flow (set this to /test/:name, the :name means that you can use that as a path parameter in your mappings)

In that same dialog, select the second tab, Map to flow inputs. The parameter “a.. name” should be selected. Select pathParams in the trigger output and add .name or simply type $.pathParams.name into the text area.

Select the next tab, “Map from flow output”. Click on “123 code” to map it to one of the suggested flow output also called “123 code”. You should see $.code appear in the text area.

Now, still from the “Map from flow output” tab, select “* data” in the “Trigger Response” list on the left to map the output data.Select “* message” from the flow output list under the text area. Click on save and close the dialog.

Click “+” and pick the Log activity

As you hover over the newly added activity, a cog will appear and as you hover over that thing, a menu will appear to configure your activity. In this window you can configure the inputs of the “Log” activity.

Click on “a.. message” and type (or copy/paste) string.concat(“Hello “, $flow.name) in the box (on the right hand side of the screen). Click “Save”.

Add a “Return” activity. To add an activity click on the large “+” sign.

Hover over the newly added activity to see the cog and select configure to bring up the modal to configure the activity. The return activity is always the last activity in a branch and sets the values that are returned to the trigger. Click on “123 code” and type 200 in the input field to set the HTTP Response code to 200.

Now click on “a.. message” and type string.concat(“Hello “, $flow.name) in the input field. Finally click “Save” to complete the mapping.

Go back to the app menu, click “Build” and select your OS.

Double click on the downloaded file. The console should open.

You should open TCP port 9233. Search Windows for “Windows Defender Firewall” and open the suggested application. Select “Inbound Rules” in the left panel and click “New Rule” in the right panel.