MQ FTE

WebSphere MQ File Transfer Edition is a managed file transfer capability for MQ to transfer files across platforms and networks.

Topology overview

MQFTE is comprised of the following components, all supported by one or more WebSphere MQ queue managers in the network:

agents -
configuration and administration commands
graphical user interface
database logger

To do its job, each component of WebSphere MQ File Transfer Edition needs to connect to one of the following types of WebSphere MQ queue managers:

Coordination queue manager
Agent queue managers
Command queue managers

The Command QM is used to connect to the WebSphere MQ network and is the queue manager connected to when you issue WebSphere MQ File Transfer Edition commands.

The Coordination QM is the central "heart" in your file transfer network. The coordination queue manager acts as a central collection point where information about MQFTE activity is gathered. The Coordination Queue Managers pub-submotor is used as the "repository" identifying where the various FTE Agents can be found. This pub-sub motor distributes the information regarding file transfers, and must be a MQ version 7 queue manager.

Agents are WebSphere MQ File Transfer Edition programs that form the endpoints for file transfer operations. Essentially, agents perform the fundamental task of transferring files through the network, using the WebSphere MQ network. So, every agent needs a queue manager, called an agent queue manager. Each agent uses its own uniquely identified queues that are separate from those used by other agents. Thus, an agent queue manager can validly host more than one agent.

MQFTE agents

As I understand it, a FTE Agent is the "entry point" for an Application to access the MQ network, so it cand send files to remore queue managers. So, why should someone place 2 agents on same (input) machine ?

There are a couple different reasons you could use more than 1 agent per queue manager. The main one being that there are different types of agents:

Transfer Agent(standard),
Protocol Agent(FTP),
Web Agent(Web Gateway), and
Connect:Direct Agent.

Also within each agent you can specify in the agent.properties, the particulars as far as how MQ will handle the transfer, chunk/block/window size as well as max transfers. One other reason, in cases where there are large number of transfers coming into a system, you can divide them up based off your needs so that there is less of an impact if you have a problem with one of the transfers or agents.

Top

MQFTE types

There are two types of MQFTE agents that correspond to MQFTE Server and MQFTE Client:

WebSphere MQ File Transfer Edition server agent
The agent supplied with WebSphere MQ File Transfer Edition Server can connect to a local queue manager using an MQ bindings connection. These agents can also connect to a local or remote queue manager using an MQ client connection.
WebSphere MQ File Transfer Edition client agent
The agent supplied with the WebSphere MQ File Transfer Edition Client uses an MQ client connection to connect to a queue manager. Client agents can be located on the sa

MQ File Transfer Edition can be installed as three different types of component, depending on your platform and overall setup.

WebSphere MQ File Transfer Edition Client - installs a file transfer agent. This agent can connect to a remote WebSphere MQ and allows you to establish client transport mode connections from agents to queue managers. You can only run the Client on a machine that does not have WebSphere MQ installed.
WebSphere MQ File Transfer Edition Server - installs a file transfer agent and includes MQ Version 7.0 CDs. The Server allows you to establish client and bindings mode connections from agents to queue managers.
WebSphere MQ File Transfer Edition for z/OS

MQ scripts have been created which must be run in order to initialize the local queue manager QM_wmqfte for two distinct roles:

In order to verify that the Agent has started properly, you should always check its log. The log is held in the file

The BFGAG0059I message indicates a successful start and that it is awaiting work.

Start MQ Explorer - we have a new entry "Managed File Transfer", and can start a file transfer (from win to win by now)

After youve finished using transferring files, youll probably want to stop the WMQ FTE Agent. This is done by using the line command fteStopAgent as illustrated below:

Puede instalar MQ File Transfer Edition utilizando una opción de slo texto (instalación de consola): -i console La documentación sobre esta opción se encuentra en: url

Top

MQFTE tools

WebSphere MQ File Transfer Edition Server includes an extension (plug-in) for the WebSphere MQ Explorer to allow you to administer file transfers.

Installing MQ File Transfer Edition Remote Tools and Documentation (C1S13ML)

Top

File Transfer

You can start a new file transfer from the MQ Explorer or from the command line and you can choose to transfer either a single file or multiple files in a group.

To start a new file transfer using the Create New Managed File Transfer wizard in WebSphere MQ Explorer, use the following steps:

In the Navigator view, click Managed File Transfer. Managed File Transfer Central is displayed in the Content view.
All of your coordination queue managers are displayed in the Navigator view. Expand the name of the coordination queue manager that the agent you want to use for the transfer is registered against. If you are currently connected to a coordination queue manager other than the one you want to use for the transfer, right-click that coordination queue manager name in the Navigator view and click Disconnect. Then right-click the name of the coordination queue manager you want to use and click Connect.
Start the Create New Managed File Transfer wizard using either of the following methods:
1. Right-click the name of any of the following nodes in the Navigator view: the relevant coordination queue manager, Transfer Templates, Transfer Log, or Pending Transfers. Then click New Transfer to launch the wizard.
2. Click File > New > Other > Managed File Transfer Wizards > New Transfer Wizard
Follow the instructions on the wizard panels. There is also context-sensitive help provided for each panel. To access the context-sensitive help on Windows, press F1. On Linux, press Ctrl+F1 or Shift+F1.

Syntax: fteCreateTransfer [-p ConfigurationOptions] -sa AgentName [-sm QueueManager] -da AgentName [-dm QueueManager] [-td TransferDefinitionFile] | ([-df File] | [-dd Directory] | [-ds SequentialDataset] | [-dp PartitionedDataset]) [-r] [-w] [-t TransferMode] [-cs ChecksumMethod] [-de ] [-sd ] [-pr ] [-md metaData] ([-tr triggerSpec ] [-tl ]) ([-ss startSchedule] [-tb timeBase] [-oi occurrenceInterval] [-of ocurrenceFrequency] [-oc occurrenceCount] | [-es endSchedule]) [-jn jobName] SourceFileSpec... where: -sa Required. The name of the agent the file is transferred from. -sm Optional. The queue manager that the source agent is connected to. If you do not specify the -sm parameter, the queue manager used is determined from the set of configuration options in use, based on the source agent name. -da Required. The name of the agent the file is transferred to. -dm Optional. The queue manager that the destination agent is connected to. If you do not specify the -dm parameter, the queue manager used is determined from the set of configuration options in use, based on the destination agent name. -td Optional. The name of the XML document that defines one or more source and destination file specifications for the transfer. If you specify the -td parameter, you cannot use the -df, -dd, -ds, -dp, -sd, -r, -de, -t, or -cs parameters, or specify source files on the command line. See Using transfer definition files. -df Optional. The name of the destination file for the file transfer. You must specify a valid file name on the system where the destination agent is running. Omit the -df parameter if you specify the transfer definition file (-td) parameter -dd Optional. The name of the destination directory that files are transferred into. You must specify a valid directory name on the system where the destination agent is running. Omit the -df parameter if you specify the transfer definition file (-td) parameter. -ds (z/OS only). Optional. The name of the sequential data set that files are transferred into. You must specify a sequential data set name or partitioned data set with a member. If the data set name is enclosed in single quotation marks, the name is treated as a fully-qualified name. Otherwise the data set is prefixed with the user name that the destination agent is using. Omit the -ds parameter if you specify the transfer definition file (-td) parameter. -dp (z/OS only). Optional. The name of the partitioned data set that files are transferred into. You must specify a partitioned data set name. Omit the -dp parameter if you specify the transfer definition file (-td) parameter. -de Optional. Specifies what action to take if the destination file is already present. The valid options are: error report as error and not transfer the file. This is the default option. overwrite overwrite the existing destination file. Omit the -de parameter if you specify the transfer definition file (-td) parameter. -sd Optional parameter. Specifies the source disposition action taken on each source file when the transfer of that file has successfully completed. The valid options are: leave the source files are left unchanged. This is the default option. delete the source files are deleted. Omit the -sd parameter if you specify the transfer definition file (-td) parameter. -pr Optional. Specifies the priority level for the transfer. The is a value in the range 0 to 9, where 0 is the lowest priority. The default priority is 0. -p Optional. Determines the set of configuration options that is used to create a file transfer. If you do not specify the -p parameter, the default set of configuration options is used. -r Optional. Recursively transfer files in subdirectories when the SourceFileSpec is a directory or wildcard. Omit the -r parameter if you specify the transfer definition file (-td) parameter. -w Optional. Specifies whether to wait for the requested transfer to complete. If you specify the -w parameter, the command waits for the transfer to complete before the command stops. The default is to return when the transfer request has been submitted to the agent. -t Optional. Determines which conversion is applied to the data transferred. The valid values for the -t parameter are: Binary The data is transferred without performing any conversion. This is the default setting if you do not specify the -t parameter. Text The file's code page and control characters can be converted. The exact conversions performed depend on the operating systems and configurations of the source and destination agents. Omit the -t parameter if you specify the transfer definition file (-td) parameter. -cs Optional. Specifies whether to validate the transfered file by computing an MD5 checksum of the data. The possible values for this parameter are: MD5 An MD5 checksum of the data is computed. The resulting checksum for the source and destination files is written in the log messages for validation purposes. This is the default setting if you do not specify the -cs parameter. none No MD5 checksum of the data is computed. In the log messages the checksum method is identified as none and no checksum value is present. If you specify this option the transfer performance might improve, depending on your environment. However, there will be no validation of the source or destination files. Omit the -cs parameter if you have already specified the transfer definition file (-td) parameter. -ss Optional. The time and date of the scheduled transfer in one of the following formats: yyyy-MM-ddThh:mm hh:mm -tb Optional. Defines what time the scheduled transfer is represented in. This option is valid only in conjunction with startSchedule. The following options are valid: admin Schedule start and end times are based on the local administrator's machine time. This is the default option. source Schedule start and end times are based on in the source agent's machine time. utc Schedule start and end times are defined in UTC. -oi Optional. Determines the interval that the schedule occurs at. The -oi parameter is valid in conjunction with the startSchedule parameter only. The following occurrence types are valid: minutes, hours, days, weeks, months, years The default is for no repeat of the scheduled transfer. -of Optional. Sets the schedule to occur every 'occurrenceFrequency' occurrenceIntervals. For example, occur every '5' weeks. If you do not specify the -of parameter, the default value of 1 is used. The -of parameter is valid in conjunction with the occurrenceInterval and startSchedule parameters only. -oc Optional. The number of times a repeatable scheduled transfer occurs before the scheduled transfer is removed. The -oc parameter is valid in conjunction with the occurrenceInterval and startSchedule parameters only, and is not valid in conjunction with the endSchedule parameter. The default value for the -oc parameter is once. -es Optional. The time and date that a repeating scheduled transfer ends, in one the following formats: yyyy-MM-ddThh:mm hh:mm The -es parameter is valid in conjunction with the occurrenceInterval and startSchedule parameters only, and is not valid in conjunction with the occurrenceCount parameter. -tr Optional. A trigger is a condition on the transfer request that must evaluate true by the sending agent. If the trigger condition is not met, the transfer request is discarded. If this command has a schedule definition, this trigger condition is applied to the transfer request generated by the scheduler. The format of the trigger parameter is: <condition>,<namelist> where <condition> can be one of the following values: file=exist at least one of the file names in the namelist exists. file!=exist at least one of the file names in the namelist does not exist. filesize>=<size> at least one of the file names in the namelist has a file size that is at least . <size> is a integer with optional units of KB, MB, or GB. If you do not specify a size unit, a size unit of bytes is assumed. <namelist> a comma separated list of file names located on the source agent's system. You can specify the -tr parameter more than once. But in that case, each separate trigger condition must be true for the transfer to be processed by the source agent. -tl Optional. Trigger log definition. The valid values are: yes Failed triggers generate log messages. This is the default value. no Failed triggers do not generate log messages. -md Optional. Parameter for the user-defined metadata that is passed to the agent's exit points. The parameter can take one or more name pairs separated by commas. Each name pair consists of a =. The -md parameter can occur more than once in a command. -jn Optional. Job name reference. A user-defined identifier for the entire transfer.

ex 1.- Simple File Transfer

C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO df c:\temp\destination\DestinationName.txt t binary de overwrite c:\temp\origin\SourceFileName.txt

ex 2.- Group File Transfer

C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO dd c:\temp\destination\ t binary de overwrite c:\temp\origin1\FileOne.zip c:\temp\origin2\FileTwo.zip

ex 3.- File Transfer using Wild Cards

C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO dd c:\temp\destination\ t binary c:\temp\origin1\*.zip C:\temp\origin2\*.jpg

ex 4.- Scheduling and Triggering File Transfers

1. Scheduled Transfer: C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO df c:\temp\destination\DestinationName.txt t binary de overwrite -tb Admin -ss 10:30 oi minutes of 1 oc 3 c:\temp\origin\SourceFileName.txt 2. Triggered Transfer: C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO df c:\temp\destination\TextFile.txt.triggered t text de overwrite -tr file=exist,C:\temp\origin\TriggerFile.txt C:\temp\origin\TextFile.txt 3. Scheduled & Triggered Transfer: C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO df c:\temp\destination\DestinationName.txt t binary de overwrite -tb Admin -ss 10:30 oi minutes of 1 oc 3 -tr file=exist,C:\temp\origin\TriggerFile.txt C:\temp\origin\OriginName.txt

ex 5.- Transfer Templates

Available ONLY on MQ Explorer !

ex 6.- Transfer Definition XML

File "GroupFileTransferSpecification.xml" has :

<?xml version="1.0" encoding="UTF-8"?> <transferSpecifications xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FileTransfer.xsd"> <item checksumMethod="none" mode="text"> <source recursive="false" disposition="leave"> <file>C:\origin_one\*.txt</file> </source> <destination type="directory" exist="overwrite"> <file>C:\destination</file> </destination> </item> <item checksumMethod="none" mode="binary"> <source recursive="false" disposition="leave"> <file>C:\origin_two\*.zip</file> </source> <destination type="directory" exist="overwrite"> <file>C:\destination</file> </destination> </item> </transferSpecifications>

Transfer request is :

C:\IBM\WMQFTE\bin> fteCreateTransfer sa AGENT_ONE -sm QM_ONE da AGENT_TWO -dm QM_TWO -td C:\origin\GroupTransferSpecification.xml

Top

My MQFTE envir

Installation squema:

Installation steps:

Install, configure and test the WMQ FTE product (Server and Tools) purely on the Windows platform
1. Install WMQ FTE Server provides the runtime Agent to perform file transfers
2. Install WMQ FTE Tools provides the graphic interface to WMQ FTE
Configure and test MQ connectivity between the Windows and AIX queue managers
Install, configure and start the WMQ FTE product (Server) on the AIX platform
Test transfers between the two platforms

Top

(user defined) CodePage change

FTE uses Unicode internaly. So, input message is translated - using what table ?

MQ does not take part in the code page translation at all. Since FTE breaks files up into messages at the byte level, it is not aware of any character boundaries (i.e. DBCS) where the first half of the character could be in one message and the second half in the next.

If you use the -td option and provide a Transfer Definition file, you can specify the destination code page. How you could specify a custom code page ?

FTE text transfers essentially transfer the source file as binary data. Then at the destination agent the data is converted from the source codepage to unicode then from unicode to the destination codepage. The character conversion tables used are that provided by the destination agent's Java SDK platform.

Top

New Agent comes into play

Let's supose we have 3 systems, (wintel, solaris and zos ... not important the kind of system) with 3 agents, one each, all running well.
Now, another system comes into the game (lets say AIX). We create a queue manager (aixqmgr), install FTE Server and create an agent (aix_agent) in the new machine.
Question : what changes must be done in "old" 3 systems in order to be able to speak (in all MQFTE possible ways) with the new machine ?

MQ connectivity between all agent's queue managers ? [yes]
MQ Connectivity to Coordinator's queue manager ? [no]

You would also need channels to/form the Coordination QM and Command QM.
If this was a clustered environment, just joining the new QM to the cluster would have been all that would have been needed.

If you install the Client only, then, when you configure it, it will ask for the location of the Co-ordination Queue Manager (hostname or IP). There should be no need to configure these channels.
If you are installing FTE Server, then you must also have MQ Server installed, and therefore you should create Channel between the multiple MQ servers.

Audit

The only audit that is available today is what is on the SYSTEM.FTE queue. A new feature will be added in next release to offload that queue and write the contents to a relational database, from there the user can query. You can also write a your own subscription that could write the contents to a log file for users to query.

{bestp}

Top

FTE Best Practices

"ideally each QM hosting an Agent (either server or client) would be its own command QM" {Robert}
it is recommended not to start the WMQ Explorer during the WMQ FTE installation as the installation modifies the WMQ Explorer instance. {WMQ_FTE_zOS_experience_-_cfarkas_-_v1.pdf}

Top

FTE bits and bytes

The -sm or -dm parms are needed ONLY if the -sa or -da agent.properties file for either agent does not exist on the local machine where the transfer request was submitted.
Send a file from zOS containing ñ's, accents (aguts i greus), ç, dièresis, ...
Customer wants to configure own conversion table, and wants to be able to tell FTE what table to use. Where is this table configured to FTE ?
There are FTE Agents for Linux, zOS, Win, Unix, Solaris ...
As there are no agents for Nowell or Unisys, we still can use (and administer) FTP file transfers.
For detailed information on properties files for WMQFTE, please refer to the following link in the infocenter: url
The following are the properties files used by WMQFTE:
- install.properties
- wmqfte.properties
- command.properties
- coordination.properties
- agent.properties
BuzzWords : ant, xml and curl.
Ant @ wiki : software tool for automating software build processes; uses XML to describe the build process and its dependencies.
Curl @ wiki : programming language designed for interactive Web content.
cURL is a freeware program that is used widely to send HTTP requests from the command line.
Homepage : curl is a command line tool for transferring files with URL syntax, supporting FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS and FILE. curl supports SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user+password authentication (Basic, Digest, NTLM, Negotiate, kerberos...), file transfer resume, proxy tunneling and a busload of other useful tricks.

CURL bits

Download software.

Install : unzip "curl_727_0.zip" and use curl.exe from command line.

Available API operations.

Few samples using libcurl

CURL help

Usage: curl [options...] <url> Options: (H) means HTTP/HTTPS only, (F) means FTP only --anyauth Pick "any" authentication method (H) -a, --append Append to target file when uploading (F/SFTP) --basic Use HTTP Basic Authentication (H) --cacert FILE CA certificate to verify peer against (SSL) --capath DIR CA directory to verify peer against (SSL) -E, --cert CERT[:PASSWD] Client certificate file and password (SSL) --cert-type TYPE Certificate file type (DER/PEM/ENG) (SSL) --ciphers LIST SSL ciphers to use (SSL) --compressed Request compressed response (using deflate or gzip) -K, --config FILE Specify which config file to read --connect-timeout SECONDS Maximum time allowed for connection -C, --continue-at OFFSET Resumed transfer offset -b, --cookie STRING/FILE String or file to read cookies from (H) -c, --cookie-jar FILE Write cookies to this file after operation (H) --create-dirs Create necessary local directory hierarchy --crlf Convert LF to CRLF in upload --crlfile FILE Get a CRL list in PEM format from the given file -d, --data DATA HTTP POST data (H) --data-ascii DATA HTTP POST ASCII data (H) --data-binary DATA HTTP POST binary data (H) --data-urlencode DATA HTTP POST data url encoded (H) --delegation STRING GSS-API delegation permission --digest Use HTTP Digest Authentication (H) --disable-eprt Inhibit using EPRT or LPRT (F) --disable-epsv Inhibit using EPSV (F) -D, --dump-header FILE Write the headers to this file --egd-file FILE EGD socket path for random data (SSL) --engine ENGINGE Crypto engine (SSL). "--engine list" for list -f, --fail Fail silently (no output at all) on HTTP errors (H) -F, --form CONTENT Specify HTTP multipart POST data (H) --form-string STRING Specify HTTP multipart POST data (H) --ftp-account DATA Account data string (F) --ftp-alternative-to-user COMMAND String to replace "USER [name]" (F) --ftp-create-dirs Create the remote dirs if not present (F) --ftp-method [MULTICWD/NOCWD/SINGLECWD] Control CWD usage (F) --ftp-pasv Use PASV/EPSV instead of PORT (F) -P, --ftp-port ADR Use PORT with given address instead of PASV (F) --ftp-skip-pasv-ip Skip the IP address for PASV (F) --ftp-pret Send PRET before PASV (for drftpd) (F) --ftp-ssl-ccc Send CCC after authenticating (F) --ftp-ssl-ccc-mode ACTIVE/PASSIVE Set CCC mode (F) --ftp-ssl-control Require SSL/TLS for ftp login, clear for transfer (F) -G, --get Send the -d data with a HTTP GET (H) -g, --globoff Disable URL sequences and ranges using {} and [] -H, --header LINE Custom header to pass to server (H) -I, --head Show document info only -h, --help This help text --hostpubmd5 MD5 Hex encoded MD5 string of the host public key. (SSH) -0, --http1.0 Use HTTP 1.0 (H) --ignore-content-length Ignore the HTTP Content-Length header -i, --include Include protocol headers in the output (H/F) -k, --insecure Allow connections to SSL sites without certs (H) --interface INTERFACE Specify network interface/address to use -4, --ipv4 Resolve name to IPv4 address -6, --ipv6 Resolve name to IPv6 address -j, --junk-session-cookies Ignore session cookies read from file (H) --keepalive-time SECONDS Interval between keepalive probes --key KEY Private key file name (SSL/SSH) --key-type TYPE Private key file type (DER/PEM/ENG) (SSL) --krb LEVEL Enable Kerberos with specified security level (F) --libcurl FILE Dump libcurl equivalent code of this command line --limit-rate RATE Limit transfer speed to this rate -l, --list-only List only names of an FTP directory (F) --local-port RANGE Force use of these local port numbers -L, --location Follow redirects (H) --location-trusted like --location and send auth to other hosts (H) -M, --manual Display the full manual --mail-from FROM Mail from this address --mail-rcpt TO Mail to this receiver(s) --mail-auth AUTH Originator address of the original email --max-filesize BYTES Maximum file size to download (H/F) --max-redirs NUM Maximum number of redirects allowed (H) -m, --max-time SECONDS Maximum time allowed for the transfer --metalink Process given URLs as metalink XML file --negotiate Use HTTP Negotiate Authentication (H) -n, --netrc Must read .netrc for user name and password --netrc-optional Use either .netrc or URL; overrides -n --netrc-file FILE Set up the netrc filename to use -N, --no-buffer Disable buffering of the output stream --no-keepalive Disable keepalive use on the connection --no-sessionid Disable SSL session-ID reusing (SSL) --noproxy List of hosts which do not use proxy --ntlm Use HTTP NTLM authentication (H) -o, --output FILE Write output to instead of stdout --pass PASS Pass phrase for the private key (SSL/SSH) --post301 Do not switch to GET after following a 301 redirect (H) --post302 Do not switch to GET after following a 302 redirect (H) --post303 Do not switch to GET after following a 303 redirect (H) -#, --progress-bar Display transfer progress as a progress bar --proto PROTOCOLS Enable/disable specified protocols --proto-redir PROTOCOLS Enable/disable specified protocols on redirect -x, --proxy [PROTOCOL://]HOST[:PORT] Use proxy on given port --proxy-anyauth Pick "any" proxy authentication method (H) --proxy-basic Use Basic authentication on the proxy (H) --proxy-digest Use Digest authentication on the proxy (H) --proxy-negotiate Use Negotiate authentication on the proxy (H) --proxy-ntlm Use NTLM authentication on the proxy (H) -U, --proxy-user USER[:PASSWORD] Proxy user and password --proxy1.0 HOST[:PORT] Use HTTP/1.0 proxy on given port -p, --proxytunnel Operate through a HTTP proxy tunnel (using CONNECT) --pubkey KEY Public key file name (SSH) -Q, --quote CMD Send command(s) to server before transfer (F/SFTP) --random-file FILE File for reading random data from (SSL) -r, --range RANGE Retrieve only the bytes within a range --raw Do HTTP "raw", without any transfer decoding (H) -e, --referer Referer URL (H) -J, --remote-header-name Use the header-provided filename (H) -O, --remote-name Write output to a file named as the remote file --remote-name-all Use the remote file name for all URLs -R, --remote-time Set the remote file's time on the local output -X, --request COMMAND Specify request command to use --resolve HOST:PORT:ADDRESS Force resolve of HOST:PORT to ADDRESS --retry NUM Retry request NUM times if transient problems occur --retry-delay SECONDS When retrying, wait this many seconds between each --retry-max-time SECONDS Retry only within this period -S, --show-error Show error. With -s, make curl show errors when they occur -s, --silent Silent mode. Don't output anything --socks4 HOST[:PORT] SOCKS4 proxy on given host + port --socks4a HOST[:PORT] SOCKS4a proxy on given host + port --socks5 HOST[:PORT] SOCKS5 proxy on given host + port --socks5-hostname HOST[:PORT] SOCKS5 proxy, pass host name to proxy -Y, --speed-limit RATE Stop transfers below speed-limit for 'speed-time' secs -y, --speed-time SECONDS Time for trig speed-limit abort. Defaults to 30 --ssl Try SSL/TLS (FTP, IMAP, POP3, SMTP) --ssl-reqd Require SSL/TLS (FTP, IMAP, POP3, SMTP) -2, --sslv2 Use SSLv2 (SSL) -3, --sslv3 Use SSLv3 (SSL) --ssl-allow-beast Allow security flaw to improve interop (SSL) --stderr FILE Where to redirect stderr. - means stdout --tcp-nodelay Use the TCP_NODELAY option -t, --telnet-option OPT=VAL Set telnet option --tftp-blksize VALUE Set TFTP BLKSIZE option (must be >512) -z, --time-cond TIME Transfer based on a time condition -1, --tlsv1 Use TLSv1 (SSL) --trace FILE Write a debug trace to the given file --trace-ascii FILE Like --trace but without the hex output --trace-time Add time stamps to trace/verbose output --tr-encoding Request compressed transfer encoding (H) -T, --upload-file FILE Transfer FILE to destination --url URL URL to work with -B, --use-ascii Use ASCII/text transfer -u, --user USER[:PASSWORD] Server user and password --tlsuser USER TLS username --tlspassword STRING TLS password --tlsauthtype STRING TLS authentication type (default SRP) -A, --user-agent STRING User-Agent to send to server (H) -v, --verbose Make the operation more talkative -V, --version Show version number and quit -w, --write-out FORMAT What to output after completion --xattr Store metadata in extended file attributes -q If used as the first parameter disables .curlrc

CURL progs

#include <stdio.h> #include <curl/curl.h> int main(void) { CURL *curl; CURLcode res; curl = curl_easy_init(); if(curl) { curl_easy_setopt(curl, CURLOPT_URL, "http://example.com"); /* Perform the request, res will get the return code */ res = curl_easy_perform(curl); /* Check for errors */ if(res != CURLE_OK) fprintf(stderr, "curl_easy_perform() failed: {%s}.\n", curl_easy_strerror(res)); /* always cleanup */ curl_easy_cleanup(curl); } return 0; }

MQ FTE

Links