Installation procedure for multiple machines

After the installation and configuration of the farm, you can start adding machines to the farm.

You can install the services separately by running the setup for all services on all machines, but registering only the services you require on each machine. We recommend that you use the Setup_dEPM_Services.exe file and then, after the setup of all services is finished, register the services you require.

For details about optimal services distribution on multiple machines, see the "Hardware and Software Recommendations" section.

To install several instances:

Double-click the Setup_dEPM_Services.exe.
Click Next.
Optionally, change the folders to which to install the 32-bit and 64-bit components.
In the Custom Setup dialog box, use the default settings to install all services.
You can select the components to be installed. You must always install Farm Tools, Service Controller, and at least one service.
Optionally, expand the list next to a feature and select Will be installed on local hard drive or Entire feature will be installed on local hard drive options.
Click Next.

Select one of these accounts for Service Controller and specify a password for a custom user:

Option	Description
Local System account	Local system windows account.
This account	The global account, indicating which account must be used on all machines.

Click Next.
Click Install.

By default, the service is installed in the Program Files\Infor\BI folder.

If the Service Expert does not start automatically, you can start it from the Windows Start menu.
Select the Join an existing farm check box.
Click Next.
Select the Connection.farmprofile file of the existing farm on the Connection Configuration dialog box.
The Connection.farmprofile contains the central key to your farm.
Click Connect.
When prompted, specify the file’s password.
Click Finish.
You can check if the new service is part of your farm by opening the Services dashboard in d/EPM Administration.
Adjust your load balancing metrics according to the number of scaling servers, and run the script.