21. File Sender: Performance Issues After Configuring A Large Amount Of Channels
Q: After configuring a large amount of File Adapter sender channels, the J2EE Engine becomes very slow and some services start to block. How can I solve this issue?
A: Up to and including XI 3.0 SP13 each File Adapter sender channel permanently consumes a J2EE application thread. To solve this issue, increase the number of configured J2EE application threads using the SAP J2EE Engine Config Tool (“cluster-data” -> “Global server configuration” -> “managers” -> “ApplicationThreadManager” -> “MaxThreadCount”).
Starting with XI 3.0 SP14 / PI 7.0 application threads are allocated on demand by the File Adapter and returned to the thread pool after it has finished the polling sequence, so thread shortage situations will typically occur much more rarely than with earlier SPs.
22. File Sender: File Modification Check For Transport Protocol “FTP”
Q: Is the file modification check (advanced mode option “Msecs to Wait Before Modification Check”) in a File Adapter sender channel supported for the transport protocol “File Transfer Protocol (FTP)”?
A: No, this option is not supported for the transport protocol “File Transfer Protocol (FTP)”, but only for the transport protocol “File System (NFS)”.
23. FTP: Active Data Connection Support
Q: Does the File Adapter support active data connections when connecting to an FTP server?
A: Up to and including XI 3.0 SP14, the File Adapter exclusively uses passive data connections. Starting with XI 3.0 SP15 / PI 7.0, active connections are available.
24. FTPS: Server certificate rejected by ChainVerifier
Q: After configuring a File Adapter FTPS communication channel, I see the following error message in the Adapter Monitor: iaik.security.ssl.SSLException: Server certificate rejected by ChainVerifier. What do I need to configure to get my scenario working?
A: The File Adapter checks whether a trusted certificate chain exists for the X.509 certificate of the FTP server it is connecting to. A certificate chain is considered trusted if the chain is valid and at least one of its certificates is directly trusted. If the certificate chain is untrusted, the above exception is thrown. To configure a single certificate or a certification authority’s CA certificate as directly trusted, add the respective X.509 certificate to the “Trusted CAs” view of the “Key Storage” service in the SAP J2EE Visual Administrator. In most cases, this will be the CA certificate that was used to sign the server certificate.
25. FTP Proxy Support
Q: Does the File Adapter provide a means to configure an FTP proxy server used to establish any FTP connections?
A: No, this is not supported. This limitation also applies to FTPS.
26. FTP Connection Problems
Q: I have configured a File Adapter channel to connect to an FTP server, but receive one of the following error messages in the adapter monitor:
Error connecting to ftp server ‘<hostname>’: SocketException: Connection reset
Error connecting to ftp server ‘<hostname>’: SocketException: Connection refused
Error connecting to ftp server ‘<hostname>’: ConnectException: Connection timed out
A: This problem is either caused by incorrect firewall / packet filter settings or an incorrect configuration of the FTP server. Also make sure that you have correctly specified the host name / IP address and port of the FTP server.
Changing the connection type from ‘active’ to ‘passive’ (or vice versa) might additionally help to work around the incorrect firewall configuration.
27. FTP Directory Listing Semantics
Q: Which semantics does the File Sender Adapter apply to determine which files to retrieve from an FTP server?
A: Up to and including XI 3.0 SP13 the File Adapter will issue an NLST command (see RFC 959) with the configured source file name scheme as first parameter to the FTP server. It will try to retrieve any of the files returned by the FTP server in response to this command.
Starting with XI 3.0 SP14 / PI 7.0, the File Adapter will issue a LIST command with the configured source file name scheme as first parameter to the FTP server. If it is able to parse the returned result (which is the case for UNIX- and Windows-style directory listings), it will retrieve any of the returned files. If it cannot parse the result, it will fall back to the pre-SP14 implementation and use the NLST command as described above.
28. sftp Support
Q: Does the File Adapter support the sftp (File Transfer over SSH) protocol?
A: No, this protocol is not supported and there are currently no plans to implement sftp support in the File Adapter.
29. File Content Conversion fieldFixedType Parameter Not Working
Q: After configuring a File Adapter channel with File Content Conversion and the fieldFixedType=byte parameter set, I noticed that this setting does not seem to have any effect.
A: The parameter’s name should correctly read “fieldFixedLengthType”. The documentation will be updated accordingly with XI 3.0 SP17 / PI 7.0.
30. Missing Features After Upgrade
Q: After applying a support package, I am unable to find a new feature advertised in the release notes in the channel configuration.
A: You most likely did not import the updated SAP_BASIS content for the support package.