sharepoint - Scope of a timer job feature -
I'm writing a timer job for the first time. I'm following the examples which can be obtained by Googling as my reference.
In many such articles, I am coming into the timer job facilities that are active at the site collection level or at the site level.
I think it's weird, because the timer for a particular web application can be just one example of the job.
Should all the timer job facility be scotched in the web application?
It depends entirely on your scenario Jobs have written, so far I have scotched the web app (it's a matter of modifying your facility. XML). However, depending on the work of your timer, it can be understood from the user's perspective that this web or site is scanned. You only need to know about your feature receiver 'parents', which are passed in the notification operators, etc. - this would be SPWeb, SPS ite or SP web application, which was active on the facility - and you yourself You can write a configuration interface to set up a user who should work with your timer job, and not technically you are right: they always have web apps Go on Ikeshn level. But since they often work with content related to the web or site, skipping this way can be a useful way to fix the timer job scope.
Comments
Post a Comment