Skip to main content
Archived

Central repository for Custom Transformers used by Desktop and Server

Related products:FME Flow

Right now, there is no ideal configuration to store a Custom Transformer exactly one time and use it within FME Desktop and FME Server as a Linked Custom Transformer. There are several workarounds:

1. Create Shared FME Folder --> use the folder within the Workbench --> upload Custom Transformers to FME Server
This works, but in fact it duplicates the Custom Transformer on each FME Server (Development, Staging, Production). When creating a new version of the Custom Transformer, it has to be uploaded to all FME Servers again.

2. Create network share and reference it as a Custom Resource within FME Server
Unfortunately, the FME Server Engine doesn't scan Custom Resources, so a Workspace with a Linked Custom Transformer from the network share will crash in FME Server.

3. Share the Engine Resource Folder of FME Server
This would also work, but I don't like the idea of exposing some server internal folder by sharing it to the network. Furthermore, it doesn't solve the problem of sharing a Custom Transformer across different FME Servers (Development, Staging, Production), because each instance would have its own Engine Resource Folder which would lead to multiple Shared FME Folders within Workbench.

4. Use Embedded Custom Transformers
Not really an option because it is impossible to use exactly the same Custom Transformer per definition.


Thus, FME Server and Desktop should be able to reference any arbitrary network folder as a source for Custom Transformers.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

4 replies

rylanatsafe
Safer
Forum|alt.badge.img+13

@stewartharper - This reminds me of the "Private" or "Enterprise" idea for FME Hub.

 

What is this idea? Having some type of FME Hub repository on-premises that only trusted users or those on your internal network could access.

rwhittington
Contributor
Forum|alt.badge.img+1
  • Contributor
  • August 17, 2017

We are dealing with the same type of scenario where we have multiple versions of fme (desktop and server) and each with a shared set of private Custom transformers. A private FME hub would kind of work but you still have to download/install from the hub to your fme installation (right?). The closest thing we have come up with is to have each version of fme server engine expose its shared resources (#3 above) as read only to fmeauthors. Yes, as @mu88 points out, this requires duplication of the repositories; however if we designate one as the master for each version of fme then we kind of have what we need as long the fme server admin manages the publishing from the master when something changes. Perhaps the best thing we can do right now is to come up with some guidance or some kind of reference implementation.


How about a Transformer Reader in FME? In FME, you could read Transformer on the Fly from a defined location where necessary. For example, from a Transformer Repository. This should be very flexible.


How about a Transformer Reader in FME? In FME, you could read Transformer on the Fly from a defined location where necessary. For example, from a Transformer Repository. This should be very flexible.


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