Hi,
My approach is differnet than yours.
1st workspace: I will start with DGN reader (single merged feature type option) and I will use published parameter to pass the file name. I will make necessary modification to the features as required and write to DWG writer.
2nd workspace: I will start with excel reader to pass the parameters with workspace runner of above workspace.
This will make 1 dgn / execution and can get rid of memory issues even when dgn files contains more number of features
Hope this helps.
Pratap
Hi,
My approach is differnet than yours.
1st workspace: I will start with DGN reader (single merged feature type option) and I will use published parameter to pass the file name. I will make necessary modification to the features as required and write to DWG writer.
2nd workspace: I will start with excel reader to pass the parameters with workspace runner of above workspace.
This will make 1 dgn / execution and can get rid of memory issues even when dgn files contains more number of features
Hope this helps.
Pratap
With your method, have you had job failure 1000+ or 2000+ files into the translation on FME Server? I've had it happen for another translation and it is why I want to avoid WorkspaceRunner or JobSubmitter in this case.
With your method, have you had job failure 1000+ or 2000+ files into the translation on FME Server? I've had it happen for another translation and it is why I want to avoid WorkspaceRunner or JobSubmitter in this case.
You mean to say that we will get memory issues, if input is 1000+ files...
As pratap already advised, I think you already mentioned your own solution. Try using a parent/child structure. It will always be a better way to process so many files/data.
You mean to say that we will get memory issues, if input is 1000+ files...
When there's 2000+ files, I'd get this error:
ERROR |Terminator_deliver_asc_xyz: Failed to
open FME feature store file `\\storage\05232112\FME\resources\logs\engine\current\jobs\9000\job_9253_0_log.ffs' for write -- ensure that the folder exists
My understanding is, this job_####_0_log.ffs
file gets overwritten again and again, based on how many times the child
workspace opens.
Did you have this behaviour?
When there's 2000+ files, I'd get this error:
ERROR |Terminator_deliver_asc_xyz: Failed to
open FME feature store file `\\storage\05232112\FME\resources\logs\engine\current\jobs\9000\job_9253_0_log.ffs' for write -- ensure that the folder exists
My understanding is, this job_####_0_log.ffs
file gets overwritten again and again, based on how many times the child
workspace opens.
Did you have this behaviour?
I have not tried in same translation i.e. dgn to dwg but I have tried to dgn to oracle db some time ago for 2000+ files. It didnt gave any error.
As far as I understand, FME wont overwrite the file as many times the child opens until we tell to FME to perform.