The following table shows the possible restrictions to the access rights in an FT profile in the left column, with the entries needed for the FT request with respect to the partner system in the right column:
Entry in the FT profile | Entries in the FT request |
Transfer admission | The transfer admission must be specified.
|
Transfer direction restricted | The value specified here must be the opposite of the entry in the FT profile. If the profile contains the transfer direction “From partner”, the remote system may only send data to the local system; with “To partner”, only read access is permitted on the local system. |
Partner systems specified | The request can only be issued by partner systems entered in the profile. This option may only be used if the names of the FTP clients are guaranteed to be no longer than 8 characters. If DNS is activated, the client name supplied by DNS is used, otherwise the entry belonging to the IP address in the SOCKET-HOST-TABLE is relevant (see “BCAM” manual). If no corresponding entry is available, the entry in the PROCESSOR-TABLE is used. In the case of local access, “LOOPBACK” is used as the name. |
Prefix for file name specified | Only part of the file name is present in the request. FTAC supplements this entry with the prefix defined in the profile to obtain the complete file name. The entry of absolute file names, or exiting a directory with “..” is prohibited by FTAC. |
Follow-up processing | This FTAC function is reserved for openFT and is not used for FTP. |
Syntax restriction | The request is executed only if it does not violate this syntax restriction. |
Exporting admissions
You can export complete admissions as well as individual admission sets and profiles to a file (export) and then import them from the file when required.