We want to allow a user to create/edit ImportAgent sessions without letting them onto the server it is installed on. Besides just granting them access to the location the XML's for the sessions are stored (and teaching them XML), has anyone found a way to install ImportAgent on a server but point the configuration to look at files stored somewhere else (e.g. a network share or another server)?
Question
Question
Answer
Hi Beau,
Shawn's proposed solution will not work because encrypted secrets stored in config profiles cannot be decrypted accross different machines. Import Agent is not a client-server application like Workflow so it cannot look at config profiles stored somewhere else.
Replies
I believe the main reason Laserfiche designed Import Agent to only allow profile creation from the server it runs on, is because this ensures that any mapped drive references are confirmed as available to the Import Agent service.
The only solution I can think of, assuming your licensing allows for multiple Import Agent instances, is to deploy an additional separate Import Agent on a machine where the user has a higher level of trust, they could then create the Import Agent profile there. Then with some guidance the user could provide the XML that is created and an individual with server access could 'import' the profile onto the server and perform any verifications required. (Verify source drive references are UNC paths or mapped drive letters match, etc)
We figured the same thing but are hoping to cut out the middleman and just have the end-user build the jobs using UNC paths instead of local paths. Similar to what Workflow Designer provides, it would be nice to build/maintain ImportAgent jobs without letting people directly onto the server. I would love it if somewhere in the config files we could choose where the sessions are stored (similar to QuickFields) or store them in a SQL database (like Workflow). Then that could allow us to have this flexibility the customer is requesting.