Rebrand Installer for 2024.0

Question

What’s changed in the rebrand installer for 2024.0? Will this break my workflows?

 Answer

There should be no changes to functionality, including silent installations. Refer to the list below for a summary of the changes.

• IDs of features in the installer renamed
  • FMEServerCore → FMEFlowCore
  • FMEServerDatabase → FMEFlowDatabase
• Installer properties names
  • FMESERVERHOSTNAME → FMEFLOWHOSTNAME
  • FMESERVERHOSTNAMELOCAL → FMEFLOWHOSTNAMELOCAL
  • FMESERVERUSER → FMEFLOWUSER
  • FMESERVERUSERPASSWORD→ FMEFLOWUSERPASSWORD
  • FMESERVERSHAREDDATA → FMEFLOWSHAREDDATA
  • FMESERVERBUILD → FMEFLOWBUILD
  • FMESERVERREQUESTPORT → FMEFLOWREQUESTPORT
• Config files renamed in <FMEFlowDir>\FMEFlow\Server or /opt/fmeflow/Server
  • fmeServerConfig.txt → fmeFlowConfig.txt
  • fmeServerWatcherConfig.txt → fmeFlowWatcherConfig.txt
  • fmeServerWebApplicationConfig.txt → fmeFlowWebApplicationConfig.txt
• Database name
  • fmeserver → fmeflow

Windows Specific

1. FME Flow Windows Services

• FME Server Application Server → FME Flow Application Server
• FME Server Core → FME Flow Core
• FME Server Database → FME Flow Database
• FME Server Engines → FME Flow Engines

2. FME Java process names in Task Manager

• FMEServer.exe → FMEFlow.exe
• FMEServer_ApplicationServer.exe → FMEFlow_ApplicationServer.exe

3. bat files in C:\Program Files\FMEFlow\Server\WindowsService

• startFMEServerWindowsService.bat → startFMEFlowWindowsService.bat
• restartFMEServerWindowsService.bat → restartFMEFlowWindowsService.bat
• stopFMEServerWindowsService.bat → stopFMEFlowWindowsService.bat

Linux Specific

1. Systemd/SysV script names

systemd scripts:

<FMEFlowDir>/Server/startup/systemd/fmeflow-appserver.service

<FMEFlowDir>/Server/startup/systemd/fmeflow-cleanup.service

<FMEFlowDir>/Server/startup/systemd/fmeflow-core.service

<FMEFlowDir>/Server/startup/systemd/fmeflow-database.service

<FMEFlowDir>/Server/startup/systemd/fmeflow-engines.service

<FMEFlowDir>/Server/startup/systemd/fmeflow-websocket.service

SysV scripts:

<FMEFlowDir>/Server/startup/SysV/FMEFlowAppServer

<FMEFlowDir>/Server/startup/SysV/FMEFlowCleanup

<FMEFlowDir>/Server/startup/SysV/FMEFlowCore

<FMEFlowDir>/Server/startup/SysV/FMEFlowDatabase

<FMEFlowDir>/Server/startup/SysV/FMEFlowEngines

<FMEFlowDir>/Server/startup/SysV/FMEFlowWebSocket

Place scripts in new paths:

/etc/init.d/FMEFlowAppServer

/etc/init.d/FMEFlowCleanup

/etc/init.d/FMEFlowCore

/etc/init.d/FMEFlowDatabase

/etc/init.d/FMEFlowEngines

/etc/init.d/FMEFlowWebSocket

2. User and group

• fmeserver → fmeflow

3. NGINX config file and location

• fmeserver.conf → fmeflow.conf
•  /etc/nginx/fmeserver →  /etc/nginx/fmeflow