[Daniel Rivera]

Partner A has two deliver exchanges. Exchange 1 uses http, and Exchange 2 uses ftp. Is it possible to send certain documents using exchange 2 while letting all other documents use exchange 1?

[remery]

You cannot have a single community send to two different exchanges on a partner.

What you can do....
If you have two local communities you can configured Community 1 to send to Partner A - Exchange 1. And Community 2 can be configured to send to Partner A - Exchange 2. Two enable this functionality you would need to specialize collaboration settings for one of the Communities. Lets say that Community 1 wants to use HTTP, Community 2 wants to use FTP. On Partner A - Exchange 1 is the default and is HTTP. Under collaboration settings - specialize settings for Community 2 - Partner A. And set the desired delivery exchange to Exchange 2.


I hope this is helpful,
ric

Partner A has two deliver exchanges. Exchange 1 uses http, and Exchange 2 uses ftp. Is it possible to send certain documents using exchange 2 while letting all other documents use exchange 1?

[Daniel Rivera]

While it is helpful, it is also not ideal at all. In creating a second community, you now have different sets of RoutingID's, certificates, etc... I had thought of creating a second instance of the partner, but soon abandoned it for the same problems your solution has. It sounds like there is no good solution to this problem.

You cannot have a single community send to two different exchanges on a partner.

What you can do....
If you have two local communities you can configured Community 1 to send to Partner A - Exchange 1. And Community 2 can be configured to send to Partner A - Exchange 2. Two enable this functionality you would need to specialize collaboration settings for one of the Communities. Lets say that Community 1 wants to use HTTP, Community 2 wants to use FTP. On Partner A - Exchange 1 is the default and is HTTP. Under collaboration settings - specialize settings for Community 2 - Partner A. And set the desired delivery exchange to Exchange 2.


I hope this is helpful,
ric

[remery]

Either having two partners, or creating 2 communities are your best choices for your use case. There is not currently (as of Interchange 5.7.1) a way within Interchange to route messages too two different Delivery Exchange Types based on the document type being sent. Sorry I can't be of more help.

Regards,
Ric

While it is helpful, it is also not ideal at all. In creating a second community, you now have different sets of RoutingID's, certificates, etc... I had thought of creating a second instance of the partner, but soon abandoned it for the same problems your solution has. It sounds like there is no good solution to this problem.