Description:
Provides a service to lookup an existing JMS ConnectionFactory using the Java Naming and Directory Interface (JNDI).
Tags:
jms, jndi, messaging, integration, queue, topic, publish, subscribe
Properties:
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the Expression Language Guide and whether a property is considered “sensitive”, meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the nifi.properties file has an entry for the property nifi.sensitive.props.key.
Name |
Default Value |
Allowable Values |
Description |
Initial Naming Factory Class |
The fully qualified class name of the Java Initial Naming Factory (java.naming.factory.initial). Supports Expression Language: true (will be evaluated using variable registry only) |
||
Naming Provider URL |
The URL of the JNDI Naming Provider to use Supports Expression Language: true (will be evaluated using variable registry only) |
||
Connection Factory Name |
The name of the JNDI Object to lookup for the Connection Factory Supports Expression Language: true (will be evaluated using variable registry only) |
||
Naming Factory Libraries |
Specifies .jar files or directories to add to the ClassPath in order to find the Initial Naming Factory Class Supports Expression Language: true (will be evaluated using variable registry only) |
||
JNDI Principal |
The Principal to use when authenticating with JNDI Supports Expression Language: true (will be evaluated using variable registry only) |
||
Credentials |
The Credentials to use when authenticating with JNDI Sensitive Property: true |
Dynamic Properties:
Dynamic Properties allow the user to specify both the name and value of a property.
Name |
Value |
Description |
The name of a JNDI Initial Context environment variable. | The value of the JNDI Initial Context Environment variable. |
In order to perform a JNDI Lookup, an Initial Context must be established. When this is done, an Environment can be established for the context. Any dynamic/user-defined property that is added to this Controller Service will be added as an Environment configuration/variable to this Context. Supports Expression Language: true (will be evaluated using variable registry only) |
State management:
This component does not store state.
Restricted:
This component is not restricted.
System Resource Considerations:
None specified.