B2B Integration

Expand all | Collapse all

Alternate destination for failed FSG delivery

  • 1.  Alternate destination for failed FSG delivery

    Posted 25 days ago
    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
    ------------------------------


  • 2.  RE: Alternate destination for failed FSG delivery

    Posted 25 days ago
    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
    ------------------------------



  • 3.  RE: Alternate destination for failed FSG delivery

    Posted 25 days ago

    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
    ------------------------------



  • 4.  RE: Alternate destination for failed FSG delivery

    Posted 24 days ago
    Edited by Michael Geier 24 days ago

    Using a custom delivery protocol would allow you to build a delivery BP that can do anything you wish.  And as part of that protocol, you could collect the primary and alternate delivery channel configuration the process would use, if needed.

    Example:

    1. Prepare file
    2. Attempt connection to primary
      1. If successful, perform any additional connectivity steps (ex. SFTP Client CD Service)
      2. If failed status, reset status value and attempt connection to alternate
    3. If failed status, raise error

      https://www.ibm.com/docs/en/file-gateway/2.2?topic=capabilities-adding-custom-protocols

      ------------------------------
      Michael Geier
      IT Engineer 3
      Enterprise Holdings, Inc
      St. Louis MO
      ------------------------------



  • 5.  RE: Alternate destination for failed FSG delivery

    Posted 24 days ago
    Thankyou Michael.

    Appreciate the helpful response!

    ------------------------------
    Regards,
    Andrew Plumb
    ------------------------------