Interchange 5.12 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content HTTP trading and Secure Relay When using Secure Relay and your community trades with partners via HTTP, follow these guidelines: On the transport maintenance page for your community, in the field named URL used by partners, the URL must specify the host and port of the computer running the DMZ node and not the computer running Interchange. If you trade via HTTPS, the common name of the SSL certificate must be the fully qualified domain name of the computer running the DMZ node and not the computer running Interchange. For more information about adding SSL certificates see Embedded transport servers. Related topics Secure Relay DMZ nodes Overview of Secure Relay nodes Add DMZ zones Add a DMZ node Run node as Windows service Enable port forwarding for an exchange Configure load balancer or firewall Configure outbound connection proxy Manage IP address whitelists Related Links
HTTP trading and Secure Relay When using Secure Relay and your community trades with partners via HTTP, follow these guidelines: On the transport maintenance page for your community, in the field named URL used by partners, the URL must specify the host and port of the computer running the DMZ node and not the computer running Interchange. If you trade via HTTPS, the common name of the SSL certificate must be the fully qualified domain name of the computer running the DMZ node and not the computer running Interchange. For more information about adding SSL certificates see Embedded transport servers. Related topics Secure Relay DMZ nodes Overview of Secure Relay nodes Add DMZ zones Add a DMZ node Run node as Windows service Enable port forwarding for an exchange Configure load balancer or firewall Configure outbound connection proxy Manage IP address whitelists