Configuring an External System as a Source or Target

When you create or edit a Micro-Integration you must supply the appropriate connection details for the external system. For details about how to configure the source or target parameters for your external system, see the vendor-specific sections linked below:

To configure your event broker service, see Configuring Your Event Broker Service as a Source or Target.

Amazon SNS

You can configure Amazon SNS only as a target . The parameters are described in the following tables:

For message headers, see Amazon SNS Message Headers.

Amazon SNS Target Parameters

The following table describes the parameters for configuring Amazon SNS as a target.

Field Description
AWS Region The AWS region for this SNS topic.

Authentication Scheme

The authentication scheme to use when connecting to Amazon SNS. One of:

  • AWS Access Key—Additional configuration is required. For more information, see AWS Access Key.

  • AWS Chained IAM Role Assumption—Additional configuration is required. For more information, see AWS Chained IAM Role Assumption.

Authentication using AWS Chained IAM Role Assumption is supported only for event brokers hosted on AWS.

Destination

The SNS ARN (Amazon Resource Name) or target SNS topic name.

If you provide the SNS topic name:

  • If the SNS does not exist, the Micro-Integration attempts to create the SNS and then returns its ARN.

  • If the SNS already exists, the Micro-Integration returns the ARN for the existing SNS.

You should be aware that when you provide the SNS topic name, the account configured for the Micro-Integration must have the necessary SNS create permissions, otherwise the creation process fails due to insufficient access.

For example, you can specify an ARN value as follows:

arn:aws:sns:us-east-2:123456789012:MyTopic

Amazon SNS Authentication Parameters

The tables that follow describe the parameters required for the selected authentication scheme. You can choose one of:

AWS Access Key

Field Description
AWS Access Key An access key identifier.
AWS Secret Key The secret key associated with the AWS Access Key.

AWS Chained IAM Role Assumption

Chained IAM role assumption allows Micro-Integrations to securely access AWS resources across different AWS accounts without requiring direct credential exchange. Chained IAM role assumption works through a trust relationship between AWS accounts:

  • The resource owner creates an IAM role (solace-mi-workload-role) in their AWS account, and configures it with the specific permissions required.

  • This role is configured to trust the Solace AWS account's role (single-pod-identity-role in account 718462147973).

  • When a Micro-Integration needs to access the resource, it uses the trust chain to temporarily assume the necessary permissions, as follows:

    [Assume single-pod-identity-role] → [Get credentials to assume solace-mi-workload-role] → 
[Assume solace-mi-workload-role] → [Get credentials to access the target vendor resource] → 
[Access the resource]

The resource owner must do the following:

  1. Create a role called solace-mi-workload-role in the resource owner's AWS account and attach the following trust policy:

    {
  "Version":"2012-10-17",
  "Statement":[{
    "Effect":"Allow",
    "Principal":{
      "AWS":"arn:aws:iam::718462147973:role/single-pod-identity-role"
     },
    "Action":[
     "sts:TagSession",
     "sts:AssumeRole"
     ]
  }]
}

  2. Attach the required resource permissions to the solace-mi-workload-role. The minimum required permissions are:

    • sns:Publish

    • sns:ListTopics

    • sns:CreateTopic

The following table describes the parameters for configuring authentication using chained IAM role assumption.

Field Description
AWS Account ID  The 12-digit AWS Account ID to be used for IAM role assumption. This is the account where the solace-mi-workload-role exists.
Session Name

The session name to use for the assumed role session (defaults to solace-mi-workload-session if not provided)
External ID

An optional external ID to use if the resource owner's trust policy requires it.

To configure it, the resource owner must separate the sts:TagSession and sts:AssumeRole into different statements in the solace-mi-workload-role trust policy and add the following condition to the sts:AssumeRole statement:

"Condition":{
  "StringEquals":{
    "sts:ExternalId":"<your_external_id_string>"
   }
 }

Amazon SQS

You can configure Amazon SQS as either a source or a target. The parameters are described in the following tables:

For message headers, see Amazon SQS Message Headers.

Amazon SQS Source Parameters

The following table describes the parameters for configuring Amazon SQS as a source.

Field Description
AWS Region The AWS region for this SNS topic.
Authentication Scheme

The authentication scheme to use when connecting to Amazon SNS. One of:

  • AWS Access Key—Additional configuration is required. For more information, see AWS Access Key.

  • AWS Chained IAM Role Assumption—Additional configuration is required. For more information, see AWS Chained IAM Role Assumption.

Authentication using AWS Chained IAM Role Assumption is supported only for event brokers hosted on AWS.

Queue Name The source SQS queue name.

Amazon SQS Target Parameters

The following table describes the parameters for configuring Amazon SQS as a target.

Field Description
AWS Region The AWS region for this SNS topic.
Authentication Scheme

The authentication scheme to use when connecting to Amazon SNS. One of:

  • AWS Access Key—Additional configuration is required. For more information, see AWS Access Key.

  • AWS Chained IAM Role Assumption—Additional configuration is required. For more information, see AWS Chained IAM Role Assumption.

Authentication using AWS Chained IAM Role Assumption is supported only for event brokers hosted on AWS.

Queue Name The target SQS queue name.

Amazon SQS Authentication Parameters

AWS Access Key

Field Description
AWS Access Key An access key identifier.
AWS Secret Key The secret key associated with the AWS Access Key.

AWS Chained IAM Role Assumption

Chained IAM role assumption allows Micro-Integrations to securely access AWS resources across different AWS accounts without requiring direct credential exchange. Chained IAM role assumption works through a trust relationship between AWS accounts:

  • The resource owner creates an IAM role (solace-mi-workload-role) in their AWS account, and configures it with the specific permissions required.

  • This role is configured to trust the Solace AWS account's role (single-pod-identity-role in account 718462147973).

  • When a Micro-Integration needs to access the resource, it uses the trust chain to temporarily assume the necessary permissions, as follows:

    [Assume single-pod-identity-role] → [Get credentials to assume solace-mi-workload-role] → 
[Assume solace-mi-workload-role] → [Get credentials to access the target vendor resource] → 
[Access the resource]

The resource owner must do the following:

  1. Create a role called solace-mi-workload-role in the resource owner's AWS account and attach the following trust policy:

    {
  "Version":"2012-10-17",
  "Statement":[{
    "Effect":"Allow",
    "Principal":{
      "AWS":"arn:aws:iam::718462147973:role/single-pod-identity-role"
     },
    "Action":[
     "sts:TagSession",
     "sts:AssumeRole"
     ]
  }]
}

  2. Attach the required resource permissions to the solace-mi-workload-role. The minimum required permissions are:

    • sqs:GetQueueAttributes

    • sqs:GetQueueUrl

    • sqs:SendMessage

    • sqs:ReceiveMessage

    • sqs:DeleteMessage

The following table describes the parameters for configuring authentication using chained IAM role assumption.

Field Description
AWS Account ID  The 12-digit AWS Account ID to be used for IAM role assumption. This is the account where the solace-mi-workload-role exists.
Session Name

The session name to use for the assumed role session (defaults to solace-mi-workload-session if not provided)
External ID

An optional external ID to use if the resource owner's trust policy requires it.

To configure it, the resource owner must separate the sts:TagSession and sts:AssumeRole into different statements in the solace-mi-workload-role trust policy and add the following condition to the sts:AssumeRole statement:

"Condition":{
  "StringEquals":{
    "sts:ExternalId":"<your_external_id_string>"
   }
 }

Azure Service Bus

You can configure Azure Service Bus as either a source or a target.

Azure Service Bus offers different service tiers, each with varying capabilities. We've tested the Premium tier with this Micro-Integration and it meets the expected performance throughput. In addition, even though the Azure Service Bus offers large message sizes of 80 MB and above, you cannot use message sizes larger than:

  • 30 MB for PubSub+ event broker services (Enterprise service classes)
  • 10 MB for PubSub+ event broker services (Developer service class).

Ensure that you select an Azure Service Bus tier that meets your requirements for performance throughput. For more information about tier differences, see Azure Service Bus Premium messaging and Azure Service Bus Quotas.

The parameters are described in the following tables:

For message headers, see Azure Service Bus Message Headers.

Azure Service Bus Source Parameters

The following table describes the parameters for configuring Azure Service Bus as a source.

Field Description

Service Bus Namespace Connection String

The Azure Service Bus connection string.

The connection string must provide one of:

  • a Shared Access Key (SharedAccessKeyName and SharedAccessKey)

  • a Shared Access Signature (SharedAccessSignature)

AMQP connection strings are not supported.

Destination Type

The type for the Azure Service Bus destination. Select either an Azure TOPIC or QUEUE.

Destination

The source destination.

Subscription

The subscription name for the group consumer.

Azure Service Bus Target Parameters

The following table describes the parameters for configuring Azure Service Bus as a target.

Field Description

Service Bus Namespace Connection String

The Azure Service Bus connection string.

The connection string must provide one of:

  • a Shared Access Key (SharedAccessKeyName and SharedAccessKey)

  • a Shared Access Signature (SharedAccessSignature)

AMQP connection strings are not supported.

Destination

The target destination.

Google Cloud Pub/Sub

You can configure Google Cloud Pub/Sub as either a source or a target. The parameters are described in the following tables: 

For message headers, see Google Cloud Pub/Sub Message Headers.

Google Cloud Pub/Sub Source Parameters

The following table describes the parameters for configuring Google Cloud Pub/Sub as a source.

Field Description
Project ID The Google Cloud project identifier.
Credentials The Google Cloud Application Default Credential (ADC). The maximum length is 10000 characters.
Destination The Google Cloud Pub/Sub topic name.
Subscription Name The Google Cloud Pub/Sub subscription name.
Auto-Create Resources The option to auto-create the Google Cloud Pub/Sub topic and/or subscription if it doesn't exist. The option is disabled by default.

Google Cloud Pub/Sub Target Parameters

The following table describes the parameters for configuring Google Cloud Pub/Sub as a target.

Field Description
Project ID The Google Cloud project identifier.
Credentials The Google Cloud Application Default Credential (ADC). The maximum length is 10000 characters.
Destination The Google Cloud Pub/Sub topic name.
Auto-Create Resources The option to auto-create the Google Cloud Pub/Sub topic if it doesn't exist. The option is disabled by default.

IBM MQ

You can configure IBM MQ as either a source or a target. The parameters are described in the following tables: 

For message headers, see IBM MQ Message Headers.

IBM MQ Source Parameters

The following tables describe the parameters for configuring IBM MQ as a source. The parameters differ depending on whether you choose to use a native connection or a JNDI lookup.

Native Connection

Field Description
Connection Name The name of the connection to IBM MQ, such as the hostname or IP address. For example, 123.123.123.123 (1414), where 123.123.123.123 is the host and 1414 is the port.
Username The username to authenticate with IBM MQ.
Password The password to authenticate with IBM MQ.
Queue Manager The name of the queue manager on IBM MQ. For example: QM1.
Channel The channel on IBM MQ. For example,DEV.APP.SVRCONN.
Additional Connection Properties

(Optional) The IBM MQ connection properties (refer to the IBM MQ documentation). Click Add Context if you need to specify additional context properties.
Destination Type Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup.
Destination The binding identifier of the queue in IBM MQ. For example: my-ibmmq-target-queue_mqConnector_mq_sourceQ_10.
Durable Subscription Name

The name of the durable subscription multiple consumers can bind to. Durable subscriptions accumulate messages even when all consumers are offline, ensuring that no messages are lost.

This value is mandatory when the Destination Type is TOPIC. It is also required if the Destination Type is UNKNOWN and the destination resolves to a topic.

JNDI Lookup

Field Description
JNDI Context

(Optional) The IBM MQ connection properties (refer to the IBM MQ documentation). The required connection properties are as follows:

  • java.naming.factory.initial
  • java.naming.provider.url

(Optional) Click Add Context if you need to specify additional contexts.
Connection Factory Name The name of the JMS connection factory that defines the properties for the connection.
Username The username to authenticate with IBM MQ.
Password The password to authenticate with IBM MQ.
Destination Type Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup.
Destination The binding identifier of the queue in IBM MQ. For example: my-ibmmq-target-queue_mqConnector_mq_sourceQ_10.
Durable Subscription Name

The name of the durable subscription multiple consumers can bind to. Durable subscriptions accumulate messages even when all consumers are offline, ensuring that no messages are lost.

This value is mandatory when the Destination Type is TOPIC. It is also required if the Destination Type is UNKNOWN and the destination resolves to a topic.

IBM MQ Target Parameters

The tables describe the parameters for configuring IBM MQ as a target. The parameters differ depending on whether you choose to use a native connection or a JNDI lookup.

Native Connection

Field Description
Connection Name The name of the connection to IBM MQ, such as the hostname or IP address. For example, 123.123.123.123 (1414), where 123.123.123.123 is the host and 1414 is the port.
Username The username to authenticate with IBM MQ.
Password The password to authenticate with IBM MQ.
Queue Manager The name of the queue manager on IBM MQ. For example: QM1.
Channel The channel on IBM MQ. For example,DEV.APP.SVRCONN.
Additional Connection Properties

(Optional) The IBM MQ connection properties (refer to the IBM MQ documentation). Click Add Context if you need to specify additional context properties.
Destination Type Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup.
Destination The binding identifier of the queue in IBM MQ. For example: my-ibmmq-source-queue_mqConnector_mq_sourceQ_10.

JNDI Lookup

Field Description
JNDI Context

The IBM MQ connection properties (refer to the IBM MQ documentation). The required connection properties are as follows:

  • java.naming.factory.initial
  • java.naming.provider.url

(Optional) Click Add Context if you need to specify additional contexts.
Connection Factory Name The name of the JMS connection factory that defines the properties for the connection.
Username The username to authenticate with IBM MQ.
Password The password to authenticate with IBM MQ.
Destination Type Select TOPIC or QUEUE when the destination name is known, otherwise use UNKNOWN for a JNDI lookup.
Destination The binding identifier of the queue in IBM MQ. For example: my-ibmmq-source-queue_mqConnector_mq_sourceQ_10.

Microsoft SQL Server CDC

 

You can configure Microsoft SQL Server CDC only as a source. The parameters are described in the table in Microsoft SQL Server CDC Source Parameters.

For message headers, see Microsoft SQL Server CDC Message Headers.

Microsoft SQL Server CDC Source Parameters

The following table describes the parameters for configuring Microsoft SQL Server as a source.

Field Description
Checkpoint Store Configuration
Checkpoint Queue  The name of the Last Value Queue (LVQ) on the PubSub+ event broker to use for checkpointing. The LVQ stores information about the files that have been processed and the files that are currently being processed. The LVQ must exist on the same event broker and VPN as the target destination.
Auto Create Checkpoint Queue Select to automatically create the LVQ if it does not exist.
Debezium SQL Server Configuration Properties
Destination The name of the table, including the schema name. Specify the destination using the <schemaName>.<tableName> format.
Database Hostname The hostname of the Microsoft SQL Server database server.
Database Port The port of the Microsoft SQL Server database server.
Database Instance The name of the Microsoft SQL Server instance.
Database Name The name of the Microsoft SQL Server database.
Skip Delete Events Select to skip the processing of delete events from the database change stream.
Authentication

Not editable. Pre-populates to Basic Authentication.
Basic Authentication
Username  The username to use for logging in to Microsoft SQL Server.
Password The password use for authenticating with the Microsoft SQL Server database.
Additional Properties

Additional properties for the SQL Server database.

(Optional) Any additional configuration related to Microsoft SQL Server. Click Add Context if you need to specify additional context properties. For more information, see Additional Properties.

Additional Properties

The following table lists some important additional properties that are available. For details about all the available properties, see the documentation for the Debezium SQL Server Component of Apache Camel.

Field Description
topicPrefix

A logical namespace for the Microsoft SQL Server database server or cluster. The topicPrefix is an internal identifier that helps distinguish between different Microsoft SQL Server sources when multiple connectors are running. It must contain only alphanumeric characters, hyphens, dots, and underscores. If not configured, it defaults to the binding name.

The topicPrefix does not become an SMF topic.
snapshotMode

The criteria for running a snapshot upon startup of the connector. The allowed values are:

  • initial—The default. Takes a snapshot on first startup, then streams changes.

  • always —Performs snapshot on every connector start.

  • initial_only—Takes a snapshot but doesn't transition to streaming.

  • no_data—Schema structure only, no data.

  • never—Never takes snapshots.

  • recovery —Takes snapshot when no offsets are available.

  • when_needed—Takes a snapshot when the connector determines it's needed.

  • configuration_based—Uses connector-specific configuration.

  • custom—Uses a custom snapshotter implementation.
skippedOperations

A comma-separated list of operations to skip during streaming. The allowed values are: 

  • c—Skip create/insert operations.

  • u—Skip update operations.

  • d—Skip delete operations.

  • t—Skip truncate operations (default).

  • none—Skip nothing (process all operations).

For example, skippedOperations=t,d indicates to skip truncations and deletions.
tombstonesOnDelete Indicates whether delete operations should be represented by a delete event and a subsequent tombstone event. When tombstonesOnDelete=true, a delete operation generates two events: a delete event and a subsequent tombstone event (key with null value). This allows message brokers with log compaction to completely remove all events for a deleted row's key.
timePrecisionMode

Times, dates, and timestamps can be represented with different kinds of precision, including:

  • adaptive—The default. Captures time and timestamp values exactly as in the database using millisecond, microsecond, or nanosecond precision values based on the database column's type.
  • adaptive_time_microseconds—Always uses microsecond precision for time fields.
  • connect—Always represents time and timestamp values using millisecond precision regardless of the database column's precision.
decimalHandlingMode

Specifies how decimal and numeric columns should be represented in change events. Valid options include:

  • precise—Represents numbers precisely in binary form using java.math.BigDecimal values.
  • double—Represents numbers using Java double values, which may result in a loss of precision but are easier to use.
  • string—Encodes numbers as formatted strings. Semantic information about the real type is lost.

 

MQTT

You can configure MQTT as a source or a target. The parameters are described in the following tables: 

For message headers, see MQTT Message Headers.

MQTT Source Parameters

The following table describes the parameters for configuring MQTT as a source.

Field Description

MQTT Server URIs

The comma-separated list of MQTT server URIs, such as tcp://host:port.

MQTT Version

(Optional) The MQTT version. The default is MQTT v5.0.

Username

(Optional) The username for authentication with the MQTT broker.

Password

(Optional) The password for authentication with the MQTT broker.

Enable Clean Session

(Optional) Enable an MQTT Clean Session when selected. This option is selected (enabled) by default.

For more information about MQTT Clean Sessions, see MQTT Sessions.

Session Expiry Interval

(Optional) The number of seconds a session survives after its client becomes disconnected. The minimum value is 0.

For more information about MQTT Session Expiry Intervals, see MQTT Clean Start and Session Expiry Interval.

Enable Automatic Reconnect

(Optional) Enable automatic reconnection when selected. The option is selected (enabled) by default.

Automatic Reconnect Delay

(Optional) The maximum number of seconds to wait before attempting to reconnect. The number of seconds can be 0 or more. The default is 30.

Connection Timeout

(Optional) The number of seconds for the connection timeout. The number of seconds can be 0 or more. The default is 30.

Keep Alive Interval

(Optional) The number of seconds for the MQTT Keep Alive interval. The number of seconds can be 0 or more. The default is 60.

For more information about MQTT Keep Alive, see MQTT Keep Alive Parameter.

SSL Configuration

(Optional) Enable or disable Secure Sockets Layer (SSL) configuration. The default is Disable SSL Configuration. If SSL configuration is enabled, additional parameters are required.

For more information, see MQTT SSL Configuration Parameters.

Will Configuration

(Optional) Enable or disable MQTT Last Will configuration. The default is Disable Will Configuration. If Last Will configuration is enabled, additional parameters are required.

For more information, see MQTT Last Will Configuration Parameters.

Destination

The MQTT topic name. This field supports multiple topics where each topic is separated by a comma, wildcards, and shared subscriptions (MQTT v5 only).

For more information about MQTT topics, see MQTT Topics and Wildcards.

Client ID

(Optional) The client identifier for the publisher connection.

QoS

(Optional) The quality of service for published messages. The default value is 1.

Enable DLT

(Optional) The option to enable Dead-Letter topics (DLT) for failed consumer messages. If the DLT Name is not configured, failed consumer messages are forwarded to the dlt/{source-topic-name} topic.

For more information about Dead-Letter topics, see Dead-Letter Topic Processing.

DLT Name

(Optional) The name of the Dead-Letter topic. If DLT is enabled, failed consumer messages are forwarded to the topic that is configured with the DLT name.

MQTT Target Parameters

The following table describes the parameters for configuring MQTT as a target.

Field Description

MQTT Server URIs

The comma-separated list of MQTT server URIs, such as tcp://host:port.

MQTT Version

(Optional) The MQTT version. The default is MQTT v5.0.

Username

(Optional) The username for authentication with the MQTT broker.

Password

(Optional) The password for authentication with the MQTT broker.

Enable Clean Session

(Optional) Enable an MQTT Clean Session when selected. This option is selected (enabled) by default.

For more information about MQTT Clean Sessions, see MQTT Sessions.

Session Expiry Interval

(Optional) The number of seconds a session survives after its client becomes disconnected. The minimum value is 0.

For more information about MQTT Session Expiry Intervals, see MQTT Clean Start and Session Expiry Interval.

Enable Automatic Reconnect

(Optional) Enable automatic reconnection when selected. The option is selected (enabled) by default.

Automatic Reconnect Delay

(Optional) The maximum number of seconds to wait before attempting to reconnect. The number of seconds can be 0 or more. The default is 30.

Connection Timeout

(Optional) The number of seconds for the connection timeout. The number of seconds can be 0 or more. The default is 30.

Keep Alive Interval

(Optional) The number of seconds for the MQTT Keep Alive interval. The number of seconds can be 0 or more. The default is 60.

For more information about MQTT Keep Alive, see MQTT Keep Alive Parameter.

SSL Configuration

(Optional) Enable or disable Secure Sockets Layer (SSL) configuration. The default is Disable SSL Configuration. If SSL configuration is enabled, additional parameters are required.

For more information, see MQTT SSL Configuration Parameters.

Will Configuration

(Optional) Enable or disable MQTT Last Will configuration. The default is Disable Will Configuration. If Last Will configuration is enabled, additional parameters are required.

For more information, see MQTT Last Will Configuration Parameters.

Destination

The MQTT topic name. This field supports multiple topics where each topic is separated by a comma, wildcards, and shared subscriptions (MQTT v5 only).

For more information about MQTT topics, see MQTT Topics and Wildcards.

Client ID

(Optional) The client identifier for the publisher connection.

QoS

(Optional) The quality of service for published messages. The default value is 1.

Retained

(Optional) The option to retain published messages. The option is disabled by default.

For more information about MQTT retained messages, see MQTT Retained Messages.

Async Publish

(Optional) The option to publish asynchronously. The option is disabled by default.

MQTT SSL Configuration Parameters

Field Description

Certificate Authority (CA) certificate

The Certificate Authority (CA) certificate.

Client Certificate

The client certificate.

Client Private Key

The client private key.

Client Private Key Password

The client private key password.

Server Hostname Verification

The option to enable server hostname verification. The option is disabled by default.

MQTT Last Will Configuration Parameters

Field Description

Last Will Topic

The MQTT Last Will topic to publish to.

For more information about MQTT Last Will or Will Message, see MQTT Will Message.

Last Will QoS

The quality of service for the MQTT Last Will. The level of the quality of service can be 0, 1, or 2. The default is 0.

Last Will Retain

The option to retain the MQTT Will Message. The option is disabled by default.

Last Will Message

The payload for the MQTT Will Message.

Will Message Delay Interval

The number of seconds for the MQTT Will Message delay interval.

Will Message Expiry Interval

The number of seconds for the MQTT Will Message expiry interval.

Will Message Content Type

The Content Type of the MQTT Will Message.

Response Topic

The topic name for the MQTT response message.

For more information about MQTT response messages, see MQTT Request and Response.

Correlation Data

The MQTT Correlation Data.

For more information about MQTT Correlation Data, see MQTT Request and Response.

Oracle AQ

You can configure Oracle AQ as a source or a target. The parameters are described in the following tables:

For message headers, see Oracle AQ Message Headers.

Oracle AQ Source Parameters

The following table describes the parameters for configuring Oracle AQ.

Field Description

Datasource URL

The URL of the connection to Oracle AQ. For example: jdbc:oracle:thin:@//localhost:1521/freepdb1.

Username

The username to authenticate with Oracle AQ. Optional. If not supplied, you must upload an Additional Properties File.

Password 

The password to authenticate with Oracle AQ. Optional. If not supplied, you must upload an Additional Properties File.

Additional Properties File

A connection properties file that contains name=value pairs that assign a value to the name of a connection property. For example:

oracle.jdbc.user=<my-user-id>
oracle.jdbc.password=<my-password>

When this file is provided, the Micro-Integration appends the query parameter oracle.jdbc.config.file=file:///file-path to the datasource URL, incorporating the properties from the uploaded file.

For more information, see the Oracle connection properties file documentation.

Destination Type

Select TOPIC or QUEUE.

Destination 

The name of the Oracle AQ topic or queue.

Durable Subscription Name

The name of the durable subscription multiple consumers can bind to. Durable subscriptions accumulate messages even when all consumers are offline, ensuring that no messages are lost.

This value is mandatory when the Destination Type is TOPIC.

Oracle AQ Target Parameters

The following table describes the parameters for configuring Oracle AQ.

Field Description

Datasource URL

The URL of the connection to Oracle AQ. For example: jdbc:oracle:thin:@//localhost:1521/freepdb1.

Username

The username to authenticate with Oracle AQ. Optional. If not supplied, you must upload an Additional Properties File.

Password 

The password to authenticate with Oracle AQ. Optional. If not supplied, you must upload an Additional Properties File.

Additional Properties File

A connection properties file that contains name=value pairs that assign a value to the name of a connection property. For example:

oracle.jdbc.user=<my-user-id>
oracle.jdbc.password=<my-password>

When this file is provided, the Micro-Integration appends the query parameter oracle.jdbc.config.file=file:///file-path to the datasource URL, incorporating the properties from the uploaded file.

For more information, see the Oracle connection properties file documentation.

Destination Type

Select TOPIC or QUEUE.

Destination 

The name of the Oracle AQ topic or queue.

Durable Subscription Name

The name of the durable subscription multiple consumers can bind to. Durable subscriptions accumulate messages even when all consumers are offline, ensuring that no messages are lost.

This value is mandatory when the Destination Type is TOPIC.

Transacted

Specifies that messages are received within a local transaction. When selected, this option indicates that the JMS consumer reads messages within a local transaction and commits the transaction when the batch has been successfully processed.

PostgreSQL CDC

The Micro-Integration for PostgreSQL CDC captures changes (inserts, updates, deletes) from a PostgreSQL database table (using Debezium) and streams them to a topic on an event broker service.

You can configure PostgreSQL CDC only as a source.

For message headers, see PostgreSQL CDC Message Headers.

PostgreSQL CDC Source Parameters

Field Description
Checkpoint Store Configuration
Checkpoint Queue  The name of the Last Value Queue (LVQ) on the PubSub+ event broker to use for checkpointing. The LVQ stores information about the files that have been processed and the files that are currently being processed. The LVQ must exist on the same event broker and VPN as the target destination.
Auto Create Checkpoint Queue Select to automatically create the LVQ if it does not exist.
Debezium PostgreSQL Configuration Properties
Destination The name of the table, including the schema name. Specify the destination using the <schemaName>.<tableName> format.
Database Hostname The hostname of the PostgreSQL database server.
Database Port The port of the PostgreSQL database server.
Database Name The name of the PostgreSQL database.
Slot Name

The name of the PostgreSQL logical decoding slot.

A logical decoding slot is a persistent object that maintains a stream of database changes. The Connector for PostgreSQL CDC consumes the change stream from the specified slot.
Skip Delete Events Select to skip the processing of delete events from the database change stream.
Authentication

The type of authentication to use when connecting to PostgreSQL. Choose one of:

Additional Properties

(Optional) Any additional configuration related to PostgreSQL. Click Add Context if you need to specify additional context properties.

Basic Authentication Parameters

Field Description
Username  The username to use for logging in to PostgreSQL.
Password The password use for authenticating with the PostgreSQL database.

Client Certificate Authentication Parameters

Field Description
Database SSL mode

The SSL mode determines the security level for client-server communications. It controls whether SSL/TLS encryption is used and how rigorously the server's identity is verified. Choose one of:

  • disable to use an unencrypted connection

  • allow to try to use an unencrypted connection first and, failing that, a secure (encrypted) connection

  • prefer to try to use a secure (encrypted) connection first and, failing that, an unencrypted connection

  • require to use a secure (encrypted) connection, and fail if one cannot be established

  • verify-ca like required but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found

  • verify-full like verify-ca but additionally verify that the server certificate matches the host to which the connection is attempted

For more information, see the Protection Provided in Different Modes section of the PostgreSQL documentation.
Client certificate The SSL Certificate for the client.
Client private key The SSL private key for the client.
Private key password The database SSL password to authenticate with the PostgreSQL database.
SSL Root Certificate The database SSL root certificate against which the server is validated.
Username  The username to use for logging in to PostgreSQL.

Qdrant (Beta)

The Qdrant Micro-Integration publishes events from a PubSub+ event broker to a Qdrant vector database. It converts event data into vectors using an embedding model. A vector is a list of numbers representing a concept or semantic meaning of a chunk of text. An embedding model is a machine learning model that performs the data conversion.

You can configure Qdrant only as a target.

Qdrant Target Parameters

The following table describes the parameters for configuring Qdrant as a target.

Field Description
Qdrant Target Connection Details

Select Content Splitter

Select the method for splitting incoming content for vectorization. Valid values are:

  • JSON Document Splitter—Splits JSON data. Additional parameters are required. For more information, see JSON Document Splitter Parameters.

  • Character Document Splitter—Splits text data using a single separator. Additional parameters are required. For more information, see Character Document Splitter Parameters.

  • Structured Text Splitter—Splits structured text using one or more separators. Additional parameters are required. For more information, see Structured Text Splitter Parameters.

  • No Splitter to Use with Pre-Split Unstructured Data—Does not split incoming data.
OpenAI-Compatible Embedding Model Provider

Endpoint URL

The API endpoint URL for the embedding model provider. For example: https://api.openai.com/v1/embeddings

Model ID

The specific version or name of the embedding model to use, following the <access-protocol-provider>/<model-id> format, for example, openai/text-embedding-3-large.

The access protocol provider specifies which service to use to access the model. The model ID specifies the embedding model within that provider's catalog.

The value of <access-protocol-provider> must be openai.

Secret Access Key

The API Secret Access Key for the embedding model provider.

Organization ID

The OpenAI Organization ID.

Chunk Size

The size of text segments into which a document is divided by an embedding model for vector database storage. The default is 1000.

Embedding Model Context Length

The maximum number of tokens to embed at once by the embedding model. The default is 8191.

Number of Embedding Dimensions

The number of dimensions in the resulting output embeddings.
Qdrant Vector Database

Endpoint URL

The API endpoint URL for the Qdrant Vector Database. For example: https://xyz-example.eu-central.aws.cloud.qdrant.io:6333

Secret Access Key

The API Secret Access Key for the Qdrant provider.

Collection Name

The name of the Qdrant collection.

A collection in Qdrant is a container that stores vectors where all vectors must have the same dimensions and have used the same model for their creation. Collections allow you to efficiently search for and retrieve vectors that are similar to a vector you specify in a query. For more information, see Collections in the Qdrant documentation.

If the specified collection does not exist, the Micro-Integration creates a new empty basic collection with the specified name.

JSON Document Splitter Parameters

Field Description

Max Chunk Size

The maximum number of tokens per text chunk during document splitting. Controls the size of segments created during text ingestion for vector storage. The default is 2000.

Larger chunks preserve more context but may reduce retrieval precision. Smaller chunks improve granular search but may lose contextual relationships.

Character Document Splitter Parameters

Field Description

Chunk Size

The maximum number of characters allowed in each text segment when splitting a document. The default is 4000.

Chunk Overlap

The number of characters that overlap between consecutive chunks. Overlap helps to maintain context between split segments. The default is 200.

Separator

The character sequence used to split text into chunks, allowing control over split points at natural boundaries like paragraph breaks. The default is "\n\n".

Structured Text Splitter Parameters

Field Description

Chunk Size

The maximum number of characters allowed in each text segment when splitting a document. The default is 4000.

Chunk Overlap

The number of characters that overlap between consecutive chunks. Overlap helps to maintain context between split segments. The default is 200.

Separators

The character sequence used to split text into chunks based on text structure allowing control over split points at natural boundaries like paragraph breaks. This can be a comma-separated list of separators like: "separator1","separator2". Each separator is applied individually. The default is "\n\n", "\n", " ", "".

Salesforce

You can configure Salesforce as a source or a target. The parameters are described in the following tables:

For message headers, see Salesforce Message Headers.

If you are deploying the Connector for Salesforce in a Customer-Controlled Region that routes outbound connections through a proxy, no additional configuration is required. The Micro-Integration receives the proxy settings automatically from the environment.

Salesforce Source Parameters

The following table describes the parameters for configuring Salesforce as a source.

Field Description

Pub/Sub API Endpoint 

The endpoint used by the Salesforce Pub/Sub API. For example, the Salesforce Global Endpoint is api.pubsub.salesforce.com. For more information, see Pub/Sub API Endpoints in the Salesforce documentation.

Pub/Sub API Port

The port used by the Salesforce Pub/Sub API. Allowed values are 7443 and 443.

Login URL

The Salesforce login URL. For example: https://<personal_domain>.develop.my.salesforce.com/

Authentication Scheme

The authentication method to use when connecting to Salesforce. Choose one of:

Last Value Queue

The name of the Last Value Queue (LVQ) on the PubSub+ event broker to use for checkpointing. The Salesforce Micro-Integration stores the last successful Salesforce Replay ID in the LVQ. The LVQ must exist on the same event broker and VPN as the target destination.

Destination

The source of events from Salesforce. For example, Change Data Capture events (/data/ChangeEvents and /data/<OBJECT_NAME>ChangeEvents) or Custom Events (/event/<CUSTOM_EVENT_NAME>__e).

Salesforce Target Parameters

The following table describes the parameters for configuring Salesforce as a target.

Field Description

Pub/Sub API Endpoint 

The endpoint used by the Salesforce Pub/Sub API. For example, the Salesforce Global Endpoint is api.pubsub.salesforce.com. For more information, see Pub/Sub API Endpoints in the Salesforce documentation.

Pub/Sub API Port

The port used by the Salesforce Pub/Sub API. Allowed values are 7443 and 443.

Login URL

The Salesforce login URL. For example: https://<personal_domain>.develop.my.salesforce.com/).

Authentication Flow

The authentication method to use when connecting to Salesforce. Choose one of:

Destination

The source of events from Salesforce. For example, Change Data Capture events (/data/ChangeEvents and /data/<OBJECT_NAME>ChangeEvents) or Custom Events (/event/<CUSTOM_EVENT_NAME>__e).

Salesforce Legacy Username and Password Parameters

Field Description

Username

The Salesforce username to authenticate with.

Password

The password that corresponds to the Salesforce username.

Security Token 

The security token generated by Salesforce. If you don’t have a security token, click your avatar in Salesforce, then click Settings > Reset My Security Token. A new token is emailed to you.

Salesforce OAuth 2.0 Client Credentials Parameters

Field Description

Client ID

The OAuth 2.0 Client ID to authenticate with. The Client ID might appear as "Consumer Key" in Salesforce.

For more information, see Configure a Client Credentials Flow in the Salesforce documentation.

Client Secret 

The OAuth 2.0 Client Secret. The Client Secret might appear as "Consumer Secret" in the OAuth Settings in Salesforce.

For more information, see Configure a Client Credentials Flow in the Salesforce documentation.

Salesforce OAuth 2.0 JWT Bearer Flow Parameters

You must set up a connected app to use JWT. For more information, see Configure a JWT Bearer Flow in the Salesforce documentation.

In addition to following the Salesforce documentation instructions, you must ensure that Plugin Policies are set to Admin approved users are pre-authorized and the user profile/permission set is authorized for the connected app.

You can build and sign a JWT using the template on jwt.io. Change the default text to your client ID and username e-mail, then add your private key to sign the token.

To test your JWT before using it in the Micro-Integration, issue the following POST request:

POST <YOUR_LOGIN_URL>/services/oauth2/token HTTP/1.1
Content-Type: application/x-www-form-urlencoded
							
grant_type= urn:ietf:params:oauth:grant-type:jwt-bearer&
assertion=eyJpc3MiOiAiM01WRz...[omitted for brevity]...ZT
Field Description

Issuer

The OAuth client_id or the connected app for which you registered the certificate. Corresponds to the iss JWT claim.
Audience

The authorization server that is the intended audience. Corresponds to the aud JWT claim. Allowed values are:

  • https://login.salesforce.com (Default value)

  • https://test.salesforce.com

  • https://site.force.com/customers (if this Micro-Integration is authenticating with a Salesforce Experience Cloud site)
Subject

The Salesforce user name to use for authentication. Corresponds to the sub JWT claim.
Private Key

The private key file used to sign the JWT. Both unencrypted and encrypted (PKCS #8 and OpenSSL/PEM) private keys are supported.
Private Key Password

The password for the private key if it is encrypted.

SFTP

You can configure SFTP as a source or a target. The parameters are described in the following tables:

For message headers, see SFTP Message Headers.

SFTP Source Parameters

The following table describes the parameters for configuring SFTP as a source.

Field Description
Checkpoint Store Configuration

Checkpoint Queue

The name of the Last Value Queue (LVQ) (spool size 0) to be used for checkpointing. The queue must exist on the same event broker and Message VPN as the target queue.

The SFTP Micro-Integration stores the current progress of file processing in a checkpoint store backed by the specified LVQ.

If the LVQ is deleted (administratively) or a message from the LVQ is deleted or consumed by another consumer, the SFTPMicro-Integration will not be able to resume from the last checkpoint. In addition, the LVQ should not be shared by multiple SFTPMicro-Integrations.

Auto Create Checkpoint Queue

Select this option to automatically create the LVQ if it does not exist.
SFTP Server Configuration

SFTP Server URI

The source SFTP server URI and start directory path.

Required format: sftp://<host>:<port>/<startDirectoryName>/

For example: sftp://localhost:22/orders-data/

Username

The username to use to log in to the SFTP server.

Password

The password to use to log in to the SFTP server, if you are using password authentication. If you don't set a password, you must upload a private key file.

Private Key File

The private key file to use for private key verification.

Private Key Passphrase

The private key file passphrase to use for private key verification.

Known Hosts File

The Known Hosts file for the SFTP server to use for host key verification.

File Format

The format of the files coming from the SFTP server:

Additional Properties

(Optional) Any additional configuration related to SFTP. Click Add Context if you need to specify additional context properties. For more information, see Additional Source Parameters for SFTP

Delimited File Configuration Properties

Field Description

Event Delimiter

The events in the files are separated by this character. For example: \n (a newline character).

Field Delimiter

The fields within the events are separated by this character. For example: , (a comma).

JSON File Configuration Properties

Field Description

JSON Path Filter Expression

The JSON path expression to extract, split, or filter the data from the JSON file.

The default value of $ means the entire JSON file content will be processed as a single event. For a JSON file larger than 30 MB, this will cause an error because the maximum size of a Solace message is 30 MB. We recommend splitting the JSON file content into multiple events by configuring the JSON path expression.

XML File Configuration Properties

Field Description

XPath Filter Expression

The XPath expression to extract, split, or filter the data from the XML file.

The default value of / means the entire XML file content will be processed as a single event. For XML file larger than 30MB, it would result in exception as max Solace message size is 30MB. We recommend splitting the XML file content into multiple events by configuring the XPath expression.

For example, for an employees.xml file with following content, the XPath expression to extract employee nodes would be //employee:

<employees>
    <employee>
        <name>John</name>
        <age>30</age>
    </employee>
    <employee>
        <name>Smith</name>
        <age>40</age>
    </employee>
</employees>

Additional Source Parameters for SFTP

The following table lists the additional source-specific parameters for SFTP. For more information, see the Apache Camel SFTP Component documentation.

Configuration Option Valid Values Description

passiveMode

(true | false)

Indicates whether to use passive mode connections. The default (false) is active mode connections.

strictHostKeyChecking

(yes | no)

Indicates whether to use strict host key checking. The default (no) is not to use strict host key checking.

ciphers

A comma-separated list of ciphers to use, listed in order of preference. Possible cipher names are defined by JCraft Java Secure Channel (JSch). Some examples include: aes128-ctr, aes128-cbc, 3des-ctr, 3des-cbc, blowfish-cbc, aes192-cbc, and aes256-cbc.

keyExchangeProtocols

A comma-separated list of key exchange protocols to use, listed in order of preference. Possible cipher names are defined by JCraft JSch. Some examples include: diffie-hellman-group-exchange-sha1, diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha256, ecdh-sha2-nistp256, ecdh-sha2-nistp384, and ecdh-sha2-nistp521.

publicKeyAcceptedAlgorithms

A comma-separated list of accepted public key algorithms. Some examples include: ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, and ecdsa-sha2-nistp521.

serverHostKeys

A comma-separated list of algorithms supported for the server host key. Some examples include: ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, and ecdsa-sha2-nistp521.

connectTimeout

> 0

The time in milliseconds to wait for a connection to be established.

soTimeout

> 0

The socket timeout, in milliseconds.

maximumReconnectAttempts

>= 0

The maximum number of times to retry to establish an initial connection to the remote FTP server. Use 0 to disable this behavior.

reconnectDelay

> 0

The delay in milliseconds to wait before retrying the connection.

serverAliveCountMax

> 0

The maximum number of keep-alive messages to send without receiving any messages back from the server. If this threshold is reached while keep-alive messages are being sent, the connection is closed.

serverAliveInterval

>= 0

The interval (in milliseconds) between keep-alive messages. If zero is specified, no keep-alive messages are sent.

binary

(true | false)

The file transfer mode, either binary or ASCII. The default (false) is ASCII.

charset

A valid charset value.

The character encoding of the file contents, for example utf-8.

noop

(true | false)

If true, the file is not deleted or moved in any way.

delete

(true | false)

If true, the file is deleted after it is processed successfully.

move

Any

An expression (such as Simple Language) used to dynamically set the filename when moving it after processing.

To move files into a .done subdirectory: .done

To move files into a .processed subdirectory and rename them: .processed/$#{file:name}.done

To move files into a .processed subdirectory and rename file with current timestamp: .processed/$#{date:now:yyyyMMdd}/$#{file:name.noext}-$#{date:now:yyyyMMddHHmmss}.done

moveFailed

Any

Expression (such as Simple Language) used to dynamically set the filename when moving it after processing.

To move failed files into an .error subdirectory: .error

To move failed files into an .error subdirectory and rename file: .error/$#{file:name}.error

To move failed files into an .error subdirectory and rename them with the current timestamp: .error/$#{date:now:yyyyMMdd}/$#{file:name.noext}-$#{date:now:yyyyMMddHHmmss}.error

sortBy

A File Language expression.

Built-in sort using File Language. Supports nested sorts: for example, you can sort by filename and then by modified date.

Sort by filename: $#{file:name}

Sort by file modified time: $#{file:modified}

recursive

(true | false)

If the specified location is a directory, the connector looks for files in all the subdirectories as well.

maxDepth

> 0

The maximum depth to traverse when recursively processing a directory.

minDepth

> 0

The minimum depth to start processing when recursively processing a directory. Using minDepth=1 means the base directory. Using minDepth=2 means the first subdirectory.

antExclude

Any

Ant-style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence. Multiple exclusions may be specified in comma-delimited format.

antInclude

Any

Ant-style filter inclusion. Multiple inclusions may be specified in comma-delimited format.

antFilterCaseSensitive

(true | false)

Indicates whether the ant* filters are case-sensitive. The default (true) is case-sensitive.

exclude

A valid regular expression

Excludes files where the filename matches the regex pattern (matching is case in-sensitive).

include

A valid regular expression

Includes files where the filename matches the regex pattern (matching is case-insensitive).

includeExt

A file extension

Is used to include files matching file extension name (case-insensitive).

For example to include .csv files, use includeExt=csv. Multiple extensions can be separated by comma; for example to include .csv and .dat files, use includeExt=csv,dat.

excludeExt

A file extension

Is used to exclude files matching file extension name (case-insensitive).

For example to exclude .bak files, use excludeExt=bak. Multiple extensions can be separated by comma; for example to exclude .bak and .dat files, use excludeExt=bak,dat.

filterFile, filterDirectory

Any

The source SFTP server URI and the directory path.

delay

Any

The amount of time that must elapse before the next poll.

initialDelay

Any

The amount of time that must elapse before the first poll starts.

timeUnit

Enum values: NANOSECONDS, MICROSECONDS, MILLISECONDS, SECONDS, MINUTES, HOURS, DAYS

The time unit for the initialDelay and delay options.

stopOnException

(true | false)

Indicates whether to stop processing the current file if an exception is encountered.

When this option is set to false (the default), the connector logs an exception and continues processing the next event in the current file.

When this option is set to true, the connector stops processing the current file and continues to the next file if any. If moveFailed is set, the file is moved to the error directory.

serverMessageLoggingLevel

Enum values: TRACE, DEBUG, INFO, WARN, ERROR, OFF

Logging levels control how much information is saved to the log file. During troubleshooting, it may be useful to raise the logging level to increase the amount of information the logs receive from the FTP server.

maxFileSize

>= 0

The maximum size, in bytes, of the files to be consumed. This option helps to prevent Out Of Memory (OOM) errors on systems with a small amount of available memory.

SFTP Target Parameters

The following table describes the parameters for configuring SFTP as a target.

Configuration Option Description
Checkpoint Store Configuration

Checkpoint Queue

The name of the Last Value Queue (LVQ) (spool size 0) to be used for checkpointing. The queue must exist on the same event broker and Message VPN as the target queue.

The Micro-Integration for SFTP stores the current progress of file processing in a checkpoint store backed by the specified LVQ.

If the LVQ is deleted (administratively) or a message from the LVQ is deleted or consumed by another consumer, the Micro-Integration for SFTP will not be able to resume from the last checkpoint. In addition, the LVQ should not be shared by multiple instances of the Micro-Integration for SFTP.

Auto Create Checkpoint Queue

Select this option to automatically create the LVQ if it does not exist.
SFTP Server Configuration

SFTP Server URI

The target SFTP server URI and start directory path.

Required format: sftp://<host>:<port>/<startDirectoryName>/

For example: sftp://localhost:22/orders-data/

Username

The username to use to log in to the SFTP server.

Password

The password to use to log in to the SFTP server, if you are using password authentication. If you don't set a password, you must upload a private key file.

Private Key File

The private key file to use for private key verification.

Private Key Passphrase

The private key file passphrase to use for private key verification.

Known Hosts File

The Known Hosts file for the SFTP server to use for host key verification.

Write Mode

The action to take if a file with the same name already exists:

  • Append—Events are added to the existing file.

  • Override—The existing file is replaced.

  • Fail—An error is generated, indicating that there is already an existing file.

Maximum File Size

The maximum size of the file in bytes. If the value is 0, then there is no limit.

Maximum Number of Events

The maximum number of events to be written to a file, after which a new file is created. If the value is 0, then there is no limit.

Additional Properties

(Optional) Any additional configuration related to SFTP. Click Add Context if you need to specify additional context properties. For more information, see Additional Target Parameters for SFTP.

Additional Target Parameters for SFTP

The following table lists the additional target-specific parameters for SFTP. For more information, see the Apache Camel SFTP Component documentation.

Configuration Option Valid Values Description

passiveMode

(true | false)

Indicates whether to use passive mode connections. The default (false) is active mode connections.

strictHostKeyChecking

(yes | no)

Indicates whether to use strict host key checking. The default (no) is not to use strict host key checking.

ciphers

A comma-separated list of ciphers to use, listed in order of preference. Possible cipher names are defined by JCraft Java Secure Channel (JSch). Some examples include aes128-ctr, aes128-cbc, 3des-ctr, 3des-cbc, blowfish-cbc, aes192-cbc, and aes256-cbc.

keyExchangeProtocols

A comma-separated list of key exchange protocols to use, listed in order of preference. Possible cipher names are defined by JCraft JSch. Some examples include: diffie-hellman-group-exchange-sha1, diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha256, ecdh-sha2-nistp256, ecdh-sha2-nistp384, and ecdh-sha2-nistp521.

publicKeyAcceptedAlgorithms

A comma-separated list of accepted public key algorithms. Some examples include ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, and ecdsa-sha2-nistp521.

serverHostKeys

A comma-separated list of algorithms supported for the server host key. Some examples include: ssh-dss, ssh-rsa, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, and ecdsa-sha2-nistp521.

connectTimeout

> 0

The time in milliseconds to wait for a connection to be established.

soTimeout

> 0

The socket timeout, in milliseconds.

maximumReconnectAttempts

>= 0

The maximum number of times to retry to establish an initial connection to the remote FTP server. Use 0 to disable this behavior.

reconnectDelay

> 0

The delay in milliseconds to wait before retrying the connection.

serverAliveCountMax

> 0

The maximum number of keep-alive messages to send without receiving any messages back from the server. If this threshold is reached while keep-alive messages are being sent, the connection is closed.

serverAliveInterval

>= 0

The interval (in milliseconds) between keep-alive messages. If zero is specified, no keep-alive messages are sent.

binary

(true | false)

The file transfer mode, either binary or ASCII. The default (false) is ASCII.

charset

A valid charset value.

The character encoding of the file contents, for example utf-8.

fileExist

(Override | Append | Fail)

The action to take if a file with the same name already exists:

  • Override: replaces the existing file.

  • Append: adds content to the existing file.

  • Fail: throws an exception indicating that there is already an existing file.

fileName

Any valid filename.

The filename to write to. It can include the leading file path. For example:

 sub1/sub2/employee.csv

If the filename is not set, a randomly generated UUID is used, in which case each event is written to a unique file.

The fileName can be specified using a Camel Simple Language expression, for example:

fileName: "backup/$#{date:now:yyyyMMdd}/test.txt"

chmod

Unix chmod value, for example, 740

The permissions (mode) to set on the file.

chmodDirectory

Unix chmod value, for example, 740

The permissions (mode) to set on the directory.

preventDuplicates

(true | false)

Indicates whether to prevent duplicate events from being written to the target file. Duplicate events are identified based on the value of the uniqueIdentifierHeader option. The default (false) is not to prevent duplicates.

preventDuplicatesOnlyForRedeliveredEvents

(true | false)

Indicates whether to check for duplicates only on redelivery. The default (true) is to check for duplicates for redelivered events only. If false, duplicate checking is performed for all events.

Use this option only when preventDuplicates is set to true.

uniqueIdentifierHeader

Any valid header name

The user property or header name to be used for uniquely identifying events.

Use this option only when preventDuplicates is set to true.

cacheSize

> 0

The size of the in-memory cache used to store event unique identifiers.

Use this option only when preventDuplicates is set to true.

maxEventsPerFile

>= 0

The maximum number of events to be written to a file. If the value is 0, then there is no limit.

maxFileSize

>= 0

The maximum size of the file in bytes. If the value is 0, then there is no limit.

prependToEvent

Any valid string

The string to be prepended to the event.

appendToEvent

Any valid string

The string to be appended to the event.

prependToFile

Any valid string

The string to be prepended to the file (for example, a header line). This is done only once when the file is created.

prependToFirstEvent

Any valid string

The string to be prepended to the first event.

serverMessageLoggingLevel

Enum values: TRACE, DEBUG, INFO, WARN, ERROR, OFF

Logging levels control how much information is saved to the log file. During troubleshooting, it may be useful to raise the logging level to increase the amount of information the logs receive from the FTP server.

Snowflake

You can only configure Snowflake as a target.

Snowflake Target Parameters

The following table describes the parameters for configuring Snowflake as a target.

Field Description

Snowflake URL

The URL of the Snowflake instance. For example, the format of the URL can be <LOCATOR>.<REGION>.snowflakecomputing.com:443. For more information about the URL and account information, see the Snowflake documentation.

Snowflake Username

The username to log in to Snowflake.

Role

The type of role in Snowflake. For example, ACCOUNTADMIN, SECURITYADMIN, USERADMIN, SYSADMIN, or PUBLIC. For more information about the Snowflake roles, see the Snowflake documentation.

Private Key Path

The path to the private key file. For more information about the private key path, see the Snowflake documentation.

Private Key Password

The password for the private key, if applicable. For more information about the private key password, see the Snowflake documentation.

Solace Transform Processor

You can only configure Solace Transform Processor as a target. The Micro-Integration provides a flexible and efficient way to transform data on queues and topic endpoints, or transform and move data between PubSub+ event brokers.

Solace Transform Processor Target Parameters

The following table describes the parameters for configuring Solace Transform Processor as a target, which is another PubSub+ event broker.

Field Description
Destination Type

The destination type to send messages to. Select TOPIC or QUEUE for the topic destination or the name of the queue, respectively.

Create the required queue on your event broker service if you haven't done so already. For more information, see Creating Event Broker Services).

Topic Name The topic endpoint to publish to. This field is available only when you select TOPIC as the Destination Type.
Queue Name

The name of the queue to publish to. This field is available only when you select QUEUE as the Destination Type.
Transacted

This option specifies whether to use a transacted session (local transaction) to publish a batch of messages to the target destination. When disabled (default), the producer sequentially publishes messages within a batch. If a publishing error occurs, the entire batch is returned to the source for reprocessing. Since the entire batch is reprocessed, messages in the batch that were already published are re-published resulting in potential duplicate messages.

When enabled, up to 255 messages are published in a single transaction (local transaction). Using a local transaction guarantees that either all messages in a batch are successfully published or none of the messages in the batch are published. For more information, see Using Local Transactions.

If you use transacted sessions, it reduces the possibility of duplicate messages published to your target but increases resource usage and overhead on the event broker.