I think it's the method you call : Agent.Run or Agent.RunOnServer, no ...?
It has to be confirmed ....
The doc says :
1) "If a Notes client invokes RunOnServer, security is through the signer
of the agent. "
2) "On a local database, the RunOnServer method works like the Run method,
that is, runs the agent on the local computer."
Hope it helps...
Vincent BOITEUX
Robert Laing <rlaing@xxxxxxxxx> A Lotus Domino on the
Envoye par : iSeries / AS400
domino400-bounces+v.boiteux=clemessy.fr@xxxxxxxxxxxx <domino400@xxxxxxxxxxxx>
cc
28/04/2008 16:22 Objet Re:
Performance/Development
+--------------------------------------------------+ question
| Veuillez repondre `a |
| Lotus Domino on the iSeries / AS400 |
| <domino400@xxxxxxxxxxxx> |
+--------------------------------------------------+
When I call the agent from the QS or PS, what determines whether the agent
runs on the server or in the user's session ?
From:
Timothy Briley <tlbriley@xxxxxxxxxxxxxx>
To:
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
Date:
04/28/2008 10:11 AM
Subject:
Re: Performance/Development question
Two things come to mind:
1) I generally put code like this in the PostSave event instead of
QuerySave in case the save doesn't take place. Stuff happens.
2) I think you will get a performance gain if the changes are made
via an agent that runs on the server. Then the QuerySave (or
PostSave) event calls the agent.
Timothy Briley
tlbriley@xxxxxxxxxxxxxx
At 09:49 AM 4/28/2008, you wrote:
>I have a database running on our 8.0.1 Domino server that serves as a
>central source of information for several other databases. When
documents
>are updated in this particular database, I need to update other databases
>with that information on an almost real time basis. I had coded these
>updates into the QuerySave event of the primary forms. For local users,
>this update process is negligible. For remote users, the update process
>takes way too long. For various reasons, we cannot utilize local
replicas
>for these remote users, nor can we bump up the bandwidth.
>
>One option I was considering was take the update out of the QuerySave
>events and make a scheduled LotusScript agent that runs every 15 minutes
>or so that will take the changes in the main database and update the
>secondary databases.
>
>Another option I was considering was to code a Java program that would
run
>on the iSeries, wake up periodically and handle the updates.
>
>Performance is a concern in this environment. Any opinions on whether it
>would be more efficient to have a frequently running LotusScript agent on
>the Domino server or a frequently running Java program running outside
the
>Domino environment but manipulating Domino objects ???
>
>Thanks in advance,
>
>Bob
>
>_______________________________________________
>This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
>To post a message email: Domino400@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit:
http://lists.midrange.com/mailman/listinfo/domino400
>or email: Domino400-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at
http://archive.midrange.com/domino400.
_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/domino400.
_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/domino400.
midrange.com
