Configuring IBM Sterling Secure Proxy with IBM B2B Advanced Communications for high availability
Ensure secure AS4 communication with SSP and load balancers
From the developerWorks archives
Date archived: January 4, 2017 | First published: August 26, 2015
This article discusses how to configure IBM® B2B Advanced Communications with IBM Sterling Secure Proxy and a load balancer for achieving high availability in case one of the SSP nodes fails. Prior knowledge of HTTP proxies and load balancers is helpful to better understand this article. The proxy that is used is IBM Sterling Secure Proxy, and the load balancer that is used is Apache. The setup involves two load balancers with a virtual IP address and two independent Sterling Secure Proxy installations. Also, B2B Advanced Communications is installed in a collective mode with both nodes capable of handling the incoming requests, processing them and responding properly back to the trading partner. This configuration helps in achieving secure AS4 communications that use the Sterling Secure Proxy by not reveling the actual B2B Advanced Communication Integration Enterprise Gateway host details. The load is balanced at the load balancer level that is at the receiving end for the request and routed to both Sterling Secure Proxy hosts. The requests then reach the B2B Advanced Communications. The key advantage is that if one of the SSP fails, the other is able to handle the requests and reroute them to the B2B Advanced Communications collective instances.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.