A DeliverPoint action results in the creation of a DeliverPoint job. DeliverPoint jobs are queued and processed by the DeliverPoint Job Execution SharePoint timer job, which runs by default every 5 minutes. When a user configures a DeliverPoint action, they specify a Transaction Type which identifies when a DeliverPoint action should be processed. There are three Transaction Types for job processing:

  • Run Now: Transactions are queued for immediate processing and will use the current information in the DeliverPoint database to make the requested changes to your farm. Transactions will only be guaranteed to be as complete as the start date and time of the last successful interrogation.

  • Run Later: Transactions are queued for processing after the next interrogation. This transaction will be guaranteed complete at the date and time the interrogation finished.

  • Both: Both Run Now and Run Later jobs are created. The advantage to running the same job twice is to accommodate for the chance a production environment is different or more up-to-date than the environment known to the DeliverPoint databases. Since the individual job executions are built using the information in the DeliverPoint database, there is always the possibility that the DeliverPoint database is not 100% in synch with your production farm. The updates in the production environment are picked up at the next interrogation, so running an identical job again to ensure your operation used the most up-to-date production information.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment