NiFi Ingest 26.1
NiFi Ingest

# PutAMQP

Accepts Knowledge Discovery documents and generates messages which are then sent to one or more AMQP message brokers.

NOTE: This processor supports AMQP v1.0 only.

## Properties

Name | Default Value | Description
--- | --- | ---
IDOL License Service |  | An IdolLicenseServiceImpl that provides a way to communicate with a Knowledge Discovery License Server.
Document Registry Service |  | A DocumentRegistryServiceImpl controller service that manages and updates a document registry database. This ensures that documents are indexed in the correct order.
Indexer Batch Size | 100 | The maximum number of FlowFiles to accumulate before indexing documents. Indexing documents in larger batches can be more efficient; indexing smaller batches more frequently means that an individual document might spend less time in the queue. Documents might be indexed in incomplete batches if the Indexing Interval Duration is reached first.
Indexing Interval Duration | 5 min | The maximum amount of time to wait between indexing batches of documents. Documents might be indexed more frequently than this if the Indexer Batch Size is reached first. Waiting longer and indexing documents in larger batches can be more efficient; indexing smaller batches more frequently means that an individual document might spend less time in the queue.
Brokers |  | A comma-separated list of AMQP brokers in the format `host:port`.
Truststore Filename |  | The location of a certificate to use to validate the certificate provided by the broker. The certificate can be in PEM format.
Username |  | The user name to use to authenticate with the brokers.
Password |  | The password to use to authenticate with the brokers.
Queue |  | The name of the message queue to write to.
Key Field Path |  | The path of the field in the document metadata to use as the message key. You can select a sub-field by using slash-separated field names such as `FieldName/SubFieldName`.
Value Field Path |  | The path of the field in the document metadata to use as the message body. You can select a sub-field by using slash-separated field names such as `FieldName/SubFieldName`.
Metadata Mapping Mode | Full | Specifies how to convert document metadata into message headers: Full - Document metadata is converted into message headers. The header names are full XPath-like indexed field paths, for example `FIELD1[1]/@attr`. Simple - Document metadata is converted into message headers. The header names are generated without the indexes, for example `FIELD1_attr`. None - Document metadata is not converted by default. Use "Header Field Names" and "Header Field Paths" instead.
Header Field Names Header Field Paths |  | You can use these properties to map document fields to message headers. If you want to set these properties, OpenText recommends using the guided setup wizard (right-click the processor and click Advanced, and follow the instructions on the GUIDED SETUP tab). Knowledge Discovery document metadata field paths are slash-separated and can reference attributes using the "@" character. For example, to reference an attribute called "name" on a field named "MyField", enter `MyField/@name`. The header name can contain placeholders, `$1`, `$2`, ... `$N` that correspond to the Nth asterisk wildcard (`*`) in the corresponding document metadata field path. An asterisk wildcard (`*`) that is used in a path can match only a whole field name or attribute name. Example header names and field paths
Header name | Field path | Description
--- | --- | ---
`myfield` | `myfield` | The value of the field "myfield" is written to the "myfield" header.
`$1` | `*` | All fields at the root of the document are added as headers with matching names.
`myfield_$1_$2` | `myfield/*/@*` | All of the attributes of subfields of "myfield" are added as headers. For example, if "myfield" has a sub-field named "subfield" with an attribute "color", then the processor creates a header named "myfield_subfield_color".

## Relationships

Name | Description
--- | ---
success | FlowFiles that were indexed successfully.
failure | FlowFiles that failed to be indexed.

Copyright 2018-2025 Open Text
Version 26.1 | Last updated January 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery NiFi Ingest 26.1

Topic Title: PutAMQP