Transport Client Usage

This program implements a transport endpoint for the Thru server. It uses Thru Web API.

You can use the program to push a single file to landing or pull the next delivery file from the Thru server.

Arguments List: (Square brackets indicate optional arguments)

• -? ………………………………………….. Show usage and exit
• [-s customJsonSettings] ……………………….. [TransportClientSettings.json] Custom config file
• -c command …………………………………… push | pull | install | uninstall

Push Parameters

• -t transportCode ……………………………. Transport public code
• [-o privateDeliveryTargetOrgPublicCode] ……….. Push private delivery target organization public code
• [-f sourceFilePath] …………………………. Push file path – Use double quotes if path contains spaces. If omitted, all pending files are pushed from source.
• [-win]……………………………………… Removes all characters from file names that are unsupported in the NTFS file system

Pull Parameters

• [-N] ………………………………………. Pull only the next pending file. If omitted, all pending files are pulled to target.

Install Parameters

• -a apiUrl ………………………………….. OptiPaaS API URL
• -v version …………………………………. Version
• -r transportClientRootFolder …………………. Path to the transport client root folder
• -i installationKey ………………………….. Installation key

Uninstall Parameters

• -s [customJsonSettings] ………………………. [TransportClientSettings.json] Custom config file

Example :

Can be used by the enterprise or the partners to avoid sftp and can be embedded into scripted/batch processes.