span8
span4
在安全亚搏在线,我们非常努力工作,以确保FME是发行版本之间的向后兼容。
例如,在FME桌面2015年的发行版本创建的工作区可以打开和FME桌面2016上运行。
向前兼容 - 在旧版本的FME的打开一个新的工作空间的能力 - 没有保证,尽管它可能在某些情况下工作。
从理论上讲,你可以在FME的新版本打开任何旧的工作空间,它会工作。
在实践中,FME是分开向后兼容很多版本。不过,也有限制这一点。在某些情况下,我们可能要修复的东西,是在以前的版本和“修复”破可以创建不同(希望更好)结果的“破”的版本。
此外,有时不兼容是由需要拆除格式,或改变其API的在线网络服务强加给我们。
因此,当FME的升级和跳过多个版本,我们建议您将它们投入生产前测试您的工作流程,或至少检查更新的列表,查看是否存在与您所使用的功能,任何东西。亚搏在线
出于这个原因(和其他人)如果打开,编辑FME可能会警告你,然后尝试保存旧的工作区在新的FME工作台,并给你的机会来保存备份副本。
Tip:Remember you can have multiple versions of FME Desktop installed on the same machine, just by using a different installation folder.So you can keep your "production" version of FME working while testing in the latest release.
一般来说,工作区是NOT向兼容。这是您在创建FME 2016年不太可能在2015年FME工作的工作空间。
这是特别重要的,当你创建一个客户工作区使用他们的FME安装考虑到,或者当您使用FME Server安装。
例如,如果升级FME桌面到最新版本,但不FME Server,则运行在发布到服务器新创建的工作区将无法成功运行的风险。
出于这个原因,如果你试图在旧的FME工作台打开一个新的工作区,或发布新的工作区旧的FME Server的FME会警告你。
Tip:Again, remember that you can have multiple versions of FME Desktop installed.So you can install the latest FME Desktop and still keep your older FME Desktop for workspaces you need to publish to your FME Server.
FME版本形式20xx.a.b.c编号 - 例如2016.1.1.2
xx | New version |
|
a | Major update |
|
b | Minor update |
|
c | Patch update |
FME的新版本意味着功能已显著改变。向后兼容性may受到损害 - 如果不可避免的 - 和向前兼容的可能性很小。例如,从2016年的工作空间是不太可能在2015年的工作。
FME——的一个主要更新:发生一次或两次 per year - also means Backwards Compatibility may be compromised - again, only if unavoidable - and Forwards Compatibility is also less likely.For example, a workspace from 2016.1 may not work in 2016.0
A minor update of FME - which occurs once or twice per major update - usually consists of only non-urgent bug fixes.向后兼容性 will not be compromised.It's also unlikely that Forwards Compatibility will be affected.For example, 2016.1.1 is likely to work in 2016.1.0 (and vice versa).
A patch update of FME is usually an emergency hotfix, and so we hope not to make any.However, if a patch update is released Backwards Compatibility should not be compromised.向前兼容 is also unlikely to be affected.For example, 2016.1.1.2 should also work in 2016.1.1.1.
You may have noticed that FME transformers have a version number.This is related to FME version compatibility, as is the type of updates made to transformers.
New Transformers: Use of a newly released transformer renders a workspace immediately incompatible with prior versions.For example, a 2016.1 workspace with theHTMLReportGeneratortransformer will definitely NOT work in 2016.0 because that transformer did not exist.
Updates without New Version:If the core processes for a transformer change then it's likely a workspace will be still backwards and forwards compatible, as it can be open and run in either version.However, it might produce slightly different results in each.Generally this would be for a bug fix, so the results of running the workspace in an older FME are likely to be incorrect;the newer FME results will be correct but different.
This is one reason we recommend testing workspaces when upgrading to a newer FME version.
Updates with New Version:If the parameters for a transformer change then it's likely the transformer will be given a new version number.Backwards compatibility is assured because opening an older workspace in a newer FME does not automatically apply an update to the newer transformer version.Adding a newer version of a transformer - as with a completely new transformer - renders a workspace incompatible with prior FMEs because that transformer version won't exist.
Not applying new versions automatically means transformers can become "out of date", which is why an"Update Transformer"tool exists in Workbench.
New Default Values:If the default value of a parameter changes - the default used to be "no" but in a newer version becomes "yes" - then backwards compatibility is assured because opening an older workspace in a newer FME does not automatically change that default.Such a change will not affect forwards compatibility either, although the newer default will be applied.
Workspaces generated with FME on any platform (Windows 32-bit, Windows 64-bit, Linux, Mac) are supported on FME for any other platform.However, some formats are not supported on particular platforms.Please consult亚搏在线safe.com/formatsfor more information.
In addition, very large 64-bit workspaces may exceed the per-process RAM limit of 32-bit FME.Please consultFME桌面寿哪个版本的ld I install?for more information on 32- vs.64-bit FME.
Functionality in beta builds of FME may be changed or removed without notice in the course of development and testing.Workspaces created using a the beta build may therefore be incompatible with the release build of that version.
The earlier in the development cycle, the more likely it is that beta build functionality will change.At the other end of the spectrum, "release candidate" beta builds are close to the final product and unlikely to have any further major updates.
In short, backwards compatibility is not guaranteed with beta builds, though in most cases it will work fine, especially close to final release.
If you have a workspace created in a prior release that does not run in a current release or beta, the issue would most likely need to be addressed by our developers.Please report the problem to ourtechnical support team, including your workspace, log and sample data if possible.
You should also make sure that you have configured the new FME version the same way as the old one.Check that you have the same:
©2020安全亚搏在线软件公司|法律