Interchange 5.12 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content High availability staged HTTP The following figure shows the staged HTTP servlet in a high availability configuration to handle inbound traffic. This involves setting up servlets on multiple web servers. A load balancer is used to direct traffic to each web server. The partner uses the virtual IP address of the load balancer in sending messages. In this clustered example, each instance of Interchange needs a staged HTTP delivery exchange for receiving messages from partners. The following describes the process illustrated in the figure. Inbound documents are routed to either staged HTTP servlet. The staged HTTP servlet receives the request and persists it to temporary storage (non-clustered storage). If the message requires a synchronous acknowledgement, the inbound connection is held open. Each instance of Interchange is configured to poll each staged HTTP servlet. Interchange receives inbound document by issuing: HTTP GET for listing of all inbound documents. HTTP GET for each inbound document HTTP DELETE to remove the document from temporary storage. If the received message requires a synchronous acknowledgement, Interchange produces the acknowledgement back to the consuming staged HTTP servlet so it can be produced back to the original inbound connection. Related topics Overview of staged HTTP Staged HTTP configuration outline Staged HTTP files to deploy Log on to servlet UI Manage mailboxes Staged HTTP UI fields Message protocols for staged HTTP File forwarding to bypass polling Deploy the web servlet Related Links
High availability staged HTTP The following figure shows the staged HTTP servlet in a high availability configuration to handle inbound traffic. This involves setting up servlets on multiple web servers. A load balancer is used to direct traffic to each web server. The partner uses the virtual IP address of the load balancer in sending messages. In this clustered example, each instance of Interchange needs a staged HTTP delivery exchange for receiving messages from partners. The following describes the process illustrated in the figure. Inbound documents are routed to either staged HTTP servlet. The staged HTTP servlet receives the request and persists it to temporary storage (non-clustered storage). If the message requires a synchronous acknowledgement, the inbound connection is held open. Each instance of Interchange is configured to poll each staged HTTP servlet. Interchange receives inbound document by issuing: HTTP GET for listing of all inbound documents. HTTP GET for each inbound document HTTP DELETE to remove the document from temporary storage. If the received message requires a synchronous acknowledgement, Interchange produces the acknowledgement back to the consuming staged HTTP servlet so it can be produced back to the original inbound connection. Related topics Overview of staged HTTP Staged HTTP configuration outline Staged HTTP files to deploy Log on to servlet UI Manage mailboxes Staged HTTP UI fields Message protocols for staged HTTP File forwarding to bypass polling Deploy the web servlet