Using a Perimeter Server in a Clustered Installation

In a clustered environment, each node must be configured with one or more perimeter servers, which is communication management software installed in a Demilitarized Zone (DMZ).

Sterling B2B Integrator uses the perimeter server to minimize firewall/DMZ issues, enhance scalability, efficiently handle large files, and improve performance.

The perimeter server is tied to a node; adapters/services that use perimeter services (such as FTP, Sterling Connect:Direct®, and the HTTP adapter) must use service groups for load balancing and failover.

The perimeter server has a one-to-one relationship with the client. Because the perimeter server is tied to a particular node, adapters and services that are using the perimeter server also must be deployed in that particular node. Multiple adapters and services can use a single perimeter server.

Inbound Load Balancing and Failover Using a Third Party Vendor

A third party vendor such as Network Dispatcher can be employed for load balancing and failover.

The following figure shows a typical configuration for perimeter server for high availability:

This can be extended to more servers in the cluster or in the DMZ, with the following restrictions:

• All adapter instances must have compatible (nearly identical) configurations.
• For inbound (server) load-balancing and failover, either the DMZ hosts must support virtual IP addressing to sepa rate the listening port of the Perimeter servers, or the load balancer must do Port Address Translation (PAT).

Outbound Load Balancing with Service Controller

Outbound traffic is load-balanced by using Service Controller and Service Group.

For outbound (client) load balancing and failover, all of the adapter instances must be placed in the same group. Business processes must reference this group rather than a specific adapter instance.

The following figure demonstrates how load balancing works with a Service Controller: