Type to start searching...
A File Integration Channel.
category : string
The category of the channel.
combine
Resolution algorithm for multiple bound services processing the same message. (Default none - meaning multiple services with the same message is not supported)
Valid values based on“string”. | |
---|---|
none |
Multiple services declaring the same message in their associated Interface Request messages are not supported. (Default) |
first |
Only the first one among the bound services with a matching message in their Interface Request messages is invoked. |
all |
All the services with a matching message in their Interface Request messages are invoked. When multiple services are bound to a channel and a message is forwarded to more than one of those services, the initial "this" variable in those services refers to the same object. This should be taken into account if the original message object can be updated in any of the services – you might want to modify a copy of the message instead. |
defaultUser : string
User account for processing the file messages.
description : string
Channel description.
encoding : string
The Java charset to use for encoding/decoding character data from the file. Leave unspecified for binary mode.
These are the charsets available on every implementation of the Java platform:
US-ASCII: Seven-bit ASCII, a.k.a. ISO646-US, a.k.a. the Basic Latin block of the Unicode character set ISO-8859-1: ISO Latin Alphabet No. 1, a.k.a. ISO-LATIN-1 UTF-8: Eight-bit UCS Transformation Format UTF-16BE: Sixteen-bit UCS Transformation Format, big-endian byte order (when decoding, ignore BOM; when encoding, do not write BOM) UTF-16LE: Sixteen-bit UCS Transformation Format, little-endian byte order (when decoding, ignore BOM; when encoding, do not write BOM) UTF-16: Sixteen-bit UCS Transformation Format, byte order identified by an optional byte-order mark. (when decoding, interpret BOM, defaulting to big-ending if no BOM; when encoding, use big-endian and write big-endian BOM)
Charset names are not case-sensitive.
UTF-8 files may begin with a BOM (byte-order mark). When the channel is configured to use UTF-8 encoding, it will automatically ignore a leading BOM for input. On UTF-8 output, the channel will never generate such a BOM.
idle : boolean
True to disable the channel if it is not used by an enabled channel.
maxReceivers : nonNegativeInt
Maximum file receiver threads per server.
Valid values based on“int”. | |
---|---|
0 (minInclusive) |
maxSenders : nonNegativeInt
Maximum file sender connections per server.
Valid values based on“int”. | |
---|---|
0 (minInclusive) |
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} - GUIDprocessedName : 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 namereceive : boolean
True if the channel can receive messages.
send : boolean
True if the channel can send messages.
stealth : boolean
True to supress the debug logging, unless nexj.system.core.meta.integration.Channel.<name> category dump logging is enabled.
transactionTimeout : nonNegativeInt
The timeout (in seconds) for transactions started on the J2EE component. Applies only to incoming transactional channels.
Set to 0 to use server default transaction timeout.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) |
Sequence of:
SenderProperties [0..1]
ReceiverProperties [0..1]
ServiceBindings [0..1] - Services bound to the incomming traffic on the channel.