Internal HPDM Repository for External Clients

2
Introduction
To configure a HP Device Manager Repository to service Thin Clients that are separated by a NAT firewall takes some behind
the scenes magic.
The HPDM Server and the HPDM Repository are separate pieces of HPDM infrastructure. In the scenario where all components
are installed together, the MRC and Console refers to the same hosts file. The MRC and Console need to “see” the HPDM
Repository using the same name as external clients use to access the HPDM Repository. While the HPDM Server will resolve
the name to a different IP address than the external thin clients, as there is a common name, everything works.
Note: HPDM Agent to HPDM Gateway traffic is handled differently than HPDM Agent to HPDM Repository traffic. While HPDM
Agent locks onto the IP address of the HPDM Gateway, the HPDM Repository address is supplied at the start of every task.
External (outside NAT firewall) clients can connect to the HPDM Gateway component via an external IP address without extra
HPDM configuration required. The only environment configuration required is an external to internal address mapping on the
NAT firewall.
For more information on HPDM go to www.hp.com/go/hpdm
To access the HP Device Manager Admin Guide for V5.0, please go to:
https://ftp.hp.com/pub/hpdm/Documentation/AdminGuide/5.0/HP_Device_Manager_5.0.3_Administrator_Guide_en_US.pdf