Apache Pulsar Connection Details
The Apache Pulsar connection is a container for all the client connection parameters used by Apache Pulsar Publisher activity and Apache Pulsar Subscriber trigger. To establish the connection successfully, specify the following connection details in the Apache Pulsar dialog box:
Field | Required | Description |
---|---|---|
Name | Yes | Specify a unique name for the connection you are creating. This name is displayed in the Connection Name drop-down list for each activity. |
Description | No | A brief description of the connection. |
Broker URL | Yes | The URL of the broker. It follows the format-
pulsar+ssl://<host_name>:<port> where
pulsar is the protocol and
+ssl is an optional parameter that shows that the connection is secured by TLS. The content following the
:// is the host name and the port on which the broker is running.
If the URL of the broker is SSL then the CaCert field is enabled. This field must be provided unless the Allow Insecure Connection option is enabled. If the authorization is enabled, then the connector would insist that you use SSL to protect the credentials when you are on the network. |
Authorization Type | Yes | You can choose the authorization type from the following options:
|
Allow Insecure Connection | Yes | The Allow Insecure Connection field is available if +ssl is present in the Broker URL field so that the self-signed development mode certificates can be used to connect to the broker. If this field is enabled, then the Broker CA field is removed as it is not needed anymore. |
Broker CA | Yes | The Broker CA field points to the certificate authority used to sign the broker's certificate for secure connections. The Flogo client now trusts the broker. |
Client Cert | Yes | If the Authorization Type field is TLS, then the Client Cert field must point to the client's certificate. The broker must trust this certificate. |
Client Key | Yes | If the Authorization Type is TLS, then the Client Key field must point to the client's key. |
JSON Web Token | Yes | If the Authorization Type is JWT, then the JSON Web Token field must contain the text contents of the JWT obtained for this connection. |
Connection Timeout | No | Connection timeout in seconds. The timeout for establishing a TCP connection. The default value is 5 seconds. |
Operation Timeout | No | Operation timeout in seconds. The operations like Producer-create and Subscribe would be retried until this interval. The default value is 30 seconds. |