The Agentry
Server runs in the standard SAP Mobile Platform clustered environment.
When
an Agentry Server is added to a node, it replicates out to all other nodes in the cluster.
The following items are important to note concerning the configuration of the Agentry Server and
the network environment when running in the SAP Mobile Platform clustered environment:
- The network environment must include a load balancer that sits
logically between the Agentry
Clients
and the Agentry
Servers within the SAP Mobile Platform nodes within the cluster.
The configuration of this load balancer is separate and different from the load
balancer for other archetypes within SAP Mobile Platform in that Agentry
client-server communications are not routed through the Relay Server.
- As a part of the communications security between the Agentry
Clients and Agentry
Server there is an
encryption key which includes a public and private key pairing. For each Agentry
Server this key
pairing is unique by default. The result of this behavior is that an Agentry
Client is tied to a
given Agentry
Server after its
initial transmit. Attempting to connect with another Agentry
Server with a
different encryption key will result in an error and will not complete
successfully. For this reason, the utility AgentryKeyUtility is
provided with each Agentry
Server installation
and is used to export the encryption key from on Agentry
Server instance and to
then import this key into all other Agentry
Server instances
within a cluster.
For information on using the AgentryKeyUtility see
the procedure SAP Mobile Platform Clustering: Configuring Agentry
Applications. For additional guidance on configuring a load
balancer, read on.
Load Balancer and SAP Mobile Platform Cluster with Agentry Applications
The
load balancer configuration for Agentry applications operating within the SAP Mobile
Platform cluster is a typical configuration that routes traffic to the Agentry
Server, as determined by the overall configuration of the load balancer. Agentry
clients contact the load balancer IP address and port, rather than an Agentry
Server's IP address and port. The instructions provided for other archetypes within
the SAP Mobile Platform are not applicable to Agentry applications.
Ensure that the configuration of the load balancer meets the following criteria:
- The load balancer should sit logically within the network
between the Agentry
Clients and the SAP Mobile Platform cluster.
- The Agentry
Clients should all connect to the IP address and port of the
load balancer.
- The load balancer should redirect traffic from Agentry
Clients to the Agentry
Servers running within the SAP Mobile Platform cluster
directly.
This traffic must not be routed through the Relay Server provided with SAP
Mobile Platform, which is used for other archetypes within the platform, but
not supported for Agentry.
There are no additional requirements beyond those of a standard load balancer
implementation. The client-server communications for Agentry applications use
standard TCP/IP communications as a part of the ANGEL connect type for transmit
configurations.