Perimeter network environments

There may be scenarios where you want to have an on-premises environment or the Dashboards components accessible from outside a private network.

This diagram shows the basic architecture for using a perimeter network environment to access components behind a firewall:

Perimeter network environment diagram

Public network

User device refers to the device used to connect to Infor d/EPM. For example, a desktop, laptop, mobile device, or tablet.

Standard reverse proxy / Load balancer server is a public-facing server that is used as a reverse proxy | load balancer to reroute traffic through a firewall to the perimeter network.

If you have Office Integration manager in the perimeter network , you need a separate standard reverse proxy / load balancer in front of theOffice Integration manager.

The firewall between the public network and the perimeter network must have open ports to communicate with the Dashboards Service and Office Integration Service managers. The firewall acts as a network isolator.

Perimeter network

The Dashboards Service and, optionally, the Office Integration Service managers, are located on the perimeter network. These services are used as reverse proxies to route traffic to the service managers and workers.

Full clients can exist on the perimeter network, meaning they are installed on a server and users connect to a remote desktop session to use them.

The firewall between the perimeter network and the private network must have open ports in order to communicate with the managers and workers.

Private network

The private network is where the scaling servers, primary server, and the OLAP server are located. The Office Integration managers can also be on the private network.

The scaling servers are for these workers:

  • Dashboards Service workers
  • Application Engine Service workers
  • Application Studio Service workers
  • Office Integration Service workers

    The Office Integration Service can also be on the primary server if the number of users does not require a scaling server.

The primary server is for these workers and managers:

  • Application Engine Service manager
  • Application Studio Service manager
  • Configuration Service worker
  • Repository Service manager / worker
  • Modeling Service manager / worker
  • Consolidation Service manager / worker
  • d/EPM Applications Service manager / worker
  • OLAP Service manager / worker

The OLAP server is for the database workers and cluster nodes.