EmbeddedContent

The EmbeddedContent processor performs an enrichment task on input documents by using an embedded Content component index (which is available as a controller service).

The processor defines one or more enrichment tasks.

Each task is a constructed Query action to send to the embedded content index, and an XSLT transformation to perform on the response. The processor sends the document text in the Text parameter of the Query, and adds any other parameters that you include in the configuration. The processor then runs the transformation on the response and injects the result into the original document as metadata.

You can use this processor with an appropriate index to perform tasks such as AgentBoolean categorization or entity matching. For more information about AgentBoolean categorization refer to the Knowledge Discovery Administration Guide and the Content Component Help. For more information about entity matching, refer to the PII Package Technical Note.

Properties

Name Default Value Description
IDOL License Service  

An IdolLicenseServiceImpl that provides a way to communicate with a Knowledge Discovery License Server.

Content Service   The ContentServiceImpl to use to query the embedded index.
TaskN  

The name of an enrichment task. N is a number, starting from 0. You set the parameter name to a task configuration section.

You can also specify a single Task property with a comma-separated list of task names.

[mytask]transformXSLT  

The path to an XSL file to apply to the query response for this task.

Mytask is the name of the task that this XSLT transform applies to. You must apply transformXSLT to a particular task. For example, if you set Task0 to People, specify the associated transform XSLT by setting a property named [People]transformXSLT.

[mytask]IDOL_query_parameter_name  

A Query action parameter and value to use in the query that the processor sends. For more information about the parameters that you can use, refer to the Content Component Help.

Mytask is the name of the task that this XSLT transform applies to. You must apply the query parameters to a particular task. For example, if you set Task0 to People, specify the combine parameter by setting a property named [People]combine:simple.

Relationships

Name Description
success Successfully processed FlowFiles are routed to this relationship.
failure FlowFiles that were not successfully enriched.