Hi @leif,
First off... I have to bring up the licensing here. FME Desktop is not licensed for server backend usage like this. I'd review the license agreement to ensure you are within the agreement. You are well within the license agreement to set a scheduled task on the system and have the workspace run in via that semi-automated way.
Database... If I understand the technical issue it is likely that your workspace contains a database connection (we call that a named connection). By default, the location of this is stored in a user's profile that created the named connection. I suspect the IIS Web Server is running under a different account. So it would not have access to the Named Connection file created by the user that created the connection and the workspace.
So, I might try to convert the database connection in the workspace to embedded and make sure that all parameters are private (and have a default value). This would keep it simple when you call the workspace you don't have to pass anything to it and ensures that it has the correct values without any need to be sent from the php script.
I wasn't understanding the need to make the database public.
Default Paths... I'm not sure what you mean here... if you are using Mapped Drives to network locations, again, this is for the user profile that is logged into the computer. The Webserver session wouldn't know anything about the user's mapped drives. So you'll have to use a local drive or proper UNC paths and ensure that the Webserver "Log in As" service setting is a user that has access to the network drive location.
Let us know if this helps.
Hi @leif,
First off... I have to bring up the licensing here. FME Desktop is not licensed for server backend usage like this. I'd review the license agreement to ensure you are within the agreement. You are well within the license agreement to set a scheduled task on the system and have the workspace run in via that semi-automated way.
Database... If I understand the technical issue it is likely that your workspace contains a database connection (we call that a named connection). By default, the location of this is stored in a user's profile that created the named connection. I suspect the IIS Web Server is running under a different account. So it would not have access to the Named Connection file created by the user that created the connection and the workspace.
So, I might try to convert the database connection in the workspace to embedded and make sure that all parameters are private (and have a default value). This would keep it simple when you call the workspace you don't have to pass anything to it and ensures that it has the correct values without any need to be sent from the php script.
I wasn't understanding the need to make the database public.
Default Paths... I'm not sure what you mean here... if you are using Mapped Drives to network locations, again, this is for the user profile that is logged into the computer. The Webserver session wouldn't know anything about the user's mapped drives. So you'll have to use a local drive or proper UNC paths and ensure that the Webserver "Log in As" service setting is a user that has access to the network drive location.
Let us know if this helps.
Hi @steveatsafe,
Thank you for the quick response. I did not know that our license had these limitations and I will scale back the functionality to match our current license. Using a scheduled task or manually start the workbench will have to suffice, and that way my technical issues are resolved as well.
FME Server is now on my wish list and I will try to get funding for it in the future.
Thank you and have a nice day!
