Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Does WebCenter Content supports transactions?
Greetings,
from what I have managed to read, there are a few ways to integrate with WebCenter Content when working with Java:
- CIS
- RIDC
- SOAP
Though, no matter how much I searched about transactions in WebCenter Content, I can not find that any of the mentioned integration ways actually supports transactions.
An example:
- Check in the document
- Execute custom logic in the code
- If custom logic fails, revert the document check in
Maybe an exception:
- WebLogic does support SOAP Atomic Transactions
- GenericSOAP endpoint in Enterprise Manager, out of the box, has configuration that would indicate it supports transaction:
Atomic Transaction Flow Option: Supports Atomic Transaction Version: Default
I have run into some problems trying to run it in a transaction, but that is a matter for another post.
A general question, does any way of WebCenter Content integration supports transactions in an context mentioned above?
Kind regards,
Ranko
Best Answer
-
Hi Ranko,
WebCenter Content follows Service Oriented Architecture. This way there is a request and a response and no transactions/sessions maintained. If you need to roll back a checkin, it has to be another request based on the business logic present in your application.
HTH
Anand U
Answers
-
Hi Ranko,
WebCenter Content follows Service Oriented Architecture. This way there is a request and a response and no transactions/sessions maintained. If you need to roll back a checkin, it has to be another request based on the business logic present in your application.
HTH
Anand U
-
Thank you for your answer Anand.
Just to clarify/confirm:
Following doesn't work (even with SOAP atomic transactions):
@Transactionalpublic void demo() { EXECUTE_DOCUMENT_CHECK_IN; //using IDC/RIDC/SOAP/CIS EXECUTE_DATABASE_UPDATE;}
Meaning, in this example, if "EXECUTE_DATABASE_UPDATE" fails, document will still be checked in?
It should be done like this:
public void demo() { EXECUTE_DOCUMENT_CHECK_IN; //using IDC/RIDC/SOAP/CIS try { EXECUTE_DATABASE_UPDATE; } catch (Exception e) { EXECUTE_DOCUMENT_DELETE; }}Meaning, in this example, if database update fails, it should be caught and explicitly handled?
Thank you for your time and kind regards,
Ranko
-
Hi Ranko,
Yes, in your example the document will get checked in even if the EXECUTE_DATABASE_UPDATE fails. The checkin of document is complete in the first section EXECUTE_DOCUMENT_CHECK_IN and you have a document number returned by WebCenter Content. Unless you have a logic to say if EXECUTE_DATABASE_UPDATE fails, run a EXECUTE_DELETE_DOCUMENT as a rollback action coded the document checkin will not be rolledback.
HTH
Anand U