camel-jt400-kafka-connector sink configuration

Connector Description: Exchanges messages with an IBM i system using data queues, message queues, or program call. IBM i is the replacement for AS/400 and iSeries servers.

When using camel-jt400-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:

<dependency>
  <groupId>org.apache.camel.kafkaconnector</groupId>
  <artifactId>camel-jt400-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

To use this sink connector in Kafka connect you’ll need to set the following connector.class

connector.class=org.apache.camel.kafkaconnector.jt400.CamelJt400SinkConnector

The camel-jt400 sink connector supports 18 options, which are listed below.

Name Description Default Priority

camel.sink.path.userID

Required Returns the ID of the IBM i user.

HIGH

camel.sink.path.password

Required Returns the password of the IBM i user.

HIGH

camel.sink.path.systemName

Required Returns the name of the IBM i system.

HIGH

camel.sink.path.objectPath

Required Returns the fully qualified integrated file system path name of the target object of this endpoint.

HIGH

camel.sink.path.type

Required Whether to work with data queues or remote program call One of: [DTAQ] [PGM] [SRVPGM] [MSGQ].

Enum values:

  • DTAQ

  • PGM

  • SRVPGM

  • MSGQ

HIGH

camel.sink.endpoint.ccsid

Sets the CCSID to use for the connection with the IBM i system.

MEDIUM

camel.sink.endpoint.format

Sets the data format for sending messages. One of: [text] [binary].

Enum values:

  • text

  • binary

"text"

MEDIUM

camel.sink.endpoint.guiAvailable

Sets whether IBM i prompting is enabled in the environment running Camel.

false

MEDIUM

camel.sink.endpoint.keyed

Whether to use keyed or non-keyed data queues.

false

MEDIUM

camel.sink.endpoint.searchKey

Search key for keyed data queues.

MEDIUM

camel.sink.endpoint.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

MEDIUM

camel.sink.endpoint.outputFieldsIdxArray

Specifies which fields (program parameters) are output parameters.

MEDIUM

camel.sink.endpoint.outputFieldsLengthArray

Specifies the fields (program parameters) length as in the IBM i program definition.

MEDIUM

camel.sink.endpoint.procedureName

Procedure name from a service program to call.

MEDIUM

camel.sink.endpoint.secured

Whether connections to IBM i are secured with SSL.

false

MEDIUM

camel.component.jt400.lazyStartProducer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

MEDIUM

camel.component.jt400.autowiredEnabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

MEDIUM

camel.component.jt400.connectionPool

Default connection pool used by the component. Note that this pool is lazily initialized. This is because in a scenario where the user always provides a pool, it would be wasteful for Camel to initialize and keep an idle pool.

MEDIUM

The camel-jt400 sink connector has no converters out of the box.

The camel-jt400 sink connector has no transforms out of the box.

The camel-jt400 sink connector has no aggregation strategies out of the box.

Back to top