Cloud and Microsoft technologies enthusiast architect in Switzerland RSS 2.0
# Tuesday, November 11, 2008

<Disclaimer>This is personal notes of what I retained during the session. This can be incomplete, partially right or wrong. It is just  part of the notes I took and what retained my attention. Nothing prevents the user to get more information on their favorite web site.</Disclaimer>

In this interactive session, Stef Shoffren tried to explain us how to develop, deploy and debug a SharePoint timer job.
SharePoint allows three different scenarios for timer jobs : batch data loading, scheduled tasks and one-off job executed accross the farm such as an IIS restart or a configuration change.
What should not be using this kind of job, typically, it sending e-mails to users, which should be handled by the SharePoint notification service, unless a company policy disallow this.
First, a timer job is implemented by inheriting from the SPJobDefinition class and overriding the Execute method. It is running using the system accounts which makes it the possibility to execute tasks on all the server farms. The problem is that IT Professionnals don't see Timer jobs with a good eye and see them as a threat because of the priviledges given to the system account.
To store the configuration, there are basically three ways :
1.- A property bag populated when defining the timer job
2.- Settings in the OWSTimer.exe.config
3.- External store such as a SQL database or a SharePoint list, which is the preferred way.
On the logging side, we can distinguish three ways :
1.- Using ULS, the out-of-the-box SharePoint Logging system. According to the audience, it is a real pain to put in setup
2.- Windows EventLog
3.- Enterprise Library Logging
In any of these choice, the logging must be part of the design of the timer job.
To test and debug a timer job, it is necessary to attach the OWSTimer process, which requires the admin rights
In order to deploy a timer job, we can see three means :
1.- Using a feature and a feature receiver
2.- Using an msi Windows Installer
3.- Using a custom executable that must be run from the central administration server.

Note for myself : look for WSPBuilder and WSSDW on codeplex to load data into SharePoint

Tuesday, November 11, 2008 11:04:21 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] -
TechEd2008
All comments require the approval of the site owner before being displayed.
OpenID
Please login with either your OpenID above, or your details below.
Name
E-mail
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):

Live Comment Preview
Google Cloud Platform Certified Professional Cloud Architect
Ranked #1 as
French-speaking SharePoint
Community Influencer 2013
Navigation
Currently Reading :
I was there :
I was there :
I was exhibiting at :
I was there :
I was a speaker at :
I was a speaker at :
I was a speaker at
(January 2013 session):
I was a speaker at :
I was a speaker at :
United Nations (UN) SharePoint Event 2011
I was a speaker at :
I was there !
I was there !
I was there !
I was there !
Archive
<October 2022>
SunMonTueWedThuFriSat
2526272829301
2345678
9101112131415
16171819202122
23242526272829
303112345
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2022
Yves Peneveyre
Sign In
Statistics
Total Posts: 290
This Year: 0
This Month: 0
This Week: 0
Comments: 20
Themes
Pick a theme:
All Content © 2022, Yves Peneveyre
DasBlog theme 'Business' created by Christoph De Baene (delarou)