The
Agentry
Server runs
in the standard SAP Mobile Platform clustered environment. 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 do 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. The instructions provided for other archetypes
within the SAP Mobile Platform are not applicable to Agentry applications.
The
configuration of the load balancer should meet 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.
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.