Adding FME Engines on a Separate Machine

The user account that runs <engineHost> must have read or read/write permissions to the FME Server System Share files on the <coreHost>. These files include Repositories and Resources. By default, an Express Installation of FME Server writes these files to the path specified by the %ALLUSERSPROFILE% environment variable, which defaults to C:\ProgramData\Safe Software\FME Server\. If your Express Installation of FME Server specified a different directory, or if your FME Server is a Distributed Installation, then these files are written to the directory specified.

Read permission:

• \resources\system\temp\upload

• \repositories

• \resources\system\temp\requestdata

• \resources\engine

Read and Write permission:

• \resources\logs

• \resources\system\temp\engineresults

• \resources\backups
• \resources\data
• \resources\temp

Additionally, if the FME Server Database is installed on a separate server, the user account that runs <engineHost> must have the same permissions as described above on that network share.

1. Start the FME Server Installer on another computer (<engineHost>).
2. On the Choose Setup Type dialog, select the Engine setup type.
3. On the Destination Folder dialog, specify the directory to install the FME Engines.
4. On the Existing FME Server System Share dialog, provide the UNC path to the System Share directory. (In most cases, the directory is the same as the <coreHost> System Share directory.)

5. On the FME Server Hostname dialog, enter the hostname of the <coreHost> computer. In a fault-tolerant installation, the primary <coreHost> should always be specified. Do not specify the failover host.

6. On the Database Server Type dialog, specify the database type that you specified when installing the FME Server Core. If you specified a database other than the "FME Server Database," enter the connection parameters in the next dialog.
7. Complete the remaining dialogs of the FME Server Installer.
8. If this <engineHost> is connecting to a <coreHost> that also hosts the built-in FME Server database and the initial FME engines, as with an Express Installation, allow the necessary connection to this machine:
1. On the <coreHost>, open file pg_hba.conf, located in <FMEServerDir>\Utilities\pgsql\data\.
2. Change the following lines:

host    all     all     127.0.0.1/32      md5

host    all     all     ::1/128         md5

to:

host    all      all       0.0.0.0/0         md5

host   all      all     ::/0             md5

3. Restart the FME Server Database service.
9. If the <coreHost> machine was an Express Installation of FME Server, complete the following steps on the <coreHost> to configure the FME Server services:
   1. Open the corresponding propertiesFile.properties file for the Data Download, Data Streaming, Job Submitter, and Notification services, located at <FMEServerDir>\Utilities\tomcat\webapps\<service_name>\WEB-INF\conf\propertiesFile.properties.

   For example, the properties file for the Data Download Service is at <FMEServerDir>\Utilities\tomcat\webapps\fmedatadownload\WEB-INF\conf\propertiesFile.properties

   2. For each properties file, locate the parameter REQUEST_DATA_DIR and change the value from a local file system path (for example, C:/ProgramData/Safe Software/FME Server//resources/system/temp/requestdata) to a UNC path that references the <coreHost> (for example, //MyHost/FME Server/resources/system/temp/requestdata).

   Note: Use forward slashes only.

   3. After saving the changes in the properties file for each service, restart the FME Server Application Server service.

1. Mount the FME Server Core installation directory shared by <coreHost>:

   mount <coreHost>:<FMEServerDir>/home/FMEServer

2. Start the FME Server Installer.
3. Select the Engine Install.

4. Choose to install only the FME Engine component by selecting Yes to the FME Engine component prompt and No to the other component prompts.

   The installer prompts you for the path to the <coreHost> installation directory. In a fault-tolerant installation, the primary <coreHost> should always be specified. Do not specify the failover host.

5. Enter the path to the mounted directory.

   The installer prompts you for the name of the FME Server Host.

6. Enter the host name of the <coreHost> computer.
7. Enter the database type you specified when installing the FME Server Core. If you specified a database other than the "FME Server Database", enter the connection parameters.
8. Complete the remaining dialogs of the FME Server Installer.
9. Manually start FME Server, and configure it to start automatically.

10. If this <engineHost> is connecting to a <coreHost> that also hosts the built-in FME Server database and the initial FME engines, as with an Express Installation, allow the necessary connection to this machine:

    1. On the <coreHost>, open file pg_hba.conf, located in <FMEServerDir>\Utilities\pgsql\data\.
    2. Change the following lines:

    host    all     all     127.0.0.1/32      md5

    host    all     all     ::1/128         md5

    to:

    host    all      all       0.0.0.0/0         md5

    host   all      all     ::/0             md5

    3. Restart the FME Server Database service.

The installation on <engineHost> starts two FME Engines by default. The FME Engines start and register with the FME Server Core running on <coreHost>. All licensed engines are listed on the Engines & Licensing page of the Web User Interface, under 'Licensed Engines'.

Note: You may have to disable any firewalls that are running on this computer.

You can also use the Engine Management page to perform the following tasks:

• To license FME Engines, see Request and Install a License.
• If you want this computer to start more or less FME Engines, see Configuring the Number of FME Engines to Start.

For more information, see Verify the Installation (Windows) or Verify the Installation (Linux).