rest-to-database-app

Key Facts (verified)

• Always run fda commands from your Flogo apps directory (e.g. ./Flogo_Apps/)
• Always use the -f <filename>.flogo flag on every fda command to target the correct file — if omitted, fda defaults to flogo-project.flogo and will error if that file already exists or is not the intended target
• REST trigger type: tr_rest — exposes HTTP endpoints (default port 9999)
• Log activity type: act_general_log
• Reply activity type: act_general_reply
• Database query activity types: act_mysql_query, act_postgresql_query, act_sqlserver_query, act_oracledatabase_query
• Database connection types: con_mysql (MySQL), con_postgresql (PostgreSQL), con_sqlserver (SQLServer), con_oracledb (Oracle)
• Activities are automatically linked in sequence when added (no need to call create-link)
• The --connection flag on create-activity links the activity to a named connection — this sets settings.connection on the activity (the input.Connection field is left empty and is unused)
• When a connection is created, its settings are automatically pre-wired to application properties (e.g. $property["MySQL.<ConnectionName>.Host"]). Set those properties to configure the actual DB credentials — do NOT set connection.settings.* directly
• Flow input parameters must be declared in flow.metadata.input before they can be referenced as $flow.<param>
• Trigger handler input mapping (action.input) is how path/query params flow from the trigger into the flow
• set-attribute for handler mappings uses --jsonValue for object values
• Always call format-flow at the end to lay out the canvas properly

Step 1: Create project and database connection

Run all commands from your Flogo apps directory. Use -f <filename>.flogo on every command to target the correct file.

fda -f <filename>.flogo create-project <AppName> "<App description>"

# Choose the connection type that matches the target database
fda -f <filename>.flogo create-connection <ConnectionName> MySQL        # or PostgreSQL, SQLServer, oracledb