Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Enlisting WSS object model/API calls in a transaction with LOB data

Asked By: Karen Coleman Date: May 12, 2006 Category: Sharepoint Views: 205

Has anyone run into the need to enlist a WSS object model/API call in a transaction, for example, with other database transactions?

One of the simplest examples is uploading a file or changing the metadata about a file in a document library in the same transaction where a line-of-business database also needs to be updated.

...and you want both the document library update and LOB data update to occur ...or neither, in the case where one of the updates doesn't succeed.

How common are these types of scenarios?

Tagged:enlisting wss object modelapi calls in transaction with lob data

2 Answers Found

Answer #1 Answered By: Dameon Dejesus Answered On: May 12, 2006

None of the API stuff is transactional. So you’ll have to manage it VERY manually.

We generally just log the failures and clean them up manually.

Answer #2 Answered By: Tejaswani Barve Answered On: May 12, 2006

Re: most of the strategies that can be used to implement it would break support on WSS since it would require direct database access ;)
Most but not all,

We've been been able to implement full MS DTC transactional support for a workflow server API (where we don't have direct access to the database). ...the approach is standard .NET and the design can be replicated for WSS.

Didn't find what you were looking for? Find more on Enlisting WSS object model/API calls in a transaction with LOB data Or get search suggestion and latest updates.