Skip to main content
Solved

FME in App(V) : virtualized


gio
Contributor
Forum|alt.badge.img+15
  • Contributor
QUOTE:

 

Has anyone had luck delivering FME in an App-V environment? Our company is trying to get all apps delivered this way. The problem we run in to with FME is the dependence on Arc licensing for certain readers/writers. From what I am told by our application packagers, App-V applications are agnostic of other App-V applications. Therefore, when running FME in App-V, ESRI readers and writers are not available.

 

 

Our workaround for now is using a standard install with FME, and starting up the App-V version of ArcGIS when FME opens. It works, but isn't exactly what we are looking for. Submitted: 11/15/2012 4:52 PM

 

aked the question we have.

 

 

Virtualized FME cannot find Esri license server.

 

 

Do any of u have a solution?

 

We are told to set an enviromental variable set in the packaged FME. Is that the only solution?

 

And why can i use gdb's ? Arn't those dependend on Esri licenses as well?

 

 

Eagerly awaiting your answer(s)

 

 

Greets,

 

Gio

Best answer by helmoet

This is what I got from our App-V developer, Rolf van Duijn:

Here is the information needed for the connection group to work and for the GPSbabel and Oracle readers to work:

 

 

- App-V 5 COM interaction is Off, since it must be equal to Esri ArcGis Pro in connection with the connection group (both COM interactions must be the same, otherwise they can not be in a connection group). In the ArcGis package, this was Off after performance testing.

 

 

- The next key must be present in the bubble so that the TOMTOM Poi reader works (there is a check by FME on the key below)

 

[HKEY_LOCAL_MACHINE \\ SOFTWARE \\ Wow6432Node \\ Microsoft \\ Windows \\ CurrentVersion \\ Uninstall \\ {1B8FE958-A304-4902-BF7A-4E2F0F5B7017} _is1]

 

 

The subkeys and values of the aforementioned registry key are now also filled. Here, among other things, the installation path of GPSbabel is included.

 

 

- An environment variable has been created in UEM that sets the Oracle instant client and the GPSBabel folder for FME in the PATH variable. The environment variable is not properly read from the bubble without this addition.

Using this, our FME-ESRI-GPSBabel-ORACLE-MSSQL “bubble" works (save a couple of issues, like one has to start ESRI ArcGIS once to add some parameters to the registry, otherwise "licensing related operations").

View original
Did this help you find an answer to your question?

9 replies

fmelizard
Safer
Forum|alt.badge.img+18
  • Safer
  • July 10, 2013
Hi Gio,

 

All ESRI products, beside the API gdb reader/writer need a ESRI license. 

gio
Contributor
Forum|alt.badge.img+15
  • Author
  • Contributor
  • July 11, 2013
Hi Itay,

 

That much is clear. (altough shp format is public....)

 

 

The problem is how to get to the Esri lisence when FME is run in a virtualised environment. FME is "bubbled".

 

FME doe not see ESRI license.

 

Strangely personal database(mdb) reader/writer is affected but not gdb.

 

We use Acces 2003. (because of compatibility with a bunch of soaftware-packages)

 

 

The qoute of the questioned is posted in 2011 and never answered. 

 

 

We recenetly, march 2013, moved to an Bubbled environment.

 

FME works nice but, we run FME2012sp2 on standard server and 2013sp2 on another. Both 32 bit.

 

 

FME2013sp2 is about to be packaged for virtualisation. We like to solve aforementioned problem before roll-out.

 

 

We are now going to use both 64 bit and 32. 32 bit to keep using the 32 bit accces mdb's.

 

 

 

Thanks for your reaction.

 

Greetings

 

Gio

  • July 15, 2013
Hello Gio,

 

 

We had an initiative to put everything in the AppV environment and our IT group worked very hard to make this happen.  FME works fine in AppV, but not when reading or writing to ArcGIS formats.  As you know, this is because it needs to check out an ArcGIS license.  In order to check out an ArcGIS license, it has to "see" the ESRI install.  However, AppV applications cannot "Talk" to each other.

 

 

Our end result is that we did not package FME as AppV

gio
Contributor
Forum|alt.badge.img+15
  • Author
  • Contributor
  • July 16, 2013
Hi Jerrod,

 

 

WE came to the same "solution".

 

We had to proof to our IT that there is no known solution for this apaart form taking FME out of AppV.

 

 

Thanks for your answers all.

 

 

Im happy to take FME out of appV anyways because it poses more issues.

 

 

Greetings to all,

 

 

GIo.

 

 

And FME forever!

gio
Contributor
Forum|alt.badge.img+15
  • Author
  • Contributor
  • July 16, 2013
I forgot to tell:

 

 

First they are going to try a so called inter-bubble communication before we abandon FME in AppV.

 

 

bb again

 

 

Gio

did anyone find a solution to this or is the solution - just dont virtualise our fme desktop if you need esri license?


helmoet
Forum|alt.badge.img+8
  • February 20, 2018

Hi, we are experiencing the same trouble. Are there any developments here? @gu19495


helmoet
Forum|alt.badge.img+8
  • August 23, 2018

Hi @MitaAtSafe and @DebbiAtSafe, I saw some fine items on the issue of FME and ESRI from your hands on the Knowledge Center. Would it be possible for one of you to comment on this issue?


helmoet
Forum|alt.badge.img+8
  • Best Answer
  • September 27, 2018

This is what I got from our App-V developer, Rolf van Duijn:

Here is the information needed for the connection group to work and for the GPSbabel and Oracle readers to work:

 

 

- App-V 5 COM interaction is Off, since it must be equal to Esri ArcGis Pro in connection with the connection group (both COM interactions must be the same, otherwise they can not be in a connection group). In the ArcGis package, this was Off after performance testing.

 

 

- The next key must be present in the bubble so that the TOMTOM Poi reader works (there is a check by FME on the key below)

 

[HKEY_LOCAL_MACHINE \\ SOFTWARE \\ Wow6432Node \\ Microsoft \\ Windows \\ CurrentVersion \\ Uninstall \\ {1B8FE958-A304-4902-BF7A-4E2F0F5B7017} _is1]

 

 

The subkeys and values of the aforementioned registry key are now also filled. Here, among other things, the installation path of GPSbabel is included.

 

 

- An environment variable has been created in UEM that sets the Oracle instant client and the GPSBabel folder for FME in the PATH variable. The environment variable is not properly read from the bubble without this addition.

Using this, our FME-ESRI-GPSBabel-ORACLE-MSSQL “bubble" works (save a couple of issues, like one has to start ESRI ArcGIS once to add some parameters to the registry, otherwise "licensing related operations").


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