Deploying FME Flow using Flow Apps or the REST API
Recently active
We just installed FME Flow 2024.1.2.1 on a Windows machine and I published a workspace. Running the workspace immediately ends in:Undefined macro `WORKSPACE_NAME' dereferenced in file `flow_testing\sqlserver_test_delete\sqlserver_test_delete.fmw' The workspace was published from an ArcGIS Interoperability Workbench [FME(R) 2024.0.1.0 (20240328 - Build 24202 - WIN64)], but I tried the same from FME Form 2024.2. The result is the same. The workspace is as simple as it gets. Just a reader and a writer, and the error appears independent if there is a name for the workspace set or not. Can somebody please point me the right direction to solve the issue?
Hi All.Our FME servers are still running 2022.2, but I need to run a specific job in FME Form 2024.1, and have it execute a workspace on the server.But the workspace refuses to connect to the server. This happens regardless of using FMEServerJobSubmitter (as copied from an old workspace), or a brand new FMEFlowJobSubmitter.The web connection used is saved in an older version (2020-2022), and works there. I tried to create and use a new connection in 2024, but that also fails.What caveats are present when trying to connect 2024 to a 2022 server ?Any insights and experiences are welcome.Cheers, Lars I.
How to setup FME Server as POST Endpoint capable of receiving HTTPS requests from AWS’s source IP range.?
I’m considering updating FME Flow to version 2024.1 on a server where we currently have ArcGIS Enterprise 10.9.1 installed. Some of my workspaces utilize Arcpy and the ArcGIS API for Python.Based on the compatibility table, ArcGIS Enterprise 10.9.1 is compatible with FME 2021.2, but not with FME 2024.1.Can anyone clarify whether Arcpy and the ArcGIS API for Python will function properly with FME Flow 2024.1 in this setup? Are there any known issues I should be aware of?https://support.safe.com/hc/en-us/articles/25407724093837-Notes-on-FME-and-Esri-Versions-and-Compatibility
We have an FME Flow automation that monitors a network directory for new files. Once new files arrive, they are emailed as attachments using an FME Flow Email (send) Action.Is there a way to make the “Email To” distribution list somewhat dynamic?We have an FME Workspace that generates a text file of the desired distribution list. Currently when it is determined a change might have occurred in the list, we open the text file and manually copy & paste the contents into the “Email To” of the FME Automation monitoring the network directory. Is there a means to have the Automation’s “Email To” parameter just use the text file directly?Or perhaps to have the workspace that generates the text file be included in the automation and provide the current distribution list once the automation is triggered?
We are in the process of setting up our production environment. I have enabled version control in Dev and have been committing/pushing my workbench edits to our external GIS repository. I have connected our production environment to the same repository, but Fetch doesn’t pull down the workbenches. Is that normal behavior, as is that user-error? I know I can make a Project file and move them, but was wondering if I’m doing something wrong.
I have multiple FME Flow/Server Apps that are used by a lot of people. We have not decided to give each individual their own account on Flow. That might be the answer, but is there a way to get the user ip address or computer name? If it is a public accessible app I know it might be tough, but I feel like it should be able to read this in the logs.
We are converting a number of GIS-focused Automations in FME Flow 2024.0 to use the new SDE Database Connections instead of the old PATH resource. FME Flow is returning an error when attempting to read the new database connection properties: ‘An error occurred while attempting to retrieve the connection parameters from the connection file’ For each of the FME Flow Database Connections, we used an FME Resource, ‘SDE_GISD’, for the path reference for the connection file. We found if we use a UNC path instead of the FME Flow resource it works as expected. Is this a limitation or are we doing something wrong?Connection works as expected on local host, local server host, and with UNC path for the database connection within FME Flow. Just not with using a Resource path in the connection.Error:315 2024-7-31 11:51:25 | Opening the Esri Geodatabase reader 316 2024-7-31 11:51:25 | An ArcGIS license is already checked out. The product checked out is 'ArcServer' 317 2024-7-31 11:51:25
