So we recently encountered an issue where when we use Gateway 6.9.1 with Integrator 2.1.1, we experience an issue with filenames that come in from Gateway with a CRLF that we then want to route internally with integrator, Integrator chokes on the FTP send. Somebody suggested the following as a workaround, which I haven’t had a chance to try. Hopefully I’ll be able to try soon, or somebody else can give it a shot to see how it works -

1) Make a custom MBC that has the FTP Send as a next activity.
In this custom MBC you have to extract the original filename from the FTP ReceiveInfo Attributes:

CODE
FOR $i_Attribute = 1 TO ARRAYSIZE($AttributeNames)
{
$AttributeValue = MBC_HIERCHMSGENV.GetAttribute($SessionId, $MessageId, $AttributeNames[$i_Attribute]);

# FTPReceiveInfo
IF $AttributeNames[$i_Attribute] = TA_FTP.$ReceiveInfoAttribute
{
$ftpinputattribute = TA_FTP.UnpackReceiveAttribute($AttributeValue);
$InputFilename = $ftpinputattribute.$RemoteFilename;
}
}

2) Now you can remove the CR/LF from the $InputFilename variable.
3) Use the ‘clean’ filename as output filename using the FTP Send Override Attributes:

CODE

# Set the filename for outgoing FTP Transfers
$ftpOverride.$Use_RemoteFilename = $TRUE;
$ftpOverride.$RemoteFilename     = $OutputFilename;

# Pack the record.
$ftpOverrideString = TA_FTP.PackSendMethodOverrideAttribute($ftpOverride);

# Set the attribute.
MBC_HIERCHMSGENV.SetAttribute $SessionId
MessageId $NewMessageId
Name TA_FTP.$SendMethodOverrideAttribute
Value $ftpOverrideString;

Good luck!