With FME now supporting web socket layer there is an inherent problem in the product I've noticed. That is, the most important part of a web socket connection is the ability to publish real time data to applications. Unfortunately this ties up an ENTIRE FME engine constantly.
From my perspective there is very little use for the web socket layer in the current model. There needs to be an extension or something on a different costing model which allows multiple feeds to be running constantly.
To give an idea of where I'm coming from I'll explain my situation. Real time traffic and transport management applications is what I'm working with at the moment and when you're receiving GPS from your assets and from monitoring systems I want to connect the data/events together in a real time web mapping application. Currently, FME can in no way be fit for purpose (unless 20 FME engine licenses suddenly drop in price).
This is the article I base any assumptions off:
https://knowledge.safe.com/articles/1305/websocket...
Released
Web Socket - FME Engine Model Change
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
I would be very interested to read what Safe might have to say about this. In the meantime, can you take a look at open-source products for options, and report your findings to this thread?
+8- Supporter
FME Cloud could be an option if you are looking at cost models and web sockets.
+5Can you explain some points:
- Why does you use FME Server for the realtime ?
- Which readers, writers do you use?
Actually, FME Server integrates Netty server for the Websocket transmission.
You can integrate in the same workbench multiples readers and one websocket writer. This writer calls a websocket server (ex: Nodejs) and you parse the flow with this server.
One FME Engine and One Websocket server :)
+4- Safer
Thanks for the feedback. I would like to learn more. There are actually 2 modes that you can use websockets with FME Server. 1 is the high speed data streaming approach that does lock an engine. The idea with this one is that for occasions where the data is coming or going at a high speed 100's, 1000's, or more of events per second. Thru this we do have clients that have used a single engine on a high speed channel to support a large number of web clients. The other approach uses the event model in which a workspace is triggered by activity on the web socket. This is fine for 1's or 10's of events per second. Be great to connect next week and learn more about your challenge and see if either of these meets your needs. We can discuss hybrid approaches. Are you around next week?
+4- Safer
Here is the plan for FME 2016.1
- We are going to extend the FME Server web socket capability so that a single web socket receiver can receive data from many streams at one time. Prior to this a single web socket receiver could only pull data from one stream resulting in a need for 1 engine for each stream. Now a single workspace (engine) will enable users to listen to as many streams as they want.
This will be available in an FME 2016.1 beta very shortly. Thanks Matt for the idea.
+14- Safer
Multiple connections (i.e. receiving data from multiple streams) has been implemented in FME 2016.1 (Build 16494) and Newer.
Documentation: WebSocketReceiver, WebSocket Publisher (FME Server), WebSocket Subscriber (FME Server)
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.