Skip to main content
Solved

FME desktop/server 2012 to 2013 Migration/compatibility

  • June 7, 2013
  • 1 reply
  • 6 views

Hi ,

 

Tried running few workbenches in built in desktop 2012 built on 2013 had macro issues hence translation failure.Had few question regarding interoperability and compatibility of desktops and servers.

 

 

1.Is there a tool/way to migrate a 2012 workbench to 2013 ? 

 

2.If we use a 2013 fme server would that seamlessly support 2012 workbenches?

 

 

3.Eager to implement transaction support for oracle spatial ,is there a suite for the same in desktop 2012 ?

Best answer by david_r

Hi,

 

 

the FME engine that is used on the Server and Desktop editions are exactly the same (given the exact same versions installed), and should work exactly the same way.

 

 

For most upgrades, it should be enough to just open the workspace in the upgraded version of FME, and it should run just fine. However, if you have used some advanced functionality, such a Python/TCL scripting, you might need to adapt the workspace / scripts slightly, depending on a lot of factors. Which error message did you get for your macro issue?

 

 

Not sure if I understand your 3rd question, could you perhaps elaborate a little? The Oracle Spatial Object reader and writer has had transaction support since at least FME2009, as far as I can tell.

 

 

David
View original
Did this help you find an answer to your question?
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.

1 reply

david_r
Celebrity
  • Best Answer
  • June 8, 2013
Hi,

 

 

the FME engine that is used on the Server and Desktop editions are exactly the same (given the exact same versions installed), and should work exactly the same way.

 

 

For most upgrades, it should be enough to just open the workspace in the upgraded version of FME, and it should run just fine. However, if you have used some advanced functionality, such a Python/TCL scripting, you might need to adapt the workspace / scripts slightly, depending on a lot of factors. Which error message did you get for your macro issue?

 

 

Not sure if I understand your 3rd question, could you perhaps elaborate a little? The Oracle Spatial Object reader and writer has had transaction support since at least FME2009, as far as I can tell.

 

 

David

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