Basically we have some fmw files that write data, and then we have a second fmw file that loads the job status info into an oracle table for logging. The first fmw, runs and then calls the DataLoadingStatus topic
Then the called mw, which populates an Oracle table with job status info from the first fmw runs, it is registered with the notification service with the “Send Notification Data to Reader” populated
We are running with engines distributed across a number of different boxes.
The process is working correctly for what it is, it is passing the correct path to the second fmw to find the temp file.
e:\\FMEServer\\Utilities\\tomcat\\temp\\603774853810044_gpas_status.txt - That file does exist on the core host.
The problem is the Engines are distributed, so when the second fmw runs on a distributed engine and goes to read that file, it is looking for that path on the local box’s E drive and not the Core host box, and that file does not exist on the local box, so it errors with:
ERROR |Text File Reader: Source dataset 'e:\\FMEServer\\Utilities\\tomcat\\temp\\605131760468036_gpas_status.txt' does not exist
Something somewhere is telling FME server where to write these temp files to this path:
e:\\FMEServer\\Utilities\\tomcat\\temp\\603774853810044_gpas_status.txt
It used to write them to the resource path, which the distributed engines could find:
resources\\system\\temp\\requestdata\\4072616362113062_gpas_status.txt'
Any Ideas where this setting might be ?
