Seon plugin seonplugin scp upload - Revision history

Admin: /* Configuration */

2018-01-30T09:45:21Z

‎Configuration

Admin: /* Bevahiour */

2015-11-20T08:32:46Z

‎Bevahiour

Admin at 14:48, 9 November 2015

2015-11-09T14:48:36Z

Admin at 08:53, 2 November 2015

2015-11-02T08:53:14Z

Admin: Created page with "== Purpose == For simple SCP/SFTP upload tasks, this plugin can transfer all job files to a target SCP/SFTP server. == Configuration == The plugin must be configured on per-p..."

2015-11-02T08:06:14Z

Created page with "== Purpose == For simple SCP/SFTP upload tasks, this plugin can transfer all job files to a target SCP/SFTP server. == Configuration == The plugin must be configured on per-p..."

New page

== Purpose ==
For simple SCP/SFTP upload tasks, this plugin can transfer all job files to a target SCP/SFTP server.

== Configuration ==
The plugin must be configured on per-partner level and has no global configuration.

Configuration parameters are:
*Target server: server hostname or IP address of SSH server being addressed.
*SCP port: default port 22, but can be changed to any valid TCP/IP port on which the remote SSH server is listening.
*Target path: target path where to upload files to.
*Username: username which is being authentificated at the remote server.
*Password: plaintext password (if available) for the user being authentificated.
*Key file: absolute path to the SSH key file of the user being authentificated.
*Debug output: enable more debug output for analyzing transmission problems.
*Enable SCP mode: If SFTP is not available, plain SCP mode can be activated with this option. '''Beware:''' enabling this option disabled the support of directory structures on remote site.

== Bevahiour ==
The plugin loops over all files of the job and handles them separately (one after another). For each file, the plugin
*Connects to the SSH server
*Uploads the file to the target directory with its absolute filename. The local filename is being analyzed if a "job directory" exists for this job. If it exists, the file is being translated into a path without the job directory, so subdirectories at remote side are possible (i.e. when extracting a ZIP archive with subdirectories before transmission). If no job directory definition exists, the basename of the file is being used.

[[Category:Plugins]]

@@ Line 41: / Line 41: @@
 *%a: ENGDAT Message Reference [UNH0062] (if given, otherwise empty)
 *%b: ENGDAT Document Number [MID1004] (if given, otherwise empty)
 == Behaviour ==

@@ Line 42: / Line 42: @@
 *%b: ENGDAT Document Number [MID1004] (if given, otherwise empty)
-== Bevahiour ==
+== Behaviour ==
 The plugin loops over all files of the job and handles them separately (one after another). For each file, the plugin
 *Connects to the SSH server

@@ Line 1: / Line 1: @@
 == Purpose ==
 For simple SCP/SFTP upload tasks, this plugin can transfer all job files to a target SCP/SFTP server.
@@ Line 15: / Line 14: @@
 *Debug output: enable more debug output for analyzing transmission problems.
 *Enable SCP mode: If SFTP is not available, plain SCP mode can be activated with this option. '''Beware:''' enabling this option disabled the support of directory structures on remote site.
 == Bevahiour ==
@@ Line 20: / Line 46: @@
 *Connects to the SSH server
 *Uploads the file to the target directory with its absolute filename. The local filename is being analyzed if a "job directory" exists for this job. If it exists, the file is being translated into a path without the job directory, so subdirectories at remote side are possible (i.e. when extracting a ZIP archive with subdirectories before transmission). If no job directory definition exists, the basename of the file is being used.