sharepoint timer job run on specific server

Timer jobs are wonderfully robust creatures. They effectively replace the "Windows Scheduled Task" for SharePoint servers, allowing you to run .Net code on a scheduled or "one off" basis.
However, there can be some confusion about running Timer Jobs on multiple servers, so this should clear it up a bit.
  1. By default Timer Jobs will only execute on the server that they are called from (typically the Central Administration server)
  2. Through code you can specify a specific box (SPServer) to run your Timer Job on.
  3. It is possible to run a Timer Job on every server on the farm (although this can be dangerous!)
The constructor includes a parameter for an SPServer object, which allows you to specify which server the timer job will run on.
Example Code 1 – Add Job to single Server:
The code below is for a Web Application scoped which will register a job definition on a single server. As Web Application scoped features are activated from Central Administration, it will use the current SPServer (i.e. the Central Admin server).
This is useful for code which modified content in the database, as you only want it to execute a single time.
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWebApplication webApp = properties.Feature.Parent as SPWebApplication;
SPJobDefinition job = new SPJobDefinition("CustomJobDef", webApp);
}
Example Code 2 – Add Job to All Servers:
The code below is for a Web Application scoped which will register a job definition on all web front end servers in the farm.
This is useful for code which modifies files or server settings, as you need it to execute separately for each server.
public Reminder() : base() { }
        public Reminder(string jobName, SPService service)
            : base(jobName, service, null, SPJobLockType.None)
        {
            this.Title = "ReminderTimerJOB";
        }
        public Reminder(string jobName, SPWebApplication webapp, SPServer server)
            : base(jobName, webapp, server, SPJobLockType.Job)
        {

             this.Title = "ReminderTimerJOB";

         }
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWebApplication webApp = properties.Feature.Parent as SPWebApplication;
foreach (SPServer server in SPFarm.Local.Servers)
{
if (server.Role == SPServerRole.WebFrontEnd)
{
SPJobDefinition job = new SPJobDefinition("CustomJobDef", webApp, server, SPJobLockType.None);
}
}
}
Hope this helps! Enjoy!

Comments

Post a Comment

Popular posts from this blog

Clearing the Configuration Cache for SharePoint

Clearing the Configuration Cache for SharePoint Perform the below steps on all the servers in the farm. 1. Stop the Timer service Start  ->  services.msc  ->   SharePoint Timer Service  (SPTimerV4) ->  Stop 2. Browse to  %SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID Note: The  Program Data  folder is a hidden file There could be more than 2 folders in this location. 3. Open the folder named as GUID’s with ‘-’ (dashed filename for the folder). Example -  1f8c67d2-2cd9-4196-ab1a-d1a2daed2aa7 4. Arrange the files by Type. You would find few xml files and a file named  cache.ini . 5. Delete all files except cache.ini (DO NOT DELETE THIS FILE - cache.ini) 6. Reset cache.ini (If you open this file, you will find a number like this – 3400261. Change the value in cache.ini to 1) 7. Start the Timer service Start  ->  services.msc  ->   SharePoint Timer Service  (SPTimerV4) ->  Start. 8. Note: The file system cache
Read more

SharePoint 2013 REST API CRUD Operations

Image
Introduction  SharePoint   2013 has greatly expanded the REST services available to developers. With this, we have much more SharePoint functionality exposed via JSOM and Web Services .  The goal of this article is to provide how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the REST services. SharePoint REST endpoint Overview: The following table contains typical REST endpoint URL examples to get you started working with SharePoint data. Prepend http://server/site/_api/ to the URL fragments shown in the table to construct a fully qualified REST URL. Below is a list of the basic commands used to get List Items from a SharePoint List through the SharePoint 2013 REST Services. URL endpoint Description Supported HTTP Method /_api/Web/Lists/ getbytitle('listname') Getting a list details by its title and updating it as well. Ifanyone changes your list title, your code will break. G
Read more

Add List Item Attachments to Task Form using Nintex Workflow and Forms

Image
DECEMBER 19, 2017  ~  NICOLE PRESTBY I had a requirement from a client recently to show all list item attachments on the various task forms in an approval process – which, if you think about it, makes total sense. With any project, we always have a common goal of making the user experience as seamless as possible for our users and approvers. So, why wouldn’t we provide all pertinent information needed (including related documents) to complete the requested review and approval, right there on the task form? I found  a post  on Nintex Connect which walks through meeting this requirement by leveraging  a custom action  created by Nintex Technical Evangelist,  Vadim Tabakman . But, what if you don’t have access to deploy a custom action to your SharePoint environment? In this case, I actually didn’t have access to the client’s server. So, I decided to come up with a solution that would produce a similar outcome, without the need for any custom actions. The Workflow Get Att
Read more