Lotusphere 2010 session content
Category lotusphere quickr event hook agent
Last week was Lotusphere. Somehow each day in Orlando seems very short. There is never enough time to see all the sessions I'd like to see. It's always fun though.
Viktor and I gave one session this year. It was titled "BP211 IBM Lotus Quickr Development Grows Up: Now This Changes Things". In the past we've given sessions that focused on creating your own applications in Quickr. This was a bit of a departure. In it we showed new ways to interact with Quickr from changing the look of the default theme (without touching the theme files), to accessing Quickr places using REST and Web Services, to using agents to process Quickr events. I've made the session content/examples available on the SNAPPS download site (direct link).
If you attended my session and also AD305 Customizing IBM Lotus Quickr Using Templates and APIs, you may have noticed that Andreas Goelzer and I gave some conflicting information about agent security for event hooks. Since my session was first, its obvious I'm right and he's wrong.
No, not really. I would
like to take some time to clarify though. In my session, I said that
it didn't matter if you checked the "Run as web user" box on
the agent because it always ran as the signer of the agent anyway. Andreas
said to check the box so that it would run with the user's credentials.
Those two positions seem mutually exclusive, but let me explain the
differences. All of my examples were written in LotusScript and his
were written in Java. Because his were written in Java, he could
access the web user session and retrieve the token and subsequently run
with the web users credentials. That is not the case for LotusScript
agents. However, in both languages the EffectiveUserName value is
the name of the agent signer. That is different than the normal way
that "Run as web user" agents work. Another difference
is that for normal agents, the web user needs some access to the database
containing the agent. Not the case here. In my example database,
both Default and Anonymous are set to No Access and yet the hook agents
run.
Have a look at the example database (QAudit.nsf). Let me know what you think.
Last week was Lotusphere. Somehow each day in Orlando seems very short. There is never enough time to see all the sessions I'd like to see. It's always fun though.
Viktor and I gave one session this year. It was titled "BP211 IBM Lotus Quickr Development Grows Up: Now This Changes Things". In the past we've given sessions that focused on creating your own applications in Quickr. This was a bit of a departure. In it we showed new ways to interact with Quickr from changing the look of the default theme (without touching the theme files), to accessing Quickr places using REST and Web Services, to using agents to process Quickr events. I've made the session content/examples available on the SNAPPS download site (direct link).
If you attended my session and also AD305 Customizing IBM Lotus Quickr Using Templates and APIs, you may have noticed that Andreas Goelzer and I gave some conflicting information about agent security for event hooks. Since my session was first, its obvious I'm right and he's wrong.
No, not really. I would
like to take some time to clarify though. In my session, I said that
it didn't matter if you checked the "Run as web user" box on
the agent because it always ran as the signer of the agent anyway. Andreas
said to check the box so that it would run with the user's credentials.
Those two positions seem mutually exclusive, but let me explain the
differences. All of my examples were written in LotusScript and his
were written in Java. Because his were written in Java, he could
access the web user session and retrieve the token and subsequently run
with the web users credentials. That is not the case for LotusScript
agents. However, in both languages the EffectiveUserName value is
the name of the agent signer. That is different than the normal way
that "Run as web user" agents work. Another difference
is that for normal agents, the web user needs some access to the database
containing the agent. Not the case here. In my example database,
both Default and Anonymous are set to No Access and yet the hook agents
run.
Have a look at the example database (QAudit.nsf). Let me know what you think.