In some cases, you may want to install 32-bit and 64-bit FME Engines on the same machine. For example, you may currently be running only 64-bit engines, but you want to run a workspace from FME Server containing a format that runs only on a 32-bit engine.
WARNING: This procedure limits the ability to configure FME Engines on the Engines & Licensing page of the Web User Interface. Run the same bit version of FME Engines unless absolutely necessary.
Note: A 64-bit engine will not run on a 32-bit version of Windows.
To Install a Different Bit Version of an FME Engine on the Same Machine
- Run the stand-alone (Engine Only) FME Engine installer and note the default installation directory. The default installation directory for a 32-bit engine is C:\apps\FME. For information about obtaining a stand-alone Engine installer, see Obtaining the Installer.
- You must license new FME Engines. For licensing instructions, see Request and Install a License.
Under the Admin section at the bottom of the file, add the following line:
Add the following line, specifying the host name and new engine name. For example:
To the same line, append the contents of an existing TEMPLATE_START_ENGINE directive, modifying the engine path to specify the newly-installed engine. For example:
START_ENGINE_MYHOST_Engine3="C:/apps/FME/fme.exe" REGISTER_FME_ENGINE localhost 7070 7069 DEFAULT "C:/Program Files/FMEServer/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME MYHOST
- Restart FME Server.
To confirm that you are using the FME Engine from the new path, check one of the following:
- The Engine Management page of the FME Server Web User Interface. The Platform column under Engines should now show your 32-bit engine.
- fmeprocessmonitorengine.log. In the log, you should see your new FME Engine path and build number reflected in the information about startup.
Note: For verification only. With different bit versions of FME Engines installed on the same machine, managing engines on the Engine Management page no longer works as expected. For more information, see Configuring the Number of FME Engines to Start.
Use Job Queues to ensure your workspaces are run by the new engine.