App Connect

 View Only

 ACE 13 FileInput FTPS issue – DELE command blocked (534 Request denied)

Pramod Pogula's profile image
Pramod Pogula posted Thu January 08, 2026 05:13 PM

Hello everyone,

I’m facing an FTP issue in IBM App Connect Enterprise 13 while using a FileInput node to connect to an FTPS (STARTTLS) server.

Setup / Environment

  • Product: IBM App Connect Enterprise 13

  • OS: Windows

  • Flow: LockboxParserFlow

  • Node: FileInput

  • Protocol: FTP / FTPS (STARTTLS)

  • Remote server: <REMOTE_FTP_HOST>

What I did

We are using a FileInput node to connect to FTPS using SSL.
I created a JKS truststore using the IBM IKeyman tool, generated a certificate request, got it CA-signed, and imported it back into the .jks file.

The truststore was copied to:













C:\ProgramData\IBM\MQSI\certificates\13.0

I then updated the integration server’s server.conf.yaml with the truststore details and restarted the server.













ResourceManagers:
  JVM:
    jvmDebugPort: 7815
    jvmSystemProperty: >
      -Djavax.net.ssl.trustStore=C:\ProgramData\IBM\MQSI\certificates\<VERSION>\ftptruststore.jks
      -Djavax.net.ssl.trustStorePassword=********
      -Djavax.net.ssl.trustStoreType=PKCS12

SSL/TLS is working fine now — there are no PKIX or handshake errors.

Error I’m seeing













File node 'File Input' in message flow 'LockboxParserFlow'.
An unexpected reply has been received from 'FTP' server '<REMOTE_FTP_HOST>'.

DELE => response: 534 Request denied for policy reasons

What I observed

  • FTP connection and authentication succeed

  • FileInput node detects and processes the file

  • Failure happens after processing, when ACE issues a DELE command

  • The FTP server blocks the delete operation with 534 (policy restriction)

This looks like a server-side restriction on file deletion, not a connectivity or SSL issue.

Questions

  1. Does the FileInput node always issue a DELE command after successful file processing?

  2. In ACE 13, is there a way to configure FileInput to:

    • Skip deleting the remote file, or

    • Rename/move the file instead of deleting it?

  3. Has anyone dealt with FTP servers that block DELE due to security/compliance policies, and how was it handled?

  4. Are there any FtpServer policy settings that control this delete behavior?

Any guidance or best practices would really help.
Thanks in advance.

Related Content