Skip to main content

FME 2025.0 - Feature Highlights

FME 2025.0 - Feature Highlights
SagitAtSafe
Safer
Forum|alt.badge.img+2

FME 2025.0 is here, packed with exciting new features that transform how you work with data. Our new stream capabilities improve real-time processing by introducing Remote and Heartbeat support, turning fast-moving data into immediate insights for smarter decision-making. Native Neo4J integration simplifies complex graph analytics, while centralized Connection Storage in FME Flow streamlines shared connection management. With 2025.0, data handling is more agile, flexible, and powerful than ever before. 

Stay tuned for big groundbreaking advancements reveals at The Peak of Data and AI.

Feature Highlights

Remote Streams: FME Flow Streams can now run on Remote Engines Services, as Remote Streams, to run streams closer to data sources, drastically reducing latency and boosting scalability. To maintain stability, Remote Streams automatically shut down after 24 hours of disconnection from the Remote Engines Service, and seamlessly resume when reconnected—all supported by an improved connection UI for a smoother setup experience. 

Heartbeat Streams: Our new Heartbeat support ensures that when streams experience extended quiet periods, the TimeWindower now processes features accurately, avoiding outdated data retention. This feature introduces a configurable heartbeat option on the connector, enabling the system to stay responsive even in the absence of data flow. KafkaConnector is the first to support this capability, with additional streaming connectors scheduled to release in the coming months. 

Want to learn more about this feature? Watch our short demo video here

 

FME Flow as Connection Storage Location: Streamline your connection management by leveraging FME Flow as a centralized repository for database and web connections. By designating FME Flow as your storage location in FME Form, teams gain immediate access to shared connections without extra setup. We’ve ensured that a Centralized Connection store enables consistent configurations, tightens access controls, and improves overall workflow efficiency. 

Neo4j Reader: FME now includes native support for Neo4j, enabling users to effortlessly integrate graph database queries into their workflows. The Neo4j Reader lets users execute Cypher queries directly to retrieve nodes, relationships, and paths, all while preserving the integrity of your graph structures. With the added flexibility of SQL transformers to refine query results, users can now more easily analyze network relationships, connected assets, or social graphs.

Additional Enhancements

Spatial Definition Table Improving Spatial Data Visibility: The new Spatial Definition Table within Reader Feature Types displays spatial column names, geometry types, and spatial types (where applicable) to enhance spatial data discovery. Additionally, enhanced canvas objects now indicate the presence of spatial data by showing the spatial column name when available, complementing the Schema Preview window for a more intuitive and efficient data exploration experience. 

User Parameters Precise Conditional Visibility Control: Building on the Conditional Visibility feature from FME 2023.0, FME 2025.0 now introduces Compound Conditions. This enhancement allows for multiple conditional statements and provides a broader set of operators, offering even more control over when parameters appear for an intuitive user interface.

Want to learn more about this feature? Watch our short demo video here. 

New and Updated Integrations

IBMMQConnector: FME now includes a dedicated IBMMQConnector for IBM MQ 9.X, streamlining both sending and receiving messages. Delivered as an FME package, the connector eliminates the need for complex JMS library setups, offering simplified connection parameters and supporting both streaming and batch message processing. 

RabbitMQConnector Quorum Queue Support: In addition to classic queues, the RabbitMQConnector now supports quorum and stream queues. With the new Queue Type parameter, users can select Classic, Quorum, or Stream, facilitating reliable and flexible message retrieval across all RabbitMQ queue types. 

Database Case Control Table and Column Names: FME now offers enhanced control for managing table and column name formatting across all database formats. Users can choose to convert names to uppercase, lowercase, or keep the original case while ensuring compatibility across different database systems. 

Databases Write Schema-Only Tables: With the new Always Create Table setting available across all major database formats, FME generates database tables even when no feature data is provided. This streamlines schema-only migrations, allowing users to replicate database structures from source to destination without requiring data. 

Want to learn more about this feature? Watch our short demo video here

Simplified Database Integrations Unified Format for Spatial and Non-Spatial Data: FME has consolidated major JDBC-based database formats to support both spatial and non-spatial tables under one unified format name. 

Improved formats:

  • Snowflake
  • Microsoft SQL Server (JDBC)
  • Microsoft Azure SQL Database (JDBC)
  • SAP HANA and SAP HANA Cloud
  • Teradata

Stay tuned for further database unification in further releases. 

Add IFC Opening Feature Reading: FME’s IFC API Reader now supports IfcOpeningElement features, allowing for more precise handling of wall, window, and door openings. This update enables accurate clipping of boundary surfaces so that walls, doors, and windows are rendered as single flat surfaces when necessary. By using IfcOpeningElement solids for geometry processing, interoperability across BIM, GIS, and 3D modeling applications has been significantly improved.

12 replies

charry
Contributor
Forum|alt.badge.img+5
  • Contributor
  • March 5, 2025

When will cesium 3dtils support 1.1 and more parameter settings? For example, double side


omerseyfettin
Contributor
Forum|alt.badge.img+7

This monring i upgrade FME version 2024.2 to last version FME 2025.0 and after upgrade i start my workbench which include “Bentley Microstation V8” reader. FME give a message “Module 'acad/ACAD' is unavailable for use with this FME edition” why ? I resarch old topic in the Community some body had some problem at 2022. But no body give any solution way for fixed this problem. Also i found acad.dll in C:\Program Files\FME\plugins\acad. 

What is real problem ?  

Note: After uptdate FME i am uninstall Autocad Map program from my computer. Think couldnt any relation maybe, because the Autocad differntly program.


luke.hicks
Safer
Forum|alt.badge.img+8
  • Safer
  • March 7, 2025
charry wrote:

When will cesium 3dtils support 1.1 and more parameter settings? For example, double side

Hi ​@charry,

   Support for Cesium 3D Tiles 1.1 is on our radar. Although I cannot guarantee this, we are looking to implement it by the end of the year.


daveatsafe
Safer
Forum|alt.badge.img+19
  • Safer
  • March 7, 2025

Hi ​@omerseyfettin,

Please try re-installing FME 2025.0 on your computer. FME and AutoCAD Map 3D share some DLLs that may have been deleted when AutoCAD was uninstalled. Reinstalling FME should fix this.


omerseyfettin
Contributor
Forum|alt.badge.img+7
daveatsafe wrote:

Hi ​@omerseyfettin,

Please try re-installing FME 2025.0 on your computer. FME and AutoCAD Map 3D share some DLLs that may have been deleted when AutoCAD was uninstalled. Reinstalling FME should fix this.

Thank your for your recomment, already i setup the old version of FME 2024.3. Now everything going well as before setup 2025.0. So, i want to upgrade my program but, i am no sure it working well and not get more problem. Reason i decided waiting some.


johannafalk1
Contributor
Forum|alt.badge.img+7

Hi, 

I installed the new Workbench 2025.0 and it seems that in this version the IFC_API writer is not available anymore. Is this on purpose? 

However, I can find the IFC_API reader. 

Thanks,

Johanna


aidanatsafe
Safer
johannafalk1 wrote:

Hi, 

I installed the new Workbench 2025.0 and it seems that in this version the IFC_API writer is not available anymore. Is this on purpose? 

However, I can find the IFC_API reader. 

Thanks,

Johanna

Hi ​@johannafalk1,

We briefly had the IFC_API writer exposed in 2025.0 betas during development - it was intentionally removed for the 2025.0 release as it's still under active development and not yet ready for general use.


charry
Contributor
Forum|alt.badge.img+5
  • Contributor
  • March 13, 2025

FME2025,3dtiles cannot be generated correctly!The results I obtained using the same process in FME 2023 and FME2025 are different. There is an issue with the 3dtiles format in FME2025, and the Z value cannot be processed correctly.

Can this issue be fixed?

 


ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • March 13, 2025

Are there any updates to the JMS Receiver on the horizon?


luke.hicks
Safer
Forum|alt.badge.img+8
  • Safer
  • March 13, 2025
charry wrote:

FME2025,3dtiles cannot be generated correctly!The results I obtained using the same process in FME 2023 and FME2025 are different. There is an issue with the 3dtiles format in FME2025, and the Z value cannot be processed correctly.

 

Hi ​@charry,

I’m sorry to hear that you are running into issues with this version of FME. Please contact our Customer Support and we will have an expert check this over with you.


steveatsafe
Safer
Forum|alt.badge.img+12
ebygomm wrote:

Are there any updates to the JMS Receiver on the horizon?

Hi ​@ebygomm, Thanks for the question!

We want to learn what Message Broker vendor you are using where JMSReceiver isn’t supporting the features you’d like to use.  Perhaps Solace? TIBCO?

But also, we would like to learn what improvements you are seeking to see in the JMSReceiver and perhaps JMSSender? 

Do you happen to have any tickets opened seeking enhancements or ideas posted on the community you can share?

Outside of JMSSender/Receiver, we have these connectors on the FMEHub that could be relevant:

  • RabbitMQConnector (link)
  • IBMMQConnector (link)
  • MQTTConnector (link)
  • MQTT Protocol
    • IBMIoTConnector (link)
    • AzureIotConnector (link)
    • AWSIoTConnector (link)
    • GoogleIoTConnector (link)
  • others AWS SQSConnector (link), AWS SNSSender, and AWSServiceBusConnector (link)

I look forward to hearing from you!


ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • March 14, 2025

Using the JMS Receiver, connecting to WebMethods/Software AG/Nirvana

 

The main issue is I can’t get the process to ever terminate, see

 

Terminate workspace with a JMSReceiver | Community

 

Also having to use an SQL executor to insert line by line, because with a time windower and group processing we seem to have no way of getting the data in a timely manner if there is a gap in the stream. Heartbeat streaming may solve this issue but it sounded like it wasn’t applicable across all streaming transformers.

 

It would also be nice if the installation process could be streamlined, currently the jar files have to go in two different places depending on whether using JMS messaging within an automation or a JMS receiver, and cacerts have to be updated in two separate places also (or 4 once you have two hosts!)


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings