The client is invoked without hard coding transports.
The setup is dynamic and can be changed on the server at any time!

Settings sample

---------------------------------------------------------------
-- TransportClientSettings.json
---------------------------------------------------------------
{
"TransportMgrApiUrl": "[TransportManagerApiUrl]",
"TransportClientEndpointCode": "[TransportClientEndpointCode]",
"TransportClientSecretKey": "[TransportClientSecretKey]",
"AS2ISCode": "",
"AS2ISSecretKey": "",
"ServiceProcessingPath": "[TransportClientRoot]\\ThruTransportClient\\_TrClientProcessing",
"PushSourceFolderPath": "[TransportClientRoot]\\ThruTransportClient\\PUSH",
"PushSourceFolderXferPath": "[TransportClientRoot]\\ThruTransportClient\\PUSH\\XFER",
"PushIsFileDeletion": false,
"PushIsPGPEncryption": false,
"PullTargetFolderPath": "[TransportClientRoot]\\ThruTransportClient\\PULL",
"PullTargetFolderXferPath": "[TransportClientRoot]\\ThruTransportClient\\PULL\\XFER",
"PullIsFileOverwrite": true,
"PullIsPGPDecryption": false,
"PullPGPDecryptionPrivateKeyFilePath": "",
"PullPGPDecryptionPrivateKeyPassPhrase": ""
}

Push to a single source transport

ThruTransportClient -c push -s “TransportClientSettingsExample.json” -t auto

Pull from multiple transports

ThruTransportClient -c pull -s “TransportClientSettingsExample.json”

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment