This scenario uses two server aliases, one for SSL-enabled external communication between Oracle HTTP Server and browsers (for example, epm.myCompany.com), and the other for routing internal non-SSL communication among EPM System servers (for example, empinternal.myCompany.com). Oracle recommends that you use a certificate tied to the server alias for external communication to prevent exposing server names to users.
You add server aliases in the hosts file on the machine. Ensure that the server aliases point to the IP address of the machine that hosts Oracle HTTP Server. Clients must resolve these aliases through DNS.