SecureTransport 5.5 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content CycleId calculation This topic describes the internal CycleId structure for PeSIT and SFTP protocol transfers. The CycleId of the original transfer is preserved when retrying or resubmitting failed SITs. Internal CycleId structure with PeSIT The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for PeSIT transfers: Offset Length PI/Value Description 1 4 “SUIV” Eye catcher 5 24 PI3 CONNECT For Transmission PI4 CONNECT For Reception 29 24 PI4 CONNECT For Transmission PI3 CONNECT For Reception 53 5 "0 " For File Transfer "65535" For Message Transfer "REPLY" For Acknowledgment 58 76 PI12 Logical file name 134 8 PI13 Transfer ID 142 12 PI51 Only the date is used (YYMMDD), and the time is filled with 6 spaces. 154 1 E For Transmission R For Reception Internal CycleId structure with SFTP The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for SFTP transfers: Offset Length PI/Value Comments 1 4 SUIV TEMP Eye catcher 5 24 Sender identifier Sender account login na me SEND: System login of the process that runs the SFTP client RECV: SFTP login name sends by the client to connect to the SFTP server 29 24 Receiver identifier Receiver login name SEND: SFTP login name sends by the client to connect to the SFTP server RECV: System login of the process that runs the SFTP client 53 5 "0" For File Transfer 58 76 Virtual Filename Logical file name, NIDF for CFT 134 8 Sequence number Unique number identifying the transfer sent, NIDT for CFT 142 12 Date YYMMDD /padded to 12 with spaces on the right/ Only the date is used (YYMMDD), and the time is filled with 6 spaces 154 1 E For Transmission R For Reception Generating common CycleID for end-to-end tracking of SFTP transfers With transfers occurring across Axway's MFT solutions SecureTransport and Transfer CFT, the CycleId is used for consistent end-to-end reporting to Sentinel. In order to report the common CycleId, you must set the dedicated configuration option Ssh.AxwayVendorExtensions.enabled to true. In order to apply this change, you must restart the SSH services and the Transaction Manager (TM) on all server and Edge instances. Note When this option is enabled, in the case when SecureTransport acts as client and Transfer CFT acts as server, make sure to name each of your transfer sites to exactly match the corresponding NIDF name in Transfer CFT. Also, for correct SFTP end-to-end reporting with CFT, make sure to use only capital letters for each SecureTransport user's Account name (Login name). Related topics: Event states Axway Sentinel tracked objects About XFB Transfer tracked objects PeSIT protocol List of PeSIT states XFB Tracked Object attributes Axway Sentinel dashboards Axway Sentinel requests Configure SecureTransport to send events to Axway Sentinel More SecureTransport 5.5 docs All docs | HTML only | PDF only Related Links
CycleId calculation This topic describes the internal CycleId structure for PeSIT and SFTP protocol transfers. The CycleId of the original transfer is preserved when retrying or resubmitting failed SITs. Internal CycleId structure with PeSIT The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for PeSIT transfers: Offset Length PI/Value Description 1 4 “SUIV” Eye catcher 5 24 PI3 CONNECT For Transmission PI4 CONNECT For Reception 29 24 PI4 CONNECT For Transmission PI3 CONNECT For Reception 53 5 "0 " For File Transfer "65535" For Message Transfer "REPLY" For Acknowledgment 58 76 PI12 Logical file name 134 8 PI13 Transfer ID 142 12 PI51 Only the date is used (YYMMDD), and the time is filled with 6 spaces. 154 1 E For Transmission R For Reception Internal CycleId structure with SFTP The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for SFTP transfers: Offset Length PI/Value Comments 1 4 SUIV TEMP Eye catcher 5 24 Sender identifier Sender account login na me SEND: System login of the process that runs the SFTP client RECV: SFTP login name sends by the client to connect to the SFTP server 29 24 Receiver identifier Receiver login name SEND: SFTP login name sends by the client to connect to the SFTP server RECV: System login of the process that runs the SFTP client 53 5 "0" For File Transfer 58 76 Virtual Filename Logical file name, NIDF for CFT 134 8 Sequence number Unique number identifying the transfer sent, NIDT for CFT 142 12 Date YYMMDD /padded to 12 with spaces on the right/ Only the date is used (YYMMDD), and the time is filled with 6 spaces 154 1 E For Transmission R For Reception Generating common CycleID for end-to-end tracking of SFTP transfers With transfers occurring across Axway's MFT solutions SecureTransport and Transfer CFT, the CycleId is used for consistent end-to-end reporting to Sentinel. In order to report the common CycleId, you must set the dedicated configuration option Ssh.AxwayVendorExtensions.enabled to true. In order to apply this change, you must restart the SSH services and the Transaction Manager (TM) on all server and Edge instances. Note When this option is enabled, in the case when SecureTransport acts as client and Transfer CFT acts as server, make sure to name each of your transfer sites to exactly match the corresponding NIDF name in Transfer CFT. Also, for correct SFTP end-to-end reporting with CFT, make sure to use only capital letters for each SecureTransport user's Account name (Login name). Related topics: Event states Axway Sentinel tracked objects About XFB Transfer tracked objects PeSIT protocol List of PeSIT states XFB Tracked Object attributes Axway Sentinel dashboards Axway Sentinel requests Configure SecureTransport to send events to Axway Sentinel More SecureTransport 5.5 docs All docs | HTML only | PDF only
CycleId calculation This topic describes the internal CycleId structure for PeSIT and SFTP protocol transfers. The CycleId of the original transfer is preserved when retrying or resubmitting failed SITs. Internal CycleId structure with PeSIT The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for PeSIT transfers: Offset Length PI/Value Description 1 4 “SUIV” Eye catcher 5 24 PI3 CONNECT For Transmission PI4 CONNECT For Reception 29 24 PI4 CONNECT For Transmission PI3 CONNECT For Reception 53 5 "0 " For File Transfer "65535" For Message Transfer "REPLY" For Acknowledgment 58 76 PI12 Logical file name 134 8 PI13 Transfer ID 142 12 PI51 Only the date is used (YYMMDD), and the time is filled with 6 spaces. 154 1 E For Transmission R For Reception Internal CycleId structure with SFTP The internal CycleId is an XFB Transfer Tracked Object attribute. This field has the following structure for SFTP transfers: Offset Length PI/Value Comments 1 4 SUIV TEMP Eye catcher 5 24 Sender identifier Sender account login na me SEND: System login of the process that runs the SFTP client RECV: SFTP login name sends by the client to connect to the SFTP server 29 24 Receiver identifier Receiver login name SEND: SFTP login name sends by the client to connect to the SFTP server RECV: System login of the process that runs the SFTP client 53 5 "0" For File Transfer 58 76 Virtual Filename Logical file name, NIDF for CFT 134 8 Sequence number Unique number identifying the transfer sent, NIDT for CFT 142 12 Date YYMMDD /padded to 12 with spaces on the right/ Only the date is used (YYMMDD), and the time is filled with 6 spaces 154 1 E For Transmission R For Reception Generating common CycleID for end-to-end tracking of SFTP transfers With transfers occurring across Axway's MFT solutions SecureTransport and Transfer CFT, the CycleId is used for consistent end-to-end reporting to Sentinel. In order to report the common CycleId, you must set the dedicated configuration option Ssh.AxwayVendorExtensions.enabled to true. In order to apply this change, you must restart the SSH services and the Transaction Manager (TM) on all server and Edge instances. Note When this option is enabled, in the case when SecureTransport acts as client and Transfer CFT acts as server, make sure to name each of your transfer sites to exactly match the corresponding NIDF name in Transfer CFT. Also, for correct SFTP end-to-end reporting with CFT, make sure to use only capital letters for each SecureTransport user's Account name (Login name). Related topics: Event states Axway Sentinel tracked objects About XFB Transfer tracked objects PeSIT protocol List of PeSIT states XFB Tracked Object attributes Axway Sentinel dashboards Axway Sentinel requests Configure SecureTransport to send events to Axway Sentinel More SecureTransport 5.5 docs All docs | HTML only | PDF only