I’m not aware of GD for FTP sessions using the B2B Server. You can implement a flow similar to the attached to catch the return code.
Flow Detail
1 SEQUENCE
1.1 try: SEQUENCE
1.11 INVOKE pub.client:ftp
Pipeline In Service In
command "put"
remoteDir dirpath
transfermode “binary”
transfertype “active”
response content
remoteFileName remotefile
sendAddr serverhost
sendPort serverport
login username
Service Out Pipeline Out
content
command
1.12 BRANCH on '/returncode'
1.121 221: MAP
returncode = 221 if ftp is successful
Source Destination
ftpResult "1"
1.122 $default: EXIT 'try'
ftp unsuccessful
1.2 catch: SEQUENCE
1.21 INVOKE pub.flow:getLastError
1.22 MAP
Source Destination
lastError (exceptionInfo)
pipeline savedpipeline
lastError (exceptionInfo)
error returncode
lastError (exceptionInfo)
alertSubject “SEI Alert: ftp error to customer “%custSysId%””
lastError (exceptionInfo)
error alertMessage
ftpResult “0”
1.23 INVOKE SEI.dbutil:updateSiteStatus
Pipeline In Service In
status "DOWN"
1.24 INVOKE SEI.services:sendAlert
Pipeline In Service In
alertType "B"
alertSubject subject
alertMessage message
Service Out Pipeline Out
alertType
subject
message
#Adapters-and-E-Standards#Integration-Server-and-ESB#webMethods