Deploying FME Flow using Flow Apps or the REST API
Recently active
We are currently running FME Server 2022.2. on prem (not cloud hosted). We had been planning on upgrading to the latest, but now even more so with the privilege escalation issue, and there apparently not being a fix for our version….except to upgrade.Looking over the “in place upgrade” portion of the documentation, it seems we can simply backup the configuration files (we’re not using version control yet), do an uninstall of 2022.2, do a fresh install of the latest 2024, and then restore the configuration backup.Are there any known issues with doing this from 2022 to 2024? I know the product was rebranded in 2023, but the differences I could see between 2022 and 2023 seemed mostly cosmetic for the rebrand. However, I know 2024 seems to be different.I just really want to dot all my i’s and cross all my t’s, and keep any down time to a minimum. And know if there are any “gotchas” that can be avoided.Thank you.
Hi, We are following this instruction Upgrading In Place, On the Same Machine and failing in the last step. what could be wrong? We are upgrading from FME flow 2023.1 to 2024.2 So what about that file: Migration) File "/temp/tomcat/fde0b0779317417da467e76dec4c9027/restServerRestore.fsconfig" does not exist for shared resource "FME_SHAREDRESOURCE_SYSTEM".
Hello,I recently received a new fme flow 2024 from my IT department and something keeps failing when i run a large workspace(1096704 kB), i get no error but the workspace fails.This same workspace runs in fme flow 2023 without any problem.Here are my system details,FME FLOW 2023System Status: 43.39 GB of disk space available in the FME temporary folder (C:\Users\Username\AppData\Local\Temp\fmeengines\{enginename}_Engine1)System Status: 30.00 GB of physical memory availableSystem Status: 126.00 GB of virtual memory availableFME FLOW 2024System Status: 65.31 GB of disk space available in the FME temporary folder (C:\Windows\TEMP\fmeengines\{enginename}_Engine2)System Status: 30.00 GB of physical memory availableSystem Status: 126.00 GB of virtual memory availableI have been reading around but i have not been able to pint out where the problem actually lies. How can i check for example how much memory has been allocated to an engine?Could it that i need to change the engine to use the tem
I’m trying to publish a new app on FME Flow, but there are no services listed to create the app. If I try open an existing app, it says “You do not have access to the "fmedatastreaming" service.” I’m logged as a admin with all possible rights. If I go to services settings, all seems normal. So Im not able to create any app and practically run any workspace. What could have gone wrong?
We make use of parallel processing within FME Flow 2023.1. However we are struggling to de-bug issues that intermittently occur in the worker processes. I can see that, whilst running, each worker process has a log file, stored under the parent job log. However, this is deleted when the worker process closes, even if it fails. This makes it very difficult retrospectively diagnose any issues.In our FME Server 2021 instance, the worker logs are surfaced in the main job log once complete, which is fine, but I can’t identify any setting to control and replicate this behaviour.Does any one know of a config change that I can make, in FME Flow 2023, to retain these worker logs somehow?
Is there any way to cancel a system restore, it appears to be hung at Unzipping migration package stage for 1.5 hours now. I think the file system/network glitched during the process. There is no cancel in the UI, no jobs running.
