The gRPC trigger acts as the server to the gRPC clients. You create the trigger when you create a flow that gets attached to the trigger.
Trigger Settings
Field
Description
Trigger Settings
Port
The port on which the trigger listens to requests. You can use any port that is open. This field can also be set using an application property.
Proto File
A file with
.proto extension that contains the methods and service(s) definition which
TIBCO Cloud Integration - Flogo (PAYG) uses to create the flows. Currently, importing a
.proto file into another
.proto file is not supported.
Note:
The gRPC trigger and gRPC activity does not support options in the
.proto file. If your
.proto file contains any options, be sure to remove the options in
.proto file before using it.
You must not use the same gRPC
.proto file for a gRPC trigger and gRPC activities in the same app. The package names for the gRPC trigger and gRPC activities must be unique.
Secure Connection
By default, it is set to
False. If you set this field to
True, you can create a secure endpoint by providing
Server Key and
CA or Server Certificate.
Server Key - A PEM encoded private key file
CA or Server Certificate - A PEM encoded CA or self-signed server certificate file
Handler Settings
Service Name
Name of the service defined in the
.proto file. You must create one gRPC trigger for any specific
.proto file. Any subsequent gRPC triggers using the same
.proto file can select the service and method they need from the dropdowns.
Method
Name of RPC method in the
.proto file. Each method in the
.proto file is represented by a separate flow and attached to the same gRPC trigger.
Map to Flow Inputs
This tab allows you to map the trigger output to flow input. The tab displays fields from your selected method.
Map from Flow Outputs
Map the flow output to the trigger reply in this tab.
