Here’s the setup:- Company A and Company B both have a replica of a db and are replicating regularly.
Company B controls the design and Company A’s server is in the ACL as Author.
Agents are signed with an ID from Company B. The ID is listed in the fields in Company A’s server document which enable it to access the server and run restricted agents. The agent ID is also in the db’s ACL as Designer.
One such agent, which is triggered by web users at Company A clicking a form button ([ToolsRunMacro]), is run successfully many times a day. (This button/agent did not work until we added the agent ID to the server doc fields mentioned above.)
Another agent scheduled to run every 30 minutes on Company A’s server does not appear to be running.
Does the Company A server need to have some minimum access setting in the ACL beyond Author? Any other ideas?
Subject: Update: Minimum server access in ACL to run scheduled agents?
The agent is now running on Server A.
The server at Company A is still listed with only Author access in the ACL. It is also assigned a role. That role is inserted into readers and authors field on docs which need to be acted upon by the agent on Company A’s server.
When certain actions are taken by users at Company B, the role is inserted into the fields.
At the next replication, these modified docs are suddenly visible to the server at Company A.
A scheduled agent on that server scans a view of these docs and sends mail back to individuals at Company B telling them that they can take further action. It also marks them as modified by the agent so it doesn’t run on them again.
The problem I was having before might have been related to an insufficient trigger. I was trying to use “New and modified documents”, but Company A’s server might not have recognized these as the docs as either when it finally saw them after replication. Switching to the view-based selection and a schedule took care of that.
There may also have been an ACL issue relating to the “Create private agents” setting. In some other threads in this forum, I was reminded of times back when I couldn’t see the scheduled agents in a db until I actually created a private agent of my own. All of a sudden the agents showed up in the agent list. So I decided to give the server at Company A that setting.
Anyway, it’s working. Thanks for your efforts, Mr. Fox.
Subject: Minimum server access in ACL to run scheduled agents?
So the Company A Server would only be able to change any documents that it was in fact the Author of, regardless of which server teh document was created on. If the one agent is only to run on Server B and the other on Server A then that is set in the Agent Properties under the server to run on. If you only want Server A to be able to act on documents created by users creating documents on Server A then you should capture the Server name in the documents when created/modified then select these document in you view, but Server A would have to have at least Editor Access to the DB or it will not be able to modify the documents because they would have been created with the users ID (unless they are created by an un-authenticated user) In any case Server A needs more than Author access.
Typically the corresponding Servers are set to have Manager Rights so that Design and ACL changes can be replicated smoothly between them.