Specifications

Architecture
17
Introduction
Customer site components
ESRS requires the following software and hardware at the customer
site:
Gateway Client(s) — This ESRS software component is installed
on a customer-supplied dedicated server or Hyper-V/VMware
instance. It can also be installed on multiple servers. The servers
act as the single point of entry and exit for all IP-based remote
support activities and most EMC connect home notifications.
Embedded ESRS Device clients: This ESRS software component
is integrated on some EMC Products and utilizes the same
technology as the ESRS Gateway Client. If the Embedded ESRS
Device Client is utilized, the device is not managed by an ESRS
Gateway Client. The the Embedded ESRS Device Client can also
use the same or a different Policy Manager as an ESRS Gateway
Client and enforces the policy, and audits just like an ESRS
Gateway Client but only on that specific device.
Policy Manager — This ESRS software component is installed on
a customer-supplied server or servers. It can be configured to
control remote access to your devices and maintain an audit log
of remote connections, file transfers connect homes) by the ESRS
Clients, and access to and administration actions performed on
the Policy Manager.
Gateway Clients The ESRS Gateway Client is the remote support solution application
that is installed on one or more customer-supplied dedicated servers.
The Gateway Client(s) become the single point of entry and exit for
all IP-based EMC remote support activities for the devices associated
with that particular Gateway or Gateway Cluster.
The Gateway Clients function as communication brokers between the
managed devices, the Policy Manager, and the EMC enterprise. The
Gateway Clients are HTTPS handlers and all messages are encoded
using standard XML and SOAP application protocols. Gateway
Client message types include:
◆ Device state heartbeat polling
◆ Connect homes
◆ Remote access session initiation
◆ User authentication requests
◆ Device management synchronization