Thanks for the response Jack.
Apologies, I could have been a little more specific. My question was in relation to SFTP transmission protocol.
I understand that the CD protocol may have a built-in feature to attempt connection to an alternate endpoint if the definition for the Snode has any "Alternate Comm Info".... but I don't believe there is any such ability or configuration for SFTP.
So I'm wondering how best to configure SFG to handle a failure to an SFTP endpoint. For example if your partner has two SFTP servers to allow for resiliency, and there is no load balancer or other device to handle the failover at the network level, and so you configure a single SSH remote profile for the primary server of your partner. If that server is down, is there any way to automatically divert a different SSH profile for the secondary server / or otherwise override the configured destination ?
------------------------------
Andrew Plumb
------------------------------
Original Message:
Sent: Wed September 01, 2021 02:16 AM
From: Wai Man Wong
Subject: Alternate destination for failed FSG delivery
Hi,
When SFG route the file to a listening consumer, only one remote profile is used for remote connection like CDSA or SFTP remote profile.
Do you mean SFG will try another remote profile when the primary channel failed? i.e. when CDSA connection failed then it try SFTP connection?
Regards,Jack
------------------------------
Wai Man Wong
Original Message:
Sent: Tue August 31, 2021 08:36 AM
From: Andrew Plumb
Subject: Alternate destination for failed FSG delivery
Hi all,
I'm wondering if anyone is aware of a SFG method to automate the delivery of a file to an alternate channel if delivery via a primary channel fails ?
------------------------------
Regards,
Andrew Plumb
------------------------------
#B2BIntegration
#SupplyChain