I am trying to create a data download service in FME Server 2016 (single engine), but have run into some problems.
I have a master workspace that is created as a Data Download Service in FME Server.
The master workspace is structured as follows:
The data order is chopped into sub-orders and passed into an FMEServerJobSubmitter. The workspace called by the FMEServerJobSubmitter stores the exported data into a folder (the folder name is specified as a parameter in the FMEServerJobSubmitter). When all the sub-orders are completed, a FeatureWriter (FileCopy) moves the folder and its contents into the FME_SERVER_DEST_DIR, and the data is then zipped and shipped.
Most of the writers in the sub-workspace have fanout, and this is where my problems begin:
- The writers that only have fanout on the feature type level work fine. For instance, a shapefile writer that simply produces shapefiles with different names works perfectly.
- The writers that have fanout on the dataset level produce junk files. For instance, for AutoCAD, this should produce something like:
WindPower.dxf with the layers Turbine (points), Park (polygon), Powerline (line), etc.
HydroPower.dxf with layers Dam (line), Reservoir (polygon), Tunnel (line), etc.
Instead, I get one single dxf with all the features crammed into one layer and the geometry defined by the first feature that enters the writer. This happens regardless of there being one or more dxf files to output, and regardless of the sub-workspace being called one or several times during a translation.
What baffles me is that this unwanted behavour only occurs when the sub-workspace is called from the master workspace. I can run the uploaded sub-workspace in FME Server and get a nice, fanned-out result. But the instance it is called from the master workspace, the end product is a junk file.
Any ideas what I am doing wrong or how to solve this? Is there some trick I do not know about when calling sub-jobs within FME Server?
Is there any other way I can set up my Data Download Service? Should I define my sub-workspace as something other than a Job Submitter Service?
