Overview of the installation process
You use the Infor EPM installation wizard to install the Infor EPM farm. This farm is a set of services that communicate with each other and that can serve requests for one or multiple tenants.
These farm modes are available:- Standalone farm: A local farm independent of Infor Cloud.
- Cloud-bound farm: A local farm that uses IFS security of an existing tenant in Infor Cloud to authenticate users.
The farm installation procedure includes these parts:
- Installing the Infor EPM services and starting Service Controller through an installation wizard.
- Connecting and configuring the services to create a secure farm. This
step is done through a wizard that starts automatically after the installation of the
services. In the wizard, you can select different security options. The installation steps
for different security options are described in these specific installation procedures:
- Installing a farm with Basic web access security
- Installing a farm with LDAP web access security
- Installing a farm with IFS web access security
When you run the wizard, these databases are created:
Database Default name Configuration database BIFarmConfig Logging database farm BIFarmLog - After configuring the farm through the wizard, Farm Expert starts automatically. During this step, the farm repository
is created, the OLAP data directory is defined,
and the Administration Service application is installed.
This step is identical for all web security options.
When you run Farm Expert, these databases are created:
Database Default name Repository BIFarmRepository Staging dEPMStaging - Optionally, you can install the standard applications, such as Self-Service, Samples, and Infor EPM business applications.
Infor EPM business applications are available in Business Modeling-based and Designer-based versions.
For the Business Modeling-based applications, these databases are created:
Database Default name Modeling database BIFarmModel Consolidation journal database BIFarmConsolidation For the Designer-based applications, these databases are created:
Database Default name Integration database dEPMInteg Changelog database dEPMChange Designer database dEPMDesigner
Extra information
For details on installing an update or patch, see “Installing an update or patch”.
The cloud-bound farm uses the IFS security setup for an Infor cloud tenant. The IFS security setup provides a single location to manage security and permissions of multiple farms.
The IFS security setup does not support, for example, ION API access, Data Fabric, and other additional cloud services.
During the cloud-bound farm setup, you generate the service provider registration file. The service provider registration file is required to create the IFS identity descriptor file and the authorized application profile. The administrator of the tenant uses the service provider registration file to provide you with the IFS identity descriptor file and the authorized application profile.
Install the security certificates on a server and configure all farm machines. You must add the master certificate to the trusted root certificates folder on the relevant clients. Ensure that the master certificate is capable of signing other certificates. Ensure that the certificate has the Is Certificate Authority flag enabled and the signing child certificate option added.
Use basic authentication for full clients because ION API is not supported in a full client.
After the services are started and the farm is configured, you can perform any ongoing administration of the Infor EPM farm in EPM Administration. See the "Administration" section.
You use Service Expert to configure global security and settings, and to configure, start, stop, and restart the services. See the "Service Expert" section.
You use Farm Expert to configure the farm repository and standard applications. See the "Farm Expert" section.
We recommend that you distribute the services of an Infor EPM farm over multiple machines. This provides scalability and redundancy. You can add additional machines to a farm by installing single services to single machines.