The following table describes the range in which the functionality used for FTP integration can be used in combination with the other existing functionality:

Table 8-28 Range in which the FTP integration functionality can be used in combination with existing functionality

Adapters	Standard reception (synchronous or asynchronous)	SOAP reception	TP1/RPC reception	FTP reception
SOAP adapter	Y	Y	Y	A
SessionBean adapter	Y	Y	Y	A
MDB (WS-R) adapter	Y	Y	Y	A
MDB (DB queue) adapter	Y	Y	Y	A
DB adapter	Y	Y	Y	A
TP1 adapter	Y	Y	Y	A
File adapter	Y	Y	Y	A
Object Access adapter	Y	Y	Y	A
Message Queue adapter	Y	Y	Y	A
FTP adapter	A	A	A	Y
File operations adapter	A	A	A	Y
Mail adapter	Y	Y	Y	Y
Data transformation	Y	Y	Y	Y
Invoke java activity	Y	Y	Y	Y

Legend:

Y: The functionality can be combined and used.

A: The operations are not supported when the functionality are combined.

• A business process must be created for each file transfer route.
• The business process must be created such that a response is returned to the FTP reception.
• You cannot process multiple files with one business process.
• You cannot use BPEL parallel processing (FLOW) in the FTP integration.

To use the FTP for operating and maintaining a server on Service Platform, you must set up a separate FTP server. In this case, specify the design in such a way that the port number or IP address of both the FTP servers is unique.

If you use the ftp commands for Linux and perform file transfer requests for the FTP client, the following two types of messages are output in the message log of the FTP inbound adapter:

• A message indicating that the SYST command, which is the command of an unsupported FTP protocol, was received (KDEC07531-E)
• A message indicating that the error response was returned to the client (KDEC07542-E)

Furthermore, the response "502 Command SYST not implemented." is returned to the FTP client, but this does not affect the file transfer requests.