***Note from Migration:***
Original Title was: Automatically disable the option redirect to FME data inspector when posting a Workspace to FME server.
When you have a long chain of workspaces and you have updated a workspace at the beginning of the chain and saw in the datainspector all data is correct you will be blind to annything else and post it as soon as possible to the server. But after hours of waiting for the result you see the process went wrong because the data wasn't written.
+5As far as I know, the redirect does not take effect on FME Server. Even if the option is activated in FME Desktop, the workspace should still work normally on FME Server, writing out all data. Have I missed something?
+1'
Here is the proof in the logfile from the server.
We have the problem once a week i think.
And all depending workspaces have not the result you want so the whole process has to be rerun.
+18Today I spend a considerable amount of time trying to find the reason why al lot of featuretypes were missing from the output of our 40+ workspaces spanning process. Eventually I found a workspace which had been deployed with 'redirect to inspector' switched on, producing no output 'on disk' on server (2016.0). Not for the first time.....
Would be nice if there were a way to avoid this, e.g. disabeling 'redirect to inspector' on saving the workspace', or ignoring this setting when ran on server. Server has no Inspector application, so even a failure-status could be seen as appropriate.
Kind regards,
Martin
'
+7Just for your information:
https://knowledge.safe.com/idea/38704/global-setting-for-redirect-writers-to-inspector.html
+18
+19
As @ekkischeffler indicates, the Publish Wizard has a feature that disables "Redirect to Inspector". It's possible there is a problem with this feature, but I want to confirm you are in fact using the Publish Wizard when this problem is encountered.
+19
+19
+19
+1
+1
+19
Unfortunately, this change is a bit too major to get into FME 2017 at this time. That said the team is seeing what else we could do to help avoid these scenarios.
Given that you're already using a Python script to do the posting, in the short term you could search the .fmw for the line:
LOG_END_BANNER *** All writer output has been redirected to the Data Inspector *
And if that is in the workspace then your script could bail out. @patrick_koning @martinkoch @jeroenstiers
+1It's not a solution but a clear indication that we have to put i right before deploying.
Hope it's in the 2017.1 version.
Thanks for thinking with us.
@martinkoch @daleatsafe @jeroenstiers
+18
Think for the short term, I will type a few extra lines of python to search through the logfiles of each process-step and give a sys.exit(1) if it finds the 'line which should not be mentioned'.
+13Testing with FME Server 2017.1.2.1 Build 17725 and FME Server 2018.0 Beta, I have observed that the 'Redirect to FME Data Inspector' flag is ignored – data is written regardless of this setting after publishing to FME Server.
Note: If you then download the workspace from FME Server, using FME Workbench, the 'Redirect to FME Data Inspector' is not selected.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
