You are here: Administrator's Guide > Upgrading FME Server > FME Engine Only Upgrade > Installing 32- and 64-bit Engines on the Same Machine

Installing 32- and 64-bit Engines on the Same Machine

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 removes 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

  1. Create a new directory for the upgraded FME.

    <FMEServerDir>\Server\fmexx (xx = 64 or 32)

    Leave the existing FME Engine in place:

    <FMEServerDir>\Server\fme

  2. Run the Engine installer and install the Engine in the newly-created directory.

  3. You must license new FME Engines.

    For licensing instructions, see Request and Install a License.

  4. Edit the <FMEServerDir>\Server\processMonitorConfigEngines.txt file:

    Under the Admin section at the bottom of the file, add the following line:

    NODE_OVERWRITE=true

    Add the following line, specifying the host name and new engine name. For example:

    START_ENGINE_MYHOST_Engine3=

    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/FMEServer/Server/fme32/fme.exe" REGISTER_SOCKET localhost 7070 "C:/apps/FMEServer/Server/fmeEngineConfig.txt"

  5. 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.

    • 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.

  • fmeprocessmonitorengine.log. In the log, you should see your new FME Engine path and build number reflected in the information about startup.

What's Next?

Use Job Routing to configure specific jobs to run on the new engine.