XFBTransfer is a Tracked Object that stores and describes Tracked Instances of transfers. Each Tracked Instance describes a single step of a single transfer process. Together the Tracked Instances in each Processing Cycle describe the transfer of a file or a message between two Transfer CFT applications.
When you configure Sentinel for Transfer CFT, you can import the XFBTransfer Tracked Object.
XFBTransfer attributes
XFBTransfer includes attributes that you can use to identify:
For each step of each Transfer CFT transfer, Transfer CFT generates one Tracked Instance. In each Tracked Instance, the State attribute identifies the relevant step of the transfer process. The following table lists and describes the possible values of the State attribute for the Tracked Instances of a single Transfer CFT transfer.
State | Details |
---|---|
Created |
The Requester prepared a transfer request and updated the transfer catalog or, alternatively the transfer mailbox. |
To_Execute |
The Requester sent the transfer request to the Server. |
Sending |
The Sender is sending data. |
Receiving |
The Receiver is receiving data. |
Sent |
The Sender sent all of the transfer data. |
Received |
The Receiver received all of the transfer data. |
Terminated |
The Sender sent all of the transfer data, and the Receiver received all of the transfer data. Both partners successfully completed the transfer. |
The set of Tracked Instances that concern a single Transfer CFT transfer are referred to as a Processing Cycle. To identify the Tracked Instances that belong to the same Processing Cycle, use the CycleId attribute.
Although each Transfer CFT transfer occurs between only two transfer partners, each transfer partner plays two roles:
The State attribute details table underscores these roles. Notice that transfer partners are referred to as Requesters, Senders, and Receivers.
For a given transfer, only the following combinations of partner roles are possible:
In each Tracked Instance, the following attributes identify the roles of the transfer partner that generated the Tracked Instance.
Attribute | Data Type |
Value |
---|---|---|
Direction |
String |
One of the following:
|
IsServer |
String |
One of the following:
|
Example 1
State | Direction | IsServer |
---|---|---|
Created |
E (Sender) |
0 (Requester) |
To_Execute |
E (Sender) |
0 (Requester) |
Sending |
E (Sender) |
0 (Requester) |
Receiving |
R (Receiver) |
1 (Server) |
Sent |
E (Sender) |
0 (Requester) |
Received |
R (Receiver) |
1 (Server) |
Example 2
State | Direction | IsServer |
---|---|---|
Created |
R (Receiver) |
0 (Requester) |
To_Execute |
R (Receiver) |
0 (Requester) |
Sending |
E (Sender) |
1 (Server) |
Receiving |
R (Receiver) |
0 (Requester) |
Sent |
E (Sender) |
1 (Server) |
Received |
R (Receiver) |
0 (Requester) |
Together, the Direction and IsServer attributes identify the role of a transfer partner in the transfer process. However, they do not explicitly identify partners. To explicitly identify transfer partners, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
Site |
String |
Partner alias that the local partner uses to identify the parameter settings for the remote partner. When the value of the Direction attribute is:
|
ReceiverId |
String |
Network identifier of the Receiver |
SenderId |
String |
Network identifier of the Sender |
RAppl |
String |
Network identifier of the Receiver application |
SAppl |
String |
Network identifier of the Sender application |
FinalReceiverId |
String |
If the Processing Cycle:
|
OriginalSenderId |
String |
If the Processing Cycle:
|
Each Sender and Receiver is a logical entity that operates from a physical machine. Each machine is referred to as a transfer monitor. To identify details about transfer monitors, use the attributes that are listed in the following table. If the value of the direction attribute is:
Attribute | Data Type | Data Type |
---|---|---|
Location |
String |
Unique and logical identifier of a transfer monitor |
Machine |
String |
Name of the Axway Managed File Transfer application and platform that runs on a transfer monitor |
Monitor |
String |
One of the following application names:
|
MonitorVersion |
String |
Version of the File Transfer application that runs on a transfer monitor |
Although Senders and Receivers perform all actions in the transfer process, they do not initiate these actions. Transfer users initiate transfer actions. Transfer users include both people and software applications. To monitor details about transfer users, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
UserId |
String |
Local identifier of the user who owns the transferred file or message |
GroupId |
String |
Local identifier of the group to which the transfer owner belongs |
RequestUserId |
String |
Local identifier of the user who requested the transfer. If the user is:
|
RequestGroupId |
String |
Local identifier of the group to which the requesting user belongs |
Trustee |
String |
If User Access Control is:
|
RUser |
String |
Local identifier of the user who received the transfer |
SUser |
String |
Local identifier of the user who sent the transfer |
To identify a transfer, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
IdAppl |
String |
If the value of the IsServer attribute is:
|
Application |
String |
Local data identifier. If the value of the Monitor attribute is:
|
FileName |
String |
If the value of the CommandType attribute is:
|
LocalId |
String |
If the value of the Direction attribute is:
Senders and Receivers use local transfer identifiers to manage transfers (cancel, delete, and so on). |
ProtocolFileName |
String |
Network transfer identifier. The Sender sent this identifier to the Receiver. |
ProtocolFileLabel |
String |
Network transfer name. The Sender sent this name to the Receiver. The Receiver can use this name to locally name the transfer. |
ProtocolId |
String |
Network transfer identifier. The Sender generated this identifier. The Receiver acknowledged this identifier. |
ProtocolMessage (Gateway only) |
String |
If the value of the CommandType attribute is:
|
PositionNumber |
Integer |
Catalog transfer identifier. If the value of the Direction attribute is:
|
ProtocolParameter |
String |
Network transfer description. The Sender sent this description to the Receiver. |
UserParameter |
String |
Local transfer description. When the Requester recorded the transfer in the transfer catalog or transfer mailbox, the Requester generated this description. The value of this attribute includes two parts:
|
Senders and Receivers can perform specific transfers only during the specified validity periods. To monitor the validity periods for transfers, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
EarliestDate |
Date |
Date on which the validity period begins |
EarliestTime |
String |
Time at which the validity period begins |
LatestDate |
Date |
Date on which the validity period ends |
LatestTime |
String |
Time at which the validity period ends |
During the transfer process, Senders and Receivers record the time and date of certain actions that they perform. To monitor these details, use the following attributes.
Attribute | Date Type | Value |
---|---|---|
CreationDate |
Date |
By default, the system date on which the Sender sent the transfer. The Sender can set this date. The Receiver can filter transfers based on this date. |
CreationTime |
String |
By default, the system time at which the Sender sent the transfer. The Sender can set this time. The Receiver can filter transfers based on this time. |
SendDate |
Date |
If the value of the Direction attribute is:
The Sender and the Receiver record each transfer only once. |
SendTime |
String |
If the value of the Direction attribute is:
The Sender and the Receiver record each transfer only once. |
AckDate |
Date |
Date on which the Receiver acknowledged the transfer. If the Receiver did not acknowledge the transfer, this attribute is empty. |
AckTime |
String |
Time at which the Receiver acknowledged the transfer. If the Receiver did not acknowledge the transfer, this attribute is empty. |
StartDate |
Date |
If the value of the State attribute is:
These dates are expressed in dd.mm.yyyy format. |
StartTime |
String |
If the value of the State attribute is:
These times are expressed in hh:mn:ss format. |
EndDate |
Date |
If the value of the State attribute is:
These dates are expressed in dd.mm.yyyy format. |
EndTime |
String |
If the value of the State attribute is:
These times are expressed in hh:mn:ss format. |
TransmissionDuration |
String |
If the value of the State attribute is:
These times are expressed in seconds. |
Most transfers are associated with three protocol layers:
Attribute | Data Type | Value | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Protocol |
String |
Name of the protocol that operates at the Protocol Layer of the transfer. The possible values of this attribute are:
|
||||||||||||||
IsSSL |
String |
One of the following:
|
||||||||||||||
SSLAuth |
String |
One of the following:
|
||||||||||||||
SSLCypher |
String |
The cipher suite that the Server and the Requester used during the SSL/TLS session. The cipher suite identifies the following:
|
To monitor transfer options, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
Compression |
String |
One of the following compression options:
|
EOTProcedure |
String |
When the value of the State attribute is:
|
Priority |
Integer |
Transfer priority. Receivers process transfers in the order of their priority. The range of possible values for this attribute is zero to 255. The lowest priority is zero. The highest priority is 255. |
RetryMaxNumber |
Integer |
Maximum number of times that the Sender can attempt to send transfers |
RetryNumber |
Integer |
Number of times that the Sender attempted to send the transfer. Each time the Sender established a connection with the Receiver, the Sender counted one attempt. |
RequestType |
String |
One of the following:
|
TransferType |
String |
One of the following:
|
To monitor the size of transferred files and messages, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
FileSize |
Integer |
Size of the transferred file or message on the Sender's monitor, before compression. This size is expressed in bytes. |
TransmittedBytes |
Integer |
Size of the transferred file or message on the Receiver's monitor, after decompression. This size is expressed in bytes. |
To monitor the structure and content of transfers, use the following attributes.
Attribute | Data Type | Value |
---|---|---|
CommandType |
String |
One of the following:
|
BlockSize |
Integer |
If the value of the CommandType attribute is:
|
FileOrganization |
String |
If the value of the CommandType attribute is:
|
String |
If the value of the CommandType attribute is:
|
|
RecordNumber |
Integer |
If the value of the CommandType attribute is:
|
RecordSize |
Integer |
If the value of the CommandType attribute is:
|
Transcoding |
String |
Character code of the transferred data. The possible values of this attribute are:
|
TranslationTableId |
String |
Translation table identifier. When a transfer partner uses a translation table that is delivered with the Axway Managed File Transfer software, the value of this parameter is INTERNAL. |
Correspondence tables (Sentinel to Transfer CFT attributes)