Skip to main content
Skip table of contents

t_ChannelConnections_FileConnection

FileConnection

A File based environment specific connection.

Properties

age : nonNegativeLong

The minimum age (in ms) of an incoming message file for it to be detected by the channel.

Valid values based on“long”.
0 (minInclusive)
channel : string

Connection channel.

condition : string

The property to which the directive is applied.

The property specified here is typically set in the .environment file. It must be prefixed with "-Dnexj" if specified on the JVM command line.
Example


condition="reporting.enabled" ... reporting.enabled="true" or "-Dnexj.reporting.enabled=true"

description : string

Channel connection description.

directive : directive

A conditional directive determining the operation to apply to the property specified in "condition".

If the operation is set to "if" or "ifnot", the property can be null. "ifdef" means "if defined". "ifndef" means "if not defined". If the operation is set to either, the property must not be null.
Example


"if", "ifnot", "ifdef", "ifndef"

Valid values based on“string”.
if
ifnot
ifdef
ifndef
enabled : boolean

The default state of enablement. (default="true")

incomingDirectory : string

The full path to the directory to scan for incoming message files.

When clustered, should be a shared directory.
interval : nonNegativeLong

The input scanning interval (in ms) between successive scans of the incoming directory.

Valid values based on“long”.
0 (minInclusive)
journalDirectory : string

The full path to the directory for the transactional journals for this channel.

levels : nonNegativeInt

The number of subdirectory levels to which the incoming directory should be scanned. Zero to scan only the incoming directory.

Valid values based on“int”.
0 (minInclusive)
maxReceivers : nonNegativeInt

Maximum file receiver threads per server. Overrides the channel setting.

Valid values based on“int”.
0 (minInclusive)
maxSenders : nonNegativeInt

Maximum file sender connections per server. Overrides the channel setting.

Valid values based on“int”.
0 (minInclusive)
merged : boolean

outgoingDirectory : string

The full path to the directory in which to place outgoing message files.

When clustered, should be a shared directory.
outgoingName : string

The template to use for automatically generating outgoing message file names. (Timestamp: ${ts}, Sequence number: ${seq}, GUID: ${guid})

${ts} - Timestamp in milliseconds ${seq} - Sequence number ${guid} - GUID
pattern : string

The like-pattern used to select incoming message files for processing.

Example


*.zip

processedDirectory : string

The full path to the directory for processed incoming messages.

Blank to delete message when processed. When clustered, should be a shared directory.
processedName : string

The template to use for generating a new name for incoming files after they have been processed. (Timestamp: ${ts}, Sequence number: ${seq}, Original path: ${orig}, GUID: ${guid})

${ts} - Timestamp in milliseconds ${seq} - Sequence number ${guid} - GUID ${orig} - The original file path, relative to the incoming directory ${origName} - The original file name
temporaryDirectory : string

The full path to the temporary directory used for preparing outgoing messages.

For best reliability and efficiency, should be on the same filesystem as "outgoingDirectory". Defaults to a directory called "tmp" inside "outgoing". When clustered, should be a shared directory.
transactionTimeout : nonNegativeInt

The timeout (in seconds) for transactions started on the component.

Applies only to incoming transactional channels. Set to 0 to use server default transaction timeout. Overrides the timeout setting on the Channel.
Valid values based on“int”.
0 (minInclusive)
warningTimeout : nonNegativeLong

Timeout in milliseconds before a warning is generated, 0 for infinite timeout.

Valid values based on“long”.
0 (minInclusive)

Parents

Parent topic: t_Connections_ChannelConnections

Parent topic: t_Environment_ChannelConnections

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.