Implements custom authentication for file transfers using the mlfiletransfer utility or the MLFileTransfer method.
In the following table, the description provides the SQL data type. If you are writing your script in Java or .NET, you should use the appropriate corresponding data type. See SQL-Java data types and SQL-.NET data types.
In SQL scripts, you can specify event parameters by name or with a question mark, but you cannot mix names and question marks within a script. If you use question marks, the parameters must be in the order shown below and are optional only if no subsequent parameters are specified (for example, you must use parameter 1 if you want to use parameter 2). If you use named parameters, you can specify any subset of the parameters in any order.
|Parameter name for SQL scripts||Description||Order|
INTEGER. Required. This is an INOUT parameter. It indicates the overall success of the authentication.
If this value is 1000-1999, file transfer is allowed. If this value is 2000-2999, file transfer is not allowed.
|s.filename||VARCHAR(128). This optional parameter is the name of the file that is being transferred that is to be authenticated. Do not include a path. The file must be located in the root transfer directory that you specified with the mlsrv11 -ftr option, or in one of the subdirectories that are automatically created.||2|
|s.remote_id||VARCHAR(128). The MobiLink remote ID. You can only reference the remote ID if you are using named parameters.||Not applicable|
|s.username||VARCHAR(128). The MobiLink user name.||3|
The MobiLink server executes this event before allowing any file transfer using the mlfiletransfer utility or MLFileTransfer method. It is executed after the user has authenticated using regular authentication. If this script is not defined, the file transfer is allowed.
The MLFileTransfer method can only be used by UltraLite clients.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|