Depm 2022.01 Hardware Software Recommendations En-Us

Infor Dynamic Enterprise
Performance Management Hardware

and Software Recommendations
Guide (On-premises)
Release 2022.01
Copyright © 2021 Infor
Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the Purpose
described above. Although Infor has taken due care to ensure that the material included in this publication
is accurate and complete, Infor cannot warrant that the information contained in this publication is
complete, does not contain typographical or other errors, or will meet your specific requirements. As
such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss
or damage to any person or entity which is caused by or relates to errors or omissions in this publication
(including any supplementary information), whether such errors or omissions result from negligence,
accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or
related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service
names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor Dynamic Enterprise Performance Management (d/EPM) 2022.01
Publication Date: December 10, 2021
Document code: depm_2022.01_hardware_software_recommendations__en-us
Contents
Contents
Contacting Infor..................................................................................................................................5
Chapter 1: Overview of the hardware and software recommendations........................................6
Chapter 2: Platform support..............................................................................................................7

Support terms....................................................................................................................................7
Migration............................................................................................................................................7
Relational database systems for farm installations...........................................................................7
Relational database systems as business database.........................................................................8
Multidimensional databases - Infor d/EPM Platform..........................................................................8
Multidimensional databases - Infor d/EPM business applications.....................................................9
Server platforms................................................................................................................................9
Client platforms...............................................................................................................................10
Microsoft .NET.............................................................................................................................10
Infor d/EPM mobile applications......................................................................................................10
Infor Operating Service...................................................................................................................11
Infor Landmark Runtime..................................................................................................................11
Browsers - Infor d/EPM Platform.....................................................................................................11
Browsers - Infor d/EPM business applications................................................................................12
Office Integration.............................................................................................................................12
Virtual environments........................................................................................................................13
Chapter 3: Hardware recommendations.........................................................................................14
Architecture.....................................................................................................................................14
Perimeter network environments.................................................................................................15
Infor Operating Service................................................................................................................16
Farm.............................................................................................................................................17
Worker and manager services.....................................................................................................17
Services.......................................................................................................................................17
Infor Dynamic Enterprise Performance Management Hardware and Software Recommendations Guide
(On-premises) | 3
Contents
Farm Expert and Service Expert.................................................................................................22

d/EPM Administration..................................................................................................................22
Front-end applications..................................................................................................................23
Applications..................................................................................................................................23
Tools for designing applications...................................................................................................24
ETL and modeling tools...................................................................................................................24
Performance warranty.....................................................................................................................25
Sizing...............................................................................................................................................25
Application factors........................................................................................................................25
Hard disk space and type............................................................................................................26
Users............................................................................................................................................27
Network server infrastructure.......................................................................................................27
Virtualized environments..............................................................................................................27
Server types....................................................................................................................................28
Single server (test or development system).................................................................................29
Enterprise topology......................................................................................................................30
Desktop computers.........................................................................................................................32
Application growth...........................................................................................................................33
Performance monitoring of applications and tools...........................................................................33
Measurement tools......................................................................................................................33
Monitoring the OLAP Service......................................................................................................34
Application Studio database requests..........................................................................................35
(On-premises) | 4
Contacting Infor
Contacting Infor
If you have questions about Infor products, go to Infor Concierge at https://concierge.infor.com/ and
create a support incident.
The latest documentation is available from docs.infor.com or from the Infor Support Portal. To access
documentation on the Infor Support Portal, select Search > Browse Documentation. We recommend
that you check this portal periodically for updated documentation.
If you have comments about Infor documentation, contact documentation@infor.com.
(On-premises) | 5
Overview of the hardware and software recommendations
Chapter 1: Overview of the hardware and software

recommendations
This document describes the hardware and software recommendations for the on-premises version of
Infor d/EPM Platform and the Infor d/EPM business applications.
(On-premises) | 6
Platform support
Chapter 2: Platform support
This section describes support levels for the various platforms for on-premises installations of Infor
d/EPM Platform and the Infor d/EPM business applications.
There are several prerequisites that must be installed before you can start the installation.
Support terms
A supported environment is one where we have system-tested the applications and have the resources
in place to recreate customer problems. We will assist with third-party support coordination (for those
products that are licensed through us) for products which are supported.
An unsupported environment is one where we have business reasons to believe that our applications
will not operate properly or are not supportable.
Migration
This release is based on the services architecture of the Infor d/EPM Platform (formerly Infor BI).
This document describes the supported environments. Contact support if you want to migrate from an
environment with components that are not listed below.
Relational database systems for farm installations

Relational farm databases are included in an installation. These databases are included:
• BIFarmRepository
• BIFarmConfig
• BIFarmLog
• BIFarmdEPMStaging
These databases are included for Infor d/EPM business applications based on Business Modeling:
(On-premises) | 7
Platform support
• BIFarmModel
• BIFarmConsolidation
These databases are included for Infor d/EPM business applications based on Designer:
• DEPMInteg
• DEPMDesign
• DEPMChange
This table shows the supported database systems for relational farm databases:
Relational databases Support level Notes

Microsoft SQL Server 2019 Standard and Enter- Supported Recommended
prise Editions
Microsoft SQL Server 2017 Standard and Enter- Supported
prise Editions
Microsoft SQL Server 2016 with Service Pack Supported Will be deprecated in
2 Standard and Enterprise Editions a future release.
PostgreSQL 10 and higher Supported for Infor d/EPM
Platform
Relational database systems as business database

A business database is a database that provides data. Business databases can be used by modeling
to fill OLAP databases (mappings), by Application Studio to create relational reports, or by Process
Editor to run processes.
Data sources with support ODBC and OLEDB like Microsoft SQL Server or Oracle are supported. It is
recommended to use the latest version. SQL Server cluster is supported.
Relational modeling supports database systems that support Ansi92 formatted SQL.
Multidimensional databases - Infor d/EPM Platform

This table shows the supported multidimensional database systems for Infor d/EPM Platform:
(On-premises) | 8
Platform support
Multidimensional databases Support level Notes

OLAP 64-bit Supported Recommended
OLAP is released
monthly. The current
monthly release is sup-
ported.
Microsoft Analysis Services 2019 Standard and Supported
Enterprise Edition
Microsoft Analysis Services 2017 Standard and Supported
Enterprise Edition
Microsoft Analysis Services 2016 with Service Supported
Pack 2 Standard and Enterprise Editions
Microsoft Analysis Services 2014 with Service Supported
Pack 2 Standard and Enterprise Editions
See Knowledge Base Article 1398688 on the Infor Support Portal for further information.
Multidimensional databases - Infor d/EPM business

applications
This table shows the supported multidimensional database systems for Infor d/EPM business
applications:
Multidimensional databases Support level Notes

OLAP 64-bit Supported OLAP is released monthly. The current
monthly release is supported.
Microsoft Analysis Services Not supported You must use the OLAP component of Infor
d/EPM Platform.
Server platforms
This table shows the supported operating systems for the server platform:
Operating system Support level Notes

Microsoft Windows Server 2022 Supported Recommended
Microsoft Windows Server 2019 Supported
(On-premises) | 9
Platform support
Operating system Support level Notes

Microsoft Windows Server 2016 Supported Will be deprecated in a future
release.
These are the only supported platforms for Infor d/EPM Platform server installations.
Client platforms
This table shows the supported operating systems for client products such as Application Studio:
Operating systems Support level Notes

Microsoft Windows 10, 64-bit with Fall Creators Update Supported
Pro and Enterprise
Infor d/EPM mobile applications

This table shows the supported operating systems for the mobile applications:
Operating systems Support level Notes

iOS on iPhone, iPadOS on iPad, Supported See the Apple App Store for the supported
and watchOS on Apple Watch versions.
Android on tablets and phones Supported See the Google Play Store for the support-
ed versions.
macOS on Apple computers See the Mac App Store for the supported
versions. The minimum supported version
is Catalina.
Microsoft .NET
Microsoft® .NET 4.7.2. is required.

The Infor d/EPM business applications are not supported on the Infor d/EPM mobile applications
because of content limitations.
(On-premises) | 10
Platform support
Infor Operating Service

This table shows the supported Infor OS versions:
Infor OS Support level Notes

Infor OS 12.0.40 (or Supported This platform includes these products:
higher) • Infor Ming.le
• Infor ION
• Infor ION Grid
• Infor Document Management
• Infor Data Lake
• Analytics
• Localization Services
• Infor Security Token Service
Infor Landmark Runtime

Infor Landmark Technology provides the runtime environment needed to run Landmark applications.
This table shows the supported Landmark versions:
Landmark Support level Notes

Infor Landmark Runtime Technology 11.0.9.0.5617 Supported
(or higher)
Browsers - Infor d/EPM Platform

This table shows the supported browsers for Infor d/EPM Platform:
Browsers Support level Notes

Latest Microsoft Edge for Microsoft Win- Supported Chromium based
dows
Latest Google Chrome 64-bit for Microsoft Supported
Windows
Latest Google Chrome, 64-bit on Mac OS Supported
Google Chrome on iOS Not supported Use the Infor d/EPM mobile
application.
(On-premises) | 11
Platform support

Google Chrome on Android Not supported Use the Infor d/EPM mobile
application.
Latest Safari on Mac OS Supported
Latest Safari on iOS on iPad and iPhone Not supported Use the Infor d/EPM mobile
application.
Browsers - Infor d/EPM business applications

This table shows the supported browsers for Infor d/EPM business applications:

Latest Microsoft Edge for Microsoft Windows Supported Chromium based
Latest Google Chrome 64-bit for Microsoft Win- Supported
dows
Latest Google Chrome, 64-bit on Mac OS Supported
Latest Safari on Mac OS Supported
Office Integration
This table shows the Microsoft Office versions that are required to use Excel Integration or Word
Integration:
Microsoft Office versions Support level Notes

Microsoft Office 2021 Supported Office 2021 with the perpetual license does not
include feature updates.
The availability of some Office Integration features
depend on Microsoft updates.
Microsoft Office 365/Microsoft Supported At a minimum, client environments should use the
365 App for Windows, version semi-annual update channel.
1903 or later The availability of some Office Integration features
Using the latest current channel (monthly channel)
is strongly recommended.
(On-premises) | 12
Platform support
Microsoft Office versions Support level Notes

Microsoft Office 365/Microsoft Supported At a minimum, client environments should use the
365 App for MacOS, version semi-annual update channel.
16.24 or later The availability of some Office Integration features
Using the latest current channel (monthly channel)
is strongly recommended.
Microsoft Office 2019 Not supported
Microsoft Office 2016 Not supported
See Knowledge Base Article 2064499 on the Infor Support Portal for further information about Microsoft
Office version requirements and how to identify which version you have.
Virtual environments
Because of the overheads inherent in virtualization, additional resources may have to be allocated to
a virtualized environment to match the performance of a non-virtualized environment.
(On-premises) | 13
Hardware recommendations
Chapter 3: Hardware recommendations
The recommendations given in this section represent a good faith effort to identify recommended
hardware configurations for Infor d/EPM.
Be aware that your initial hardware configuration might not be adequate in the future and, you may
need to upgrade hardware to accommodate application growth and expansion. Use the recommendations
as a starting point for a general configuration and then monitor performance over time.
See the Infor Operating Service Installation Guide for information on sizing Infor OS.
Architecture
The Infor d/EPM architecture is services based.
This diagram shows the basic infrastructure:
Infor d/EPM infrastructure Additional infrastructure
Primary server
OLAP server
(Services and SQL Server or
(A single
most of the database host
machine)
Workers)
<>
Infor OS
Scaling server 1 ... Scaling server 2 ... Scaling server n (Optional for
IFS)
(On-premises) | 14
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:
Public network Perimeter network Private network
Standard
reverse proxy / Dashboards
Scaling servers
Load balancer manager
server
Firewall
Firewall
User device
Standard Office
reverse proxy / Integration
Primary server
Load balancer manager
server (optional)
Dedicated
remote desktop
OLAP server
protocol for full
clients
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.
(On-premises) | 15
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.
Infor Operating Service

Infor OS is a collection of Infor applications, databases, and services that work together to enable a
set of integrated features provided by those products.
Infor OS is a foundation component of the deployed Infor products. Infor OS provides key functional
areas of security, mobile access, integration, and document storage for both intranet and internet users
across an enterprise. Infor OS is scalable and configurable to provide high availability if properly planned
processes are followed.
Infor OS is required if you plan to use Infor Federation Services.
(On-premises) | 16
See the Infor Operating Service Installation Guide Release 2020-x on the Infor Support Portal for
information.
Farm
A farm is a set of Infor d/EPM Platform services which are configured to run together.
That means that a set of services that communicate with each other are working together in a farm. A
distributed farm installed to multiple computers provides scalability and failover. For testing and
familiarization purposes you can install all services on a single computer. Typically, a production farm
is installed over multiple computers.
Worker and manager services

All services, except the Configuration Service, include service workers and managers.
A service manager is the entry point to a service. It receives all requests within, and from outside, the
farm and allocates them to a service worker. The service manager is responsible for load-balancing,
monitoring, and failover. It is also the service through which service workers communicate with each
other.
A service worker is the software application. It performs the tasks associated with each request, such
as data retrieval and storage.
Infor d/EPM Platform services talk to each other and some of the services can be contacted from
outside the farm. Communication is always handled by managers which are the front-facing part of
Infor d/EPM Platform services. Managers are internal and cannot be contacted directly.
Services
Each service has a specific purpose. For example, the Log Service provides logging for the farm.
These services are installed:
• Service Controller
• Configuration Service
• Administration Service
• Log Service
• Repository Service
• Application Engine Service
• Application Studio Service
• Dashboards Service
• OLAP Service
• Modeling Service
(On-premises) | 17
• Office Integration Service

• Financial Consolidation Service
• d/EPM Applications Service
The Infor d/EPM Platform farm is Windows/.NET Framework based.
The Dashboards Service and Office Integration Service are self-hosted web servers that run on the
ASP .NET Core framework.
Several services require databases.
Configuration Service
The Configuration Service provides central configuration for the farm. It also it tracks active sessions
and database locks for OLAP.
The Configuration Service stores the farm configuration in a database. The farm configuration includes
these components:
• Farm configuration
• Security configuration
• Database directories for OLAP
• Available service instances per service
• Service-specific settings
• Farm resources
The Configuration Service registers these relational farm databases:
• Configuration database
• Repository database
• Logs database
• Staging database
• Modeling Service database
• Financial Consolidation database
• OLAP database registrations
The Configuration Service registers all OLAP databases of the farm.
• Application plugins
Store plugin codes for a plugin supported service. This storage enables successful distribution of
plugins to all workers during the runtime of the farm and assists with maintenance of plugin supported
applications.
The Configuration Service scales with the number of service instances in the farm.
Dependency on number of users is low.
Application Engine Service

The Application Engine Service handles the execution of Application Engine processes.
(On-premises) | 18
The Application Engine processes are scripts that can access database data sources and retrieve,
write, or calculate data. With the Application Engine, you can create business processes for financial
and other applications to integrate them with Infor d/EPM Platform solutions.
The Application Engine Service scales with:
• The number of users.
• The frequency and kind of tasks.
The number of workers depends on the nature of the applications. The number of instances peaks at,
for example, the start and end of accounting periods and planning phases.
Repository Service
The Repository Service provides the central storage of application metadata for other services of the
farm.
The Repository Service scales with:
• The frequency of certain operations.
• The size of the repository database.
Additional impacts to consider are shared media and attachments because they can contain large
data streams or chunks.
OLAP Service
The OLAP Service is a service that stores data in multidimensional in-memory databases and provides
the data to other services.
The data is pre-aggregated in the cubes which contributes to improved performance of the OLAP
database.
There can be multiple databases. Cases of insufficient response times and higher load characteristics
on the OLAP computer, you may need to scale vertically with additional memory or CPU to that specific
computer.
You can improve the overall handling of multiple OLAP databases by running them on separate OLAP
cluster nodes. One OLAP database runs on one computer and cannot be distributed over several
computers.
The OLAP Service scales with:
• The number of users connected to the database.
OLAP Service calculates the data requested by each user, on demand. Multiple users can use the
OLAP database in parallel. This means that if you add more processor cores, the performance of
OLAP Service improves for multiple users.
• The size of the OLAP databases.
(On-premises) | 19
The number and size of the loaded cubes affect the size and the memory consumption of the data
model. The size of a cube depends on the number of dimensions the number of elements in the
dimensions, and the number of values stored.
Because of the pre-aggregation of the data, the file sizes on disk do not match the size of the
database in memory.
When cubes are not used for a certain configurable time, the OLAP database can unload them
from memory.
• The number and complexity of rules.
Application Studio Service

The Application Studio Service is an application service that handles loading and rendering reports for
users.
The Application Studio Service uses users' security profiles to ensure that they can view only the reports
and data to which they have access. When a user requests a new report, the Application Studio Service:
• Requests the report definition from the repository. This is cached per tenant and shared between
users.
• Requests the required data from the associated business database.
• Calculates the reports.
• Delivers the report as DHTML.
The Application Studio Service scales with:
Application Studio Service is multi-threaded and can use all processor cores, serving multiple
users.
• The size of reports.
The memory required by the rendering process depends on the kind of report and the size of the
data model in the business database. In addition to the values, the metadata in the Repository
database is transferred from the database server to the report engine when first accessed to
calculate the reports correctly. That information is then cached and shared between users.
Dashboards Service
All content in Infor d/EPM Platform is presented through dashboards. A dashboard contains one or
multiple widgets with summary information from which you can drill down to more detailed reports and
charts.
With dashboards, you can display multiple Application Studio reports and web content in widgets in a
web browser, an iPhone, iPad, or an Android device.
Reports that are loaded into dashboard widgets are calculated and rendered by Application Studio
Service and do not add to the dashboards load. The dashboard catalog and the report catalog are also
separate entities handled by separate applications.
(On-premises) | 20
The Dashboards Service scales with:

• The size of the dashboard catalog.
• The amount of memory consumption per user.
The memory consumption depends on the size of the dashboard catalog:
• The number of folders and dashboards.
• The dashboard definitions.
Administration Service
The Administration Service is an application service that provides functionality for administering repository
content, user management, OLAP database administration, application management, and other tasks
related to a farm.
The Administration Service scales with:
• The frequency of tasks that require a lot of resources. User and roles management may require a
lot of resources as the service scales with the number of users.
The number of instances is low.
Modeling Service
The Modeling Service is used for OLAP modeling such as creating cubes and dimensions. The Modeling
Service is also used for relational modeling such as creating staging tables, filling the tables with data
from Infor Data Lake, and filling the integration schema for Infor d/EPM business applications.
The Modeling Service scales with:
• The frequency of tasks that require a lot of resources. These tasks may require a lot of resources:
• Browsing the structure of an OLAP database.
• Exporting and importing data.
• Loading data into the Integration database.
• Creating and editing cubes and dimensions.
• Editing rules.
Office Integration Service

The Office Integration Service is a web application. The web application is shown in the Task Pane
within the host application which is Microsoft Office Excel.
The Office Integration Service scales with the number of users.
(On-premises) | 21
Financial Consolidation Service

The Financial Consolidation Service provides business logic for the Infor Financial Consolidation
module. It accesses the Financial Consolidation relational database and the existing OLAP database.
The Financial Consolidation Service scales with:
• The number of Financial Consolidation users.
d/EPM Applications Service

The d/EPM Applications Service provides business logic that is common across all Infor d/EPM modules.
It accesses the existing OLAP database.
The d/EPM Applications Service scales with:
• The number of Infor d/EPM users.
Service Controller
The Service Controller is installed on all machines of a farm.
The Service Controller is required for these actions:
• Enabling remote configuration of each service through Service Expert or using command lines.
• Ensuring that services are running.
Farm Expert and Service Expert

Infor d/EPM Platform services are configured during installation, using full clients.
Service Expert is installed on all machines. Farm Expert is usually only available on a single computer
in the farm.
d/EPM Administration
All configuration and daily administration of Infor d/EPM Platform is done in d/EPM Administration.
During farm configuration, the d/EPM Administration application is installed in Farm Expert. You can
update d/EPM Administration through patches.
d/EPM Administration provides standard administration dashboards for many purposes. Those standard
administration dashboards are installed during the configuration of the farm and cannot be changed.
The standard administration dashboards are organized in these categories:
(On-premises) | 22
• User and Permission Management

• Applications Administration
• OLAP
• Logs
• Farm Administration
Infor d/EPM Platform applications are installed through the d/EPM Administration dashboard. Select
Applications Administration > Applications. In the Manage Applications widget click Applications
to install new, updated, and customized applications. You can manage applications such as d/EPM
Administration and Office Integration.
Front-end applications
This section describes the front-end applications.
Dashboards
Dashboard content is stored in the repository database.
Dashboards can connect to multiple Application Studio report catalogs at a time to show their reports.

Android and IOS apps are available for mobile devices.
Excel Integration
Excel Integration is an add-in to Microsoft® Excel.
To use Excel Integration, the computer on which Microsoft® Excel is installed must have access to the
internet.
Applications
This section provides a high-level overview of the applications.
Infor d/EPM business applications

The Infor d/EPM business applications run on Infor d/EPM Platform.
(On-premises) | 23
The preconfigured applications are Budgeting & Planning, Workforce Planning, and Financial
Consolidation.
Tools for designing applications

Tools for designing applications can be installed on the server and accessed through terminal or other
remote services. The tools can also be installed to desktop computers.
Application Studio
Application Studio full client is a tool that enables you to create and change Application Studio content.
Application Studio stores its content in a farm database. Application Studio can connect to different
business databases such as OLAP, relational business databases, or Microsoft Analysis Services.
Application Studio full client is downloaded from d/EPM Administration.
Application Engine Process Editor

Application Engine Process Editor is a tool that enables you to develop Application Engine processes.
Application Engine processes are written in the BI# programming language. Application Engine Process
Editor includes a text editor and supports the entire life of a process.
Designer
Designer is a modeling application for OLAP databases. It is also used to load data into an OLAP
databases. In some scenarios, other tools used.
Designer stores its content in a relational database.
When Designer is used for data loads, the load process is a significant performance factor. During the
load process, the data is extracted from a source system, transformed as needed, and loaded into the
OLAP database.
The duration of the load process depends on many variables such as the amount of data. The load
times can last from several minutes to many hours.
Designer is downloaded and installed from d/EPM Administration.
ETL and modeling tools

These tools are available:
(On-premises) | 24
• OLAP modeling in d/EPM Administration

• Application Engine
• ImportMaster
• Designer
Performance warranty
Infor has performed this sizing thoroughly but cannot guarantee optimal performance because there
are many variables in the sizing procedure. Infor assumes no liability for any damages or extra costs
that result from recommendations.
Sizing
Sizing is not a one-time activity. Sizing is an ongoing process and must be carried out several times
during the lifetime of a solution. The hardware architecture must be adjusted to the changes of the
enterprise.
Sizing is frequently carried out for pre-sales reasons at the beginning of an implementation to estimate
the hardware budget. The sizing in this situation is approximate and high-level because few details are
known.
During later stages of the implementation project, more detailed information, which has influence on
the sizing, becomes available. The customer's business process and how Infor d/EPM Platform will be
used becomes clear. These can have an impact on the size of the hardware infrastructure.
Before going live, we recommend that a reevaluation of the sizing be done. Purchase equipment as
late as possible to reflect ongoing changes during project implementation.
Application factors
Two factors affect hardware requirements. First is the user load distribution. At most customer sites,
the load distribution varies according to the nature of the application, but all applications have peaks
and troughs.
Peak periods may have a daily or weekly rhythm for analytic or reporting applications. Budgeting
applications experience high peaks during the budgeting process, with the heaviest loads occurring
just before deadlines. Management reporting applications experience their highest demands during
the period after new results are available. For correct sizing, these peak periods must be anticipated,
and equipment sized accordingly.
The second factor is the complexity of the application. There are several factors that can affect the
suitability of these recommendations, including, but not limited to, amount or level of data, number of
(On-premises) | 25
dimensions, number of elements in dimensions, formulas, number of databases and applications,

complexity of report definitions and number of users.
The hardware sizing recommendations were derived by using a series of customer reports of average
complexity to estimate peak user load. In the current architecture, this memory consumption was
recorded:
Component Scaling server memory requirement per user

Web-based main access to dashboards and 200 - 2840 MB
d/EPM Administration using OLAP. A simple report opened in Application Studio
Service and dashboards takes 20 - 40 MB. A
large report with a lot of data can be much higher,
depending on the size. For example, each user
may open multiple reports inside a dashboard.
Hard disk space and type

Infor d/EPM usually requires 50 to 100 GB space on the hard disk for installation, Microsoft SQL Server,
and for the OLAP database central storage system. For the installation, and for some other tasks, the
hard disk performance is not relevant. For the production operation, the performance of the hard disk
storing the databases can have an impact.
Hard disk performance is relevant in these scenarios:
• Permanent logging during production operations.
• Auditing.
• Relational database storage.
Consider the use of high bandwidth SSD drives in these scenarios.
Processors
Better performance can be achieved with higher processor clock rates. This conflicts with the trend to
decreasing clock rates on server computers.
While high clocks rates are important, the number of cores is important as well, especially for multiple
user scenarios.
Technical aspects
Basic performance is defined as the response average users receive during normal usage when they
request information from the application. Memory is allocated per user and can take advantage of all
existing memory in 64-bit operating systems.
(On-premises) | 26
Users
Each user who connects to dashboards causes load on most other services.
Concurrent users vs. named users

All user numbers given in this document are concurrent users, all being active at a given moment in
time. When sizing applications for concurrent or named users, we have typically seen ratios of around
10%. For example, of 100 users, 10% or 10 users would, on average, be concurrent at any time. This
ratio varies according to the way in which Infor d/EPM Platform is implemented.
Network server infrastructure

If you have installation scenarios with multiple computers, good network performance is essential. A
low latency gigabit Ethernet network is recommended in all scenarios. A latency over 10 ms is
unacceptable and less than 5 ms is recommended.
To use dashboards outside a Wi-Fi connection, at least a 4G network connection is required.
Virtualized environments
There are no hardware-related functions implemented in Infor d/EPM Platform. The software functions
error-free in virtualized systems provided all operating system functions are passed on through the
virtual environment.
Virtualization does not increase server capacity. Virtualization has an overhead which results in less
server capacity or less server throughput. The benefit of virtualization is that idle resources can be
used more efficiently. By running multiple VMs on the same physical server, overcommitment of physical
resources such as CPU and memory can occur. In this case, all VMs on this host will suffer performance
problems.
Running OLAP on virtualized environments

An OLAP database is an in-memory database. All the data is held in-memory and used from there
when it is run. Therefore, the fast availability of enough RAM is a critical performance factor. If the
computer starts to swap out memory to disc, performance suffers dramatically.
This dependency on fast RAM access also has consequences for virtual environments. In such
environments, the resources RAM, and cores are shared among multiple virtual computers. This can
have a negative effect on the performance because the VM with the OLAP Service must wait for the
system resources. We recommend that you run the cluster node either on dedicated, physical hardware
(On-premises) | 27
or as the only virtual computer on a host system. This enables the cluster node to deliver the best
possible performance.
Consider these performance aspects:
• Memory aspect
The increased writeback performance of OLAP is because OLAP is an in-memory technology.
However, this means that the OLAP Service requires exclusive full access from the processor to
the memory. In a virtualized environment, each VM shares access to the main memory with all
other VMs. Normally, this access cannot be configured. The number of channels to the memory
is limited. In such an environment, the OLAP Service cannot reach full performance.
• CPU aspect
OLAP database calculation time is normally spread over thousands and millions of single
calculations. In virtualized environments, processor cores can be assigned to VMs. However, this
setting cannot always guarantee exclusive access to these cores. For example, assigning four
cores to a VM means that if during a time period the host system recognizes that a VM needs more
processor power, then the system assigns more cores to this VM for this time period and up to a
maximum of four cores. This overhead can lead to serious performance issues.
Server types
Infor d/EPM performance is dependent on many factors, including the complexity of the calculations,
available hardware, and number of concurrent users. Although Infor d/EPM can be installed on a single
server, it can also be distributed over multiple servers to balance concurrent user and processing loads.
The distribution over multiple computers depends on your business needs and usage characteristics.
This section offers hardware recommendations for single server installation and for distributed installation
which scales to multiple servers.
All recommendations are for production environments running on 64-bit operating system servers
where more than 8 GB memory is required. We used at least 4 core processors in our tests. You can
use similar or better hardware.
Although all services can be installed on a single server, common levels of user load normally require
that the services be installed on dedicated computers responsible for specific tasks.
This table shows the dedicated server types that can be used to build an enterprise architecture to
host users figures from small to large:
Server type Description Host/Connected to

Database server We recommend a dedicated Farm databases (Repository,
server to host all relational farm Configuration, Log)
databases. Integration database
Designer database
(On-premises) | 28
Server type Description Host/Connected to

Primary server All Infor d/EPM Platform ser- Farm databases
vices managers and workers Business database
are installed on this computer
except those installed on the
scaling or OLAP server.
OLAP database server We recommend running OLAP OLAP database
databases on servers dedicated
to OLAP only.
Scaling server We recommend the worker
processes that have the biggest
loads are installed on the scal-
ing server. Typically, these
worker processes have the
biggest load:
• Dashboards Service worker
• Application Studio Service
worker
• Application Engine Service
worker
Infor d/EPM Platform scales horizontally. That means as the number of concurrent users increases,
you add more scaling servers.
Single server (test or development system)

Infor d/EPM can be run on a single server. You install all Infor d/EPM Platform services including OLAP
and the database server to a single server.
A single server can be used as for demonstration purposes or testing environments. We do not
recommend single server setup in a production environment.
This table shows the recommendations for a single server:
Specification Recommendation
Concurrent users 1-5
CPU cores 4
Memory (GB) 16 plus the size of OLAP database
(On-premises) | 29
Enterprise topology
The installation process for Infor d/EPM to multiple machines is explained in the "Installing on multiple
machines" topic in the Installation section.
Primary server
The primary server is the infrastructure server. Everything, except OLAP and the workers you install
to the scaling server, is installed on this computer.
This table shows the recommendations for the primary server:
Concurrent users <20 <75 >200
CPU cores 4 4 8
Memory (GB) 16 16 32
Database server
The relational database server has Microsoft SQL Server installed. It is the primary data store for the
metadata, fact data, report definition, and user permissions.
This table shows the recommendations for the database server:
CPU cores 4-8
Memory (GB) 8-16
OLAP database server

The memory requirements depend primarily on the size of the database.
This table shows the recommendations for the OLAP database server:
Concurrent users <20 >75
CPU cores 4 16
Memory (GB) 16 32
(On-premises) | 30
Scaling server
These are the services which you typically install to a scaling server:
• Application Studio Service worker
• Application Engine Service worker
• Dashboards Service worker
This table shows the minimum recommendations for the scaling server:
CPU cores 4
Memory (GB) 16
Infor d/EPM Platform comes with more services and scales horizontally so you can group the services
based on the usage. That means as the number of concurrent users increase, you add more scaling
servers. However, it is the overall memory and number of cores that are available to the farm that is
important not the number of servers.
The nature and complexity of each different user profile makes is difficult to give a common
recommendation. Each project and each user has a different activity profile. The application itself is
extremely flexible. In addition, it gives you control over the basic implementation structure, such as the
dimensions, the structure of their hierarchies, all data access profiles and rules, and so on. Overall,
each user profile, combined with the distribution of concurrent users across these profiles, determines
the overall machine requirements.
In general, that makes it difficult to give a fixed sizing recommendation per concurrent user figures that
fits all projects.
If you are migrating from a previous version, we recommend you map your existing server infrastructure
into the new topology. A key aspect is to verify if the memory is still enough. Adding a few more
processors will make the server faster.
This table shows the recommendations for multiple scaling servers:
Concurrent users <50 <100 <200
Number of scaling 1 2 3
servers
We recommend you add an additional scaling server for every 100 additional concurrent users with at
least the minimum server specifications.
This table shows the recommendations for adding multiple scaling servers if your application has a
high number of concurrent planner users:
Concurrent planner <20 <75 <200
users
(On-premises) | 31
Number of scaling 1 3 5
servers
For each additional 50 concurrent planner users, you should add an additional scaling server.
Desktop computers
In addition to the server installation which runs the farm, a computer with a browser or a dedicated
windows environment is required for each user.
This table shows the required desktop computer types:
Desktop type Description

Thin client, browser Web-based access to dashboards and d/EPM
Administration.
Full clients Required for a small number of report developers
to create and modify Application Studio reports,
Application Engine scripts and modify Designer
database models. The full clients are:
• Application Studio
• Application Engine
• Designer
In cloud environments, the geographical proximity
of the client to the Amazon Web Services zone
on which the tenant runs has a bearing on the
performance of the client. This applies particularly
to Application Studio, which will not perform sat-
isfactorily if, for example, the client and tenant
are on different continents.
Microsoft Excel using the full client Excel Integration
For administration purposes, a desktop computer is recommended with at least these specifications:
CPU cores 4
Memory (GB) 8 or higher
(On-premises) | 32
Application growth
As your application grows, in terms of number of users, application complexity, or database size, it is
good practice to monitor the resource used by your servers.
Use the Windows Performance Monitor during peak usage times, and during large consolidations, to
observe processes such as processor and memory utilization. Such periodic monitoring helps to ensure
that your users continue to obtain reliable performance as the environment and application change.
If the application begins to require additional resources, these are two options to help scale the
application.
• Scale horizontally by adding servers.
• Scale vertically by upgrading the hardware, by adding memory or by using servers with additional
processors or faster processors.
Performance monitoring of applications and tools

This section provides a high-level understanding of how to monitor your environment. Monitoring
components such as servers or databases is useful in identifying bottlenecks within your applications.
The topics in this section describe a set of common tools that can be used to monitor and measure the
components of interest. You must have basic knowledge of the Windows operating system and of
Windows administrative tools.
Measurement tools
This section describes the monitoring and measurement tools that are usually installed with the Windows
operating system.
This table shows the tools used for the different monitoring tasks:
Tool Description
Windows Task Add these columns to the Processes tab of Windows Task Manager:
Manager • Virtual Memory Size: the virtual memory size lists memory consumption
more precisely
• CPU time: the CPU time shows in detail how much time the process con-
sumes
Performance The Performance Monitor, as part of the Windows installation, is used to monitor
Monitor measures like the Virtual Memory size more precisely and can record over a
long time if required. Additionally, the data it gathers can be collected and ana-
lyzed using common Microsoft Excel work sheets.
For convenience, the OLAP Service installs additional counters that can be se-
lected within the Performance Monitor.
(On-premises) | 33
Tool Description
SQL Server Profil- The SQL Server Profiler enables you to monitor in detail each single SQL request
er sent to the server. The requests can be collected and analyzed. For example,
the time consumed by the server for specific requests.
Monitoring the OLAP Service

The OLAP Service starts a separate Infor.BI.Olap.DatabaseWorker.exe process for each
database.
If you have multiple databases running, you can distinguish the processes by checking the command
line in Task Manager. The ID of the resource, database name, and tenant are part of the command
line and can be mapped to the database that you want to monitor.
OLAP is an in-memory database and delivers the best performance if all memory required by the server
process is in the RAM. If the process memory is moved out to the page file, the performance will be
slowed down.
To check the memory usage of a database process, you can check the commit size or private bytes
of the process. This represents the memory allocated by OLAP. If you are using the Process Explorer
from Microsoft Windows SysInternals, you can check for the peak private bytes which provides the
maximum since the start of the database.
Use Task Manager to check the memory load on the machine. If the Committed value is higher than
the RAM in the machine, it is overloaded. This number should be well under the amount of RAM on
the machine.
OLAP database in production environment

The OLAP database in a production environment consumes CPU power and memory in conjunction
with the number of users and individual work processes. These are some examples of the processes
that consume CPU power and memory:
• Reading data.
• Writing data.
• Automated mass data processes.
You can use the Databases dashboard in d/EPM Administration to monitor activity.
The OLAP Service offers additional performance monitor counters to gather more information. For
example, the number of active users.
(On-premises) | 34
OLAP database calculations

The OLAP database calculates all values on request. Depending on the design of the database, in
terms of element structure, rules, mass data processes, and so on, the calculation could take several
seconds.
You can identify long running operations using the Database Overview dashboard.
Performance Monitor offers the percentage processor time. To get the actual time used, use the Task
Manager.
Application Studio database requests

Application Studio reports and Infor d/EPM Platform user management are stored in the farm database.
Run the farm database on a database server without any additional products installed. It can be
monitored with the SQL Server Profiler tool. SQL Server Profiler can be used to monitor all repository
requests on the database.
From a logical point of view, the requests sent to the farm database can be separated into two main
sections.
User management requests

The Repository Service sends requests for all required authentication objects that are assigned to
users' accounts. Depending on the depth of permission inheritance, the SQL Server Profiler can monitor
long lasting requests.
Business database requests

Each report displays data from a connected business database. The requests to connect to the
associated database are usually sent immediately after a user is authenticated.
(On-premises) | 35

Depm 2022.01 Hardware Software Recommendations En-Us

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Depm 2022.01 Hardware Software Recommendations En-Us

Uploaded by

Copyright:

Available Formats

Infor Dynamic Enterprise

Performance Management Hardware

Chapter 1: Overview of the hardware and software recommendations........................................6

Chapter 2: Platform support..............................................................................................................7

Farm Expert and Service Expert.................................................................................................22

Chapter 1: Overview of the hardware and software

Chapter 2: Platform support

Relational database systems for farm installations

Relational databases Support level Notes

Relational database systems as business database

Multidimensional databases - Infor d/EPM Platform

Multidimensional databases Support level Notes

Multidimensional databases - Infor d/EPM business

Multidimensional databases Support level Notes

Operating system Support level Notes

Operating system Support level Notes

Operating systems Support level Notes

Infor d/EPM mobile applications

Operating systems Support level Notes

Infor d/EPM mobile applications

Infor Operating Service

Infor OS Support level Notes

Infor Landmark Runtime

Landmark Support level Notes

Browsers - Infor d/EPM Platform

Browsers Support level Notes

Browsers Support level Notes

Browsers - Infor d/EPM business applications

Browsers Support level Notes

Microsoft Office versions Support level Notes

Microsoft Office versions Support level Notes

Chapter 3: Hardware recommendations

Infor d/EPM infrastructure Additional infrastructure

Perimeter network environments

Public network Perimeter network Private network

The primary server is for these workers and managers:

Infor Operating Service

Worker and manager services

• Office Integration Service

Application Engine Service

Application Studio Service

The Dashboards Service scales with:

Office Integration Service

Financial Consolidation Service

d/EPM Applications Service

Farm Expert and Service Expert

• User and Permission Management

Infor d/EPM mobile applications

Infor d/EPM business applications

Tools for designing applications

Application Engine Process Editor

ETL and modeling tools

• OLAP modeling in d/EPM Administration

dimensions, number of elements in dimensions, formulas, number of databases and applications,

Component Scaling server memory requirement per user

Hard disk space and type

Concurrent users vs. named users

Network server infrastructure

Running OLAP on virtualized environments

Server type Description Host/Connected to

Server type Description Host/Connected to

Single server (test or development system)