Install the FME Server Services and Configure for Failover
Perform the following tasks:
- Install the FME Server Services
- Configure the FME Server Services for Failover
- Configure Firewall Settings
- (Oracle WebLogic only) Disable WebLogic Authentication
Install the FME Server Services
- Start the FME Server Installer on the <webHost>.
- Select the Distributed Install.
- On the Custom Setup dialog, select only the Web Services component for installation.
- The installer prompts you for the UNC path to the remote file system.
- The installer prompts you for the name of the FME Server Host. Enter the host name of the computer you want to serve as the primary FME Server Core host (<coreHost>). Do not specify the failover core host machine.
- The installer prompts you to install a web application server. If already provided, it is recommended that you shut down the service during installation.
-
On the <webHost>, mount the FME Server installation directory shared on the <coreHost>:
mount <coreHost>:<FMEServerDir>/home/FMEServer
- Start the FME Server Installer.
- Select the Distributed (Custom) install option.
-
At the feature selection dialog, select only the Web Services component.
The installer prompts you for the name of the FME Server Host.
-
Enter the host name of the computer you want to serve as the primary FME Server Core host (<coreHost>). Do not specify the failover core host machine.
The installer prompts you for the path to the remote file system.
-
Enter the path to the mounted directory.
The installer prompts you to install a web application server. If already provided, it is recommended that you shut down the service during installation.
-
Manually start FME Server and configure it to start automatically.
- In order for the Data Download and Data Streaming web services to reference the correct web host location when outputting results that are returned from an FME Engine, you must manually change this location in your FME Engine configuration files:
- Locate your FME Engine configuration files, under <FMEServerDir>\Server\fmeEngineConfig*.txt
- For each file, under the SUB_SECTION for FILE_DOWNLOAD_SERVICE and STREAM_DOWNLOAD_SERVICE, modify the SUCCESS_RESPONSE directive as follows:
From:
SUCCESS_RESPONSE 0:Translation Successful|OutputLocation=!FME_AUTO_DIR_NAME!
To:
SUCCESS_RESPONSE 0:Translation Successful|OutputLocation=<webHost>/DefaultResults/!FME_AUTO_DIR_NAME_SIMPLE!
Following the installation on <webHost>, the FME Server Web Application Server automatically starts. If you used your own web application server, you can restart that service.
To verify the installation, see Verify the Installation (Windows) or Verify the Installation (Linux).
Configure the FME Server Services for Failover
-
Open each web application properties file located at:
<WebAppDir>\<fmeServiceName>\WEB-INF\conf\propertiesFile.properties
-
Find the following line in this file:
#FAILOVER_SERVER_NAMES=<namelist>
-
Uncomment this line and replace <namelist> with the names of your FME Server Core hosts, separated by spaces. For example:
FAILOVER_SERVER_NAMES=fmecore1 fmecore2
- Restart the web application server.
Configure Firewall Settings
The FME Server Services and other clients communicate with the FME Server Core over TCP/IP. Requests are sent to the FME Server Core over port 7071. Result messages are returned to clients over a randomly assigned port created by the FME Server Core. Therefore, be sure to configure any firewall settings on the <webHost>
with a rule to allow for full communication with the <coreHost>
machines.
(Oracle WebLogic only) Disable WebLogic Authentication
If you are using an Oracle WebLogic server, you must disable WebLogic authentication. This step is necessary to prevent WebLogic from intercepting login requests, which interferes with FME Server authentication.
- Locate and open the following configuration file in your WebLogic installation:
- Add (or change) the following lines before the security configuration closing tag </security-configuration>:
- Save and close the file.
<WebLogic_install_dir>/user_projects/domains/<your_domain>/config/config.xml
<enforce-valid-basic-auth-credentials>
false
</enforce-valid-basic-auth-credentials>